Public Review CandidateBuild 15 · SIW / Canon Reader integrationReview guidenoindex · review deployment
Genesis AiXGoverned knowledge
architecture
View
ProfileHistorical Prototype
Genesis AiX›Governance Lineage
Build 12.6 · lineage reconciliation

Lineage is not dependency, and chronology is not authority.

Build 12.6 separates three relationships that Build 12.5a compressed into one arrow: historical development sequence, conceptual contribution, and mandatory runtime dependency.

Independent review A-03 dispositionThe 12.5a packet and site told different ordering stories for GPM/GDE and WEDGE. The linear four-node path is retired. The current site states chronology separately and does not use chronology as proof of dependency or authority transfer.
Historical development chronology

Current public chronology.

This is the narrow sequence supported by the current review record. It does not claim uninterrupted code lineage or automatic succession.

FoundationLifeStack

Broader governance architecture preserved identity, authority, consent, provenance, trust, continuity and protected conditions.

Boundary responseWEDGE

The consequence boundary became explicit: standing, executor, route, refusal/no-bind, replay, substitution and verification.

RefinementGPM / GDE

Later work made governed memory, diligence, actor/authority scope, persistence, decision evidence and continuity questions more exact.

Inquiry environmentSIW

SIW applies accumulated governance distinctions to inquiry, inspection, activation, branching, selective merge, composition, binding and evidence.

Relationship types

Three questions must be answered separately.

A relationship should say what it means rather than asking an arrow to carry several meanings at once.

Chronology

What emerged earlier or later in the engineering record?

Conceptual contribution

Which earlier distinctions materially inform a later architecture or representation?

Runtime dependency

Which component must actually be present in the execution path for the later system to operate?

Build 12.6 rule: a shared invariant or lineage relationship does not establish mandatory dependency, code identity, ownership, succession or authority transfer.

Architecture roles

Related architecture can remain distinct.

The current public role descriptions remain useful once the ordering ambiguity is removed.

LifeStack

Broader governance: policy, provenance, trust, security, knowledge and governed infrastructure.

WEDGE

Consequence boundary: current standing, route, executor, refusal/no-bind, replay, substitution and verification.

GPM / GDE

Governed continuity and diligence: memory, actor/authority scope, admissibility review, persistence, provenance and receipts.

SIW

Governed inquiry: inspection, activation, bounded branching, selective merge, composition, binding and evidence.

Genesis Knowledge Fabric™

Governed knowledge and representation environment connecting Canon, lifecycle, lineage, evidence and navigation without collapsing representation into authority.

Federated SDI

Bounded collaboration/evolution architecture in which signed claims may compose while authority remains local and separately governed.