The makers
Lore
The first word was spoken: "to". It means wood.
[run: seed="reed"; tick=1; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 3; chronicle/100.text"]
The chronicle preserves a word and its English gloss in seed reed. The
sentence is engine narration; a receipt and a captured player-visible result
remain separate evidence targets.
Recording method and revision.
Proposal: picture a workshop just beyond the shore, where a maker leaves a lamp beside an unfinished map. The lamp is an editorial image, not a placed object or a belief attributed to bembe. The map is an invitation drawn from the expanded seed §0: a world whose lives become richer over time, and whose history can be inspected by someone arriving late.
Proposal: RURAL is the database beneath that desired world. A database keeps structured state: what exists, what changed, and what a reader may inspect. The expanded seed §0 asks for everything that happens to be a receipted transaction. Its world is intended to test the keeper through conflict, distribution and replay. Those technical questions have a scale a visitor can care about: did a life continue, did a promise survive, did a journey arrive?
In one small beginning, seed makers-shore reports six living bembe and zero word records at tick 1. At tick 120 it reports six living bembe and eleven word records. Equal population counts do not establish that the same individuals survived. [run: seed="makers-shore"; tick=1; log=".zig-cache/wiki/makers-makers-shore.jsonl"; locator="line 1"] [run: seed="makers-shore"; tick=120; log=".zig-cache/wiki/makers-makers-shore.jsonl"; locator="line 120"]
Interpretation: the changing count offers a doorway into the workshop. It invites questions about the eleven records, their meanings and their makers. A count alone cannot answer those questions. A growing vocabulary is a subject to investigate, not a translated conversation to invent.
Preview prompt for Lore
Write the makers section overview for the BEMBE wiki. 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-overview.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.Mechanism
RURAL and the world
Proposal: Map mechanics to transactions, receipts, storage and capabilities; label service emulation honestly. Source: demos/bembe/SPEC.md §0–6; docs/bembe/SPEC/00-SEED-EXPANDED.md P6, P23. Planned sub-page: makers/rural-and-the-world.md.
Proposal: the game is intended to test RURAL through the pressure of a world, as expanded seed §0 explains. A single stored number is easy to inspect. A world asks whether related changes stay together, whether competing histories can meet, and whether memory remains readable after interruption. These are design questions, not results established by a short count of living bembe and words.
Proposal: P6 asks each mechanic to name the database feature carrying it, with a test that fails when the game bypasses that feature. Explain the particular load placed on RURAL, the observable outcome, and the failure that would reveal a broken connection. Preserve real/service/unavailable capability distinctions: service emulation must not acquire an engine capability through poetic wording.
| Proposed world question | Concern to investigate | Source |
|---|---|---|
| Can a change remain whole? | Atomic commits and receipts | Expanded seed §0; PLAN §2 |
| Can two histories meet? | Branches and conflict | Expanded seed P6 |
| Can a node remember tomorrow? | Storage and checkpoints | Expanded seed P6, P29 |
| Can another island be inspected? | Replication and projections | Expanded seed P2, P6 |
| Can an act be authorized? | Intent, mandates and identity | Expanded seed P6 |
| Can the past explain the present? | History and read views | Expanded seed P6, P23 |
Proposal: this table maps investigations, not coverage. The copied VISION-AUDIT, dated 2026-10-12 21:58, records shallow adoption and failures of visible civilization. PLAN §0 records a later node-work programme. These are dated testimony and planned work; neither proves those outcomes in this run. Keep their moments distinct rather than making either a timeless account of the world.
Preview prompt for RURAL and the world
Map mechanics to transactions, receipts, storage and capabilities; label service emulation honestly. for the BEMBE wiki. 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 (10), 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-rural-and-the-world.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.Minds, art and sound
Proposal: Explain pure minds, procedural art, voices and shared control intent across browser and desktop. Source: demos/bembe/SPEC.md §4, §7–8; docs/bembe/SPEC/00-SEED-EXPANDED.md P22, P25, P30, P33. Planned sub-page: makers/minds-art-and-sound.md.
Proposal: PLAN §2 separates engine, minds and surfaces. In its architecture, the engine keeps the world records, minds calculate changes, and surfaces make the world available to a player. Expanded seed P25 asks for families of appearances; P30 and P33 describe desktop and controls. Ask which layer a claim concerns before choosing evidence.
Proposal: an exact coined word would support a language passage; a captured frame would support an appearance passage; an audio capture would support a heard voice. P25 and P27 give the design context. This headless trace supplies counts, so it cannot establish what a bemba looked like, what sound reached a player, or whether a control was discoverable.
Preview prompt for Minds, art and sound
Explain pure minds, procedural art, voices and shared control intent across browser and desktop. for the BEMBE wiki. 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 (20), 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-minds-art-and-sound.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.Harness and evidence
Proposal: Explain headless observations, visual checks and stress scenarios without exposing private files or implying schedules exist. Source: docs/bembe/SPEC/00-SEED-EXPANDED.md P27–28; docs/bembe/V1-NODES.md §7. Planned sub-page: makers/harness-and-evidence.md.
A headless harness advances the world without drawing it. Its records let another reader inspect an event; a visual check asks whether the player can see the corresponding change. Each answers a different question.
Keep seed, tick, command, revision and record locator beside an observation. A count of words cannot recover their sound. A passing file-existence check cannot establish authentic quotation or a usable page. Read the claim and its cited record together, then test the surface the player actually uses. The chronicle's recording method shows how committed documents were collected alongside summary samples.
Proposal: connect a chronicle event, its transaction receipt and a captured frame in one bounded experiment (expanded seed P6/P27). The current excerpts do not yet provide that complete path.
Preview prompt for Harness and evidence
Explain headless observations, visual checks and stress scenarios without exposing private files or implying schedules exist. for the BEMBE wiki. 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 (30), 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-harness-and-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.Contributing to the atlas
Proposal: Explain copy prompts, review, source consistency and how a proposed page earns observed status. Source: docs/bembe/SPEC/00-SEED-EXPANDED.md P34. Planned sub-page: makers/contributing-to-the-atlas.md.
Choose a question small enough to answer honestly. Use its prompt, then read README and CONTRIBUTING. Submit one UTF-8 Markdown document at the concrete contrib path in the prompt, or a pull request adding it. Planned sub-pages are future integration destinations, not live links. Review and publication are separate.
| Front matter field | Required form |
|---|---|
title | Quoted string matching the single H1 |
section | Quoted allowed section; here "makers" |
order | Nonnegative integer; this landing is 9 |
status | Bare real, proposed or mixed |
sources | Nonempty JSON array of existing source paths |
runs | JSON array of seed, ticks and log objects |
summary | Quoted plain text, 20–40 words |
Keep these seven fields in order between standalone front matter delimiters. Normal contributions use Lore, Mechanism, Evidence, Proposals and gaps as their H2s, and 400–700 body words excluding headings, citations and comments. Section landings can be longer; their prompts still request the ordinary contribution length.
Real means behavioural claims are observed and cited; proposed means none is offered as observed; mixed means both occur, with paragraph labels. These editorial states differ from engine capabilities. A proposed page can be accepted as a useful design account; acceptance does not turn wishes into events or satisfy a chronicle gate.
Preview prompt for Contributing to the atlas
Explain copy prompts, review, source consistency and how a proposed page earns observed status. for the BEMBE wiki. 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 (40), 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-contributing-to-the-atlas.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.Naming a life
Write a bemba for one creature, bembe for many, and BEMBE for the game. These are the binding forms in PLAN §1 and README. Keep exact code identifiers in code formatting when they matter to inspection. God names the player's in-world role; distinguish that role from any belief a people is said to hold. Attribute belief with evidence or a labelled proposal.
| Referent | Wiki form |
|---|---|
| One creature | a bemba |
| Several creatures | bembe |
| The game | BEMBE |
| Player's in-world role | God |
| Source identifier | Exact spelling in code formatting |
Evidence
A short world, exactly located
The observation uses seed makers-shore, 120 requested
ticks and --tick-ms 0. No --acts file, peer, listen endpoint
or persistent store was supplied. The simple runner uses
the opened branch when returned, otherwise branch 1
(demos/bembe/headless/run.mjs, run). The sample records
do not identify that branch. No remote node is claimed.
The source revision is
54f1d6d1a704228a1e55552e70c48a358e281582.
This identifies checkout HEAD, not a rebuilt wasm artifact.
Reproduction command, from the repository root:
node demos/bembe/headless/run.mjs --seed makers-shore --ticks 120 --tick-ms 0 --log .zig-cache/wiki/makers-makers-shore.jsonlThe command exited 0. The last recorded simulation tick is 120. These quotes preserve complete JSONL records, including field order. They are numerical log excerpts, not words spoken by bembe. Lines are counted from 1. [run: seed="makers-shore"; tick=120; log=".zig-cache/wiki/makers-makers-shore.jsonl"; locator="line 120"]
Line 1, tick 1:
{"U":0,"tick":1,"head":12,"alive":6,"words":0,"petitions":0,"era":0}
[run: seed="makers-shore"; tick=1; log=".zig-cache/wiki/makers-makers-shore.jsonl"; locator="line 1"]
Line 30, tick 30:
{"U":0,"tick":30,"head":41,"alive":6,"words":7,"petitions":0,"era":0}
[run: seed="makers-shore"; tick=30; log=".zig-cache/wiki/makers-makers-shore.jsonl"; locator="line 30"]
Line 60, tick 60:
{"U":0,"tick":60,"head":71,"alive":6,"words":10,"petitions":0,"era":0}
[run: seed="makers-shore"; tick=60; log=".zig-cache/wiki/makers-makers-shore.jsonl"; locator="line 60"]
Line 120, tick 120:
{"U":0,"tick":120,"head":131,"alive":6,"words":11,"petitions":0,"era":0}
[run: seed="makers-shore"; tick=120; log=".zig-cache/wiki/makers-makers-shore.jsonl"; locator="line 120"]
The runner's sample function counts word-record keys
and filters petitions to status open. That defines these
measurements (demos/bembe/headless/run.mjs, sample).
At tick 120, the record reports zero open petitions
and era zero. It cannot establish the absence of every
kind of question or every historical petition.
[run: seed="makers-shore"; tick=120; log=".zig-cache/wiki/makers-makers-shore.jsonl"; locator="line 120"]
The reed excerpt above preserves a born word and its gloss.
The makers-shore samples contain only numerical summaries.
The cache artifact is locally retrievable for review,
not a public download. README requires accessible evidence;
public integration must arrange authorized preservation
or keep affected claims proposed.
The e2e evidence rule
Proposal: expanded seed P27 requires visual end-to-end evidence for game UI work. Its requested suite boots the desktop server on an ephemeral port, hatches a world, runs ticks at 16x, exercises god acts and panels, and saves screenshots and HUD text. Each UI packet lists this in ev. The project agent reviews screenshots before accepting a UI row; L1 and Eris review at milestone closes. This is the required standard, not a passing run here.
Proposal: P33 asks for before/after screenshot pairs for controls; P27 asks for screenshots per screen. A stored change can coexist with a misleading surface. The dated VISION-AUDIT's terrain findings explain why that distinction matters. Headless counts cannot answer whether an act changed the picture. This writing packet provides no browser capture, rendered-route evidence or demonstrated clipboard behaviour.
Proposals and gaps
Proposal: follow one ordinary event from world record to receipt to player-visible result, as P6 and P27 request. The four planned sub-pages remain future destinations. Their retained prompts cover the unfinished investigations; the overview prompt is also the continuation prompt.
Proposal: extend the verified word excerpt with its receipt and a captured player-visible result. P34 supplies the purpose. Record exact seed, tick and locator. The following prompt covers that specific gap.
Preview prompt for Proposals and gaps
Write verified chronicle evidence for the makers section, including a named word or concept and explicit limits of interpretation. Read docs/bembe/WIKI/README.md and docs/bembe/WIKI/CONTRIBUTING.md; consult docs/bembe/SPEC/00-SEED-EXPANDED.md P34, docs/bembe/VISION-AUDIT.md and docs/bembe/WIKI/makers.md. 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 (50), 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-chronicle-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.Proposal: preserve evidence for public retrieval and verify the rendered page and copy controls before release, as README and expanded seed P27, P34 require. Chronicle proof and public presentation are separate missing pieces.
Preview prompt for Proposals and gaps
Write a public evidence and rendering handoff for the makers page, distinguishing local cache review from public retrieval and verifying rendering and copy controls only with actual e2e evidence. Read docs/bembe/WIKI/README.md and docs/bembe/WIKI/CONTRIBUTING.md; consult docs/bembe/SPEC/00-SEED-EXPANDED.md P27 and P34 and docs/bembe/WIKI/makers.md. 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 (60), 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-public-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.The editorial PROMPTS catalogue preserves every continuation and its full contribution contract.