Skip to content

ONB — TFW-55 / Phase B.2: Restore and Localize the Project README

Date: 2026-08-26 Author: Codex Executor Status: 🟠 ONB — Complete; no blocking questions Parent HL: HL-TFW-55 Phase HL: Phase B.2 derivation TS: TS Phase B.2 Plan baseline / Executor start: 2a534c70f31807b0f131b7a83e46e249715697e0 Master freeze: 5dee93d31fde4ee5ea279880137e83fb50fca296

1. Understanding

Corrective Phase B.2 restores the root project README's practical guide function from the exact public prefix of b924926:README.md, then applies only source-backed factual, authority, navigation, Edition/command/path, and minimal Philosophy-of-Trace corrections. The live Task Board tail comes only from the Executor start commit and may change only in the normal TFW-55 row. Russian and Kazakh become complete, natural localizations of the restored practical guide—not summaries, literal structural translations, or second versions of the Project North Star—and carry no Task Board. Execution creates new Phase B.2 ONB, EV, RU/KK critic reports, and RF, preserves the superseded B1 chain unchanged, and stops after RF without starting formal review or post-APPROVE docs work.

The exact historic prefix was reproduced before any production edit at 1,485 whitespace-delimited words and SHA-256 d14f9b89b174a59f8cd3177dfd111147ec2efdfcb3254fd3790788896b11638d. The checkout is clean and exactly at the approved plan baseline.

2. Entry Points

  • Production targets: README.md, README.ru.md, and README.kk.md.
  • Historic functional baseline: public prefix of b924926:README.md, ending immediately before ## Task Board.
  • Live board source: 2a534c70f31807b0f131b7a83e46e249715697e0:README.md; normalized LF tail SHA-256 4a11135d87a8dbe8583560faab61147dd5c7a0b0d769029cc3aed6e7ff409ccc; normalized non-TFW-55 tail SHA-256 02b8e94e0052907a40b129b3a463111017999d81070a933adfde5e4eb7330a37.
  • Read-only semantic source: reviewed Project North Star, blob 71a4d725cff7d0d7508403589195e9f87a0fc49a.
  • Current fact sources: Editions guide, Quick Start, conventions, glossary, adapter directories, LICENSE, .tfw/VERSION, and the checked repository tree.
  • Corrective authority: approved Phase B.2 HL, approved Phase B.2 TS, and master Amendment A6 at 5dee93d.
  • Superseded chain retained read-only: original Phase B ONB, RF, EV, RU/KK language reports, review stages, and REVIEW.
  • New evidence targets: evidence/EV__phase-b2__project_readme_localization.md, evidence/LANG_REVIEW__phase-b2__ru.md, evidence/LANG_REVIEW__phase-b2__kk.md, and RF__phase-b2__project_readme_localization.md.

3. Questions (blocking — cannot proceed without answers)

No blocking questions. The owner correction, exact historic prefix, live-tail rule, keep/update/add/remove ledger, semantic minimum, localization standard, critic protocol, scope exclusions, and hard stop are explicit in the approved HL/TS and delegation.

4. Recommendations (suggestions, not blocking)

  1. Reconstruct English as historic practical prefix + exact live tail, then edit the prefix section-by-section against the approved ledger; do not use the current compressed prefix as drafting material.
  2. Freeze one English/Russian/Kazakh draft commit only after deterministic fact, link, command, path, UTF-8, anti-paraphrase, newcomer-walkthrough, board, blob, and source-scope checks pass.
  3. Give both language critics the same fixed authority/functional/materiality packet and only their relevant target language. Preserve every initial finding and use the same critic for the exact-final recheck.
  4. Keep descriptions of configured build commands honest: the repository entries are echo placeholders, so TS-specific document checks—not placeholder echoes—are the substantive verification gates.

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

  1. The practical baseline contains several unsupported promises (automatically captures, traces replace documentation, decisions document themselves, no manual documentation, same lifecycle/artifacts in every domain, unbounded agent-team language). Correction must remove the claims without deleting the sections and newcomer functions that carried them.
  2. The baseline Quick Start predates the visible Editions topology. A blind copy of .tfw/ for every new/existing project would bypass Edition choice; the current Editions guide and Full Quick Start must jointly govern updates.
  3. The baseline .tfw/ inventory says the essay contains lifecycle, anti-patterns, and evolution, but those mechanics were deliberately moved to conventions/glossary/history. Navigation must be corrected without replacing the inventory with philosophy prose.
  4. The full RU/KK files will be substantially larger than the rejected B1 localizations. Critic feedback can tempt compression; functional parity and naturalness, not length symmetry, govern decisions.
  5. Task Board state can move concurrently after the start commit. The approved reconstruction preserves the frozen start tail except the normal TFW-55 row; any later parallel change observed before commit must be surfaced to the coordinator instead of silently merged or rolled back.

6. Inconsistencies with Code (spec vs reality)

