08 — Pilot 1: DOT Registry List (deep-dive)

Goal: show end-to-end how the DOT list is (or isn't) live / auto-counted / pivot / IU-KG / birth-governed / DOT-refreshable / UI-visible. Counts read from pivot, not hand-counted.

Live DOT catalogs

• dot_tools (309) — the operational DOT registry. Tier: A=60, B=230, null=19. Status: active=291, published=16, null=2. paired_dot not null = 131/309 (178 unpaired). description 100% populated; operation populated only 50/309; coverage_status null 103/309; file_path 228/309. ~35 distinct domain values (largest: collection 51, infrastructure.schema 41, infrastructure.sync 22, monitoring.integrity 17).
• dot_iu_command_catalog (54) — IU-DOT command catalog. 100% metadata complete (0 null category, 0 empty target_functions). mutating=39, reversible=41. Categories: collection 11, lifecycle 14, read 13, health 9, piece 7. No schema/test/paired_test column — IU-DOT test/pairing is not modeled here at all.
• dot_operations (20), dot_domains (46) (no description col; 13 top-level + sub), dot_domain_rules (67), dot_coverage_required (11), dot_config.

Planned DOTs in KB/design

• s146-m4d-a-dot-classification-audit (152 tools historically), s161-p2-kg-dot-registration-report (36 DOT-KG, 18 paired pairs, tier A18/B18), dot-registry-audit-report.md (repo 82 / VPS 75, 7 unsynced). IU-DOT completeness matrix flags missing DOTs: delete-edge, fn_iu_enact wrapper, vector reindex/sync.

pg_proc function reality (DOT)

• fn_refresh_dot_count() (trigger) → updates meta_catalog WHERE code='CAT-DOT' = count of active/published dot_tools.
• fn_refresh_orphan_dot() (advisory-locked) → CAT-DOT.orphan_count (null/empty desc or category).
• fn_validate_dot_origin(), fn_enforcement_validate_dot(), gen_code_dot_tools(), fn_dot_iu_command_log(...) (fail-closed IU-DOT logger), fn_normalize_dot_filepath().
• dot_iu_command_run + dot_iu_runtime_lease (lease acquire/release) = governed runtime execution log + concurrency control.

Test status / paired tests

• dot_tools paired_dot: 131/309 (42%) — 178 unpaired. Domains fully paired: normative (11/11), KG sub-domains. Domain workflow 0/10 paired.
• dot_iu_command_catalog: no test/paired column → IU-DOT test status is NOT tracked in that table. (Đ35 §11 paired-test retrofit is the relevant governance program.)

Metadata completeness

• description 309/309 ✅; operation 50/309 ❌; coverage_status 206/309 (103 null) 🟡; tier 290/309 (19 null) 🟡.

Pivot readiness — ✅ LIVE

• PIV-007 "DOT Tools — Total" (source dot_tools) → 309 → feeds CAT-006 via refresh_meta_catalog_from_pivot (pure-total branch).
• PIV-104 "dot_tools by category" filters status='published' → sees only 16 rows → non-representative grouped pivot (291 are 'active'). Defect to fix: change PIV-104 filter to include 'active', or drop the status filter.
• Dual count target: PIV-007→CAT-006 (dot_tool) vs fn_refresh_dot_count/fn_refresh_orphan_dot→CAT-DOT. Two CAT codes count the same table; CAT-006 cross_check = LỆCH (record 309 vs count_b 163). → RECONCILE to a single canonical CAT.

Birth / collection trace

• dot_tool species present in birth_registry (592 births). dot_tools is a managed collection in meta_catalog (CAT-006). Birth-governed ✅ (soft gate).

IU / profile relation

• dot_tools is not an IU (information_unit holds law_units + design_doc_sections only). DOT semantics surface in KG via universal_edges (dot_tools→taxonomy 469). IU-DOT bridge exists only as the 54-row command catalog. → Optionally project DOT profiles as IUs later; not required for the list to be live.

Scanner coverage

• fn_refresh_orphan_dot (orphan DOTs), fn_birth_onboarding_full_scan, Đ23 inverse-check (unmonitored/unregistered), Đ19 orphan-scanner (Side B). Coverage reported 100% in orphan-scan-report (0 orphans).

Pilot verdict — FOUND_LIVE, PARTIAL on quality

The DOT Registry List is already a live, pivot-counted, birth-governed, DOT-refreshable, UI-visible (spec) list. It does NOT need a new engine. Reuse-first actions:

1. RECONCILE dual count (CAT-006 vs CAT-DOT) → one canonical CAT, one pivot.
2. Fix PIV-104 filter (published→include active).
3. EXTEND metadata fill: operation (50/309), coverage_status (103 null), tier (19 null) via the existing dot-metadata-fill DOT (REUSE, don't rebuild).
4. Retrofit paired tests for 178 unpaired under Đ35 §11 (governed, not ad-hoc).
5. Add a test/paired view over dot_iu_command_catalog if IU-DOT test tracking is wanted (additive view, no new table).

• Do NOT manually count DOTs anywhere; PIV-007 is canonical.