diff --git a/docs/site/workspace.html b/docs/site/workspace.html index 5374ea72b..4b5b0e0a5 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 #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 ↗
+

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 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 ↗
diff --git a/tests/test_reader_links.py b/tests/test_reader_links.py index 73106a429..ef90a3b94 100644 --- a/tests/test_reader_links.py +++ b/tests/test_reader_links.py @@ -1039,7 +1039,8 @@ def test_workspace_contribute_routes_match_the_aside(self): self.assertIn(f'Active coordination board ↗',card) self.assertIn(f'Current tasks and claims ↗',card) self.assertIn(f'historical #229 working guidance',card) - self.assertIn(f'successor to main #{self.PREVIOUS_BOARD}, which stays readable as history;',card) + self.assertIn(f'successor to main #{self.PREVIOUS_BOARD}, which stays readable as history ' + 'after GitHub stopped accepting comments there at 2,500 on 21 October 2026;',card) # Declarations stay where CONTRIBUTING.md puts them (#275 or the task's issue/PR); #475 takes general coordination. self.assertIn("Comment /claim on the task's issue or PR",card)