GPT Review — Axis/Proposal/Authorization Substrate Design Conditional PASS; Needs Hardening Before Build

Date: 2026-06-02 Reviewer: GPT Council

Verdict

The design package one-roof-axis-proposal-authorization-operating-substrate-design-2026-06-01/ is accepted at architecture direction level, but it is not yet sufficient for build. It correctly identifies the model shift: PG remains truth/runtime; proposal layer is PG-native/hybrid; official axes/topics are born/governed objects; UI is projection; human e-sign is reserved for L4 sovereign acts; technical build authorization needs its own L3 substrate.

Evidence checked

Reviewed docs 00, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, and 15.

What is good

• The authorization model separates technical build authorization from sovereign e-sign.
• The axis model is common across reconstruction, containment, topic, pivot, and future axes.
• The storage model stays PG-first and avoids a separate topic island.
• Proposal layer recommendation is practical: hybrid PG-native now, Git-like semantics without external dependency.
• Topic workflow separates human, AI-proposed, and KG-provisional paths.
• Reconstruction/containment are treated as deterministic validation axes, not semantic proposal axes.
• Governance coverage is tiered: candidate = input-quality, born/active/UI-visible = governed.
• UI is correctly projection-only.
• Phase-1 impact is conservative: substrate spine only after authorization model change; operational topic/T6/T7/backfill deferred.

Remaining gaps before implementation

1. Authorization L0–L4 needs hardening into exact state machine, required records, anti-forgery proof, TTL/revocation, and verifier algorithm.
2. Axis Registry and axis_assignment need detailed CREATE-TABLE-level design and compatibility with existing taxonomy/taxonomy_facets/entity_labels/iu_relation/KG tables.
3. Topic promotion/birth rules need exact criteria: which candidate becomes born object, who can promote, and what minimum evidence is required.
4. Proposal layer needs exact reuse decision for unit_edit_draft, approval_requests, iu_merge_set, doc_reviews; avoid vague hybrid design.
5. Governance auto-coverage needs precise detector inputs, severity/noise controls, and issue types before operational scanner design.
6. UI projections need exact view contracts for tree/graph/topic/detail/reconstruction readers.
7. Phase-1 build plan must be repatched after M-1 redefinition and SB-0 authorization substrate are hardened.

Decision

Do not resume Phase-1 build yet. Run one large hardening and detailed-design macro that folds this package into the implementation-index and produces exact build-ready designs for:

• SB-0/L3 technical build authorization;
• axis_registry and axis_assignment;
• proposal layer integration;
• governance coverage detectors;
• projection view contracts;
• updated Phase-1 build impact.

No COMMIT or implementation until that macro passes.