docs: define evidence-backed execution handoff contract

[dapi]

Problem

Issues #83 and #85 define the declared context that an agent should load before a route or stage. They do not define a compact, evidence-backed way to hand off what actually happened during execution.

Outcome

Define Execution Handoff as a derived, read-only artefact for a human or agent to safely continue work. It does not become a source of truth and does not replace Memory Bank.

An Execution Handoff contains:

• the starting task owner or document;
• canonical documents and explicit upstream dependencies;
• relevant decisions;
• changed files and commits;
• verification artefacts and results;
• open questions, blockers, and next steps;
• a direct reference to the primary source for every item.

The contract distinguishes declared priming context from observed execution context.

Constraints

• Keep Memory Bank as the canonical documentation and ownership layer.
• The handoff is a derived read-only projection; it must never edit, merge, or become an owner of documents.
• Do not infer semantic relationships as facts without explicit evidence.
• Do not require an LLM to create the artefact.
• Preserve progressive disclosure: a handoff must be compact enough to resume one concrete task.

Acceptance

• A governed process document owns the term, purpose, lifecycle, and schema.
• The glossary defines Execution Handoff.
• Feature Flow has one worked example.
• Every included claim resolves to a primary source.
• The contract explicitly separates declared priming context from observed execution context.
• Root and flow indexes make the material reachable.

Dependencies

• docs: add route-specific context priming profiles #83
• docs: add per-process priming manifests #85

[dapi]

Human Gate: the validated documentation checkpoint is ready in the worktree, but this restricted runtime has .git read-only (git_write=no). HEAD is a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da; no branch, commit, push, or PR mutation was attempted. Checks passed: ruby tools/validate-priming-manifests.rb template/memory-bank, memory-bank-cli lint --scope-root template/memory-bank --entrypoint template/memory-bank/README.md, memory-bank-cli doctor --profile template, and git diff --check. Resume this run in a full-delivery profile with .git write and authenticated GitHub write enabled; then create/push codex/gh-95, open the PR, and update labels.

[dapi]

Workflow: Small Change

Design: not required
Reason: the issue defines a documentation-only contract and the change follows the existing governed process-document patterns in template/memory-bank/flows/templates/process/; it creates no runtime, API, event, schema, configuration, or integration contract.

Plan: not required
Reason: the change is one local, atomic documentation set (contract, indexes, glossary, Feature Flow example, and priming-manifest reachability) with known documentation validation surfaces.

Verify:

• ruby tools/validate-priming-manifests.rb template/memory-bank
• memory-bank-cli lint --scope-root template/memory-bank --entrypoint template/memory-bank/README.md
• memory-bank-cli doctor --profile template
• git diff --check
• Semantic read-through of ownership, provenance, declared-versus-observed context, and index reachability

Validation profile: documentation
Triggers / rationale: only Markdown documentation and a data-only priming manifest change; no executable behavior, contract, production configuration, or release path changes.
Downgrade approval: none

[dapi]

Human Gate: GH-95 documentation checkpoint is validated but this runtime keeps .git delivery operations restricted. HEAD is a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da; the worktree is detached and contains the prepared, uncommitted documentation change set. No branch, commit, push, PR, or label mutation was attempted. Checks passed: ruby tools/validate-priming-manifests.rb template/memory-bank, memory-bank-cli lint --scope-root template/memory-bank --entrypoint template/memory-bank/README.md, memory-bank-cli doctor --profile template, git diff --check, and a final semantic documentation review. codex review --uncommitted was attempted but its local app-server initialization was denied by this runtime. Resume this same run in a full-delivery profile with .git write enabled; re-ground state, create/push codex/gh-95, open the PR, then replace codex-ready with human-review.

[dapi]

Human Gate: the prepared GH-95 documentation change set remains validated, but this run is in the restricted delivery profile where .git is read-only. HEAD is a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da; no branch, commit, push, PR, or label mutation was attempted. Rechecked successfully: priming manifest validation, template lint, template doctor, and git diff --check. Please resume this same run in a full-delivery profile with .git write enabled; then re-ground and create/push codex/gh-95, open the PR, and replace codex-ready with human-review.

