rtt=1 | coherence=declared | drift=bounded | paradox=structural
⚠️ Draft — The LINEAGE README is not yet available in this directory. This overview is grounded in the L-Ops definition from Framework Field Theory. It will be updated when LINEAGE canonical documentation lands.
What Is LINEAGE?#
LINEAGE is the canonical protocol governing Lineage Operators (L-Ops) across all TriadicFrameworks modules. L-Ops are the fourth operator family in FFT's seven-family grammar — they track the provenance, derivation, and inheritance chain of every structural component.
Without L-Ops, a system may be internally coherent but externally unverifiable. LINEAGE makes verification possible.
What L-Ops Do#
| Function | Description |
|---|---|
| Track origin | Record where a component was first declared |
| Track derivation | Map how a component changed from its origin to its current form |
| Track inheritance | Identify what a component carries forward from its ancestors |
| Enforce traceability | Ensure every transition can be traced back to its source |
Where LINEAGE Appears#
LINEAGE is not confined to a single module — it is a cross-cutting protocol:
- Every
rtt:doc-idin front matter is a LINEAGE anchor - Every
rtt:superseded-byis a LINEAGE pointer - The
TEL/LINEAGEsubmodule adds temporal event ordering to standard lineage - The
docs/LINEAGE/directory at the site root is the canonical lineage registry
Related Modules#
- Framework Field Theory — defines L-Ops formally
- TEL/LINEAGE — temporal event lineage extension
- Conditions Substrate Model — CSM manifests are LINEAGE-versioned
- Governance Substrate Model — governance history tracking uses L-Ops
© 2026 Nawder Loswin · Byte Books Publishing · LCCN 2026917007