GPM/GDE + WEDGE
Build 14 carries forward GPM/GDE and WEDGE as related governance antecedents while preserving an important distinction: GPM/GDE continuity/review work and the later WEDGE consequence-boundary architecture should not be collapsed into one implementation lineage.
The visual is explanatory, not a claim that every historical demo implements the complete runtime architecture.
GPM/GDE and WEDGE are related, but they are not the same implementation.
GPM/GDE carries LifeStack-derived governed memory, continuity, actor/authority scope, admissibility, review, persistence, provenance, and receipt patterns. WEDGE later formalizes current standing, route, executor, no-bind/refusal, replay, substitution, and protected-state evidence at the consequence boundary.
GPM / GDE
- Governed memory and continuity
- Actor + authority scope
- Admissibility / review records
- Persistence, provenance, receipts
WEDGE
- Current standing at bind time
- Route + executor constraints
- No-bind / refusal
- Replay, substitution, verification
SIW carries these principles into the inquiry lifecycle: acceptance is not activation; merge is selective and revalidated; composition is inspectable; binding commits to exact conditions.
Concept explanation and proof are not the same object.
The concept surface helps visitors understand the architecture. The WEDGE proof surface is where bounded claims, routes, protected state, fixtures, observed results, and verification context belong.
GPM/GDE WEDGE
- Human-facing architecture orientation.
- Interactive navigation and conceptual relationships.
- Useful for understanding the governance checkpoint.
WEDGE / Threat Stream
- Bounded evidence and inspection path.
- Scope, route, protected state, fixtures, and result.
- Does not become universal proof merely because the demo passes.