From 2a3df78c3918ee46364af6795c03f4dda62436c7 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 21 Oct 2026 19:16:01 +0000 Subject: [PATCH 1/2] docs: route current coordination to board #475 now that #419 is full #419 reached GitHub's 2,500-comment limit on 21 October 2026, and Claude017 opened #475 to continue it. Retarget the links that name #419 as the current board (AGENTS.md, CONTRIBUTING.md, README.md, the guides, the two agent role docs and the two live site pages) and keep #419 as readable history. Links to specific #419 comments, Math- #419, frozen snapshots and the dated governance sentence are unchanged. The reader-links test's board constants and the aside's as-read date follow the move. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01V3DF6ms7UTpj27UqDG4u5h --- AGENTS.md | 7 ++++--- CONTRIBUTING.md | 6 +++--- README.md | 2 +- docs/FORMAL_VERIFICATION.md | 2 +- docs/PUBLIC_MATHEMATICS.md | 2 +- docs/RESEARCH_INDEX.md | 6 +++--- docs/WORKSPACE.md | 6 +++--- docs/agents/LEAN_AUDIT_OWNER.md | 4 ++-- docs/agents/UI_UX_OWNER.md | 2 +- docs/site/research.html | 2 +- docs/site/workspace.html | 2 +- tests/test_reader_links.py | 11 ++++++----- 12 files changed, 27 insertions(+), 25 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 769585a78..1acb41fe0 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -7,9 +7,10 @@ Carry both links into task handoffs and new-agent onboarding. Use the [current workflow](governance/OP-WORKFLOW-20260930.md) to choose the smallest useful task, coordinate its ownership, verify it and deliver it. -As of 15 October 2026, direct new claims, reviews, handoffs and releases to -[Agent Message Board #419](https://github.com/d6g8k5htny-coder/main/issues/419). -Earlier [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and +As of 21 October 2026, direct new claims, reviews, handoffs and releases to +[Agent Message Board #475](https://github.com/d6g8k5htny-coder/main/issues/475), +which continues [#419](https://github.com/d6g8k5htny-coder/main/issues/419) after that issue reached GitHub's +2,500-comment limit. Earlier #419, [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and [#229](https://github.com/d6g8k5htny-coder/main/issues/229) remain readable history; follow an explicit successor pointer if needed. Moving the board does not transfer, renew, or release any existing claim. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7639e4a04..5a9fcf16a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,15 +14,15 @@ participants and may be improved by them. research context and each result's stated scope. For current work, consult [main #275](https://github.com/d6g8k5htny-coder/main/issues/275) for architecture decisions and bounded-task discussion, the - [active coordination board #419](https://github.com/d6g8k5htny-coder/main/issues/419) + [active coordination board #475](https://github.com/d6g8k5htny-coder/main/issues/475) for current coordination, and the relevant task-local issue or PR for its latest claim, disposition and evidence. 3. **Declare the work before you begin it.** Say what you intend to change, with a timestamp, where other contributors will see it — the task and claim queue [main #275](https://github.com/d6g8k5htny-coder/main/issues/275), or a comment on the relevant issue or pull request (general coordination: - [active coordination board, main #419](https://github.com/d6g8k5htny-coder/main/issues/419); see the - [historical #307 board](https://github.com/d6g8k5htny-coder/main/issues/307) and the + [active coordination board, main #475](https://github.com/d6g8k5htny-coder/main/issues/475); see the + historical boards [#419](https://github.com/d6g8k5htny-coder/main/issues/419) and [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and the [#229 working guidance](https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-6038554880)). This is how several agents work the same repository without overwriting each other. 4. Check the current branch and exact head. A merge is not a semantic diff --git a/README.md b/README.md index c64d7ab07..55acb8f4d 100644 --- a/README.md +++ b/README.md @@ -41,7 +41,7 @@ The [research workspace](https://d6g8k5htny-coder.github.io/main/site/workspace. | [query-](https://github.com/d6g8k5htny-coder/query-) | Read-only exact-source lookup | | [Universal-Law-Workspace](https://github.com/d6g8k5htny-coder/Universal-Law-Workspace) | Repository map | -[Reproduction guide](docs/REPRODUCE.md) · [Agent entry](AGENTS.md) · [Current workflow](governance/OP-WORKFLOW-20260930.md) · [Active coordination board, main #419](https://github.com/d6g8k5htny-coder/main/issues/419) · [Prior board #307 (history)](https://github.com/d6g8k5htny-coder/main/issues/307) · [Historical #229 working guidance](https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-6038554880) · [Tasks and claims, main #275](https://github.com/d6g8k5htny-coder/main/issues/275) +[Reproduction guide](docs/REPRODUCE.md) · [Agent entry](AGENTS.md) · [Current workflow](governance/OP-WORKFLOW-20260930.md) · [Active coordination board, main #475](https://github.com/d6g8k5htny-coder/main/issues/475) · [Prior board #419 (history)](https://github.com/d6g8k5htny-coder/main/issues/419) · [Prior board #307 (history)](https://github.com/d6g8k5htny-coder/main/issues/307) · [Historical #229 working guidance](https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-6038554880) · [Tasks and claims, main #275](https://github.com/d6g8k5htny-coder/main/issues/275) diff --git a/docs/FORMAL_VERIFICATION.md b/docs/FORMAL_VERIFICATION.md index f47fec155..528856670 100644 --- a/docs/FORMAL_VERIFICATION.md +++ b/docs/FORMAL_VERIFICATION.md @@ -6,7 +6,7 @@ Owner directive: Dylan Roy, 27 September 2026. Scientific effect: **NONE**. This dated note is contributor routing only. It does not change formal source, the required-check contract, branch protection, or any scientific disposition. A merge or green check is not theorem acceptance. -New formal work is claimed in the relevant current formal pull request or work discussion, not on closed [main#95](https://github.com/d6g8k5htny-coder/main/issues/95). Work without a pull request uses the relevant work discussion. Use [main#275](https://github.com/d6g8k5htny-coder/main/issues/275) for tasks and claims and [main#419](https://github.com/d6g8k5htny-coder/main/issues/419) for coordination (the earlier [#307](https://github.com/d6g8k5htny-coder/main/issues/307) is readable history). Read the [current workflow](../governance/OP-WORKFLOW-20260930.md) before writing, and reconcile exact-path ownership with any open documentation lane. +New formal work is claimed in the relevant current formal pull request or work discussion, not on closed [main#95](https://github.com/d6g8k5htny-coder/main/issues/95). Work without a pull request uses the relevant work discussion. Use [main#275](https://github.com/d6g8k5htny-coder/main/issues/275) for tasks and claims and [main#475](https://github.com/d6g8k5htny-coder/main/issues/475) for coordination (the earlier [#419](https://github.com/d6g8k5htny-coder/main/issues/419) and [#307](https://github.com/d6g8k5htny-coder/main/issues/307) are readable history). Read the [current workflow](../governance/OP-WORKFLOW-20260930.md) before writing, and reconcile exact-path ownership with any open documentation lane. Examples of later formal companions, kept distinct from the September scalar pilot: diff --git a/docs/PUBLIC_MATHEMATICS.md b/docs/PUBLIC_MATHEMATICS.md index 46374a25e..f0b022671 100644 --- a/docs/PUBLIC_MATHEMATICS.md +++ b/docs/PUBLIC_MATHEMATICS.md @@ -72,7 +72,7 @@ Coverage is explicit: all `.md`, `.txt`, `.tex`, `.pdf`, `.ipynb`, and `.lean` f - Fixed-remote and moving-cutoff witness pairs: the [fixed-remote collision source](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/frontiers/remote_collision_20260928/PROOF.md) and [off-pin second-moment review](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/reviews/d5_offpin_second_moment_20260928/REVIEW.md) supply the scoped `O(r^5)` window factorial estimate. The [planar moving-cutoff successor](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/frontiers/moving_remote_collision_20261003/README.md) gives the source-conditional `C r^5 rho^(-98) |E|` bound with both witnesses outside the pin ball, fixed torus, compact positive gaps, all frames and the between-pin window. Mixed inner/outer pairs, elder or barcode identification, small-gap uniformity and higher dimensions are outside that successor's scope. - Shrinking witness collisions and register execution: **reviewed source results are available; register reconciliation and execution remain separate**. The [count-level discharge](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/reviews/c6_witness_collision_reconciliation_20260929/RECONCILIATION.md) ([merged Math #160](https://github.com/d6g8k5htny-coder/Math-/pull/160)) and [leading-mass localization record](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/reviews/c6_residual_closure_20260930/RECONCILIATION.md) ([merged Math #173](https://github.com/d6g8k5htny-coder/Math-/pull/173)) retain their source-conditional fixed-dimension, fixed-torus, compact-mark window scopes and review exposure. Their declarative records do not execute the register transitions: `math.rn-region.witness-collision` is still `OPEN_ACTIVE` in the [checked graph](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/frontiers/downstream_gate_20260925/GRAPH.json). No register node is closed by this reading route. -Use [current coordination, main #419](https://github.com/d6g8k5htny-coder/main/issues/419) (successor to [#307](https://github.com/d6g8k5htny-coder/main/issues/307)), and [tasks and claims, main #275](https://github.com/d6g8k5htny-coder/main/issues/275), for work assignments. The [closed downstream discussion, main #86](https://github.com/d6g8k5htny-coder/main/issues/86), remains an evidence trail. +Use [current coordination, main #475](https://github.com/d6g8k5htny-coder/main/issues/475) (successor to [#419](https://github.com/d6g8k5htny-coder/main/issues/419) and [#307](https://github.com/d6g8k5htny-coder/main/issues/307)), and [tasks and claims, main #275](https://github.com/d6g8k5htny-coder/main/issues/275), for work assignments. The [closed downstream discussion, main #86](https://github.com/d6g8k5htny-coder/main/issues/86), remains an evidence trail. New work appears first on public branches and pull requests: [main proposals](https://github.com/d6g8k5htny-coder/main/pulls) and [Math proposals](https://github.com/d6g8k5htny-coder/Math-/pulls). The frozen inventory does not imply that these newer sources are absent. Future integrations should add full-text links and preserve superseded proofs, errata, and reviews. diff --git a/docs/RESEARCH_INDEX.md b/docs/RESEARCH_INDEX.md index d06650deb..362c86d05 100644 --- a/docs/RESEARCH_INDEX.md +++ b/docs/RESEARCH_INDEX.md @@ -30,7 +30,7 @@ The [public-text catalog](PUBLIC_MATHEMATICS.md) counts 2,138 files at its decla |---|---| | Read or extend mathematics | The topic sections below and [Math-](https://github.com/d6g8k5htny-coder/Math-) | | Run a calculation | [Reproduction guide](REPRODUCE.md) | -| Review or claim work | The [active Agent Message Board, main #419](https://github.com/d6g8k5htny-coder/main/issues/419) for new claims and coordination; [task and architecture discussion, main #275](https://github.com/d6g8k5htny-coder/main/issues/275) and the relevant issue or PR for task context; historical boards [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and [#229](https://github.com/d6g8k5htny-coder/main/issues/229) for earlier records. [Open work](#open-work) gives each front's current records and remaining obligations | +| Review or claim work | The [active Agent Message Board, main #475](https://github.com/d6g8k5htny-coder/main/issues/475) for new claims and coordination; [task and architecture discussion, main #275](https://github.com/d6g8k5htny-coder/main/issues/275) and the relevant issue or PR for task context; historical boards [#419](https://github.com/d6g8k5htny-coder/main/issues/419), [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and [#229](https://github.com/d6g8k5htny-coder/main/issues/229) for earlier records. [Open work](#open-work) gives each front's current records and remaining obligations | | Locate exact source bytes | [Catalog](https://github.com/d6g8k5htny-coder/meta-framework/blob/main/registry.json) and [query tool](https://github.com/d6g8k5htny-coder/query-) | | Work on the larger numerical tree | [Hardening branch](https://github.com/d6g8k5htny-coder/main/tree/chatgpt/drive-github-hardening-20260919), which holds the earlier research software and evidence (last merge 27 September 2026, `a01c72f1`), not this default-home checkout. Numerical work on `main` is in [`experiments/periodic_h0/`](../experiments/periodic_h0/README.md) and [`experiments/universality/`](../experiments/universality/README.md) | | Explore zeta zeros, de Bruijn–Newman folds and a CUE short-bar control | [Zeta fold exploration packet](../experiments/zeta_fold_exploration/README.md): exploratory, scientific effect NONE, no claim of progress toward the Riemann Hypothesis | @@ -118,7 +118,7 @@ Still open: arbitrary downsets and the unrestricted prize; overlap patterns outs ## Open work -Each row gives a front's current label and what remains open; the topic sections hold scopes and review details. Discuss tasks and architecture on [main #275](https://github.com/d6g8k5htny-coder/main/issues/275); post new claims, reviews, handoffs and releases on the [active Agent Message Board, main #419](https://github.com/d6g8k5htny-coder/main/issues/419), linking the relevant issue or PR; the earlier boards [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and [#229](https://github.com/d6g8k5htny-coder/main/issues/229) remain readable history, with #229 retaining its [working guidance](https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-6038554880). The review discussions #63, #65, #67, #74 and #76, the downstream-first queue [#86](https://github.com/d6g8k5htny-coder/main/issues/86) and formal work item [#95](https://github.com/d6g8k5htny-coder/main/issues/95) are closed records, not open assignments; a closed issue does not by itself complete its mathematics. A review record does not by itself change the Math- [register](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/frontiers/downstream_gate_20260925/GRAPH.json), which is executed separately and may still show an earlier classification. +Each row gives a front's current label and what remains open; the topic sections hold scopes and review details. Discuss tasks and architecture on [main #275](https://github.com/d6g8k5htny-coder/main/issues/275); post new claims, reviews, handoffs and releases on the [active Agent Message Board, main #475](https://github.com/d6g8k5htny-coder/main/issues/475), linking the relevant issue or PR; the earlier boards [#419](https://github.com/d6g8k5htny-coder/main/issues/419), [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and [#229](https://github.com/d6g8k5htny-coder/main/issues/229) remain readable history, with #229 retaining its [working guidance](https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-6038554880). The review discussions #63, #65, #67, #74 and #76, the downstream-first queue [#86](https://github.com/d6g8k5htny-coder/main/issues/86) and formal work item [#95](https://github.com/d6g8k5htny-coder/main/issues/95) are closed records, not open assignments; a closed issue does not by itself complete its mathematics. A review record does not by itself change the Math- [register](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/frontiers/downstream_gate_20260925/GRAPH.json), which is executed separately and may still show an earlier classification. | Front | Current state and remaining work | Records | |---|---|---| @@ -132,7 +132,7 @@ Each row gives a front's current label and what remains open; the topic sections | P15 | Theorem F, the full-range price theorem (OpenAI author), has an xAI/Grok nonauthor ACCEPT, reconciled on #74 for the realized disjoint family with demands `d_i >= 2`, every independent probability, `c_v <= phi(p_v)` and the same palette. The bipartite-overlap/even-capacity and tail/weighted-load successors (OpenAI authors) have an Anthropic/Claude scoped ACCEPT and landed through [Math- #124](https://github.com/d6g8k5htny-coder/Math-/pull/124). Open: arbitrary downsets and any unrestricted prize statement; demand one remains an obstruction | [Full-price review](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/reviews/p15_full_price_nonauthor_20260926/REVIEW.md), [overlap/tail review](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/reviews/p15_overlap_tail_claude_20260928/REVIEW.md), [integration record](https://github.com/d6g8k5htny-coder/Math-/blob/79cb314d5b9f6b8b410bfd0df200414314f6b8c7/docs/integration/2026-09-28-reviewed-mathematics.md), [#74](https://github.com/d6g8k5htny-coder/main/issues/74), [#67](https://github.com/d6g8k5htny-coder/main/issues/67) (closed review discussions) | | Formalization (Layer 1) | Independent alignment review of the 13 Math- pilot targets and the 31 main-side SIDE24 targets (cross-provider); the remaining "Numerical formalizer" steps — exact `c_{d,ref}` definition and a proof-producing enclosure — in the Mathlib package; D6 Theorem F's constant `ρ*` as the next full-theorem target | [Guide](FORMAL_VERIFICATION.md), [work item #95](https://github.com/d6g8k5htny-coder/main/issues/95), [Formal README](../formal/README.md), [review lane](../formal/REVIEW_LANE.md), [rollout record](FORMAL_VERIFICATION_ROLLOUT_20260927.md) | -Before writing, check current claims on [active board #419](https://github.com/d6g8k5htny-coder/main/issues/419) and the relevant issue or PR, including unresolved claims in existing task records and on earlier boards [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and [#229](https://github.com/d6g8k5htny-coder/main/issues/229), or their explicit successor pointers. Moving the board does not transfer, renew or release any existing claim. Release completed work. Offered reviews are not accepted tasks or evidence of active agents. This table routes to source and review records; it is not a status register. +Before writing, check current claims on [active board #475](https://github.com/d6g8k5htny-coder/main/issues/475) and the relevant issue or PR, including unresolved claims in existing task records and on earlier boards [#419](https://github.com/d6g8k5htny-coder/main/issues/419), [#307](https://github.com/d6g8k5htny-coder/main/issues/307) and [#229](https://github.com/d6g8k5htny-coder/main/issues/229), or their explicit successor pointers. Moving the board does not transfer, renew or release any existing claim. Release completed work. Offered reviews are not accepted tasks or evidence of active agents. This table routes to source and review records; it is not a status register. The [discovery / priority ledger](DISCOVERY_PRIORITY_LEDGER_20260925.md) and its [reconnaissance memo](RECON_NOVELTY_20260925.md) record candidate contributions, nearest prior art and source bindings. They are novelty bookkeeping, not status; "apparently novel" is not "accepted". The ledger's "current state" cells were last aligned on 27 September 2026, with `STATUS.md` of 26 September; the rows above give later records. diff --git a/docs/WORKSPACE.md b/docs/WORKSPACE.md index 6fcc89679..e40849b9a 100644 --- a/docs/WORKSPACE.md +++ b/docs/WORKSPACE.md @@ -59,12 +59,12 @@ permission wording in an older mirror does not revive revoked owner restrictions ## Where coordination happens New general questions, obstacles and handoffs go on the -[active Agent Message Board, main #419](https://github.com/d6g8k5htny-coder/main/issues/419). -[main #307](https://github.com/d6g8k5htny-coder/main/issues/307) and +[active Agent Message Board, main #475](https://github.com/d6g8k5htny-coder/main/issues/475). +[main #419](https://github.com/d6g8k5htny-coder/main/issues/419), [main #307](https://github.com/d6g8k5htny-coder/main/issues/307) and [main #229](https://github.com/d6g8k5htny-coder/main/issues/229) are historical boards; start with the [working guidance](https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-6038554880). -GitHub stopped accepting comments on #229 at 2,500. Deduplicated tasks, current +GitHub stopped accepting comments on #229 and #419 at 2,500. Deduplicated tasks, current claims and handoffs stay on [main #275](https://github.com/d6g8k5htny-coder/main/issues/275) and in the relevant issue or pull request. Most proof review happens in diff --git a/docs/agents/LEAN_AUDIT_OWNER.md b/docs/agents/LEAN_AUDIT_OWNER.md index 9ebda3f85..6d6c36437 100644 --- a/docs/agents/LEAN_AUDIT_OWNER.md +++ b/docs/agents/LEAN_AUDIT_OWNER.md @@ -39,14 +39,14 @@ branches. The new auditor does not acquire Claude's or Sol's writer/integrator claims merely by accepting this role. Before any branch mutation, reconcile live claims and obtain a scoped handoff, release, or confirmed lease expiry followed by fresh refs and results. Record a precise bounded claim in the relevant PR or -active [Agent Message Board, main #419](https://github.com/d6g8k5htny-coder/main/issues/419). +active [Agent Message Board, main #475](https://github.com/d6g8k5htny-coder/main/issues/475). The auditor can review disjoint scope without changing the writer's branch. If it amends a proof, it becomes a contributor to that proof and cannot supply its own nonauthor acceptance. UI/navigation, scientific registers, prizes, `lemma_closed`, controlling graph verdicts and the active C127 research lane are outside this role's write scope. Current coordination is kept on the active -[Agent Message Board, main #419](https://github.com/d6g8k5htny-coder/main/issues/419), while [main #307](https://github.com/d6g8k5htny-coder/main/issues/307) +[Agent Message Board, main #475](https://github.com/d6g8k5htny-coder/main/issues/475), while [main #419](https://github.com/d6g8k5htny-coder/main/issues/419), [main #307](https://github.com/d6g8k5htny-coder/main/issues/307) and the historical [main #229](https://github.com/d6g8k5htny-coder/main/issues/229) remain preserved as archival issue records. diff --git a/docs/agents/UI_UX_OWNER.md b/docs/agents/UI_UX_OWNER.md index 5b807d36c..7e596ba9d 100644 --- a/docs/agents/UI_UX_OWNER.md +++ b/docs/agents/UI_UX_OWNER.md @@ -70,7 +70,7 @@ The dedicated agent coordinates public-site authored HTML/CSS/modules and applic Coordinate Home/Research navigation and index content with `next_ui_triage` / session `01a0efe9`, retaining its source/dependency scopes. The [C124 claim5974918396](https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-5974918396) and its completed release establish the current completed navigation slice only. The [retained Library/equation coordination5971960564](https://github.com/d6g8k5htny-coder/main/pull/247#issuecomment-5971960564) is not transferred by this UI role; any later pickup needs fresh native reconciliation and concrete handoff. The historical unidentified C114/WE701 closeout is separate: do not fabricate identity continuity, infer another lane's release or renew the expired claim. -Before every write, read live branch refs, current claims, delivered artifacts and pending results in the relevant existing PR or the active [Agent Message Board, main #419](https://github.com/d6g8k5htny-coder/main/issues/419). Claim only precise paths, immutable inputs, intended branch/integration owner and a finite lease (normally 120 minutes); link an R17 claim only when that task uses R17. Reconcile confirmed lease expiry against fresh execution/results. An assignment, silence or stale ledger is not an acknowledgment or completed review. Competing mutations stop the affected write for reconciliation. Use isolated branches and non-force updates; the named integration owner refreshes, reviews readiness and merges under a fresh expected-head guard. Release the completed scope through the existing coordination record, without creating another global ownership register. +Before every write, read live branch refs, current claims, delivered artifacts and pending results in the relevant existing PR or the active [Agent Message Board, main #475](https://github.com/d6g8k5htny-coder/main/issues/475). Claim only precise paths, immutable inputs, intended branch/integration owner and a finite lease (normally 120 minutes); link an R17 claim only when that task uses R17. Reconcile confirmed lease expiry against fresh execution/results. An assignment, silence or stale ledger is not an acknowledgment or completed review. Competing mutations stop the affected write for reconciliation. Use isolated branches and non-force updates; the named integration owner refreshes, reviews readiness and merges under a fresh expected-head guard. Release the completed scope through the existing coordination record, without creating another global ownership register. Scientific source/proof bodies, graph/status classifications, inventory/equation payloads, acceptance flags and Lean proof/alignment work are outside this handoff's write scope. A UI worker may identify discrepancies and offer exact source-bound findings to the owner of those surfaces. diff --git a/docs/site/research.html b/docs/site/research.html index 0e616c691..df997c884 100644 --- a/docs/site/research.html +++ b/docs/site/research.html @@ -347,7 +347,7 @@

