the site is one zoomable map: nested regions with semantic zoom, three views over one node set, fragments in a panel, and intake as prefilled issues (S5)

Maintainer ruling, taken in conversation on 2026-10-30; executed by the site-vertical-slice round's follow-up on its open pull request.

S5. The site's one UI is the map: one full-viewport network graph. The front page fills the viewport with a single pannable, zoomable network laid out from /assets/map.json by vanilla JavaScript (site/assets/map.js): the curated network of state/concepts.json, a wiki of the agent-foundations theory relevant here whose members span five kinds — goal/thread of the research, new construction, mathematical object, prior work, philosophical concept — encompassing the repository wiki's terms and going beyond them. Small circles colour-coded by kind with a legend, force-laid and free of walls, each carrying its name and a two-line summary; the question and lede sit in an about panel over the canvas, and a reader is not shown more text until they click in for it. The links are hand-chosen by a pass over the candidate pairs, never a near-complete graph, each carrying one or more relation categories and a one-line why shown on edge hover. Every click opens a centred popup — the entry's wiki page fragment where one exists, else its /concepts/<id>/ fragment, each ending in a reverse-chronological expandable list of its tagged merged work — and /#c=<id> deep-links a concept. The frame tree, the rounds and the digested pull requests are pages and popups, not canvases; every per-id URL of S4 stands, each object remaining a full page, so the contract is unchanged. Walks are not part of the site; the one shipped walk leaves with this ruling, and its open review entry leaves the queue. Intake is verbs on every node page and fragment — comment, challenge, estimate, want — each a prefilled GitHub issue carrying the node id and a protocol-shaped body; the site accepts no write, and a maintainer round sweeps what lands into ledger events under graph/PROTOCOL.md's authorship rules.

The pull-request digests. Every merged pull request gets a key-points digest in state/prs.json: number, title, merged date, its rounds, topic tags drawn from the wiki pages and frames, one or two paragraphs of results in plain register, and — where a result was later displaced — a supersession note with references. The digests are AI-generated against the round reports and registries, provenance-marked, and read by the site alone; nothing adjudicates on them. The site's palette and type are amberns.com's (paper #0e0e10, ink #ececec, bone accent #c8c4ba, Lexend self-hosted), dark only.

Rejected alternatives: a page-per-object site with hand-written walks as the guided layer (the maintainer judged the walk unnecessary once the map itself is the guide); a continuously-zooming canvas (the maintainer ruled levels discrete, entered and left as levels); nested-region treemap levels with previews of their contents (the maintainer ruled for plain network graphs, nothing marking a node composite); a write path from the page (a backend is its own decision, not taken here).