GPT Direction — After Registries-Pivot Rehearsal: Doc Governance and Next Macro

Date: 2026-05-31 Reviewer: GPT Council

Current verdict

The package registries-pivot-os-agency-count-integrity-orphan-phantom-label-pin-rehearsal-2026-05-31/ is a design/rehearsal pass, not final implementation. It provides enough evidence to move from exploration to a consolidated Master Design, but implementation should wait until the Master Design is ratified.

Document governance decision

Use this structure:

1. Canonical product/design docs: knowledge/dev/design/registries-pivot-os-agency/

2. Investigation/reports/evidence: knowledge/dev/reports/architecture/registries-pivot-*/

3. UI preview specs: knowledge/dev/ui/registries-pivot/

4. Laws / future law patches: knowledge/dev/laws/ only for actual law drafts/amendments, not design reports.

5. Runtime/static preview files: /ui-preview/registries-pivot/<version>/ on VPS only after a preview is needed.

Immediate next step

Run one large macro:

REGISTRIES_PIVOT_MASTER_DESIGN_V0_1_AND_READINESS_GATE

Purpose:

• consolidate prior reports into canonical Master Design v0.1;
• preserve reuse-first decisions;
• define data contract, drill-down, invariant, orphan/phantom, label/grouping, pinning, notification trigger, and no-hardcode rules;
• produce implementation/readiness gate;
• produce follow-up prompts for read-only rehearsal, PG view rehearsal, UI preview, and implementation.

Guardrails:

• no PG mutation;
• no Nuxt implementation;
• no schema commit;
• no production UI;
• no hardcode;
• no frontend count logic;
• every count must be pivot-backed or marked PIVOT_MISSING.