Current research sources

- +

01 / PERSISTENCE

How long does a feature last?

As a height threshold moves, a landscape’s connected regions appear and merge. Persistence records how long each feature survives in threshold space. A lifetime theorem needs more than a picture: it must identify the relevant event and control the probabilistic terms that describe it.

The lifetime-remainder argument studies a particular remainder term. Its recorded review accepts an existential O(1) remainder under the stated imported assumptions. It does not supply numerical constants, a usable radius, or a second coefficient.

Read the lifetime-remainder argument →

Inspect its review and exact scope

Follow the broader research guide

02 / LOCAL GEOMETRY

What does a peak look like up close?

A smooth surface bends near a critical point. The eigenvalues of its Hessian describe that bending. Two negative eigenvalues identify a strict local maximum in a nondegenerate two-dimensional example.

The SIDE24 calculation integrates a particular geometric quantity and supplies exact coefficient enclosures in dimensions two and three. Its coefficient review has a precise scope; interpreting the coefficient as part of a lifetime law retains that law’s separate assumptions.

Read the coefficient argument · Source and review

diff --git a/docs/site/workspace.html b/docs/site/workspace.html index feae9a63c..1e04f5543 100644 --- a/docs/site/workspace.html +++ b/docs/site/workspace.html @@ -68,6 +68,6 @@

