Skip to content

docs(missions): wall backlog map -- 25 unproved nodes mapped, and the grant-gate hole that #569 closes - #574

Merged
DrMurphyIsIn merged 2 commits into
mainfrom
wall/backlogmap
Sep 19, 2026
Merged

DrMurphyIsIn merged 2 commits into
mainfrom
wall/backlogmap

Conversation

@DrMurphyIsIn

Copy link
Copy Markdown
Owner

Every not-proved node across all four campaigns (25: rh 6, mirrormere 9, anduril 4, bg 6) mapped onto the wall-assault facets, one table row each, plus 14 concrete registry operations and three registry-health answers.

The health finding that matters, and it was demonstrated rather than inferred. The grant gate could mark a node proved on a false premise. On a throwaway probe campaign, a node whose registered statement was RiemannHypothesis was granted proved with closure_clean = true from an artifact whose only proof was sorry, while its declared dependency sat at draft, and mission verify reported OK with zero errors.

I confirmed the mechanism independently: normalize_lean strips a trailing := by sorry before comparing, so a stub's normalized text is the bare statement and containment passes. #569 (merged) closes it by rejecting sorry / admit / native_decide in artifact code, comments and strings stripped first. I tested the fixed gate against a fake proof of the conjecture: rejected.

Two further health findings, recorded with root causes rather than patched blind:

  • Five nodes carry dependency edges the corpus does not support. The root cause is structural: there is no cross-campaign edge mechanism, so authors substitute a same-campaign proxy while the honest title names the real source. The D3 node is the named exemplar and is still unfixed on its branch.
  • Proof links are 44 of 44 via = direct; the reduction mechanism has zero instances across all four campaigns. The registry supports a reduction relation that nothing uses.

Docs only; no registry file touched by this PR. conjecture1_proved = False.

🤖 Generated with Claude Code

Dr. Murphy and others added 2 commits September 19, 2026 00:11
Maps every not-proved node across rh/mirrormere/anduril/bg onto six facets
cut along the uniformity-vs-instance seam, with a verdict per node.

Headline finding (registry health question c), demonstrated with a throwaway
probe campaign rather than inferred: the grant gate can mark a node proved on
a false premise. A node whose registered statement is RiemannHypothesis was
granted proved with closure_clean=true off an artifact proved by `sorry`,
while its declared dependency sat at draft -- and `mission verify` reported OK
with zero errors and zero warnings. Three composing defects:
  G1 grant_status decides by normalized text containment only; normalize_lean
     strips a trailing sorry with a $-anchored regex, so a sorry-carrying
     artifact matches by design. The right checker already exists
     (telperion audit, cli.py:635) and the gate never calls it.
  G2 grant_status never inspects depends_on; dep-awareness lives only in
     open_leaves, a scheduling query, not a gate.
  G3 closure_clean is recomputed only for via="reduction"; 44 of 44 live proof
     links are via="direct", so the cascade guard has never run on a real node.
     Nothing errors on a proved node with closure_clean=false either.
Fixes R11-R14 proposed in priority order; R11 is a call into existing code.

Also: 5 nodes whose deps claim what the corpus does not support (the D3
exemplar is still unfixed on its branch; RH_bl_explicit_formula's title
refutes both its own edges), root-caused to the absence of any cross-campaign
edge mechanism; 2 genuinely stale drafts (MM_torus_section_dictionary blocks
an open node and replaced a statement caught as trivially rfl, never
re-audited); and the structural gap that facet F1 rests on facet F2, which
has one registered node.

No Lean built, no node status changed, no registry file touched.
conjecture1_proved = False

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@DrMurphyIsIn
DrMurphyIsIn merged commit c22ca1e into main Sep 19, 2026
100 of 101 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant