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
16 changes: 11 additions & 5 deletions docs/site/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,8 @@ Check real desktop/mobile layouts, keyboard operation, light/dark appearance and
## Latest public work is a reading cut

`research.html#latest-work` is static editorial navigation checked at its displayed
UTC time. It links the landed soft-model chain at Math `07320089`, the separately
UTC time, except its closing **Check newer work** route list (`#newer-work`), which
carries its own "as read" date. It links the landed soft-model chain at Math `07320089`, the separately
landed cap formalization at `0fda855b`, exact public C81–C84 issue-comment proofs and
reviews (model and source-bound actual/contact scopes kept distinct), the finite numerical work at main `1e1c9a1c`, and the existing catalog and
query sources. The named boundaries are part of each reading path. This is a
Expand All @@ -55,14 +56,19 @@ to this cut. Later dated cuts were added above it: `#reading-addendum` (3 Octobe
link the newest cut. `#latest-work` keeps its 18:00 UTC heading, wording and pins; its
later additions are a forward pointer to the 20:01 addendum and two labeled
reviewer-lineage notes beside its 3 October review links, which the 7 October cut
discloses. Two further labeled source-identity notes close the 20:01 and 00:18 cuts
discloses, and the maintained contents of its closing `#newer-work` route list
(below), which is navigation, not cut text. Two further labeled source-identity notes close the 20:01 and 00:18 cuts
with the SHA-256 identities their pinned links lacked, and one dated
`<p class="cut-pointer">` inside the 7 October cap card records that Math #193 was
reopened eight minutes after that cut. The 9 October 2026 cut (`#reading-cut-20261009`) restates all five in its source disclosure, so none
is the only record.

Exact-commit citations preserve the reading cut. The **Check newer work** section
intentionally follows mutable upstream branches and discussions. Comment links
(`#newer-work`) intentionally follows mutable upstream branches and discussions. It is
maintained navigation, not cut text: it carries an "as read" date, and when the
coordination board or task queue moves, its routes and the matching Join-the-work card
in `workspace.html` are updated in place without re-pinning any cut
(`NewerWorkRoutes` in `tests/test_reader_links.py` checks them). Comment links
identify the public record but comments remain editable; their reviews record the
reviewed identity. A missing source is unavailable evidence. No browser fetch or
execution of those sources is claimed. The Library, status and museum snapshots
Expand All @@ -77,10 +83,10 @@ check, not something established by a screenshot or link.

### Adding a dated reading cut

Insert the new `<section id="…" class="latest-work" tabindex="-1" aria-labelledby="…">` with its own `<time datetime="…Z">` immediately before the current newest cut. Never edit an earlier cut's text. In the same change:
Insert the new `<section id="…" class="latest-work" tabindex="-1" aria-labelledby="…">` with its own `<time datetime="…Z">` immediately before the current newest cut. Never edit an earlier cut's text; the closing **Check newer work** route list (`#newer-work`) is maintained navigation with its own as-read date. In the same change:

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. Four digests pin the page below the newest cut: 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 stripped; 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. Only the Further-reading section and the footer stay outside the pins.
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. Four digests pin the page below the newest cut: 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.
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.
Expand Down
6 changes: 3 additions & 3 deletions docs/site/app.js
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
import {verifiedJSON, verifiedBytes, validateStatus, validateCoefficient, safeSourceURL, hex40, hex64} from './core.mjs?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3';
import {connectCatalogQuery} from './catalog-query.mjs?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3';
import {prepareWorkspaceFragment} from './workspace-fragment.mjs?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3';
import {verifiedJSON, verifiedBytes, validateStatus, validateCoefficient, safeSourceURL, hex40, hex64} from './core.mjs?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436';
import {connectCatalogQuery} from './catalog-query.mjs?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436';
import {prepareWorkspaceFragment} from './workspace-fragment.mjs?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436';
const finishFragment=prepareWorkspaceFragment();
const el=id=>document.getElementById(id);
const node=(tag,text,cls)=>{const n=document.createElement(tag);if(text!==undefined)n.textContent=text;if(cls)n.className=cls;return n;};
Expand Down
2 changes: 1 addition & 1 deletion docs/site/brand.css
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ body > header {
color: var(--ul-text); font-weight: 750; letter-spacing: .13em;
position: relative; padding-left: 57px; min-height: 44px; line-height: 1.65;
}
.brand::before { content: ""; position: absolute; left: 0; top: 1px; width: 42px; height: 42px; background: url("brand/mark.svg?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3") center/contain no-repeat; }
.brand::before { content: ""; position: absolute; left: 0; top: 1px; width: 42px; height: 42px; background: url("brand/mark.svg?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436") center/contain no-repeat; }
.brand span { color: var(--ul-muted); font-size: 12px; letter-spacing: .16em; text-transform: uppercase; }
nav { gap: 12px 24px; flex-wrap: wrap; }
nav a { color: var(--ul-text); min-height: 44px; display: inline-flex; align-items: center; font-size: 13px; padding: 0 6px; margin: 0 -6px; }
Expand Down
6 changes: 3 additions & 3 deletions docs/site/cite.html
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,14 @@
<meta name="description" content="Cite exact proofs, calculations and software sources with their real metadata, immutable commits and stated scope.">
<meta http-equiv="Content-Security-Policy" content="default-src 'self'; connect-src 'none'; style-src 'self'; script-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'none'; form-action 'none'">
<title>Cite · Universal Law</title>
<link rel="stylesheet" href="style.css?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3"><link rel="stylesheet" href="brand.css?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3"><link rel="stylesheet" href="home.css?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3"><link rel="stylesheet" href="reference.css?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3"><link rel="icon" type="image/svg+xml" href="brand/mark.svg?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3"><meta name="color-scheme" content="dark light"><meta name="theme-color" media="(prefers-color-scheme: light)" content="#f6f8fc"><meta name="theme-color" media="(prefers-color-scheme: dark)" content="#07111f">
<script type="module" src="cite.mjs?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3"></script>
<link rel="stylesheet" href="style.css?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436"><link rel="stylesheet" href="brand.css?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436"><link rel="stylesheet" href="home.css?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436"><link rel="stylesheet" href="reference.css?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436"><link rel="icon" type="image/svg+xml" href="brand/mark.svg?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436"><meta name="color-scheme" content="dark light"><meta name="theme-color" media="(prefers-color-scheme: light)" content="#f6f8fc"><meta name="theme-color" media="(prefers-color-scheme: dark)" content="#07111f">
<script type="module" src="cite.mjs?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436"></script>
</head><body class="reader-home"><a class="skip-link" href="#main-content">Skip to content</a>
<header><a class="brand" href="index.html">UNIVERSAL LAW <span>MATHEMATICS IN THE OPEN</span></a><nav aria-label="Primary"><a href="index.html">Home</a><a href="explore.html">Explore</a><a href="research.html">Research</a><a href="workspace.html#inventory">Library</a></nav></header>
<nav class="reader-tools" aria-label="Research tools"><span class="reader-tools-label" aria-hidden="true">Research tools</span><a href="reproduce.html">Reproduce</a><a href="cite.html" aria-current="page">Cite</a></nav>
<main id="main-content" tabindex="-1">
<section class="hero"><p class="eyebrow">A REFERENCE SOMEONE ELSE CAN FOLLOW</p><h1>Cite the work<br>you actually used.</h1><p class="intro">A research program, a proof, and a calculation are different sources. Point readers to the exact object and version that support your work.</p><div class="actions"><a class="button" href="#identity">Choose an exact source ↓</a></div></section>
<section id="choose"><h2>Choose the right object.</h2><div class="idea-grid"><article><h3>The research website</h3><p>Use <a href="https://github.com/d6g8k5htny-coder/main/blob/main/CITATION.cff">main’s citation metadata</a> for this public guide and reproduction surface. GitHub’s “Cite this repository” menu supplies APA and BibTeX formats.</p></article><article><h3>A mathematical result</h3><p>Find the result in <a href="https://github.com/d6g8k5htny-coder/Math-/blob/main/PROOF_INDEX.md">Math-’s current proof index</a>, then cite its exact proof, full commit and the review you used. Preserve the authorship and hypotheses stated by that object; a repository maintainer is not automatically every proof’s author. Math- has its own <a href="https://github.com/d6g8k5htny-coder/Math-/blob/main/CITING.md">citing guide</a> and <a href="https://github.com/d6g8k5htny-coder/Math-/blob/main/CITATION.cff">citation metadata</a>; follow them for Math- objects.</p></article><article><h3>A tool or data artifact</h3><p>Name the package or artifact, its version or commit, and its own citation guidance. <a href="https://github.com/d6g8k5htny-coder/query-">query-</a> identifies source bytes; it does not certify the mathematical claim they contain.</p></article></div></section>
<section id="choose"><h2>Choose the right object.</h2><div class="idea-grid"><article><h3>The research website</h3><p>Use <a href="https://github.com/d6g8k5htny-coder/main/blob/main/CITATION.cff">main’s citation metadata</a> for this public guide and reproduction surface. GitHub’s “Cite this repository” menu supplies APA and BibTeX formats.</p></article><article><h3>A mathematical result</h3><p>Find the result in <a href="https://github.com/d6g8k5htny-coder/Math-/blob/main/PROOF_INDEX.md">Math-’s selected, dated proof index</a>. For results it does not list, including proofs kept in main, look in the Research page’s <a href="research.html#cut-list-heading">dated reading cuts</a> and its <a href="research.html#newer-work">current source routes</a>. Cite the exact proof, its full commit and the review you used. Preserve the authorship and hypotheses stated by that object; a repository maintainer is not automatically every proof’s author. Math- has its own <a href="https://github.com/d6g8k5htny-coder/Math-/blob/main/CITING.md">citing guide</a> and <a href="https://github.com/d6g8k5htny-coder/Math-/blob/main/CITATION.cff">citation metadata</a>; follow them for Math- objects.</p></article><article><h3>A tool or data artifact</h3><p>Name the package or artifact, its version or commit, and its own citation guidance. <a href="https://github.com/d6g8k5htny-coder/query-">query-</a> identifies source bytes; it does not certify the mathematical claim they contain.</p></article></div></section>
<section id="identity"><p class="eyebrow">EXACT SOURCES</p><h2>Give a future reader a fixed point.</h2><p>Use a commit permalink for the content you read. Branch links such as <code>main</code> can change. Record the repository, complete Git commit and file path; include a SHA-256 or artifact identifier when the source provides one.</p><p>A source reference locates bytes. Add the source’s own authors, title and publication details when preparing a bibliography. A review should be cited separately when your argument relies on that review’s scope.</p><p><strong>No DOI or tagged-release version is declared in main’s citation metadata</strong> (as read on 8 October 2026: CITATION.cff at main <code>30e5cf5c</code> has no doi or version field, and the repository has no tags or releases). Use a commit reference now. A future archive deposit must supply its actual identifier before a DOI is advertised. Citation and archival identifiers do not establish scientific acceptance.</p>
<details><summary>A complete example</summary><p><a href="https://github.com/d6g8k5htny-coder/Math-/blob/f430fdecbb1d8802d8af40419b701f12af87c039/coefficients/side24_v1/PROOF.md">SIDE24 coefficient proof, Math- commit <code>f430fdecbb1d8802d8af40419b701f12af87c039</code>, <code>coefficients/side24_v1/PROOF.md</code></a>. Pair this source with its <a href="museum.html#d3-side24-coefficient">recorded review and scope</a> when discussing acceptance. <a href="reproduce.html">Replay its calculation</a>.</p></details></section>
<section id="reference-builder" hidden><p class="eyebrow">LOCAL REFERENCE BUILDER</p><h2>Make an exact source link.</h2><p>This tool formats the identity you enter. It does not contact GitHub, check that the commit exists, retrieve a file, assign authorship, or evaluate its correctness. Only syntax is checked. Built references can be shared in the page address; include public source metadata only. Nothing is submitted to a verification service.</p>
Expand Down
2 changes: 1 addition & 1 deletion docs/site/cite.mjs
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
import {wireReferenceForm} from './source-reference.mjs?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3';
import {wireReferenceForm} from './source-reference.mjs?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436';
const byId = id => document.getElementById(id);
wireReferenceForm({form:byId('reference-form'), repository:byId('reference-repository'), commit:byId('reference-commit'), path:byId('reference-path'), sha256:byId('reference-sha256'), output:byId('reference-output'), json:byId('reference-json'), bibtex:byId('reference-bibtex'), link:byId('reference-link'), status:byId('reference-status'), actions:byId('reference-actions'), copyText:byId('reference-copy'), copyJSON:byId('reference-copy-json'), copyBibTeX:byId('reference-copy-bibtex'), share:byId('reference-share'), clipboard:globalThis.navigator?.clipboard, location:globalThis.location, history:globalThis.history, events:globalThis.window});
byId('reference-builder').hidden = false;
2 changes: 1 addition & 1 deletion docs/site/conditionals.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ export function renderProjection(document,host,data,source){
el(document,'p','Generated from verified source bytes. This graph is not formal verification, a proof review, or a scientific-status register.'));
host.replaceChildren(article);
}
const services=()=>import('./museum.mjs?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3');
const services=()=>import('./museum.mjs?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436');
// The museum module already verifies config → manifest → index/status once per
// page fetch and caches every pinned byte request. This route consumes that same
// verified startup, so it adds only the audited-descriptor check and projection.
Expand Down
2 changes: 1 addition & 1 deletion docs/site/curvature-export.mjs
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
// Bounded, local export of the Peaks and saddles teaching diagram. No source fetch
// or proof verification occurs here; the identity below is recorded provenance.
import { coneModel } from './explore-models.mjs?site-release=126f4e0b68ae8ef1967d30950ce204527ae9469e9f76d3974cb60bfa31ea63f3';
import { coneModel } from './explore-models.mjs?site-release=76f61a1e04a75db930f63796bfe338fd6982853a0359ff2e7f1886b4113e7436';

const SVG_NS = 'http://www.w3.org/2000/svg';
const PUBLIC_EXPLORE = 'https://d6g8k5htny-coder.github.io/main/site/explore.html';
Expand Down
Loading
Loading