Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/site/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ The front and technical layers use the same existing evidence. No second scienti

## Current source publication

`tools/current_site_data.py` resolves public main and Math- commits once, verifies their complete Git trees and the seven acquired source files, and extracts exact indented proof displays. Other inventory rows bind paths and Git blobs; their document bytes are not downloaded. The page calls equation blocks excerpts and keeps their surrounding proof scope available by pinned line links. `tools/current_site_build.py` renders one payload offline into marked current sections and static node pages; Research and Formal stay script-free. Current observations and original dated reading cuts have separate identities.
`tools/current_site_data.py` resolves public main and Math- commits once, verifies their complete Git trees and the seven acquired source files, and extracts exact indented proof displays. Other inventory rows bind paths and Git blobs; their document bytes are not downloaded. The page calls equation blocks excerpts and keeps their surrounding proof scope available by pinned line links. `tools/current_site_build.py` renders one payload offline into marked current sections and static node pages. Formal remains script-free. Research preserves its dated reading cuts and their source pins, with a separately identified current observation. Generated Research pages use the existing `current.mjs` module to verify the advertised local `current.json` observation and progressively update its clock-derived freshness label (`current`, `stale` or `clock disagreement`); the same observation becomes stale after two hours. The module checks freshness each minute and on page/visibility events; it does not poll for a new observation or refresh editorial reading cuts. Generated current navigation, the observation timestamp and source pins remain readable without JavaScript. Current observations and original dated reading cuts have separate identities.

"Resume this node" appears in the atlas inspector and on each current static node page. Both come from `resumeProjection` in `current-model.mjs`; `tools/current_site_history.py` keeps a Python copy, and `tests/test_current_site_resume.mjs` checks that the two agree on every node. The block names the snapshot's graph commit, path, SHA-256 and observation time, and warns readers to refresh from the live record before any ownership- or head-dependent action. Recorded `review_*` fields are labelled as review records, not as the current task, an owner or completion. Next action, missing input, owner evidence and retained stop read "not recorded in this snapshot" on the snapshot-only projection, because the graph records none of them. The atlas inspector also passes `node-status.json`, the published copy of `records/node_status`, into that same projection. Static node pages stay on the snapshot-only call. An owner object is shown only when `evidence_url` matches the shared comment pattern; `released_url`, when present, stays on that object and the atlas says released. The panel shows the recorded status and `observed_at`, and says stale when `observed_at` is more than 24 hours before the render clock. Status is freshness of that view, not scientific validity, and `scientific_effect` stays NONE. A bare `review_issue` number names no repository, so it is not linked. Continuation links come only from the small site-maintained `RESUME_TASK_RECORDS` table of explicitly identified operational pointers; they are not graph metadata, scientific acceptance or source-binding admission. Archived snapshot pages are unchanged.

Expand Down Expand Up @@ -120,7 +120,7 @@ Insert the new `<section id="…" class="latest-work" tabindex="-1" aria-labelle
1. Point Home's "Read the latest public work →", Research's hero "Latest public work" and the Library's latest-work links at the new id. Give the new cut one uniquely named link to the cut below it; exact link names must stay unique. Update the `<time datetime>` and visible date beside the Home and Library entry links to the new cut’s timestamp (`tests/test_reader_links.py` pins them). The Home About link line links Source records, Dependencies and Formal, and its disclosure links Measure; keep ‘dated’/‘synthetic’ in those labels. In the Research hero, add one row for the new cut at the top of the “Dated reading cuts” list (its question heading and the `<summary>` text of its source disclosure) and update the “Newest reading cut” `<time>`; if the cut introduces a status token not listed under `#status-words`, add a quoted-provenance row for it (where it is quoted from, never a definition).
2. In `tests/test_reader_links.py`, update the entry fragments, add the cut's pins to `EXPECTED_READING_URLS` and `EXPECTED_HASH_BINDINGS` (the parser joins the text of all `<code>` elements in an `<li>` into one string and binds that string to each pinned link in that `<li>`, so keep an item's `<code>` text equal to its intended digest), update the pinned-link total and the `p.latest-boundary` count, and add a byte-identity pin for the cut that is no longer newest. Five digests pin the page below the newest cut: the 9 October cut whole; the 7 October cut whole (cut-pointer included); `#shrinking-bin-sampling` whole; the cuts digest from `#pair-endpoint-rate` up to `#lifetimes`, with lineage notes and the contents of the `#newer-work` aside stripped (its opening tag and its place as the last child of `#latest-work` stay pinned); and the paths digest from `#lifetimes` up to `#further-reading`. A cut that stops being newest gets its own byte-identity pin, as the 06:20 cut has. Outside the pins stay the contents of `#newer-work` (maintained routes, checked by `NewerWorkRoutes` in `tests/test_reader_links.py`), the Further-reading section and the footer.
3. In `tools/public_shop_browser_check.py`, update `check_latest_work_flow` and `check_reading_addendum_flow`: entry focus, datetime, card and pinned-link counts.
4. Keep `research.html` script-free, its IDs unique and every local fragment resolvable.
4. Keep dated reading-cut bodies static, their IDs unique and every local fragment resolvable. Preserve the generator’s existing `current.mjs` progressive enhancement for current-observation freshness; it does not update the reading cuts or their source pins.
5. Append the new cut, with its date and UTC time, to the list of later dated cuts earlier in this section, so this guide does not stop at an older cut.
6. Rerun the release tool and the public-shop steps above.

Expand Down
20 changes: 20 additions & 0 deletions docs/superpowers/specs/2026-10-13-current-research-site.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,3 +40,23 @@ Negative controls cover truncated inventories, wrong blob, missing sources, grap


Prepared-but-unpublished recovery follows the reviewed dispatch-only [operator runbook](../runbooks/current-site-publication-recovery.md): republish the exact qualified P artifact under a distinct actual dispatch identity, require exact public P readback, then let ordinary successor preparation append Observed P with its new observer. Never fake the old run attempt, roll back the prepared floor or delete pointers for bootstrap. The runbook is documented; a recovery executor and actual replay require separately qualified integrator execution.


## Implementation correction — 25 October 2026

The script-free Research sentence in **Reader experience** above records the
original 13 October design. Since merged [PR #587](https://github.com/d6g8k5htny-coder/main/pull/587),
`tools/current_site_build.py` inserts the existing `current.mjs` module into
generated Research pages. Formal remains script-free.

The generator still publishes readable current navigation, the static observation
timestamp and pinned source links without JavaScript, separately from preserved
dated editorial reading cuts. On generated Research pages, `current.mjs` verifies
the advertised local `current.json` observation and then recomputes its
clock-derived freshness label (`current`, `stale` or `clock disagreement`) each
minute and on page/visibility events; the same observation becomes stale after
two hours. Initial observation loading includes one digest-keyed fallback after
an integrity mismatch, not recurring polling. This enhancement does not acquire
new upstream source documents, update the observation's source pins, refresh
editorial reading cuts or revalidate scientific claims. The original design text
and the historical cuts keep their dates and identities.
Loading