Intellectual lineage

Program lineage

Dated changes in program direction and typed relations among research artifacts.

Chronology

  1. Detection hypothesis registered

    The program tested whether local-to-global disclosure deficits diagnose consequential composition failure.

  2. Execution kill test

    Execution-derived labels falsified coherence fee as a runtime-failure predictor and included fee-zero breaches.

  3. Research reset

    The predictor and false corollaries were withdrawn. Formal, disclosure, and benchmark results were retained only within their recorded scope.

  4. Accountability descent preregistration

    Coverage, persistence, authority binding, non-equivocation, and remedy were specified as separate from formal gluing.

  5. Receipting contract revised

    Bulla and Glyph were aligned on persistent receipts, witnessing, reliance, challenge, and executable recourse.

Relations

Artifact relations

These edges record intellectual development, not theorem dependencies or runtime architecture.

Map types

Dependency, lineage, and operation

Formal dependency

Mathematical prerequisites

The Proofs graph records prerequisites and verification status.

Intellectual lineage

Research decisions

This page records motivation, testing, narrowing, falsification, supersession, and retention.

Operational consequence

Implementation sequence

Glyph and Bulla record occurrence, persistence, authority, reliance, challenge, and remedy.