title: "Extract — "What do we NOT see?"" source: "tasks/TFW-55__canonization_program/research/iter1/3_extract.md"
Extract — "What do we NOT see?"¶
Mindset: Analyst. You have the raw findings. Now build structure. Make combinations visible that nobody proposed. Test: "Does my configuration space reveal at least one combination that nobody proposed in the Briefing?" Parent: HL-TFW-55 Goal: Cross-reference the Gather dimensions into coherent TFW identity, authority, trace, responsibility, exposition, and adoption configurations without selecting a winner.
Configuration Space¶
Build the full solution space by cross-referencing Gather's dimensions. Use the same dimension names as column headers.
Do NOT evaluate yet — list all combinations that are not obviously contradictory.
D9 promoted — Human/agent consumption contract¶
The Gather steering required a human-reader versus agent-orientation compatibility test. It varies independently of D6 Public exposition architecture: a project may keep the same human-facing doorway/essay while requiring agents to read that essay, a living specification, or only task-local cited traces. D9 is therefore promoted as a ninth dimension.
| Dimension | Alt A | Alt B | Alt C | Alt D |
|---|---|---|---|---|
| D9 — Human/agent consumption contract | One common canonical text is the mandatory semantic core for both | Human doorway/essay and agent specification are optimized separately under an explicit semantic-parity contract | Humans use doorway/essay; agents load task-local citations/traces first and treat the essay as optional orientation | Agent-first living specification is authoritative; human prose is a derived communication layer |
Coherent configurations¶
The theoretical cross-product is too large to list usefully. The table retains nine non-obviously-contradictory configurations; each differs from C1 on at least one Gather dimension. Hybrids are explicit rather than silently averaged.
| Config | D1 — Primary category | D2 — Official authority | D3 — Minimum trace payload | D4 — Project self-awareness claim | D5 — Human/agent relation | D6 — Public exposition architecture | D7 — Adoption/teaching sequence | D8 — Editions in foundation | D9 — Human/agent consumption contract |
|---|---|---|---|---|---|---|---|---|---|
| C1 Layered discipline | Discipline for traceable AI-delegated work | Corpus + canonical essay + living specification | Selected intent/decision/continuation trace | Retain six-question operational capability | Bounded delegate; human owns purpose, authority, acceptance, stop | Root doorway + canonical .tfw essay |
Useful work → limit → next mechanism → named principle | Non-universal learning example | Separate human/agent entry points with semantic parity |
| C2 Philosophy projection | Philosophy with method beneath it | Corpus + canonical essay + living specification | Full assurance chain | Expand toward reflexive learning/self-correction | Relation varies by domain/risk | Root doorway + canonical .tfw essay |
Concepts/vocabulary, then practice | Omit Editions from the foundation | One common canonical semantic core for humans and agents |
| C3 Methodology first | Methodology combining stable behaviors | Corpus + canonical essay + living specification | Selected intent/decision/continuation trace | Retain six-question operational capability | Bounded delegate | Root doorway + canonical .tfw essay |
Branch by prior knowledge, risk, and role | Proportional implementations only | Separate human/agent entry points with semantic parity |
| C4 Framework-only challenger | Practical prompt-and-files framework with philosophical framing | Layered repository authority: corpus preserves provenance, essay explains stable meaning, specification governs current mechanics | Selected intent/decision/continuation trace | Retire “self-aware”; use inspectability/self-description | Bounded human oversight; no agent authority claim | Root doorway + explanatory essay; specification is operational | Branch by work risk/prior knowledge | Optional proportional implementation/teaching aid | Human essay and agent specification optimized separately with semantic parity |
| C5 Specification canon | Practical framework | Living specification alone selects official meaning; repository retains history | Full assurance chain | Retire “self-aware”; use inspectability/self-description | Relation varies by domain/risk | Living specification first; READMEs are summaries | Explain complete framework first | Omit Editions | Agent-first specification; human prose is derived |
| C6 Corpus monism | Discipline | Repository corpus alone | Full assurance chain | Reflexive learning/self-correction | Agent as team member on an assurance gradient | Root README is the complete explanation/index into corpus | Useful work → limit → next mechanism | Central canonical progression | Humans use root; agents load task-local traces first |
| C7 Standalone minimal canon | Philosophy with method beneath it | Separate minimal canon outside current surfaces; repository remains evidence/history | Selected intent/decision/continuation trace | Retain six-question operational capability | Bounded delegate | Future 20–30 page guide becomes primary human authority | Useful work → limit → next mechanism | Central guide spine | One common guide is the semantic core; specification adds mechanics |
| C8 One-surface methodology | Methodology | Corpus + root canonical explanation + living specification | Selected intent/decision/continuation trace | Retain six-question operational capability | Bounded delegate | Root README is the complete canonical explanation; .tfw/README.md is retired or derived |
Concepts/vocabulary, then practice | Omit Editions | One common root text for meaning; agents add specification |
| C9 Quiet semantics | Methodology | Corpus + canonical essay + living specification | Selected trace as floor; evidence/review/verified knowledge scale with risk | Keep six-question test in the specification but drop “self-aware” as the public label | Bounded delegate | Root doorway + canonical essay | Branch by prior knowledge, risk, and role | Omit Editions from the essay; keep them in usage/teaching surfaces | Human essay and agent specification optimized separately with semantic parity |
Findings¶
E1 — Corpus and selector are separate functions in every viable authority model¶
The central D2 mistake is to make one thing do two jobs:
- corpus function: retain primary traces, evidence, superseded decisions, rejected experiments, and evolution;
- selector function: tell a reader or agent what TFW officially means and how it operates now.
The repository can perform the corpus function under every configuration. What changes is the selector.
| Config | What preserves history/evidence? | What selects current official meaning? | What selects current operational mechanics? |
|---|---|---|---|
| C1 | Repository corpus + Git | Canonical essay | Living specification |
| C2 | Repository corpus + Git | Canonical philosophical text shared by essay/spec | Living specification interpreted through that text |
| C3 | Repository corpus + Git | Canonical methodology essay | Living specification |
| C4 | Repository corpus + Git | Explanatory essay, without a new-category claim | Living specification |
| C5 | Repository corpus + Git | Living specification itself | Same living specification |
| C6 | Repository corpus + Git | The corpus, resolved by current branch/state and internal links | Current files in the corpus; no separate selector |
| C7 | Repository corpus + Git | Separate minimal canon/guide | Living specification |
| C8 | Repository corpus + Git | Root README | Living specification |
| C9 | Repository corpus + Git | Canonical essay; operational six-question check remains in spec | Living specification |
The 53-commit TFW-48/49 episode does not decide whether TFW is a philosophy. It proves three narrower points that all configurations must handle:
- the corpus can preserve a rejected experiment and an explicit restoration without erasing history;
- the current branch/tree can recover operational authority after over-engineering;
- a corpus without a selector forces readers to infer whether an old frozen HL, an approved-but-reverted RF/REVIEW, a restoration commit, or the current specification is authoritative.
The narrow external control strengthens the separation without prescribing an imitation. Scrum Guides explicitly names one English guide/version as the current official definition, labels translations by version, and sends readers elsewhere for revision history. Its revision history preserves changes and explains why the 2020 text became less prescriptive and less IT-specific. This is one mature example where selected current meaning, translations, and history have distinct roles. It does not prove that TFW needs Scrum's governance, a separate BoK, or an immutable definition.
E2 — Category and implementation are independent dimensions¶
The Configuration Space exposes a pattern hidden by the Briefing's “fundamental philosophy vs framework” debate:
- C1 and C6 use discipline but radically different authority systems.
- C3 and C9 use methodology while one retains the public self-awareness label and Editions example and the other removes both.
- C4 makes no higher-category claim yet preserves the same layered corpus/essay/spec architecture as C1.
- C2 is philosophy-led but may require a larger trace assurance chain than C1.
- C5 is framework-led and collapses meaning/mechanics into one specification.
Therefore the category decision cannot be inferred from current files, number of artifacts, or self-canon structure. H2 remains provisional. W3C/NIST show that components are not novel; only Iteration 2 can test whether the operational composition and scope justify a distinctive category.
E3 — Trace floor and assurance layers should not be synonymized¶
Across C1–C9, three compatible roles recur:
selected continuity trace
↓ when required by risk or lifecycle
evidence + review
↓ after verification/consolidation
verified reusable knowledge
This does not yet select C1, C3, C4, or C9. It makes one hidden incompatibility visible: if the essay defines “trace” as the entire assurance chain, Light and ordinary work inherit Full's machinery; if it defines trace as provenance-only, it loses the intent, rejected alternatives, and continuation context that internal evidence treats as important. C9 makes the proportional hybrid explicit: a selected trace is the semantic floor, while evidence/review/verified knowledge remain separately named layers that scale with risk.
The term must continue to exclude raw chat exports and hidden chain-of-thought. A transcript may be a source, and provenance may describe it, but neither automatically becomes a useful project trace.
E4 — Human-reader versus agent-orientation compatibility test¶
The test is cross-cutting because humans and agents need different densities without being allowed different meanings.
| Test | Human requirement | Agent requirement | Failure signal |
|---|---|---|---|
| T1 Identity | Explain what TFW is/is not without artifact jargon | Resolve category, boundaries, authority, and current task rules | Human and agent give materially different definitions |
| T2 Start | Choose a proportional entry and act without reading the whole corpus | Load exact current instructions and relevant traces | Simplification removes needed start information or agent loads marketing instead of rules |
| T3 Authority | Know where official meaning, current mechanics, and evidence/history live | Know which source governs conflicts and which files are historical | Corpus, essay, and spec can contradict with no precedence |
| T4 Load budget | Root ≤800 words; essay ≤2,000 words; link outward | Progressive disclosure; task-local context before unrelated corpus | One “universal” text becomes too vague for action or too long for orientation |
| T5 Drift | One stable definition across public surfaces | Machine-readable navigation is not required, but citations/links must resolve | Separate entry points evolve into separate semantics |
| Config | Human legibility | Agent executability | Main compatibility tension to carry into Challenge |
|---|---|---|---|
| C1 | Doorway and essay separate why/meaning | Spec and task traces provide exact rules | Semantic-parity contract must be explicit and testable |
| C2 | Coherent philosophy may aid understanding | Full assurance chain/common core may overload routine agent orientation | Philosophy may become too abstract for action or too prescriptive for domains |
| C3 | Methodology language may be concrete | Spec remains exact | Primary category may still be generic or indistinct |
| C4 | Honest explanatory frame without novelty burden | Spec remains exact | Public value may become “just docs/process” unless composition is explained clearly |
| C5 | Humans must read specification-led prose | Strongest operational precision | Specification may become both reference and essay, repeating current Full-first failure |
| C6 | Root can narrate the corpus | Agents can load traces directly | No authoritative selector when historical/current/rejected claims conflict |
| C7 | Guide can optimize human learning | Agents still need spec; common guide adds context | New surface duplicates authority before demonstrated external-author need |
| C8 | One human surface is easy to find | Agents add spec | Root likely regains essay/reference bloat and duplicates mechanics |
| C9 | Small public story with no anthropomorphic headline | Spec carries operational capability and rules | Dropping the memorable term/Editions may reduce explanatory distinctiveness |
D9 Alt B is the only configuration pattern that explicitly optimizes both audiences while demanding semantic parity; that is an analytical pattern, not yet a recommendation. Alt A, C, and D remain viable until Challenge tests load, drift, and authority.
E5 — Teaching states remain separate under every configuration¶
| State | What the corpus contains | Permitted interpretation in Iteration 1 | Not permitted |
|---|---|---|---|
| Teaching observation | Day-1 folder confusion after practice was squeezed; Day-2 starter/practice “worked normally” without tests; Day-3 manifesto discussion; university Day-2 artifacts were more concrete with participant attrition | A dated, founder-led observation about this material/audience | General learning efficacy, causal effect, or independent facilitation |
| Proposed pedagogical mechanism | useful work → visible insufficiency → add context/mechanism → compare attempts → name principle; delayed recall and transfer gates designed later | A falsifiable mechanism and design candidate | A demonstrated universal sequence |
| Demonstrated learning outcome | Immediate artifacts and speaker/owner acceptance; no delayed unfamiliar-task transfer or independent-facilitator result in the selected corpus | Immediate artifact completion only where recorded | Durable “mindshift,” transfer, retention, or causal superiority |
This separation changes configuration routing:
- an invariant or boundary may enter the essay after Challenge;
- an owner interpretation remains sourced as such;
- a pedagogical mechanism belongs primarily in the future guide/course unless it explains an essential method boundary;
- a teaching observation stays in research/evidence;
- a demonstrated learning claim requires the assessment gate actually to have run.
C1/C3 may mention the Editions path as a bounded example. C2/C5/C8/C9 can omit it from the foundation without denying the teaching observations. C7 can make it central to the guide without promoting it to a universal philosophical truth.
E6 — Hypothesis/configuration map¶
| Hypothesis | Configurations that keep it alive | Configurations that attack or narrow it | Extract result |
|---|---|---|---|
| H1 self-canon sufficiency | C1–C4, C8, C9 retain existing repo surfaces as corpus plus some selector | C5 collapses selector into spec; C6 tests corpus-alone; C7 adds a separate canon | “Repository is primary corpus” survives broadly; “repository alone is official authority” is a distinct and vulnerable C6 claim |
| H2 distinct identity | C1 discipline, C2 philosophy, C3/C9 methodology | C4/C5 framework-only explanations | Still provisional; the Configuration Space proves category is separable from architecture, not which label wins |
| H3 lecture knowledge belongs | All configs can route true invariants into their selector | C4/C5/C9 impose the strictest exclusion of pedagogy/brand from foundation | Candidate concepts exist, but routing depends on provenance class and Challenge consistency |
| H4 subtraction/two surfaces | C1–C4, C9 preserve the frozen two-surface structure | C5 spec-first, C6/C8 root-heavy, C7 new guide authority are controls | Human/agent compatibility must decide whether subtraction preserves both meanings and executable orientation |
E7 — Candidate invariants for Challenge, not decisions¶
The following recur across multiple otherwise different configurations. Challenge must test rather than assume them:
- Corpus ≠ selector: history/evidence preservation and current official meaning are separate functions.
- Principle ≠ mechanism: current artifacts may implement a principle but cannot define the principle by themselves.
- Trace ≠ transcript/hidden reasoning: a trace is selected, durable, inspectable project memory with provenance; assurance layers remain distinct.
- Delegation ≠ authority creation: a role or task assignment can bound authority but cannot manufacture owner legitimacy or independent identity.
- Capture ≠ verified knowledge: work may generate candidates by design; maintenance, review, and consolidation remain real actions.
- Teaching observation ≠ mechanism ≠ outcome: each has a separate evidence threshold and destination.
- Edition path ≠ universal maturity ladder: current proportional implementations and founder-led pedagogy do not establish one path for all users.
- Human/agent density may differ; semantics may not: different entry points require a parity/precedence rule.
- Rejection is part of self-description: a self-applying corpus must retain rejected paths without making them current authority.
E8 — Unexpected configuration revealed¶
C9 Quiet semantics was not proposed in the Briefing. It separates memorable claims from operational capability:
- keeps the layered self-canon architecture and a methodology-level category;
- retains the six-question self-description test in the living specification;
- does not use “self-aware project” as the public identity phrase;
- defines selected trace as the floor and assurance layers as proportional additions;
- omits Editions from the canonical essay while leaving them in usage and teaching surfaces;
- gives humans and agents different entry points under one semantic-parity contract.
This combination matters because it shows that H1/H4 can survive even if the owner-preferred self-awareness label and Light → Assisted → Full essay bridge do not. Challenge must compare it with C1, C3, and C4 rather than treating label rejection as architecture rejection.
E9 — OODA orientation and Extract decisions¶
Observe. Nine configurations cover philosophy-, discipline-, methodology-, framework-, specification-, corpus-, guide-, one-surface-, and quiet-semantics models. D9 exposes a cross-audience decision omitted from Gather.
Orient. The major dependencies are not “more philosophy means more files.” Category (D1), authority (D2), trace floor (D3), public label (D4), and delivery surfaces (D6/D9) can move separately. That is why the framework-only challenger and the layered self-canon can share most architecture while disagreeing on identity.
Decide. Extract is sufficient for focused mode: the Configuration Space contains all Gather dimensions plus justified D9; corpus/selector roles are explicit; the human/agent test is operational; teaching evidence states are separated; and C9 is an unanticipated viable combination. No configuration has been eliminated.
Act. Carry C1–C9, invariants I1–I9, the H1–H4 map, and the exact C4 challenger into Challenge. Challenge should use pairwise consistency and falsification against frozen DoD/DoF, source evidence, authority resolution, claim calibration, human/agent compatibility, and over-engineering cost.
Checkpoint¶
| Found | Remaining |
|---|---|
| Nine coherent configurations cross all Gather dimensions; C9 reveals a previously unproposed label/capability split. | Challenge must eliminate, narrow, or combine them through explicit consistency criteria rather than preference. |
| Corpus preservation and current-meaning selection are separate functions in every authority architecture. | C6 corpus-alone and C5 specification-alone remain live controls until attacked. |
| D9 makes human versus agent consumption explicit and testable across identity, start, authority, load, and drift. | No cold-reader/agent test is executed in Iteration 1; H4 outcomes remain design-level. |
| Teaching observation, mechanism, and demonstrated outcome now have separate routes and claim limits. | Which lecture concepts qualify as foundation invariants remains for Challenge. |
| C4 framework-only challenger is intact and fully specified. | H2 category/novelty judgment remains provisional until Iteration 2 even after Challenge. |
| Scrum Guide provides one narrow real-world control for selected-current-definition versus separate history/revisions. | It is not a model to copy automatically and says nothing about agent-oriented consumption. |
Sufficiency: - [x] External source used? — official Scrum Guide current-version and revision-history surfaces as a narrow authority-architecture control. - [x] Briefing gap closed? — corpus/selector split, D9 human/agent tension, teaching evidence states, unchanged C4 challenger, and H2 provisional boundary are explicit. - [x] Configuration Space built from Gather dimensions? — C1–C9 use D1–D8 plus promoted D9; no configuration eliminated.
Stage complete: YES → User decision: close stage — coordinator confirmed that D9 is independent of D6, C4 is a faithful strongest framework-only challenger, and C1–C9 cover the materially different architectures without requiring a Cartesian enumeration.
Coordinator direction carried into Challenge¶
- Separate evidential viability from compatibility with the frozen HL. A candidate that better explains the evidence but conflicts with a frozen section remains an amendment-proposal candidate rather than being eliminated by contract.
- Apply the same criteria before preference; do not privilege C9 for novelty or C1 for proximity to the approved architecture.
- Run an explicit head-to-head for at least C1/C3/C4/C9. Exclude other configurations only through a concrete falsifier, evidence gap, contradiction, or over-engineering cost.
- Test C6's central contradiction explicitly: the corpus preserves history but may not select current official meaning by itself.
- End Challenge with survivors, eliminated configurations and reasons, conditional H1–H4 status, possible frozen-HL amendment candidates, and Iteration-2-driving open questions.
- Do not close H2 in Iteration 1 and do not presume D9 Alt B wins merely because four strong configurations use it.