lineage-map FE-EVAL-LINEAGE-2026-07-23

Framework Engineering Lineage and Authority Map

Framework Engineering Lineage and Authority Map

Field Value
Record ID FE-EVAL-LINEAGE-2026-07-23
Version 1.0
Status evaluated map; unresolved links are explicit
Authoring agent Codex
Created 2026-07-23T14:05:00-04:00
Repository baseline 214c08f
Parent records FE-EVAL-REP-2026-07-23
Supersedes none
Confidence moderate at family level; low for legacy file-level provenance
Completion state complete for major conclusion path

Major dependency path

Draft constitution / charter / principles
  ├─> FE-008 and FE-008A characterization
  ├─> FE-011A structured-redesign pilot
  ├─> FE-012A primitive extraction
  └─> FE-012B primitive synthesis
          │
          v
Theory of Framework Engineering v0.1
  ├─> traceability + confidence + competing explanations
  ├─> FE-012C replication instruments
  └─> FE-013 procedural-language hypothesis
          │
          v
ECR-000001 calibration and comparator evolution
          │
          v
Comparator 3.1.0 freeze + 3.2 explainability
          │
          v
ECR-000003 representation-sensitivity evidence
          │
          v
Hypothesis Review Board summary (proposal_only)
          │
          x
Blank human decision — no canonical promotion yet

The operating-system branch (registries, review templates, dashboards, queues, publisher) supports every step but is itself a design intervention whose net benefit is untested.

Authority rules reconstructed

  1. Evidence outranks authority when claims conflict, per research charter.
  2. An accepted human decision outranks a proposal summary for governance state.
  3. Frozen instrument documentation controls quantitative interpretation for its run.
  4. Theory v0.1 is the best current explanatory synthesis but remains provisional.
  5. Top-level draft principles are normative inputs, not validated findings.
  6. Generated output is derived evidence, not automatically canonical.
  7. Recency and filename do not establish acceptance.

Divergence and unresolved provenance

  • Normative branch: broad engineering discipline and product relevance.
  • Empirical branch: narrow characterization method with Low/Very Low causal confidence.
  • Grammar branch: finite reasoning primitives versus prompt-induced convergence.
  • Execution branch: separate execution grammar versus incomplete unified vocabulary.
  • Representation branch: backbone invariance versus detailed instability and recognition effects.
  • Governance branch: append-only aspirations versus editable Markdown and sparse supersession links.

Records requiring review when this evaluation changes

CURRENT_STATE.md, theory confidence assessment, hypothesis registry, scientific claims registry, research queue, product-architecture bridge, publisher authority model, and future mission index.

The companion JSON contains only evaluated critical-path nodes. It is not a fabricated full dependency graph.

Related Documents