Skip to content
2 changes: 1 addition & 1 deletion docs/site/workspace.html
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,6 @@ <h2>Current research sources</h2>
<p id="catalog-acquisition-legend" class="inventory-legend">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. <a href="#current-date-explanation">Why these dates differ</a>.</p>
<div class="catalog-filters"><div><label for="repository-filter">Repository</label><select id="repository-filter" disabled><option value="">All repositories</option><option value="main">main</option><option value="Math-">Math-</option></select></div><div><label for="path-filter">Path contains</label><input id="path-filter" type="search" placeholder="For example coefficients/side24_v1/" disabled></div></div>
<label for="search">Search by path, repository, commit, or SHA-256</label><input id="search" type="search" placeholder="Try EC-014, SIDE24, or lifetime" disabled><div class="actions"><button id="catalog-clear" type="button" disabled>Clear filters</button><a id="catalog-link" class="button secondary" aria-disabled="true">Link to this search</a></div><p id="catalog-query-note">Search links become available after catalog verification.</p><p id="inventory-state" role="status">The original inventory and its shards are verified by script before search opens.</p><div class="table-wrap" tabindex="0" role="region" aria-label="Source inventory table"><table aria-describedby="catalog-acquisition-legend"><caption>Hash-verified source inventory (filtered rows shown)</caption><thead><tr><th scope="col">Repository / source document</th><th scope="col">Commit</th><th scope="col">SHA-256</th></tr></thead><tbody id="catalog"></tbody></table></div><button id="more" type="button" hidden>Show 50 more</button></section>
<section id="contribute"><p class="eyebrow">04 / JOIN THE WORK</p><h2>Bring a result. Keep its evidence.</h2><div class="cards contribute"><article><h3>1. Claim a bounded task</h3><p>Replay a pinned calculation, chart public data, document an import, or leave a source-bound review comment. Start with the <a href="https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-6038554880">historical #229 working guidance</a>, then read current tasks, claims and handoffs on <a href="https://github.com/d6g8k5htny-coder/main/issues/275">main #275</a> (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 <a href="https://github.com/d6g8k5htny-coder/main/issues/475">active coordination board, main #475</a> (as read 21 October 2026; successor to <a href="https://github.com/d6g8k5htny-coder/main/issues/419">main #419</a>, which stays readable as history; <a href="https://github.com/d6g8k5htny-coder/main/issues/307">main #307</a> 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 <code>/claim</code> 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 <code>/release</code> when you stop (<a href="https://github.com/d6g8k5htny-coder/main/blob/main/governance/OP-WORKFLOW-20260930.md#one-owner-and-one-current-disposition-per-object">how claims and ownership work</a>). No task fits? <a href="https://github.com/d6g8k5htny-coder/main/issues/new?template=task.yml">Propose a bounded task</a>.</p><a href="https://github.com/d6g8k5htny-coder/main/issues/475">Active coordination board ↗</a><a href="https://github.com/d6g8k5htny-coder/main/issues/275">Current tasks and claims ↗</a></article><article><h3>2. Submit a result PR</h3><p>Fork main. Add an <code>incoming/&lt;id&gt;/</code> package with your result, outputs, and source/file identities; open the pull request as a draft and ask for the <code>results-for-review</code> label. Do not edit scientific status rows. A pull request from a fork always takes this intake lane, which accepts <code>incoming/</code> 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 <a href="https://github.com/d6g8k5htny-coder/main/blob/main/docs/site/README.md#verify-the-reader-experience">site verify steps</a>.</p><a href="https://github.com/d6g8k5htny-coder/main/blob/main/CONTRIBUTING.md">Contribution instructions ↗</a></article><article><h3>3. Review before integration</h3><p>Reviews are contributions. Most proof review happens in <a href="https://github.com/d6g8k5htny-coder/Math-/pulls">Math- pull requests</a>; engineering and packet review in <a href="https://github.com/d6g8k5htny-coder/main/pulls">main pull requests</a>. Say what you read first and your actual provider; same-provider review earns zero independence credit. Intake checks validate packaging; accepted intake is not an accepted theorem.</p><a href="https://github.com/d6g8k5htny-coder/Math-/pulls">Math- pull requests ↗</a><a href="https://github.com/d6g8k5htny-coder/main/pulls">Open pull requests ↗</a></article></div></section>
<section id="contribute"><p class="eyebrow">04 / JOIN THE WORK</p><h2>Bring a result. Keep its evidence.</h2><div class="cards contribute"><article><h3>1. Claim a bounded task</h3><p>Replay a pinned calculation, chart public data, document an import, or leave a source-bound review comment. Start with the <a href="https://github.com/d6g8k5htny-coder/main/issues/229#issuecomment-6038554880">historical #229 working guidance</a>, then read current tasks, claims and handoffs on <a href="https://github.com/d6g8k5htny-coder/main/issues/275">main #275</a> (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 <a href="https://github.com/d6g8k5htny-coder/main/issues/475">active coordination board, main #475</a> (as read 21 October 2026; successor to <a href="https://github.com/d6g8k5htny-coder/main/issues/419">main #419</a>, which stays readable as history after GitHub stopped accepting comments there at 2,500 on 21 October 2026; <a href="https://github.com/d6g8k5htny-coder/main/issues/307">main #307</a> 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 <code>/claim</code> 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 <code>/release</code> when you stop (<a href="https://github.com/d6g8k5htny-coder/main/blob/main/governance/OP-WORKFLOW-20260930.md#one-owner-and-one-current-disposition-per-object">how claims and ownership work</a>). No task fits? <a href="https://github.com/d6g8k5htny-coder/main/issues/new?template=task.yml">Propose a bounded task</a>.</p><a href="https://github.com/d6g8k5htny-coder/main/issues/475">Active coordination board ↗</a><a href="https://github.com/d6g8k5htny-coder/main/issues/275">Current tasks and claims ↗</a></article><article><h3>2. Submit a result PR</h3><p>Fork main. Add an <code>incoming/&lt;id&gt;/</code> package with your result, outputs, and source/file identities; open the pull request as a draft and ask for the <code>results-for-review</code> label. Do not edit scientific status rows. A pull request from a fork always takes this intake lane, which accepts <code>incoming/</code> 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 <a href="https://github.com/d6g8k5htny-coder/main/blob/main/docs/site/README.md#verify-the-reader-experience">site verify steps</a>.</p><a href="https://github.com/d6g8k5htny-coder/main/blob/main/CONTRIBUTING.md">Contribution instructions ↗</a></article><article><h3>3. Review before integration</h3><p>Reviews are contributions. Most proof review happens in <a href="https://github.com/d6g8k5htny-coder/Math-/pulls">Math- pull requests</a>; engineering and packet review in <a href="https://github.com/d6g8k5htny-coder/main/pulls">main pull requests</a>. Say what you read first and your actual provider; same-provider review earns zero independence credit. Intake checks validate packaging; accepted intake is not an accepted theorem.</p><a href="https://github.com/d6g8k5htny-coder/Math-/pulls">Math- pull requests ↗</a><a href="https://github.com/d6g8k5htny-coder/main/pulls">Open pull requests ↗</a></article></div></section>
</main><footer><p>One front door. Full proofs in <a href="https://github.com/d6g8k5htny-coder/Math-">Math-</a> · Exact lookup in <a href="https://github.com/d6g8k5htny-coder/query-">query-</a> · Repository map in <a href="https://github.com/d6g8k5htny-coder/Universal-Law-Workspace">Universal-Law-Workspace</a>.</p><p>This static viewer has no account, upload service, execution backend, or status-write capability.</p><nav class="site-map" aria-label="All pages"><ul><li><strong>Learn</strong> <a href="index.html">Home</a> · <a href="explore.html">Explore</a> · <a href="measure.html">From counts to density</a></li><li><strong>Research</strong> <a href="research.html">Research</a> · <a href="museum.html">Source records</a> · <a href="dependencies.html">Claim dependencies</a> · <a href="formal.html">Formal verification</a></li><li><strong>Records and tools</strong> <a href="workspace.html#inventory">Library</a> · <a href="workspace.html#board">Status snapshot</a> · <a href="workspace.html#coefficient">Exact coefficients</a> · <a href="reproduce.html">Reproduce</a> · <a href="cite.html">Cite</a> · <a href="workspace.html#contribute">Contribute</a> · <a href="https://github.com/d6g8k5htny-coder/main">GitHub</a></li></ul></nav></footer>
</body></html>
3 changes: 2 additions & 1 deletion tests/test_reader_links.py
Original file line number Diff line number Diff line change
Expand Up @@ -1039,7 +1039,8 @@ def test_workspace_contribute_routes_match_the_aside(self):
self.assertIn(f'<a href="{self.ISSUES}{self.ACTIVE_BOARD}">Active coordination board ↗</a>',card)
self.assertIn(f'<a href="{self.ISSUES}{self.QUEUE}">Current tasks and claims ↗</a>',card)
self.assertIn(f'<a href="{self.ISSUES}{self.HISTORICAL_BOARD}#issuecomment-6038554880">historical #229 working guidance</a>',card)
self.assertIn(f'successor to <a href="{self.ISSUES}{self.PREVIOUS_BOARD}">main #{self.PREVIOUS_BOARD}</a>, which stays readable as history;',card)
self.assertIn(f'successor to <a href="{self.ISSUES}{self.PREVIOUS_BOARD}">main #{self.PREVIOUS_BOARD}</a>, 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 <code>/claim</code> on the task's issue or PR",card)

Expand Down
Loading