Facet Succession
Facet was published on 2026-07-29 to capture an architectural inversion: continuously available human–AI attention can reduce the standing interface surface required at an outside boundary.
Its most durable result was the system behind those surfaces:
evidence -> reconciliation -> reviewed delta -> current truth -> encounterFlow implemented that loop first. Inference operations, cloud operations, and project proposals then reproduced parts of its discipline in unrelated domains. Kinra Corpus implemented the complete evidence, record, change, and current-selection loop while explicitly requiring no facet or publication surface.
That later evidence reversed the hierarchy. The truth machine is the portable core. A facet is one optional projection at its boundary.
Successor decision
Section titled “Successor decision”On 2026-08-09 Blake directed Kinra AI to establish this repository as the
professional successor and to retain Facets as an optional pattern. The
pre-project decision and exact source reviews are recorded as PP-0003 in the
private project-proposals repository.
Preservation
Section titled “Preservation”Truth Machine does not rewrite Facet’s history into having always held the new boundary. The separate retirement completed on 2026-08-09:
- the private GitHub repository is archived and the local checkout is retained;
- the historical repository identifies Truth Machine as successor;
- the original essay and vocabulary remain available in that record;
facet.kinra.airedirects permanently to the Facets pattern after the successor’s independent public verification; and- portfolio and hosting records identify the standalone runtime and private direct-host appointment as retired with an exact protected predecessor.
Evidence packet TME-20260809-0011 binds the public and bounded private
observations without copying private topology or protected rollback contents
into this repository.
The active specification uses literal professional vocabulary. Historical metaphor remains available where it explains provenance, not where it would obscure a normative requirement.