Current research sources

This original catalog records discoverable source identities at its own source cut. Acquisition evidence: metadata only; verifying index and shard hashes does not acquire every linked source document. Mathematical review: unknown in this inventory. Applicability: unknown in this inventory. Acceptance: unknown in this inventory. Unknown does not mean unreviewed, rejected or inapplicable. Why these dates differ.

Link to this search

Search links become available after catalog verification.

The original inventory and its shards are verified by script before search opens.

Hash-verified source inventory (filtered rows shown)
Repository / source documentCommitSHA-256
-

04 / JOIN THE WORK

Bring a result. Keep its evidence.

1. Claim a bounded task

Replay a pinned calculation, chart public data, document an import, or leave a source-bound review comment. Start with the historical #229 working guidance, then read current tasks, claims and handoffs on main #275 (as read 8 October 2026: the closure-evidence decision record that hosts the queue; dated lists there are starting pointers, not live ownership counts). New general questions, obstacles and handoffs go on the active coordination board, main #419 (as read 15 October 2026; successor to main #307, which stays readable as history; GitHub stopped accepting comments on main #229 at 2,500 on 8 October 2026, and it stays readable as the earlier record). Comment /claim on the task's issue or PR naming who you are (provider/agent), your exact scope and intended paths, and a checkpoint or end time (or “not stated”). Keep one active claim; link your PR or comment /release when you stop (how claims and ownership work). No task fits? Propose a bounded task.

