Product status

Clear about what is available and what is direction.

Lineage XI's catalogue is aligned through 0.55.0-rc1 / schema 065. Release-candidate implementation still requires real browser, database and deployment QA before being described as production-proven.

RC capability

Implemented in the current release-candidate baseline, subject to deployment and QA verification.

Product direction

Planned, optional or future-facing capability that should not be marketed as currently delivered.

Long-term direction

Strategic direction, including federation and wider ecosystem connectivity.

Known release-candidate baseline at this document revision

This catalogue is aligned through:

Lineage XI 0.55.0-rc1
Database schema 065

The supplied repository remains authoritative if it reports a different/newer version.

Release-candidate capability progression since the previous catalogue baseline

| Release | Schema | Major catalogue alignment | | --- | ---: | --- | | 0.38.0-rc1 | 049 | Unified people/contextual identities and login workflows | | 0.39.0-rc1 | 050 | Fixture attendance and Parents' Player of the Match | | 0.39.0-rc2 | 050 | People & Accounts SQL/runtime hotfix and release-pipeline hardening | | 0.40.0-rc1 | 050 | Grounds & Facilities consolidation | | 0.40.0-rc2 | 050 | PPOTM candidate/electorate refresh and destructive reset rules | | 0.41.0-rc1 | 051 | Competitive/Friendly statistical classification and editable Matchday squad | | 0.41.0-rc2 | 051 | Draggable Matchday starting-shape editor | | 0.42.0-rc1 | 052 | Member football portal and coach-assisted/proxy parent ballots | | 0.42.0-rc2 | 052 | Member Matchday results/timeline/awards and duration compliance guard | | 0.43.0-rc1 | 053 | Canonical fixture officials and fixture-specific squad staff | | 0.44.0-rc1 | 054 | Published Player Development portal and home-practice drill layer | | 0.45.0-rc1 | 055 | Legal/preferred names and FA Number/FAN metadata | | 0.46.0-rc1 | 056 | Focused development review sessions and isolated Fun Day engagement fixtures | | 0.46.0-rc2 | 057 | Club Event one-day/TBC scheduling and canonical venue selection | | 0.47.0-rc1 | 058 | Guardian identification/avatar photos, audited sensitive reveal and child handover | | 0.48.0-rc1 | 059 | Reports & Insights, club/team reporting and Club Health aggregation | | 0.49.0-rc1 | 059 | Season Centre with Open / Run / Close & roll forward operational readiness | | 0.50.0-rc1 | 060 | Player Medical & Welfare Readiness with coach-safe minimum operational projection | | 0.51.0-rc1 | 061 | Player & Team Kit Management, issue/acknowledgement/return lifecycle and overdue-return actions | | 0.52.0-rc1 | 062 | Controlled Action Centre automation, in-app/optional email notifications and escalation | | 0.53.0-rc1 | 063 | Guardian & Safeguarding continuation: handover policy, coach-safe readiness, guardian ID-photo reviews and missing-declaration reminders | | 0.54.0-rc1 | 064 | Player Development v2: age-group/goalkeeper programmes, trends, recurring reviews and family acknowledgement | | 0.55.0-rc1 | 065 | Finance & Commercial Insights, permission-aware commercial reporting, Treasurer/Committee pack and finance Action Centre exceptions |

These are implemented release-candidate capabilities subject to real deployment/browser/database verification. A release-candidate implementation should not be marketed as production-proven merely because static/regression validation passes.

Internal status discipline

This document intentionally contains a mixture of:

  • Available / implemented RC capability
  • In QA / RC hardening
  • In development
  • Planned enhancement
  • Long-term direction

Older sections explicitly worded as "potential", "future" or "planned" must not be silently advertised as available.

Before publishing marketing copy, maintain an internal status against each feature:

  • Available
  • In QA / RC
  • In development
  • Planned
  • Long-term direction

Mobile access and app delivery

  • Available: Responsive browser access across desktop, laptop, tablet and mobile.
  • Available option: Progressive Web App (PWA) installation where enabled on supported browsers.
  • Coming soon: Dedicated iOS and Android apps for the Apple App Store and Google Play.

The native apps are product direction and should not be represented as currently shipped until they are released through their respective app stores.

Current product phase

The planned feature-expansion sequence is now aligned through 0.55.0-rc1. Unless a genuine release-blocking capability is identified, the next phase should be treated primarily as product polish and release hardening, not another run of isolated feature domains.

Lineage should increasingly favour consolidation and proof of behaviour through:

  • Page-by-page visual inspection
  • Cross-module information architecture and navigation consistency
  • Club-brand/theme consistency
  • Public/admin/member view review
  • Responsive desktop/tablet/mobile QA
  • Accessibility and keyboard-navigation review
  • Empty/loading/error-state review
  • RBAC-role walkthroughs
  • Sensitive-data reveal/audit walkthroughs
  • Guardian handover safeguarding walkthroughs
  • Impersonation/elevation checks
  • Real MySQL migration testing
  • Workflow integration testing
  • Action Centre and Club Calendar consolidation
  • Reports & Insights and Finance & Commercial Insights integration
  • Season Centre end-to-end walkthrough
  • Medical/Welfare readiness privacy walkthrough
  • Development programme/trend/family-acknowledgement walkthrough
  • Shop/order/stock/payment lifecycle testing
  • Accessibility review
  • Release/build/update hardening
  • Customer-facing Help verification

Do not use the existence of a release-candidate implementation as a substitute for real browser/database/deployment QA.