From 050af8f444e826b9329a9057f4af637b42e68edb Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 26 Oct 2026 19:40:38 +0000 Subject: [PATCH 1/3] docs: route tasks and claims to #619 and architecture to #666 (#275 option B) Dylan chose option B for #275 and placed its roles on 26 October: tasks-and-claims routes go to the active board #619, and the architecture decision discussion continues on the new #666. This repoints the operative #275 routes in nine of the eleven files listed by the routing check. The decision-record citation in WORKSPACE stays. FORMAL_VERIFICATION's coordination route moves from #475 to #619 in the same line. formal/README.md and formal/REVIEW_LANE.md are hash-pinned in formal/manifest.json, which #631 also changes, so they follow in a separate change after #631 lands. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01V3DF6ms7UTpj27UqDG4u5h --- CONTRIBUTING.md | 14 +++++++------- README.md | 2 +- docs/FORMAL_VERIFICATION.md | 4 ++-- docs/PUBLIC_MATHEMATICS.md | 2 +- docs/RESEARCH_INDEX.md | 4 ++-- docs/WORKSPACE.md | 7 ++++--- docs/site/research.html | 2 +- docs/site/workspace.html | 2 +- tests/test_reader_links.py | 12 ++++++------ 9 files changed, 25 insertions(+), 24 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 237a0fe40..f2a412eb4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -12,16 +12,16 @@ participants and may be improved by them. only points there. 2. Read the [research guide](docs/RESEARCH_INDEX.md) for source-linked 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 + [main #666](https://github.com/d6g8k5htny-coder/main/issues/666) (continued from [#275](https://github.com/d6g8k5htny-coder/main/issues/275)) for + architecture decisions, the [active coordination board #619](https://github.com/d6g8k5htny-coder/main/issues/619) (continued from [#539](https://github.com/d6g8k5htny-coder/main/issues/539), which continued from [#475](https://github.com/d6g8k5htny-coder/main/issues/475) and [#419](https://github.com/d6g8k5htny-coder/main/issues/419)) - for current coordination, and the relevant task-local issue or PR for its + for current coordination and bounded-task discussion, 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 + a timestamp, where other contributors will see it — the task and claim queue on the + [active coordination board, main #619](https://github.com/d6g8k5htny-coder/main/issues/619), or a comment on the relevant issue or pull request (general coordination: [active coordination board, main #619](https://github.com/d6g8k5htny-coder/main/issues/619); see the [prior #539 board](https://github.com/d6g8k5htny-coder/main/issues/539), the @@ -37,7 +37,7 @@ participants and may be improved by them. Use [public tasks](https://github.com/d6g8k5htny-coder/main/issues?q=is%3Aissue+is%3Aopen+label%3Aeng-only) (none open on 7 October 2026), the -[current task and claim queue](https://github.com/d6g8k5htny-coder/main/issues/275) +[current task and claim queue, main #619](https://github.com/d6g8k5htny-coder/main/issues/619) or [propose a bounded task](https://github.com/d6g8k5htny-coder/main/issues/new?template=task.yml). The starter types are `replay`, `chart`, `review-comment`, `catalog-stub`, and `docs`. Cite the existing key, public path, full commit and digest from @@ -167,7 +167,7 @@ back regardless of how good the result looks. Read the [formal-verification guide](docs/FORMAL_VERIFICATION.md) first and claim work in the relevant formal pull request; use -[main #275](https://github.com/d6g8k5htny-coder/main/issues/275) to find current +[active coordination board, main #619](https://github.com/d6g8k5htny-coder/main/issues/619) to find current tasks and link that claim when coordination requires it. [#95](https://github.com/d6g8k5htny-coder/main/issues/95) is closed formal-rollout history. The diff --git a/README.md b/README.md index 9a770bbe7..13374d2b7 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 #619](https://github.com/d6g8k5htny-coder/main/issues/619) · [Prior board #539 (history)](https://github.com/d6g8k5htny-coder/main/issues/539) · [Prior board #475 (history)](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) +[Reproduction guide](docs/REPRODUCE.md) · [Agent entry](AGENTS.md) · [Current workflow](governance/OP-WORKFLOW-20260930.md) · [Active coordination board, main #619](https://github.com/d6g8k5htny-coder/main/issues/619) · [Prior board #539 (history)](https://github.com/d6g8k5htny-coder/main/issues/539) · [Prior board #475 (history)](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) · [Architecture discussion, main #666](https://github.com/d6g8k5htny-coder/main/issues/666) · [Closure-evidence decision record, main #275](https://github.com/d6g8k5htny-coder/main/issues/275) diff --git a/docs/FORMAL_VERIFICATION.md b/docs/FORMAL_VERIFICATION.md index 528856670..638db13e3 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#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. +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#619](https://github.com/d6g8k5htny-coder/main/issues/619) for tasks, claims and coordination and [main#666](https://github.com/d6g8k5htny-coder/main/issues/666) for architecture discussion (the earlier boards [#539](https://github.com/d6g8k5htny-coder/main/issues/539), [#475](https://github.com/d6g8k5htny-coder/main/issues/475), [#419](https://github.com/d6g8k5htny-coder/main/issues/419) and [#307](https://github.com/d6g8k5htny-coder/main/issues/307), and the decision record [#275](https://github.com/d6g8k5htny-coder/main/issues/275), 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: @@ -53,7 +53,7 @@ The controls include false fold and power inequalities, a `sorry` proof, an indi ## Historical standing instructions (September 2026 pilot) -The following offer table is retained as the September pilot record. It is not the current claim route. Current claim route: the relevant current formal pull request or work discussion, with tasks and claims on main#275 and coordination on main#419 (successor to main#307). Closed #95 and Math- PR92 remain the historical pilot references used to avoid rewriting that record. +The following offer table is retained as the September pilot record. It is not the current claim route. Current claim route: the relevant current formal pull request or work discussion, with tasks, claims and coordination on main#619 (successor to main#539, main#475, main#419 and main#307). Closed #95 and Math- PR92 remain the historical pilot references used to avoid rewriting that record. Use #95 and PR92 to claim work and avoid duplicate writers. The OpenAI implementation author does not supply independent review credit. Read the exact head before reviewing; changed source, scope or dependencies invalidate the prior alignment record. diff --git a/docs/PUBLIC_MATHEMATICS.md b/docs/PUBLIC_MATHEMATICS.md index f361a3c03..dc85ff2b3 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 #619](https://github.com/d6g8k5htny-coder/main/issues/619) (successor to [#539](https://github.com/d6g8k5htny-coder/main/issues/539), [#475](https://github.com/d6g8k5htny-coder/main/issues/475), [#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. +Use [current coordination, main #619](https://github.com/d6g8k5htny-coder/main/issues/619) (successor to [#539](https://github.com/d6g8k5htny-coder/main/issues/539), [#475](https://github.com/d6g8k5htny-coder/main/issues/475), [#419](https://github.com/d6g8k5htny-coder/main/issues/419) and [#307](https://github.com/d6g8k5htny-coder/main/issues/307)), for tasks, claims and work assignments, and [architecture discussion, main #666](https://github.com/d6g8k5htny-coder/main/issues/666) (continued from [#275](https://github.com/d6g8k5htny-coder/main/issues/275)). 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 a6876a281..4420e1447 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 #619](https://github.com/d6g8k5htny-coder/main/issues/619) 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 [#539](https://github.com/d6g8k5htny-coder/main/issues/539), [#475](https://github.com/d6g8k5htny-coder/main/issues/475), [#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 | +| Review or claim work | The [active Agent Message Board, main #619](https://github.com/d6g8k5htny-coder/main/issues/619) for new claims, tasks and coordination; [architecture discussion, main #666](https://github.com/d6g8k5htny-coder/main/issues/666) (continued from [#275](https://github.com/d6g8k5htny-coder/main/issues/275)) and the relevant issue or PR for task context; historical boards [#539](https://github.com/d6g8k5htny-coder/main/issues/539), [#475](https://github.com/d6g8k5htny-coder/main/issues/475), [#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 #619](https://github.com/d6g8k5htny-coder/main/issues/619), linking the relevant issue or PR; the earlier boards [#539](https://github.com/d6g8k5htny-coder/main/issues/539), [#475](https://github.com/d6g8k5htny-coder/main/issues/475), [#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. +Each row gives a front's current label and what remains open; the topic sections hold scopes and review details. Discuss architecture on [main #666](https://github.com/d6g8k5htny-coder/main/issues/666) (continued from [#275](https://github.com/d6g8k5htny-coder/main/issues/275)); discuss tasks and post new claims, reviews, handoffs and releases on the [active Agent Message Board, main #619](https://github.com/d6g8k5htny-coder/main/issues/619), linking the relevant issue or PR; the earlier boards [#539](https://github.com/d6g8k5htny-coder/main/issues/539), [#475](https://github.com/d6g8k5htny-coder/main/issues/475), [#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 | |---|---|---| diff --git a/docs/WORKSPACE.md b/docs/WORKSPACE.md index 15271e972..29ca4cd4f 100644 --- a/docs/WORKSPACE.md +++ b/docs/WORKSPACE.md @@ -68,9 +68,10 @@ New general questions, obstacles and handoffs go on the 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 -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 +claims and handoffs go to the +[active coordination board, main #619](https://github.com/d6g8k5htny-coder/main/issues/619) and the relevant +issue or pull request; architecture discussion continues on +[main #666](https://github.com/d6g8k5htny-coder/main/issues/666) (continued from [#275](https://github.com/d6g8k5htny-coder/main/issues/275)). Most proof review happens in [Math- pull requests](https://github.com/d6g8k5htny-coder/Math-/pulls). Dated queue lists in these threads are starting pointers, not live ownership counts; neither thread is a scientific-status register, a permanent ownership register or a lock. diff --git a/docs/site/research.html b/docs/site/research.html index 6871f039b..848e042bc 100644 --- a/docs/site/research.html +++ b/docs/site/research.html @@ -368,7 +368,7 @@

