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: Map every ROADMAP.md priority and phase to specific spec IDs or to operational initiatives that are tracked separately. Ensures 100% roadmap coverage and traceability. Last Updated: 2026-03-09

Module Priorities (Current)

Roadmap bulletSpec(s) / trackingNotes
FA — Cost allocation and bank-reconciliation automationFA-15, FA-21FA-15 Complete; FA-21 Specification.
RH — Compliance and outcomes reportingRH-06, RH-07Both Complete.
CE — Pipeline reporting and RingCentral embeddableCE-05, CE-14CE-05/CE-14 Specification.
FM — Extended facilities specifications and implementationFM-14, FM-15, FM-16; FM-01–FM-13FM-14/15/16 Planned; base FM specs Complete.
IT — Security/admin page coverageIT-05Complete.
Production Readiness — Runbooks, monitoring, incident response, deployment hardeningOperational initiativeSee Roadmap-only initiatives below.

Sequencing Phases

PhaseRoadmap textSpec coverageTracking
Phase 1Platform + shared capability stabilizationPF specs (e.g. PF-03, PF-04, PF-35, PF-36)Per-core tables in SPEC_STATUS_REGISTRY.md.
Phase 2Core feature completion (FA, RH, CE, FM, IT)FA-15, FA-21, RH-06, RH-07, CE-05, CE-14, FM-14–16, IT-05Same as Module Priorities.
Phase 3Production hardeningOperational readiness workstream; no single spec.Track via ops docs and runbooks.

Roadmap-only initiatives

These outcomes are not single-spec deliverables; they are cross-cutting or operational. Track via the following:
InitiativeDescriptionWhere tracked
Production ReadinessRunbooks, monitoring, incident response, deployment hardeningdocs/operations/ (monitoring, runbooks, recovery) and docs/operations/content-plans/ for content-planning artifacts.
Phase 1 outcome“Platform Foundation quality, security, cross-cutting capabilities”Aggregate of PF spec completion; SPEC_STATUS_REGISTRY.md PF row.
Phase 2 outcome“Close high-impact gaps for operational workflows”Aggregate of FA, RH, CE, FM, IT priority specs above.
Phase 3 outcome“Operational readiness, observability, compliance posture, deployment reliability”Same as Production Readiness; optional epic or GitHub Project view.
Recommendation: For “Production Readiness” and Phase 3, create a GitHub Project view or operational epic (e.g. “Production Readiness”) that links to runbook tasks, monitoring alerts, and deployment checklists rather than to spec IDs.

How to update

  • If the roadmap text changes, update the table rows above and add or remove spec IDs.
  • Add a row to Module Priorities for any new priority and, if it corresponds to a spec, link to SPEC_STATUS_REGISTRY.md.
  • For new roadmap-only initiatives, add a row under Roadmap-only initiatives and link to the tracking doc or project.

See also