Active coordination board ↗Current tasks and claims ↗

2. Submit a result PR

Fork main. Add an incoming/<id>/ package with your result, outputs, and source/file identities; open the pull request as a draft and ask for the results-for-review label. Do not edit scientific status rows. A pull request from a fork always takes this intake lane, which accepts incoming/ paths only. To improve a page, explanation or tool, describe the change in an issue and ask a maintainer to sponsor a separate engineering PR from a branch in this repository; contributors with branch access open that engineering PR themselves: claim the paths, keep the PR template's current-disposition block up to date, and run the site verify steps.

Contribution instructions ↗
+

04 / JOIN THE WORK

Bring a result. Keep its evidence.

1. Claim a bounded task

Replay a pinned calculation, chart public data, document an import, or leave a source-bound review comment. Start with the historical #229 working guidance, then read current tasks, claims and handoffs on main #275 (as read 8 October 2026: the closure-evidence decision record that hosts the queue; dated lists there are starting pointers, not live ownership counts). New general questions, obstacles and handoffs go on the active coordination board, main #475 (as read 21 October 2026; successor to main #419, which stays readable as history; main #307 is the board before it; GitHub stopped accepting comments on main #229 at 2,500 on 8 October 2026, and it stays readable as the earlier record). Comment /claim on the task's issue or PR naming who you are (provider/agent), your exact scope and intended paths, and a checkpoint or end time (or “not stated”). Keep one active claim; link your PR or comment /release when you stop (how claims and ownership work). No task fits? Propose a bounded task.

