Reconcile the records with the result

Use chirality-root:bundled:workflow:bounded-reconciliation for bounded comparisons within one planned documentation/governance closeout after intended implementation/evidence integration and before the final PR. Ordinary document work needed by implementation stays with that production assignment. Missing required implementation or evidence returns to the graph and is completed before the affected comparison is backchecked. The comparison produces warranted document changes when writes are authorized; a report alone is insufficient. Identify one deliverable or a small connected group, its integrated candidate and evidence, governing decisions, named sections and permitted writes. Read controlling amendments and return a precise question where mapping is uncertain. Bounded reconciliation §§1–2

Compare in both directions. Follow the document's affected claims into the implementation and evidence: is the described behavior present, is the constraint enforced, and was the claimed check performed? Then follow the bounded implementation result back into the documents: did it settle a TBD, change an interface, reveal a limitation, satisfy a prerequisite, or leave an unrecorded consequence? A future requirement can legitimately remain unimplemented. A resolved setup assumption should not remain current merely because it was once true. Bounded reconciliation §§2–3

Classify the response before editing:

These are actions under the bounded reconciliation method, not a new taxonomy that replaces a formal program's controlled dispositions.

Keep claims at the level the project needs to preserve. Root concordance Revision 2 gives three tests: changing the statement would require a decision; another deliverable, user, project, or governing document relies on it; or named verification can check it. A statement failing all three is implementation detail, kept in code, tests, or developer documentation and cited as supporting evidence when useful. A decision-bound mechanism still belongs on the claim surface. Borderline cases remain visible for human ruling. Concordance §3.1

For example, “a failed save preserves the prior accepted document” is a stable product obligation. The name of a private helper used to implement it usually is not. A storage representation depended on by another consumer may itself be an adopted interface requirement. The distinction turns on the statement's consequences and warrant, not whether its vocabulary sounds technical. Granularity repair cannot erase a requirement or reverse a decision simply because the code now differs. Concordance §3.1

D-GOV-44's Revision 2 applies through its stated effective and adoption rules. In-flight programs keep their selected kernel/workflow bytes until their own authorized adoption. A new Root principle and a receiving notice do not silently revise a running program's repair posture. The App September 21 program's later owner rider was explicitly separated from publication of the principle. Follow that program's actual records before acting. D-GOV-44

Make authorized document edits and check them together. Account for unfulfilled obligations through their owning graph or decision; preserve legacy Remaining inputs under still-pinned contracts. Keep structured dependencies and their summary consistent when both are affected. Preserve IDs, source references, future scope, historical text, and other contributors' changes. Lifecycle, acceptance, identity, formal dependency-basis, and pinned-authority changes retain separate authority. Code repair is a separate node unless the brief explicitly includes it. A report-only return leaves application outstanding when writes were authorized and required. Bounded reconciliation §§3–5

Before saving, compare each target with the version inspected and recheck an affected comparison if the code or evidence basis changed. A supported no-change result can complete the bounded comparison; missing inputs or blocked inspection leave it incomplete. Return exact proposed edits when writes are outside the assignment, with their application still outstanding. Bounded reconciliation §§3–5

A single closeout stage can contain several independently bounded comparisons; it does not require one oversized assignment. A proposed departure from the undertaking's closeout requirement needs the owning human decision naming affected scope, substitute completion terms, and surviving obligations. An intermediate merge or a statement of completion does not supply that decision. Apply the actual undertaking basis and its reserved decisions. Human manual §§1.9, 5.6

A formal corpus concordance program is a larger selected method with activation, frozen discovery, calibration, bounded waves, independent verification, cross-Package synthesis, human dispositions, authorized repairs, and post-repair backcheck. It does not run merely because a small code slice needs document upkeep. Under the shared method, activation and its record land on the required common baseline before dispatch; discovery remains separate from repair; the pinned method does not drift as later files change. Concordance §§3, 5–7 · Reconciliation workflow

The unit of formal comparison is the claim. One deliverable can contain aligned claims, stale wording, unimplemented obligations, and uncertain evidence simultaneously. Derive summaries from the accepted claim rows. Each wave receives structural validation and independent examination under the calibrated conventions; defective ledgers are rerun through fresh bounded work, with earlier findings retained. A discovery backcheck does not verify later repairs. Concordance method · Reconciliation contract

The representation-migration profile has a narrowly bounded allowance to avoid redundant third-layer member reproduction. Use its complete selected contract to establish eligibility: complete deterministic member checks and independent member verification remain, as do full aggregate, manifest, and simulation coverage, exception reproduction, the prescribed deterministic clean sample, and fail-closed escalation. This allowance does not authorize general sampling of production or professional review. Reconciliation contract · Reconciliation method, R2

Formal R6 backcheck creates a new derivative bound to the repaired source state and preserves the discovery snapshot. Re-extract changed claim references and prove exact multiset equality to the authorized repair manifest, accounting explicitly for authorized no-change rows. For newly adopted graph-led programs, the final OBLIGATION_ACCOUNT.csv accounts for every compared deliverable and its unfulfilled obligations with their actual owning graph/decision, or evidence that none remains in the stated scope. It is a source-bound closing snapshot, not another maintained queue. A still-pinned REMAINING_WORK_CENSUS.csv retains its exact population and convention until the program explicitly migrates it. The return retains held/deferred repairs, stale derivatives, blockers, lifecycle posture and rerun needs. The handoff reports evidence coherence at that scope, not issuance or professional approval. A continuing run uses its adopted contract and pins even when a later shared edition is available. Reconciliation contract · Reconciliation method, R6