Skip to content

ONB — TFW-50: Minimal Agent Commit Attribution

Date: 2026-08-05 Author: Codex / Executor Status: ✅ ONB — Revised contract approved by Coordinator on 2026-08-05 Parent HL: HL-TFW-50 TS: TS TFW-50 Research: RES Iteration 1

1. Understanding

Execute the revised TS produced from RES Iteration 1. Commit Attribution is one universal subject-format rule for commits that occur under Coordinator, Researcher, Executor, or Reviewer ownership; it does not introduce commit cadence. After this ONB is approved, corrective writes are limited to exact terminology in .tfw/conventions.md and .tfw/glossary.md. The other four total-allowlist files and the wider workflow/adapter/skill corpus are verification-only and must remain byte-stable; no runtime, Git hook/config/history change, new implementation file, or remote mutation is permitted.

2. Entry Points

  • .tfw/conventions.md — corrective MODIFY: exact universal terminology and sole normative owner under §4.
  • .tfw/glossary.md — corrective MODIFY: concise definition plus Git author/committer metadata boundary.
  • research/iter1/RES.md — C7 consumer model, no-cadence boundary, exact terms, and evidence confounders.
  • .tfw/workflows/handoff.md, .agent/workflows/tfw-handoff.md, .claude/commands/tfw-handoff.md, RELEASE.md — PRESERVE + VERIFY against 389168a.
  • All other workflows, adapters, skills, and entry files — read-only verification corpus; no symmetric sync edits.
  • README.md, this ONB, the required EV, and RF — lifecycle traces, not implementation scope.
  • Baselines: published tree bc6779e; preserve-file implementation 389168a; revised approved plan 021f039.

3. Questions (blocking — cannot proceed without answers)

# Question Answer
— No blocking questions. Revised HL/TS and RES Iteration 1 define the universal all-role semantics, exact two-file corrective boundary, four byte-stable preserve paths, no-cadence rule, evidence confounders, and no-publication boundary. APPROVE revised ONB — Coordinator, 2026-08-05

4. Recommendations (suggestions, not blocking)

  1. Apply the revised terminology contract only in conventions and glossary; keep every other consumer referential or instantiated so AC-1 has one owner.
  2. Hash all four preserve files against 389168a before and after corrective execution, and audit the wider corpus read-only for conflicting subjects, automatic push, or newly introduced cadence.
  3. Report cross-role history as searchability/compatibility evidence only, naming explicit prompts and rejected TFW-49 machinery as confounders; leave Reviewer completion pending independent review.
  4. Run unit and integration docs tests separately, record results in EV/RF, then remove only generated outputs and caches while preserving pre-existing ignored user files.

5. Risks Found (edge cases, potential issues not in TS)

  1. Editing any verification-only file for symmetry would violate the revised TS even if semantics stay aligned; four preserve blobs must remain byte-identical to 389168a.
  2. Existing stage/WAIT/STOP language can be misread as TFW-50 cadence; verification must distinguish pre-existing workflow behavior from newly added commit requirements.
  3. Explicit attribution prompts and prior TFW-49 machinery confound the observed role history, so compliance must not be presented as causal proof or authentication.
  4. Docs verification can generate site/, .pytest_cache/, or __pycache__/; cleanup must target only paths generated by the test run and preserve all shared-checkout work.

6. Inconsistencies with Code (spec vs reality)

No blocking inconsistencies were found. The revised TS-declared corrective state was confirmed:

  1. The current conventions sentence lacks the revised exact derivation for normalized agent, open normalized scope, canonical-owner role, and Git metadata boundaries; this is the approved corrective edit.
  2. The current glossary separates attribution from authentication and unmarked-human inference but does not yet state separation from Git author/committer metadata; this is the second approved corrective edit.
  3. Canonical handoff, both installed handoff copies, and RELEASE.md already contain the approved conflict reconciliation and are byte-identical to their 389168a blobs. The known canonical-vs-installed Evidence drift remains out of scope.

7. Knowledge Citations

# HL §7.2 ref Read? Applied / N/A Notes
1 .tfw/README.md — Traces Over Code ✅ Applied The subject becomes a compact, searchable execution trace.
2 .tfw/README.md — Naming Creates Behavior ✅ Applied Preserve the five subject components and exact all-role derivation without explanatory duplication.
3 .tfw/README.md — Single Source of Truth; Portability ✅ Applied One Markdown owner; no runtime or duplicated rule.
4 KNOWLEDGE.md §1 — D15, D23 ✅ Applied Keep workflow consumers thin and template/workflow prose compact.
5 KNOWLEDGE.md §1 — D24, D28 ✅ Applied Put the short action cue at the commit point and retain precise terminology.
6 knowledge/philosophy.md — F22 ✅ Applied Do not add optional blocks, registries, or prompt-surface bloat.
7 knowledge/process.md — F3, F4 ✅ Applied Use exact naming where commits already occur; do not add new commit actions or cadence.
8 knowledge/process.md — F6, F22 ✅ Applied Enforce the six-file ceiling and reject generic mechanism overhead.
9 .tfw/conventions.md §11 — Token density; Progressive Disclosure ✅ Applied Keep the canonical instruction to one sentence plus one example.
10 knowledge/convention.md — F5 ✅ Applied Treat canonical handoff as source while preserving explicitly protected installed-copy drift.
11 NEW: knowledge/convention.md — F3 ✅ Applied Verified the actual files and existing drift instead of trusting the TS description alone.
12 NEW: RES Iteration 1 — D1, D2, D4, D8 ✅ Applied Universal owner, no cadence, two-file correction, and non-causal evidence boundary govern this resumed execution.

ONB — TFW-50: Minimal Agent Commit Attribution | 2026-08-05