Source observation

- +

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.

See the idea in a minuteCount bars into a density (synthetic example)

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.

Shape a peakInspect exact coefficients

Read the coefficient argument · Source and review

diff --git a/docs/site/workspace.html b/docs/site/workspace.html index cd1899aa8..9b5e15338 100644 --- a/docs/site/workspace.html +++ b/docs/site/workspace.html @@ -94,6 +94,6 @@

Source observation

Pinned source bytes are verified by script before the endpoints are shown.

Exact lower endpoint
—
Exact upper endpoint
—
Reference cone moment
—
Approximate display only. Bar lengths use binary floating point; the exact endpoints remain visible at left. The enclosure width is too small to show at this scale.

This engineering-only coefficient exhibit retains the artifact’s original scientific_acceptance: false. Read the later scoped coefficient review and its limits separately. The parent theorem’s open dependencies remain open.

Source identity and method
-

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 #619 (as read 26 October 2026; successor to main #539, which remains readable history after reaching the comment limit; before it, main #475, main #419, which stays readable as history after GitHub stopped accepting comments there at 2,500 on 21 October 2026; 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 ↗
+

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 the active coordination board and in each task's issue or PR, and take architecture questions to main #666 (as read 26 October 2026: it continues the architecture role of main #275, the closure-evidence decision record; dated lists on the boards are starting pointers, not live ownership counts). New general questions, obstacles and handoffs go on the active coordination board, main #619 (as read 26 October 2026; successor to main #539, which remains readable history after reaching the comment limit; before it, main #475, main #419, which stays readable as history after GitHub stopped accepting comments there at 2,500 on 21 October 2026; 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 ↗Architecture discussion ↗

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 cc45be0da..184b46092 100644 --- a/tests/test_reader_links.py +++ b/tests/test_reader_links.py @@ -942,7 +942,7 @@ class NewerWorkRoutes(unittest.TestCase): ACTIVE_BOARD = 619 # current coordination successor; guide routing may await its own amendment PREVIOUS_BOARD = 539 HISTORICAL_BOARD = 229 - QUEUE = 275 + ARCHITECTURE = 666 # architecture discussion, continued from #275 (option B, 26 October) ISSUES = SOURCE_ROOT+'main/issues/' AS_READ = r'as read \d{1,2} (?:January|February|March|April|May|June|July|August|September|October|November|December) 20\d\d' # The aside's routes in reading order, each with its exact name; a renamed or reordered route is a deliberate edit here. @@ -965,7 +965,7 @@ class NewerWorkRoutes(unittest.TestCase): ('main/issues/475', 'main #475'), ('main/issues/419', 'main #419'), ('main/issues/307', 'main #307'), - ('main/issues/275', 'task and claim queue, main #275'), + ('main/issues/666', 'architecture discussion, main #666'), ('main/issues/229', 'historical board, main #229'), ('main/blob/main/CONTRIBUTING.md', 'contribution guide'), ('meta-framework/blob/main/registry.json', 'current curated catalog'), @@ -1005,7 +1005,7 @@ def is_historical_board(self, href): def test_routes_reach_both_repositories_and_the_board_in_use(self): aside=self.aside() self.assertEqual(self.anchors(aside),[(SOURCE_ROOT+href,name) for href,name in self.ROUTES]) - for n in (self.ACTIVE_BOARD,self.QUEUE,self.HISTORICAL_BOARD): + for n in (self.ACTIVE_BOARD,self.ARCHITECTURE,self.HISTORICAL_BOARD): with self.subTest(issue=n):self.assertIn(f'main/issues/{n}',[href for href,_ in self.ROUTES]) self.assertTrue(aside.startswith('