Skip to main content
Purpose: Map implementation log / registry status to GitHub Project status (Done / In progress / Backlog) for manual or scripted update. Single source for all cores. Source: specs/SPEC_STATUS_REGISTRY.md, per-core specs//IMPLEMENTATION_LOG.md.
2026-03-09 reconciliation note: Active coverage is now validated with npx tsx scripts/verify-spec-tracking-coverage.ts --scope active, and bucket-level reconciliation (including deferred/enhancement/no-spec items and duplicate cleanup candidates) is generated by npx tsx scripts/audit/reconcile-spec-tracking.ts --scope active --format markdown. Use those scripts as the operational source of truth before manually applying updates from this mapping table.

Status mapping rules


Manual update steps

  1. Open the Encore Spec Progress (or equivalent) GitHub Project.
  2. Filter by Core = XX or label core:XX.
  3. For each issue, set the Status field per the table for that core.
  4. Optional: For Backlog / In progress issues, set “Next Action” from eos-spec next --spec <SPEC-ID>.

Scripted update (optional)

When gh has project scope (gh auth refresh -s project), a script could call gh project item-list, match issues by number, then gh project item-edit --id <item-id> --field-id <Status-field-id> --project-id <project-id> --single-select-option-id <option-id>. Obtain project ID and Status field/option IDs from gh project list and gh project field-list <project-id>. Until then, use manual steps.

CE (Community Engagement)


CL (Clinical)


FA (Finance & Accounting)

Note: Prefer new-format issues (longer titles matching registry) for status updates. Some legacy issues #436–#448 have shorter titles.

FM (Facilities Management)


FW (Forms & Workflow)


GR (Governance & Risk)


HR (Human Resources)


IT (IT & Security)

Note: Legacy issues #563, #564, #565 can be closed as duplicates of #629, #633, #638.

LO (Leadership & Operations)

Note: Legacy issues #492–#496 can be closed as duplicates; use the issue numbers below for the 25 canonical LO specs.

PF (Platform Foundation)


PM (Practice Management)

Note: Older issues with same Spec ID but different titles (e.g. #611–#614) are legacy; use the issue whose title matches the current registry name.

RH (Recovery Housing)


Enhancement & Expansion Issues (added 2026-03-09)

These issues were created during GitHub reconciliation. The recommended project status for all of these is Backlog unless noted.

PM Enhancements (core:PM, enhancement)

CL Enhancements (core:CL, enhancement)

FA Enhancements (core:FA, enhancement)

HR Enhancements (core:HR, enhancement)

Expansion / Phase specs (expansion label)

See GITHUB_PROJECT_SPEC_TRACKING_PLAN.md for project setup and status values.