Repository navigation
Decision ADR 0006 Issue Localization
Superseded on 2026-11-15. The arXMCP–Lean contract this record belongs to was retired: derived-alg-geo-lean#1906 removed MathFormalContract,
mfc, the registry and the attestation records, and arXMCP#547 removed arXMCP's side. Kept as history.
- Status: accepted (provisional — has an explicit un-park trigger)
- Date: 2026-08-04
- Deciders: Chris Dare
The contract spans two repos and will eventually span three (see ADR-0007). Work items therefore have three plausible homes. The relevant facts:
-
chris-dare-dev/arXMCPhas a mature roadmap machine: 12 milestones, ~300 open issues, atype:milestonelabel consumed by a/milestone-pipeline, epics named<track>-e<N>carrying<!-- roadmap-gh: track/id -->markers, andplans/*/roadmap.yamlas the source of truth. -
chris-dare-dev/bridgeland-stab-leanhad, before this ADR, the nine GitHub default labels, zero milestones, and zero issues. - Roughly 70% of the contract work is owned by this repo; arXMCP's share is
three offline CLIs, one SQLite migration, two MCP resources, and the
lean_verifyrepairs.
Filing contract work into arXMCP would bury it under 300 issues and perturb a pipeline built for a different track structure. Splitting it across both repos this early means neither milestone shows real progress and every dependency is a cross-repo link.
All contract work, both repos' worth, is filed on
chris-dare-dev/bridgeland-stab-lean.
- arXMCP's label taxonomy is mirrored verbatim onto this repo
(
type:*,sev:*,area:*,gate:*,epic,cross-repo,blocked,parked,agent-ready) so issues read the same in both places and can be transferred without relabelling. - Work that lands in arXMCP's tree carries the
cross-repolabel, and its body names the target repo and file paths in the first line. - Epics follow arXMCP's convention exactly: title
contract-v1-e<N>: <Title>, theepiclabel, a milestone, and a trailing<!-- roadmap-gh: contract-v1/contract-v1-e<N> -->marker. -
.claude/roadmap/contract-v1.yamlis the local source of truth and mirrors arXMCP'splans/*/roadmap.yamlschema, so one parser reads both.
Un-park trigger. Split the tracker when either holds:
- arXMCP's share exceeds ~15 open
cross-repoissues, or - a second topic repo adopts the contract — at which point cross-repo issues belong in the contract repo, not in any one topic's tracker.
Until then, one place.
Good. One backlog, one milestone burndown, one place to look. arXMCP's roadmap machinery is untouched, so nothing there needs to learn about a track it does not own.
Cost. cross-repo issues are filed where they cannot be closed by a commit —
GitHub will not auto-close them from an arXMCP push, so they must be closed by
hand with the arXMCP commit SHA in the closing comment. Accepted: ~10 issues.
This ADR does not bind arXMCP. If the contract work there grows its own
plan track (arXMCP/plans/formal-contract/), that track's roadmap is
authoritative for arXMCP's half and this ADR's trigger 1 has fired.
Exported from .claude/decisions/ADR-0006-issue-localization.md at the commit that removed it from the tree.
Architecture
- Canonical roots and specialization trees
- Structural cutover ledger
- Generalization backlog
- Dependency direction
- Loop-engineering friction log
- Mathematical ownership and abstraction boundarie
- Declaration placement
- When a proposition-valued class is justified
- Enhanced spherical twists: conventions and remai
- Verification history
CI and runners
- Bounded audit batching probe, 2026-09-27
- CI1.10: audit and exception record contention, 2
- Proposed hosted-only CI cutover for CI1.07
- Mac VM runners
- Owner CI lane: self-hosted runners in a private
- CI performance baseline, 2026-09-27
- CI1.07 exact-tree Ubuntu routing sample, 2026-09
- Ubuntu workstation runners (historical topology)
Decision records
- ADR-0001 — The seam is cold: files, not runtime (superseded)
- ADR-0002 — Identity is minted in the topic repo, (superseded)
- ADR-0003 — Elaboration and axiom evidence is pro (superseded)
- ADR-0004 — The statement registry lives in the t (superseded)
- ADR-0005 — Seven axes, four values, no aggregate (superseded)
- ADR-0006 — All contract issues are filed on `bri (superseded)
- ADR-0007 — Where the contract package lives (superseded)
-
ADR-0008 —
@[cites]ships as a shared Lake dep (superseded) - ADR-0009 — The contract package lives with the e (superseded)
- ADR-0010 — How a dg category is encoded, and whe
- ADR-0011 — Hom-complexes are complexes of abelia
- ADR-0012 — One Mathlib-style source root
- ADR-0013 — Own reusable moduli infrastructure in
- ADR-0014 — Stacks, algebraic spaces and moduli:
Roadmaps