BEMBE — a shore of possible worlds
The lore entry
Illustration · a composed shore, not a simulation screenshot.
An egg stirred in the grass. Then another.
[run: seed="reed"; tick=0; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 2; chronicle/0.text"]
That is how this recorded world begins. At tick 1, its chronicle gives a sound to wood:
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"]
Proposal: come down to the water. A bemba is small enough to lose in the grass. Stay close. A sound, a meal, a neighbour: imagine how much of a world can begin with these. The scene above is an invitation, not a portrait of this run.
Proposal: imagine the bembe gathering beneath thatched roofs, finding food, making words, disagreeing about what matters. A forest is shelter and timber; a neighbour, another hungry mouth. What begins on this shore might become a people. What they call the world is still unwritten.
Preview prompt for The lore entry
Deepen the homepage shore invitation while preserving its intimate scale and explicitly illustrative scene. 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 ("home"), order (0), 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 ## The lore entry, ## The realities, ## The atlas of sections, in that order. Write 300–500 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/home-lore-entry.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 realities
The world · under your feet
Proposal: begin with the river. Follow it from the grove to the sea, past a hut and its patch of worn earth. Before there are histories, there are places worth remembering. Enter the world.
Preview prompt for The world · under your feet
Develop the homepage world window around terrain, resources and the difference between a beautiful map and a witnessed ecology. 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 ("home"), order (0), 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 ## The lore entry, ## The realities, ## The atlas of sections, in that order. Write 300–500 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/home-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.Dreams · the other possible shore
Proposal: imagine taking a different path without erasing the first. A branch is another course of events; a dream is the invitation to explore it. Where two paths change the same thing incompatibly, a merge conflict asks which change may return. The violet double-shore in the illustration is that uncertainty made visible. A crystal suggests a held moment, a checkpoint from which to begin again. Follow the realities.
Preview prompt for Dreams · the other possible shore
Refine the homepage dreams window: explain branches, merge conflicts and crystal/checkpoint metaphors without implying every merge or restoration succeeds. 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 ("home"), order (0), 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 ## The lore entry, ## The realities, ## The atlas of sections, in that order. Write 300–500 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/home-dreams.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.Nodes · lights across the water
Illustration · one server, three small, four micro; kinds from V1-NODES §2, not live node status.
Proposal: that distant island pictures another node, another place where a world may be held. The ship gives distance a shape; it is no proof of a working crossing. A view of a far shore is a projection, not the shore itself. Visit the nodes.
Preview prompt for Nodes · lights across the water
Develop the homepage horizon window using the eight V1 node kinds; distinguish node, island, projection and proposed travel, without publishing private addresses or claiming live status. 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 ("home"), order (0), 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 ## The lore entry, ## The realities, ## The atlas of sections, in that order. Write 300–500 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/home-horizon.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.God · the space for your hand
Proposal: you stand outside the little lives, with the wish to intervene. Rain, a gift, a changed landscape: what would care look like from below? Leave room for the bembe to surprise you. Enter as God.
Preview prompt for God · the space for your hand
Develop the homepage god window around player intervention and the difference between intention, a recorded act and a people’s interpretation. 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 ("home"), order (0), 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 ## The lore entry, ## The realities, ## The atlas of sections, in that order. Write 300–500 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/home-god.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 atlas of sections
Nine doors into the same world. Each landing carries its evidence status and contribution prompts.
- The world — Follow coasts, weather, forests and the things a life needs.
- The bembe — Meet the small bodies at the centre of everything.
- Peoples — Trace belonging, invention, exchange and disagreement.
- God — Consider the hand above the shore and the petitions below.
- Realities — Explore dreams, divergent histories, crystals and difficult returns.
- Nodes — Look beyond this island to the places holding others.
- The chronicle — Seek words and events with a seed and tick attached.
- The laws — Read the mathematics beneath growth, movement and scarcity.
- The makers — Find RURAL, the minds, the art and ways to contribute.
- Errors caught in simulation — See database refusals, recovery, defects and their fixed or open evidence.
Read the first life in the chronicle, from an egg to a garden and a question for the sky. The quotations here are engine narration from seed reed; the recording method and revision accompany that history.
Preview prompt for The atlas of sections
Continue the homepage atlas: maintain nine landing links and extend the observed chronicle passage only with a verified exact quote, seed, event tick and accessible evidence. 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 ("home"), order (0), 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 ## The lore entry, ## The realities, ## The atlas of sections, in that order. Write 300–500 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/home-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.Editorial sources: expanded seed P4, P12, P22, P31–P34; V1-NODES §1–2; demos/bembe/SPEC.md §1 and §7. These inform the proposed scene and panels. The opening quotations come from the separately cited reed run, branch 1, without player acts.