# AceLM documentation alignment evidence register

Reviewed October 5, 2026. Patch baseline: `51fa608ac36746d5439e7e11746a4662c2bf0001` in `fariello/acelm-website`. Scope: design documents, public prose, diagrams, generated docs, and website regression checks. This is not verification of the AceLM engine, CLI, supervision, or storage implementation.

## Authority and maturity

The user's two authoritative sources are [the transition catalog](acelm-artifact-transition-catalog.md) and [status/terminal UX](acelm-status-and-terminal-ux.md). Their explicit proposals and open decisions stay open. All other documents and this register defer to them. A reconciliation summary does not establish new authority.

Finalized behavior includes phase retention after authorized actual start; separate lifecycle, selected assignment/Run, named-action readiness, intervention, and liveness; the finalized `died` and other Run labels; `need-ok`; preserved crash progress; four retry families and the cumulative ceiling of 20 x resolved `MAX_RETRY`. Successful assignment delivery does not establish artifact completion.

The [status migration contract](acelm-status-migration.md) separates retained lifecycle values from favored common names. Open decisions include specification `verifying`, direct backlog states, graduation-as-activity, independent plan-set states, milestone predicates, and administrative reopening policy. These are not finalized by this patch.

## October 5 audit corrections

| Finding | Correction or evidence | Boundary |
| --- | --- | --- |
| A01 | Lifecycle rules distinguish phase entry from retention; main SVG says fulfillment begun | Untouched queued artifacts remain accepted |
| A02 | Release stays reviewing during ordinary remediation waits; diagram separates invalidated review | Changed candidates refresh evidence and authorization |
| A03 | Metadata proposes separate activity/outcome/intervention/liveness; finalized Run derived by precedence | Serialization is a proposal, not implemented storage |
| A04 | Direct backlog completion requires accepted scope, execution evidence, independent verification | Historical shortcut assets remain visibly historical |
| A05 | fail-gate requires unrecoverable gate or exhausted authorized remediation | Dependency and approval waits alone are not failure |
| A06 | reviewed is acceptance pending; public stage names review and acceptance separately | Acceptance is not unconditional permission to start any action |
| A07 | Obsolete open Run questions removed; finalized readiness and Run distinguished from naming proposals | Common lifecycle naming remains open |
| A08 | Type-specific migration table, import aliases, full portable values and compact display rules | No silent persisted lifecycle rename |
| A09 | This evidence register replaces blanket alignment assertions; indexes fix precedence | Human semantic review remains necessary |
| A10 | Plan chain applies to plans; plan-set closure explained separately | No invented independent set states |
| A11 | Current baseline already corrected runtime SVG; preserved and checked with source/public copies | Publishing remains a separate action |
| A12 | Generator protects bare E/V patterns; source prose uses code spans | Regression exercises bare tokens and normal emphasis |
| A13 | Verification diagrams separate code repair, evidence repair, revised scope, infrastructure recovery | Counters/history persist; expected waits consume no retries |
| A14 | Public derivation starts draft children with separate acceptance; required-child additions revalidate closure | Reopening protocol remains an explicit open decision |
| A15 | Assessment verdict separated from named-action readiness; unspecified readiness explained | No unsupported conditional ship-verdict scheme |
| A16 | Focused semantic regressions, all rule label/copy checks and embedded-source checks added | Website checks are not a transition-engine test |

## Verification evidence and limits

The patch bundle records exact validation output and file hashes. Required checks are documentation regeneration, static validation, contact API tests, source/rendered label and embedded Mermaid consistency, and clean-baseline patch application followed by regeneration and tests. Regeneration must be reproducible. Tests reject specific contradictory wording and lost literal item patterns; they do not prove every possible design interaction correct.

Historical `panels/` assets and `acelm-baseline.mmd` remain unchanged for traceability. At their point of use, the index explains that accepted-to-done arrows compress actual execution and independent verification. Detailed diagrams show the current gate/routing contract while visibly preserving proposed state choices.

This patch repairs the identified documentation defects. It does not update absent pitch decks or deploy the website. Following application, compare deployed assets against the resulting commit before describing production as synchronized.