[dapi]

Human Gate: GH-95 remains at the Small Change delivery gate because this runtime restricts .git writes. I re-grounded the existing candidate at detached HEAD a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da; no branch, commit, push, PR, or label mutation was attempted. The prepared documentation change set passed ruby tools/validate-priming-manifests.rb template/memory-bank (16 manifests), template lint, template doctor (0 errors, 0 warnings), and git diff --check, plus a semantic documentation review. Resume this same run in a full-delivery profile with .git write enabled; re-ground the ledger and issue state, then create/push codex/gh-95, open the PR, verify CI, comment with the PR and verification, and replace codex-ready with human-review.

[dapi]

Human Gate: re-grounding confirms the prepared Small Change remains valid, but this restricted runtime does not permit .git delivery writes. The candidate is still uncommitted at detached HEAD a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da; no codex/gh-95 PR exists. Re-ran successfully: ruby tools/validate-priming-manifests.rb template/memory-bank, memory-bank-cli lint --scope-root template/memory-bank --entrypoint template/memory-bank/README.md, memory-bank-cli doctor --profile template, and git diff --check. Resume this same run in a full-delivery profile with .git write enabled; re-ground the ledger and issue, create/push codex/gh-95, open the PR, verify CI, then comment with the PR and replace codex-ready with human-review.

[dapi]

Human Gate: re-grounding confirms the prepared Small Change candidate remains validated, but this workspace profile provides .git read-only access. HEAD is a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da in a detached worktree; no codex/gh-95 PR exists. The issue remains open with codex-ready; dependencies #83 and #85 remain open. GitHub authentication is available, but the required branch, commit, push, PR, and CI gates cannot be performed without .git write. Resume this same run in a full-delivery profile with .git object/ref write enabled; re-ground, then commit/push the existing eight-artifact candidate, open the PR, verify CI, and replace codex-ready with human-review.

[dapi]

Human Gate: re-grounding confirms the validated Small Change candidate remains unchanged at detached HEAD a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da; git diff --check passes, the issue is open with codex-ready, and no codex/gh-95 PR exists. This restricted runtime does not permit .git delivery writes, so no branch, commit, push, PR, or label mutation was attempted. Resume this same run in a full-delivery profile with .git write enabled; re-ground the ledger, issue, worktree, PR and CI, then create/push codex/gh-95, open the PR, verify CI, comment with the PR and verification, and replace codex-ready with human-review.

[dapi]

Human Gate: re-grounding confirms the validated Small Change candidate remains uncommitted at detached HEAD a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da; no codex/gh-95 PR exists. The restricted runtime does not guarantee .git writes, so branch creation, commit, push, PR creation, CI verification, and the required label transition cannot proceed. Revalidated successfully: ruby tools/validate-priming-manifests.rb template/memory-bank (16 manifests), memory-bank-cli lint --scope-root template/memory-bank --entrypoint template/memory-bank/README.md, memory-bank-cli doctor --profile template (0 errors, 0 warnings), and git diff --check, plus a semantic artifact review. Resume this same run in a full-delivery profile with .git write enabled; re-ground the ledger, issue, worktree, PR, and CI, then create/push codex/gh-95, open the PR, verify CI, comment with the PR and verification, and replace codex-ready with human-review.

[dapi]

Human Gate: re-grounding confirms the Small Change candidate remains validated at detached HEAD a1cad4ee2745fbf4f9fe80e91b5d8f0393f4e2da; dependencies #83 and #85 are open, the issue retains codex-ready, and no codex/gh-95 PR exists. This runtime still restricts .git delivery writes, so no branch, commit, push, PR, CI, or label mutation was attempted. Fresh checks passed: ruby tools/validate-priming-manifests.rb template/memory-bank, template lint, template doctor (0 errors, 0 warnings), and git diff --check. Resume in a full-delivery profile with .git write enabled; re-ground this ledger and external state, then create/push codex/gh-95, open the PR, verify CI, comment with the PR and verification, and replace codex-ready with human-review.