Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Purpose: Single canonical set of status values for the spec portfolio. All registry entries, scripts, and reports should use these values. Legacy or variant strings are mapped here for consistency. Last Updated: 2026-03-09

Canonical Status Set

Canonical LabelRegistry DisplayMeaning
Done✅ CompleteBase implementation and in-scope enhancements complete.
In Progress🚧 In ProgressImplementation started; not yet complete.
Backlog📋 SpecificationSpec written; implementation not started.
Specified📋 SpecificationSame as Backlog (spec exists).
In Review🚧 In ProgressWork complete; verification/spec-complete pending. Treated as In Progress.
Archived🗄️ ArchivedCompleted and moved to archive, or superseded/deprecated/consolidated into another spec.

Mapping: Legacy / Variant → Canonical

Use this table when normalizing existing data or parsing external sources.
Seen in Registry / SourceMap to CanonicalRegistry Display
✅ CompleteDone✅ Complete
CompleteDone✅ Complete
ImplementedDone✅ Complete
🚧 In ProgressIn Progress🚧 In Progress
In ProgressIn Progress🚧 In Progress
Active DevelopmentIn Progress🚧 In Progress
Scaffolded / 🏗️ ScaffoldedIn Progress🚧 In Progress
📋 SpecificationBacklog📋 Specification
SpecificationBacklog📋 Specification
📝 Not Started (0%)Backlog📋 Specification
Not StartedBacklog📋 Specification
🔜 PlannedBacklog📋 Specification
PlannedBacklog📋 Specification
📋 DeferredBacklog📋 Specification
(empty / blank)Backlog📋 Specification
UnknownBacklog📋 Specification
🗄️ Superseded/ArchivedArchived🗄️ Archived
SupersededArchived🗄️ Archived
ArchivedArchived🗄️ Archived

Enhancement / Expansion Status

  • Enhancements: Shown as N/M (e.g. 3/3) in registry. All complete ⇒ treat spec as having enhancements done.
  • Expansion phases: Tracked in DEFERRED_DASHBOARD.md. Status per expansion: ✅ Phase Complete, 📋 Specified, 🚧 In Progress.

Usage

  • audit-spec-completion.js uses this taxonomy in formatStatus() so that --update-registry writes only canonical values.
  • Weekly governance report and any new tooling should classify specs into: Done, In Progress, Backlog/Specified, Archived.
  • When adding new status variants (e.g. from a new core), add a mapping row above and update the audit script if it parses that source.

See Also