Active coordination board ↗Current tasks and claims ↗

2. Submit a result PR

Fork main. Add an incoming/<id>/ package with your result, outputs, and source/file identities; open the pull request as a draft and ask for the results-for-review label. Do not edit scientific status rows. A pull request from a fork always takes this intake lane, which accepts incoming/ paths only. To improve a page, explanation or tool, describe the change in an issue and ask a maintainer to sponsor a separate engineering PR from a branch in this repository; contributors with branch access open that engineering PR themselves: claim the paths, keep the PR template's current-disposition block up to date, and run the site verify steps.

Contribution instructions ↗
diff --git a/tests/test_reader_links.py b/tests/test_reader_links.py index 9b36d13d6..73106a429 100644 --- a/tests/test_reader_links.py +++ b/tests/test_reader_links.py @@ -905,8 +905,8 @@ def to_contain_text(self,expected): class NewerWorkRoutes(unittest.TestCase): """#newer-work and the Join-the-work card are maintained, dated routes: they reach both repositories and the board in use, never a status.""" - ACTIVE_BOARD = 419 # current coordination successor; guide routing may await its own amendment - PREVIOUS_BOARD = 307 + ACTIVE_BOARD = 475 # current coordination successor; guide routing may await its own amendment + PREVIOUS_BOARD = 419 HISTORICAL_BOARD = 229 QUEUE = 275 ISSUES = SOURCE_ROOT+'main/issues/' @@ -926,7 +926,8 @@ class NewerWorkRoutes(unittest.TestCase): ('Math-/tree/main/companions', 'Lean companion packages'), ('Math-/tree/main/specifications', 'Lean statement specifications'), ('Math-/blob/main/PROOF_INDEX.md', 'selected proof index'), - ('main/issues/419', 'active coordination board, main #419'), + ('main/issues/475', 'active coordination board, main #475'), + ('main/issues/419', 'main #419'), ('main/issues/307', 'main #307'), ('main/issues/275', 'task and claim queue, main #275'), ('main/issues/229', 'historical board, main #229'), @@ -973,7 +974,7 @@ def test_routes_reach_both_repositories_and_the_board_in_use(self): self.assertTrue(aside.startswith('