Status: proposed

Wiki review — T-W022

Review outcome

Reviewed on 2026-10-13, continuing the interrupted packet from its existing files. All Markdown resources and rendered index pages were read, with programmatic checks of quotation provenance, prompt previews and local links. The homepage and nine section landings pass the local content checks. This review page is editorial; its proposed status makes no simulation claim. Deployment and browser appearance are not established by static generation.

The entry now opens with an egg and a born word, then offers four illustrated windows and nine doors into the atlas. Its warm shore imagery stays explicitly proposed; illustrations are labelled as compositions. Existing prose from the interrupted cut was retained where it was already evocative and accurate.

What changed

Completed the interrupted review rather than restarting its lore. Verified exact excerpts against retained logs, separating engine narration from creature speech and numerical samples from chronicle quotations.
Corrected the parameter-inheritance account in The bembe and The laws: the id-seeded helper is not the whole path. Faction founding persists the mutated parent vector in cells and reads it back.
Kept differences explicit: three implemented faith regimes versus P9's five desired stances; five-term unity versus the older four-term formula and P20's broader ambition; projections versus voyages; finite eras and fixed needs versus P16/P26. No run here establishes ONE or cross-node migration.
Reconciled stale visual instructions with mixed page status and reuse of server-rendered copy buttons; normalized the homepage's God link.
Rebuilt PROMPTS from the complete source blocks, including multiline continuations, the example and this review. Each copied prompt specifies field types/order, headings, length, evidence rules and a concrete path.
Pasted CONTRIBUTING's example unchanged into contrib/example.md. Added a bounded preview helper within this packet's scope and documented its limits. It uses the shared renderer and explicitly admits only the reviewed example.
Added a repeatable, read-only content check in check-review.py.

Per-page evidence and controls

Counts are occurrences of verbatim chronicle records with an adjacent seed, event tick and log locator. Repeated use across pages counts on each page. Numerical samples, word documents, petitions outside the chronicle collection and diagnostic strings do not count. Status describes lore evidence, not deployment or engine capability. Copy counts are actual rendered buttons.

Source page	Status	Chronicle quotes with seed and tick	Prompt buttons
index.md	mixed	2	6
world.md	mixed	1	9
bembe.md	mixed	1	5
peoples.md	mixed	1	6
god.md	mixed	1	8
realities.md	mixed	1	8
nodes.md	mixed	1	8
chronicle.md	mixed	9	7
laws.md	mixed	1	11
makers.md	mixed	1	7
contrib/example.md	proposed	0	1
REVIEW.md	proposed, editorial	0	3

README, BUILD, CONTRIBUTING, TEMPLATE, PROMPTS and VISUALS are reviewed editorial resources, not public pages; their rendered counts are not applicable. TEMPLATE intentionally contains placeholders. Proposed contributions need not invent a quotation; the nine section landings satisfy the real-quote gate.

Validation and contribution path

Commands from the repository root:

