KB-6DCE
T2 RP Audit — 10 Bugs, Gaps & Priorities
5 min read Revision 1
10 — Bugs, Gaps & Priorities
Headline
No TRUE_BUG that produces a silently-wrong count was found. Every divergence audited is exposed by a status/warning/drift/coverage column. The system is honestly self-describing. The reliability deficits are adapter blind spots, reconciliation gaps, and candidate-only governance, not arithmetic errors.
Classified findings
COUNT_UNRELIABLE (correct number, misleading if headline read without its label)
- AX-PROCESS "19 candidates" mixes genuine processes with BACKUP_OR_NOISE / OS_LEVEL_INFRA / COMPONENT_OF_EXISTING_PROCESS. Real birth-ready ≈ 6 (per ledger). Show the lane, not the raw 19.
- AX-TRIGGER "event_type 52" includes 22 inactive (30 active). Show active/inactive split.
dot_tools309 as "live executables" — only ~119 have script_path; 41 have no file. Reliable as registry, not as executables.- AX-TRIGGER "525" / Process×Trigger = DB-only; excludes ~76 host triggers. Label "DB/dot triggers".
ADAPTER_BLIND_SPOT (counts undercount/unknown because source isn't natively governed)
- KB SOP enumeration — count UNKNOWN, only 2 docs, FP-risk ("doc mentions process ≠ process"). Biggest hole.
- host_crontab (54, 49 active) — the TRUE dot-runner schedule is here, DB-invisible;
dot_tools.cron_schedulemay be wrong. - systemd_timers (22), fs_scripts (42) — DB-invisible host workflows.
- Host triggers absent from the 525 trigger universe.
STALE_DATA
trigger_registry(107, all enabled) — stale parallel inventory; live census sees 408 with 27 disabled. Risk only if UI readstrigger_registry. Live surface correctly ignores it.v_dot_registry_no_file= 41 — registry rows pointing to missing files.MTX-TESTtest pivot still in node_contract (flagged retire candidate) — exclude from UI.wf_*_digest_v2tables ~1 day old (06-04 09:53) — bind UI to live views.
DUPLICATE_RISK (low)
normalized_signatureNULL on all 39 pivots — signature-dedup guard inert. Low impact today.
NEEDS_LAW_DEFINITION
- Non-partition parents PIV-001 (169 vs 492), MTX-L1 (matrix 2× double-count) — labeled ADVISORY_NO_PARTITION_LAW; define partition law or keep UI from summing.
- 3 synthetic axes (AX-BASE/TRIGGER/PXT) not in
axis_registry— register or formally mark derived.
UNVERIFIABLE
- PIV-301/302/303/310 aggregate pivots referenced in docs do not exist. Remove from any UI/contract claim.
OWNER_BLOCKED_NOT_BUG / CANDIDATE_EXPECTED
- official AX-PROCESS axis_assignment = 0; both registered axes CANDIDATE; 0 official nodes; all 12 ledger gaps
safe_now=false; job:cut READY_FOR_PRESIDENT (unvoted);real_run_enabled=false, REAL_RUN=0 (6 obs all DRY/SIM). All correct, authority-blocked, NOT bugs.
ACCEPTABLE_BACKGROUND_DRIFT
- birth_registry 1,194,844 growing; 7 drift nodes; PIV-313 system_issues growing. Live recompute keeps surfaces correct; drift flag is a feature.
NEEDS verification (non-blocking)
- Automated scanner schedule's first 04:10 fire unproven (last run 06-04 09:53). Live views compensate.
Priority — must fix BEFORE trusting a UI count headline
- P1 Label every host/KB-derived count as partial/unknown (esp. KB SOP, host cron/systemd). Never present them as complete.
- P1 In UI, show AX-PROCESS candidates by lane (genuine vs noise/infra/component), and AX-TRIGGER event types by active/inactive; label trigger universe "DB/dot only".
- P2 Resolve
dot_toolsvs bin/script_path reconciliation (41 registry_no_file; 119/309 script_path) or label dot_tools as registry-not-executables. - P2 Retire
MTX-TEST; reconcile or deprecatetrigger_registry(107) against live census. - P2 Remove PIV-301/302/303/310 references from contract/docs.
- P3 Register or formally mark the 3 synthetic axes; define partition law for PIV-001/MTX-L1; populate
normalized_signature.
Can be shown NOW with warning labels
- Base RP counts (live, reconciled) — show with the 14 no-count nodes greyed "no count".
- AX-TOPIC 7 nodes / 25 assignments — badge "CANDIDATE / unratified".
- AX-PROCESS job:cut (8, verified) and the 6 genuine candidates — badge candidate; hide/segregate noise lanes.
- AX-TRIGGER 525 — badge "DB/dot triggers", show active/inactive.
- Process×Trigger actionability ledger (12) — fully attributed, safe to show as a worklist.
- PIV-311 (219) and PIV-313 (220,170 open) — trustworthy, show live.