Checkpoint — Reuse Extraction Map v0.1 (2026-06-09)

Phase: Authority Contract v0.1 → Reuse Extraction Map v0.1 → (next) GPT review → Gap-only Scope Spec (read-only surface only). Final status: REUSE_EXTRACTION_MAP_READY_FOR_GPT_REVIEW. Production mutation: NO. No install, no PG/Directus/registry/filesystem mutation, no system_issues write, no tool/schema/runner created, no FIX7 resumed, no filesystem DOT invoked, no command called, no detector executed, no denominator collapsed, no Codex-sealed decision reopened. No fresh live read taken — the sealed 2026-06-09 07:11 UTC baseline stands.

What was done

Produced a read-only, capability-by-capability Reuse Extraction Map for the future read/report-only Implementation Package DOT v0.1, grounded entirely in the sealed evidence chain (Authority Contract v0.1 + Codex seal BCDGH_SEALED + fresh-read closure + baseline ledger + reuse audit). Each of the 18 required capabilities classified into exactly one of six classes: A REUSE_AS_IS · B REUSE_WITH_ADAPTER (read-only, file-report-only) · C REFERENCE_ONLY · D PROHIBITED_OVERLAP · E TRUE_GAP · F UNVERIFIED.

Key reframing vs. the (pre-seal) reuse audit: that audit assumed the tool could call engines and eventually run commands. The Authority Contract sealed v0.1 as read/report-only with no calls and no filesystem DOT invocation, so "call directly" reuse was downgraded to read-only reads, and the command-runner "true gap" was reclassified as DEFERRED behind the not-yet-sealed Call Contract.

Documents created

• reports/reuse-extraction-map-v0-1-2026-06-09.md (main map; rev 1) — verdict, exec summary, 18-row capability table, reuse-as-is/adapter/reference/prohibited/true-gap/unverified lists, Gap-only Spec readiness, minimal next step.
• reports/reuse-extraction-map-v0-1-2026-06-09.json (machine mirror; rev 1).
• checkpoints/checkpoint-reuse-extraction-map-v0-1-2026-06-09.md (this file).
• 00-index.md updated (rev 23 → next) — adds the map row, advances current phase.

Headline findings

• Biggest reuse: deployed reconciliation + graph + corpus read surfaces, consumed strictly read-only (dot_tools 309 listing; v_dot_reconciliation_reliability over wf_fs_dot_bin_snapshot; universal_edges 2199 / v_kg_edges_all 2259 / entity_dependencies 142; information_unit 219 + tac_logical_unit 102 dual-report; the tool-kiem-thu report+json+checkpoint pattern). All live SELECT/KB-read, full provenance.
• Biggest prohibited overlap: a second runner/dispatcher that invokes anything (filesystem DOT or IU command); plus a third cut/verify/manifest authority, a new logger, a new graph/duplicate/orphan/canonical-id resolver, and any TAC↔IU bridge/merge/canonical choice.
• True gaps (all narrow/bounded): (1) command-runner with exit codes [DEFERRED — Call Contract]; (2) run/pass half of the claim↔test binder [DEFERRED]; (3) generic package_manifest schema [DEFERRED — owner lineage decision]; (4) --selftest N/N + module_sha256 self-pin [post-spec build]; (5) audit_dead_links() engine [read-only report reusable now, engine+sink deferred]. The doc-level canonical-id resolver is NOT a true gap — UNPROVEN (Domain G), needs a gap proof first.
• Biggest unverified: filesystem-DOT runnability (NOT AVAILABLE, Domain B) and the actual_count=163 filter (external dot-catalog-sync artifact, UNVERIFIABLE/UNSAFE). Secondary: Directus 100%-DOT-control (PARTIAL_EVIDENCE_ONLY); the UNPROVEN doc-level canonical-id gap; the two unresolved owner decisions.

Gap-only Spec readiness

PARTIAL_READY. Ready for the read/report-only gap surface (existence resolver, claim-inventory extractor existence-half, dual-corpus reporter, reconciliation report, provenance writer, read-only dead-link report, FIX7 read/report pilot). The execution-dependent gaps (command-runner, run/pass binder, generic manifest schema) must be carved out — blocked behind the Call Contract and two unresolved owner decisions.

Sealed boundaries preserved (not reopened)

A/E/F/I/J adopted defaults; B/C/D/G/H BCDGH_SEALED; the 7-denominator contract (never collapsed); read/report-only; no calls; no filesystem DOT; dual-report TAC/IU; no new runner/registry/logger/graph/corpus authority. All intact.

Minimal next step (exactly one)

GPT review Reuse Extraction Map. No further read is productive (the unverified residuals are owner decisions or permanently unreachable read-only). No tool/schema/runner, no call, no mutation until reviewed and a spec is approved.