Family cycle
Trigger, intake, compress, test, expand, return, align, shape, receipt, propagate, then settle or retest.
Notes · Graphite Engine
Nine families. One center. No orphan brick.
The Graphite engine keeps the taxonomy dynamic. The nine integrity families share a common center. Any family can implicate adjacent families. No family is permanently first or last. The twelve nouns are intake classes available to every family, not twelve extra families.
Overview
Test, then shape, then receipt.
A finding enters a family, is compressed through fractionalization, then tested. Testing is adversarial: corroboration, contradiction search, reproduction, dependency retrace, stale-generation checks. Surviving material is shaped before it may settle. The shaping arbiter cannot create evidence or invent truth. If evidence is insufficient, the finding holds. Canonical architecture is assembled incrementally. No brick without a course. No course without anchorage. No architecture without receipts.
Activity
Stable: receipt-bound, no active trigger.Watch: aging evidence or an open condition. Active: material delta in flight. Critical: contradiction, authority breach or unproven high-impact transition. Activity is not confidence.
Probes
A family may extend temporary probes into public surfaces, repositories, tests and traces.Probes collect, verify, corroborate or contradict. They do not hold authority.
Settlement
Accept, generalize, subsume, reject, hold, split or retest.Shape, align, deduplicate, fence observation from authority, propagate adjacent impact, record proof debt, then receipt.
Coupling
Evidence realization can trigger identity and freshness.Policy coverage can trigger cutover and recovery. Stale observation can block publication. No family cools in isolation.
Outputs
No delta, corroboration, subsumed finding, new watch trigger, revised invariant, new test obligation, runtime block, cutover block, publication candidate, correction.
Idle
The engine never becomes permanently finished.It becomes stable enough to idle: instrumented families, active watch triggers, aging evidence, and the ability to retest the correct family without reopening the whole architecture.
Proof
The engine is not a source of truth.
Fractionalization asks whether a claim is safe to use. Taxonomy says what kind of thing it is. A Graphite family says which integrity law owns it. The shaping arbiter says whether it is formed well enough to settle. A runtime test and receipt say whether the settled architecture is actually true.