Skip to content

Completion plan

The original 65 outstanding topics are divided into four passes. All four passes are complete: 85/85 reviewed, with no remaining writing assignments. Each pass follows a connected set of responsibilities and produces a reviewed documentation increment, an updated continuation assignment and a distributable HTML edition. The original 20 reviewed topics retain their declared source and evidence scopes.

Pass Topics Result Total reviewed after delivery
1 16 Sources, integrations, AI and background work 36 / 85
2 19 Product, architecture and application paths 55 / 85
3 14 Finance, imports and information security 69 / 85
4 16 Infrastructure, delivery, operations and evidence 85 / 85

Pass 1 connects preserved sources to interpretation, integrations and asynchronous outcomes. Pass 2 reuses the existing access/database/workflow articles while explaining application responsibilities. Pass 3 has fewer topics because financial and import reconciliation need deeper evidence comparisons. Pass 4 closes the runtime, release, diagnosis and evidence contracts. This balances review effort; topic counts alone do not measure complexity.

Pass 1: Sources, integrations, AI and background work

Section titled “Pass 1: Sources, integrations, AI and background work”

Pass 2: Product, architecture and application paths

Section titled “Pass 2: Product, architecture and application paths”

Pass 3: Finance, imports and information security

Section titled “Pass 3: Finance, imports and information security”

Pass 4: Infrastructure, delivery, operations and evidence

Section titled “Pass 4: Infrastructure, delivery, operations and evidence”

A reviewed topic answers its registered question with the current mechanism, responsible records/components, admission and failure boundaries, a synthetic example or diagnostic path, and scoped evidence. Preserve article types, topic IDs and old summary anchors. Link the owning explanation instead of repeating whole access or transaction chapters. Split articles when that improves the reader’s route; use a common reviewed source set when several topics share an implementation.

Source review does not establish deployed behavior. Distinguish inspected tests, new executions, reused identical-input evidence and named release observations. A missing source or unresolved product decision remains explicit; a favorable summary is not proof. Keep provider-write, private-data and environment boundaries from AGENTS.md throughout all four passes.

Before delivery, reconcile the register and links, inspect the full diff, run the handbook’s Node 24 verify/browser/package commands and selected repository checks, resolve fresh required CI, and verify the extracted clean HTML edition. Record actual results in the PR. Continue its branch while open; start from main after merge. During the four passes, NEXT.md assigned each complete following pass. After pass 4, NEXT.md defines maintenance, concrete evidence gaps and implementation-driven review rather than another writing batch.

The four-pass writing assignment is complete. NEXT.md defines implementation-driven maintenance, canonical-link review and scoped evidence updates. Independent product acceptance and the recorded gaps remain separate; completion of these 85 answers does not close them.