---

title: 12 — Implementation Readiness Gate + Classification date: 2026-05-31

12 — Implementation Readiness Gate

Per Đ20 (Design-before-Implementation): nothing is built until this gate passes. No condition may be satisfied by self-approval.

Gate conditions (ALL must be true before any implementation)

#	Condition	Current state	Blocker
RG1	Master Design v0.1 ratified by human/council	authored, NOT ratified	awaits review
RG2	Count-integrity P0 accepted (invariant + leaf-scope + drift surfacing)	designed + live FAILED evidence (doc 05)	awaits accept
RG3	Missing pivots classified (PIV-500/30x/31x/32x defined, not yet inserted)	ledger complete (doc 05/11)	awaits accept of pivot list
RG4	Phantom definition accepted OR deferred (LAW_DEFINITION_GAP)	operational def proposed (doc 06)	council decision
RG5	Label/pin registry strategy accepted (registry_pin NEW; labels REUSE Đ24)	designed (docs 07/08)	awaits accept; Species-Collection v0.5 + Đ36 are DRAFT (GATED_BY_APPROVAL)
RG6	UI contract accepted (Đ28 render-shell, registered templates, columns)	designed (doc 10)	awaits accept
RG7	No-hardcode test plan accepted (T-COUNT/LABEL/DRILL/PIN/COVERAGE/CONTRACT)	designed (doc 11)	awaits accept
RG8	Rollback plan accepted (Đ30: additive only, BEGIN..ROLLBACK first, version-pin, soft-retire)	designed (below)	awaits accept

Rollback / reversibility plan (Đ30/Đ33)

• All schema work is additive (phantom_count column, registry_pin table, new pivot rows, v_count_integrity view, fn_count_integrity_check()). No destructive DDL.
• Every change rehearsed BEGIN..ROLLBACK first; COMMIT only after Đ32 approval, off-peak.
• Reversal: DROP the additive view/fn/column/table; DELETE the new pivot rows; pins soft-retire (active=false), never hard-delete.
• The Đ28 retirement of health.get.ts gap-math is gated behind the pivot replacements being live (no gap where the old number disappears before the pivot exists).

Full classification (REUSE / EXTEND / WRAP / RECONCILE / DEFER / NEW)

NEW is allowed only where prior reports prove no suitable artifact exists.

Item	Verdict	Action
pivot engine (pivot_count/query/matrix, pivot_definitions, pivot_results, refresh_meta_catalog_from_pivot, v_pivot_*, v_registry_counts_compat)	REUSE	none
meta_catalog accounting cols + fn_refresh_orphan_col/dot/species + check_registry_coverage	REUSE	route to surface
fn_birth_onboarding_full_scan (new-object scanner)	REUSE	route output → system_issues + surface
label/taxonomy (label_rules/taxonomy/taxonomy_facets/taxonomy_matrix/entity_labels/species_collection_map/collection_groups, Đ24/Đ29)	REUSE	grouping source
system_issues + event_outbox/event_type_registry (Đ31/Đ45)	REUSE	notification/cleanup channel
design_templates + template_statuses + coverage scanner (Đ28)	REUSE	UI render-shell
/knowledge/pivot render-shell pattern	REUSE	template for the converged surface
pivot_definitions.parent_code (drill hierarchy, NULL on all 37)	EXTEND	populate (data) + add child-pivots
meta_catalog.phantom_count	EXTEND	add column (additive)
registry_pin	NEW	propose-only, born+registered+governed
v_count_integrity + fn_count_integrity_check()	NEW	propose (design-only)
PIV-500 grand-total, PIV-30x orphan/phantom/drift, PIV-31x label, PIV-32x pin	NEW (PIVOT_MISSING)	propose pivot_definitions INSERTs
frontend gap-math (health.get.ts, registries/index.vue)	WRAP→RETIRE	replace with pivot reads + PIVOT_MISSING
stored record_count ↔ live pivot; CAT-006(309) vs CAT-DOT(307) dual count	RECONCILE	one canonical CAT + one pivot
/knowledge/registries ↔ /knowledge/pivot ↔ /knowledge/registries-pivot route	RECONCILE	converge to one surface (route string GATED_BY_APPROVAL)
phantom law article	NEW (LAW_DEFINITION_GAP)	propose to council
ghost (cross-store) detection	DEFER	needs Qdrant read (DETECTION_DEFERRED)
IU 219 / KG 2,259 pivots	DEFER	PIVOT_MISSING; later macro
Species-Collection Law v0.5, Đ36 Collection v5.0	DEFER (GATED_BY_APPROVAL)	DRAFT laws; don't depend on un-enacted clauses

Survey-then-design-then-implement gate (prompt standard)

• Đ26/Đ28 are enacted → design pack is allowed (this package).
• Implementation is allowed only after this design is accepted (RG1) and the relevant additive changes pass BEGIN..ROLLBACK rehearsal under Đ32.

Readiness verdict

DESIGN COMPLETE / NOT YET IMPLEMENTABLE. All eight gate conditions are designed and evidenced; none is accepted. Next step = human/council ratification (RG1), then the read-only rehearsal macro (doc 13), not implementation.