node scripts/bembe_wiki.mjs
node scripts/bembe_wiki.mjs --check
node docs/bembe/WIKI/render-example.mjs --check
python3 docs/bembe/WIKI/check-review.py
grep -L 'copy-prompt' website/static/bembe/wiki/*/index.html
test -s docs/bembe/WIKI/REVIEW.md
test -s website/static/bembe/wiki/contrib/example/index.html

The standard renderer produces 11 pages and 78 exact prompt previews after adding this review. The explicit example helper produces 12 pages and 79 previews. Renderer tests cover escaping, inert fences, unique IDs and exact prompt order/text; clipboard tests use a DOM double for success and denied or missing clipboard access. They do not establish real browser interaction.

The content check validates 106 citations against 13 retained logs, exact quoted records, all public prompt previews and local wiki links. These are existing historical artifacts; no new headless run or clean-revision replay is claimed. Their recorded working-tree and WASM limitations remain in each page.

The helper asserts byte equality between the fenced example and the submitted file. It renders the example at /bembe/wiki/contrib/example/ and includes it in search.json. No edits to the pasted document are required. Run the helper last: the ordinary scanner still excludes contrib and rewrites search.json without that entry. The helper checks its integration anchors and fails if the shared renderer changes. This proves a bounded example preview, not automatic acceptance of arbitrary contributions.

Open questions for Eris

Site build or committed output

Should the site build generate the wiki, or should reviewed static output be committed and checked for freshness? The shared renderer is outside this packet's own set. A follow-up should integrate an explicit reviewed-contribution list, replacing the scoped example adapter, whichever hosting path is chosen.

Preview prompt for Site build or committed output

Write the BEMBE wiki build and reviewed-contribution integration decision, distinguishing site-build generation from committed static output and preserving explicit review before publication. Read docs/bembe/WIKI/README.md and docs/bembe/WIKI/CONTRIBUTING.md; consult docs/bembe/SPEC/00-SEED-EXPANDED.md, docs/bembe/CIVILIZATION-SPACE.md, docs/bembe/V1-NODES.md, demos/bembe/SPEC.md and the target outline. Return exactly one UTF-8 Markdown document, no enclosing code fence or commentary. Begin with --- delimited front matter in this exact order: title (nonempty quoted string), section ("makers"), order (9), status (real|proposed|mixed), sources (nonempty JSON array of existing repository-relative spec paths), runs (JSON array of {"seed":string,"ticks":nonnegative integer,"log":repository-relative path}; [] without verified observations), summary (quoted 20–40 word string). Then # <title>, followed by ## Lore, ## Mechanism, ## Evidence, ## Proposals and gaps, in that order. Write 400–700 body words excluding front matter, headings, citations and comments. Every behavioural lore claim must cite [run: seed="<seed>"; tick=<event tick>; log="<path>"; locator="<line or record key>"] matching runs or begin Proposal:. Never invent a run, quote or receipt; separate specification intent, code and observation. Include a verbatim observed chronicle quote when verified, otherwise state Proposal: chronicle evidence pending. Use a bemba for one, bembe for many, BEMBE for the game. Include one continuation prompt and a prompt per remaining gap, each repeating this exact output contract with a concrete task and contribution path. Submit docs/bembe/WIKI/contrib/makers-wiki-build-decision.md or a pull request adding that file. Emit each continuation or gap prompt as a standalone HTML comment: concatenate "<" with "!-- prompt: " to open, then the full prompt text, then concatenate "--" with ">" to close. Do not fence these comments. Use exactly the seven front matter fields; JSON strings use double quotes and status is one bare enum value. Never copy placeholder values into the final document.

Browser screenshot once Playwright is granted

The wiki still needs a route-level e2e screenshot at desktop and 320/375 px widths, with the scene, nine cards and expanded prompt visible. Verify keyboard copy, real clipboard denial, no-JavaScript previews, local fonts, reduced motion and the example route. No Playwright screenshot was taken in this packet. Which approved environment should capture these acceptance artifacts?

Preview prompt for Browser screenshot once Playwright is granted

Document the BEMBE wiki browser acceptance evidence once Playwright is granted: desktop and narrow screenshots, keyboard and clipboard paths, no-JavaScript prompts and the example route. Claim only checks actually performed. Read docs/bembe/WIKI/README.md and docs/bembe/WIKI/CONTRIBUTING.md; consult docs/bembe/SPEC/00-SEED-EXPANDED.md, docs/bembe/CIVILIZATION-SPACE.md, docs/bembe/V1-NODES.md, demos/bembe/SPEC.md and the target outline. Return exactly one UTF-8 Markdown document, no enclosing code fence or commentary. Begin with --- delimited front matter in this exact order: title (nonempty quoted string), section ("makers"), order (9), status (real|proposed|mixed), sources (nonempty JSON array of existing repository-relative spec paths), runs (JSON array of {"seed":string,"ticks":nonnegative integer,"log":repository-relative path}; [] without verified observations), summary (quoted 20–40 word string). Then # <title>, followed by ## Lore, ## Mechanism, ## Evidence, ## Proposals and gaps, in that order. Write 400–700 body words excluding front matter, headings, citations and comments. Every behavioural lore claim must cite [run: seed="<seed>"; tick=<event tick>; log="<path>"; locator="<line or record key>"] matching runs or begin Proposal:. Never invent a run, quote or receipt; separate specification intent, code and observation. Include a verbatim observed chronicle quote when verified, otherwise state Proposal: chronicle evidence pending. Use a bemba for one, bembe for many, BEMBE for the game. Include one continuation prompt and a prompt per remaining gap, each repeating this exact output contract with a concrete task and contribution path. Submit docs/bembe/WIKI/contrib/makers-wiki-browser-evidence.md or a pull request adding that file. Emit each continuation or gap prompt as a standalone HTML comment: concatenate "<" with "!-- prompt: " to open, then the full prompt text, then concatenate "--" with ">" to close. Do not fence these comments. Use exactly the seven front matter fields; JSON strings use double quotes and status is one bare enum value. Never copy placeholder values into the final document.

Public evidence and continuation

The cited cache logs were retrievable locally during review, but are not public downloads. Which authorized location should preserve them, with revision and artifact hashes, for readers outside this checkout? Until that handoff, the site's citations establish a local review trail with a public retrieval gap.

Preview prompt for Public evidence and continuation

Continue the BEMBE wiki review by preparing an authorized public evidence preservation plan and verifying citation provenance, without publishing private logs or turning unresolved observations into universal claims. Read docs/bembe/WIKI/README.md and docs/bembe/WIKI/CONTRIBUTING.md; consult docs/bembe/SPEC/00-SEED-EXPANDED.md, docs/bembe/CIVILIZATION-SPACE.md, docs/bembe/V1-NODES.md, demos/bembe/SPEC.md and the target outline. Return exactly one UTF-8 Markdown document, no enclosing code fence or commentary. Begin with --- delimited front matter in this exact order: title (nonempty quoted string), section ("makers"), order (9), status (real|proposed|mixed), sources (nonempty JSON array of existing repository-relative spec paths), runs (JSON array of {"seed":string,"ticks":nonnegative integer,"log":repository-relative path}; [] without verified observations), summary (quoted 20–40 word string). Then # <title>, followed by ## Lore, ## Mechanism, ## Evidence, ## Proposals and gaps, in that order. Write 400–700 body words excluding front matter, headings, citations and comments. Every behavioural lore claim must cite [run: seed="<seed>"; tick=<event tick>; log="<path>"; locator="<line or record key>"] matching runs or begin Proposal:. Never invent a run, quote or receipt; separate specification intent, code and observation. Include a verbatim observed chronicle quote when verified, otherwise state Proposal: chronicle evidence pending. Use a bemba for one, bembe for many, BEMBE for the game. Include one continuation prompt and a prompt per remaining gap, each repeating this exact output contract with a concrete task and contribution path. Submit docs/bembe/WIKI/contrib/makers-wiki-evidence-preservation.md or a pull request adding that file. Emit each continuation or gap prompt as a standalone HTML comment: concatenate "<" with "!-- prompt: " to open, then the full prompt text, then concatenate "--" with ">" to close. Do not fence these comments. Use exactly the seven front matter fields; JSON strings use double quotes and status is one bare enum value. Never copy placeholder values into the final document.