# Approved/source claim Repository state at 2a534c70 Disposition
1 Master HL §7.2 and the Task Board cite research/iter2/RES.md tasks/TFW-55__canonization_program/research/iter2/RES.md is absent Pre-existing, non-blocking for B.2. Phase A's reviewed result and approved B.2 contracts contain the controlling consequences. Do not reconstruct research under Executor scope; record the gap in RF observations.
2 KNOWLEDGE D66 describes the rejected compact doorway as current architecture D66 and the Public Entry architecture row are stale after owner rejection Explicitly deferred to mandatory post-APPROVE /tfw-docs; Executor does not edit KNOWLEDGE.
3 Phase B.2 historic baseline is 1,485 words with the named SHA-256 Reproduced exactly from b924926:README.md before the Task Board Consistent; this is the production-source gate.
4 Phase B.2 starts from plan baseline 2a534c70… and freeze 5dee93d HEAD equals the full plan baseline; both approved artifacts are present; worktree is clean Consistent; safe to create ONB and request the gate.
5 .tfw/README.md must remain reviewed blob 71a4d725… HEAD:.tfw/README.md equals the required blob Consistent; recheck at every production/final gate.

7. Knowledge Citations

# HL §7.2 ref Read? Applied / N/A Notes
1 b924926:README.md — practical landing, audiences, Editions, starts, FAQ, mechanics, structure, adapters, concepts, updating, links ✅ Applied Exact prefix reproduced; every heading enters the keep/update/add/remove ledger, with practical function kept by default.
2 [.tfw/README.md](../../../concepts/philosophy.md) — reviewed Project North Star ✅ Applied Read-only authority for the small definition/human-boundary/Trace correction and anti-paraphrase limit.
3 KNOWLEDGE.md — D2, D35, D40, D52–D60 ✅ Applied Preserves root/essay separation, business-first breadth, evidence honesty, current Editions, and capability boundaries; stale D66 is deferred.
4 knowledge/philosophy.md — F3, F6, F8, F10–F16, F21–F25, F32–F33 ✅ Applied Keeps critical, domain-agnostic, continuation-oriented messaging while removing self-documentation and determinism overclaims.
5 [.tfw/conventions.md](../../../reference/conventions.md) — §§3, 11, 14 ✅ Applied Governs Project North Star separation, English artifact language, scope budgets, placeholders, evidence honesty, trace preservation, and Executor role lock.
6 knowledge/convention.md — F7, F9, F17–F19 ✅ Applied Retains stable brand names and practical newcomer language; naming/identifier exactness is part of localization parity.
7 knowledge/process.md — F2, F11, F16, F22, F25, F27 ✅ Applied Source-checks content claims, avoids new ceremony, and keeps responsibility/status maintenance limitations visible.
8 knowledge/constraint.md — F2, F3, F6–F7 ✅ Applied Prevents filler, state contamination, and code-only verification; the live board and .tfw/README.md remain separate protected sources.
9 knowledge/domain.md — F1–F3 ✅ Applied Preserves the repository-as-queryable-memory benefit and problem-led vocabulary without repeating a definition essay.
10 knowledge/stakeholder.md — F1, F4 ✅ Applied Keeps practical business value, audience recognition, and low-friction Edition choice before detailed mechanics.
11 TFW-32 Phase D RF ✅ Applied critically Retain audience/use-case capability and business-first framing; reject old self-maintenance claims and do not let positioning override current authority.
12 TFW-51/52 — Editions and capability limits ✅ Applied Light/Assisted/Full remain proportional; Assisted's manual fallback and lack of measured superiority/automatic hook guarantee stay explicit.
13 TFW-55 RES Iteration 1 ✅ Applied Preserves corpus/essay/spec authority separation, bounded human authority, selected continuity, and the full-strength anti-overclaim challenger.
14 [TFW-55](../HL-TFW-55__canonization_program.md) RES Iteration 2 ⚠️ unavailable Applied through approved successors The file is absent. Its approved consequences are carried by the master freeze, reviewed Phase A essay/RF/REVIEW, and B.2 HL/TS; absence is preserved as an observation.
15 Owner mini-essay 0.8 corpus N/A to direct B.2 loading Applied through Phase A B.2 localizes the reviewed practical English guide and uses the reviewed Project North Star, not private-source prose, as public semantic authority.
16 Owner architecture note N/A to direct B.2 loading Applied through Phase A The approved Philosophy of Trace → TFW methodology → realization architecture is frozen in the master and reviewed essay.
17 Owner BoK v0.1 working map N/A N/A The working BoK is non-authoritative and explicitly out of B.2 scope.

No new PV item changes the approved execution. The owner correction itself is already the controlling Amendment A6 and Phase B.2 contract.

8. Scope Budget Gate

Budget Configured maximum TS estimate Admission
Total execution-stage files 30 8 PASS
New files 15 5 PASS
Modified files 30 3 PASS
Changed LOC 3,000 ≤1,800 PASS

At onboarding, the authorized file set is exactly the three root READMEs plus the five new Phase B.2 artifacts named by the TS. The Task Board transition is part of README.md, not a ninth path. No scope split or contract escalation is required.

ONB — TFW-55 / Phase B.2: Restore and Localize the Project README | 2026-08-26