00 — Readme First

Date: 2026-06-04 · Mode: EXECUTION_MODE · Macro: WORKFLOW_ORPHAN_REMEDIATION_PROCESS_CANDIDATE_RP_ASSIGNMENT_UI_CONTENT_AND_CANON_GATE Continues: checkpoint-universal-workflow-adapters-scanner-coverage-lift-2026-06-04

What this phase did

Took the scanner's cross-layer output (453-entrypoint universe, 143 orphan/remediation rows, 80 host-only unmanaged entrypoints, RP visible 0/453) and turned it into an operational process-candidate layer that Registries-Pivot can list — without unsafe canon, owner approval, or any process birth.

Headline before → after (live)

dimension	before	after
orphan objects with a disposition	0 / 143	143 / 143
candidate clusters	0	17 populated (19 seeded)
new managed-process candidates	0	6
host candidate-visible (RP-listable)	0	69 objects
host explicitly not-a-process	0	40 objects
host owner-gated	unknown	11 (docker)
host needs-review	unknown	23
official AX-PROCESS RP assigned	0 / 453	0 / 453 (still owner-gated — no fake)

Safety one-liner

DB-engineering is birth-free: birth_registry 1,168,741 before == after every apply; guard_alerts 129 unchanged; axis_assignment untouched (AX-PROCESS official = 0); dot_tools untouched; no approval_requests written; full rollback staged. KB doc uploads (this report) increment births as documentation — that is not DB-engineering mutation.

Read order

01 live state · 02 triage (143) · 03 candidate generation · 04 merge/split · 05 assignment surface · 06 RP coverage after candidates · 07 AI review/action panel · 08 owner/governance/birth queue · 09 remediation v2 · 10 UI/API packet · 11 content resume · 12 canon gate · 13 safety audit · 14 next macro · 15 final summary · 16 MCP checkpoint.

Artifacts (host)

/opt/incomex/docs/mcp-writes/workflow-candidate-2026-06-04/: 01_candidates_apply.sql, 02_views_reviews.sql, 99_candidates_rollback.sql. Checkpoint: knowledge/dev/reports/architecture/checkpoint-workflow-orphan-remediation-process-candidates-2026-06-04.md.