The world
Lore
A small beginning
The chronicle opens:
An egg stirred in the grass. Then another.
[run: seed="wiki-world"; tick=0; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 4"]
This is narrator text.
The seed wiki-world begins at (25,34), west of two fords.
Its map holds meadow, grove, high ground and crystal tiles.
[run: seed="wiki-world"; tick=0; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 1"]
Proposal: imagine the crossing as a world's first invitation: a narrow place between the familiar bank and everything beyond it. This is editorial imagery for P4, not an observed belief of bembe.
Preview prompt for A small beginning
Write the world 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 ("world"), order (1), 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/world-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
Islands and continents
The base map measures 96×64 tiles. “Walkable” and “fertile” are recorded predicates. [run: seed="wiki-world"; tick=0; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 1"]
| Terrain | Tiles | Walkable | Fertile |
|---|---|---|---|
| Deep water | 2,488 | No | No |
| Shallow water | 277 | No | No |
| Beach | 306 | Yes | No |
| Meadow | 1,611 | Yes | Yes |
| Grove | 637 | Yes | Yes |
| Hill | 361 | Yes | No |
| Rock | 376 | Yes | No |
| Crystal | 15 | Yes | No |
| River | 71 | No | No |
| Ford | 2 | Yes | No |
Table evidence: [run: seed="wiki-world"; tick=0; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 1"]
Proposal: P4 expands this intimate scale into islets and continents,
with multiple landmasses, chunked coordinates and live terrain state.
World topology remains proposed.
Planned sub-page: world/islands-and-continents.md.
Preview prompt for Islands and continents
Cover coasts, rivers, landmass sizes and chunked geography. 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 ("world"), 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/world-islands-and-continents.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 river
Two recorded fords sit at (48,24) and (46,42). Journeys remain unobserved. [run: seed="wiki-world"; tick=0; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 1"]
Proposal: compare actual crossings with generation rules in
demos/bembe/web/world/terrain.mjs: north/south river walks,
spaced ford candidates and removal of unreachable walkable land.
P4 supplies the river ambition; these details need journey evidence.
Preview prompt for The river
Write an evidence-led account of the river and actual ford crossings for the BEMBE wiki; distinguish walkability predicates from journeys.
Read docs/bembe/WIKI/README.md and
docs/bembe/WIKI/CONTRIBUTING.md; consult
docs/bembe/WIKI/world.md, docs/bembe/SPEC/00-SEED-EXPANDED.md
P4, P15, P19 and P24, demos/bembe/web/world/terrain.mjs,
demos/bembe/web/minds/world.mjs and demos/bembe/web/minds/economy.mjs.
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 ("world"),
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.
Record commands, revision, parameters and interventions.
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/world-river-crossings.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.Resources and ecology
At genesis, resource nodes include the following kinds.
These are deposits.
Grouping follows demos/bembe/web/minds/data.mjs, NODE_DEF.
[run: seed="wiki-world"; tick=0; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 2"]
| Surface kinds | Underground kinds | Ocean kinds |
|---|---|---|
| 68 bushes; 70 trees | 30 ore nodes | 32 fish nodes |
| 40 rocks; 13 crystals | 18 veins | 16 salt nodes |
| 3 springs | — | — |
Table evidence: [run: seed="wiki-world"; tick=0; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 2"]
Bush n0 holds five units at tick 0 and six at tick 200.
This measures net change.
[run: seed="wiki-world"; tick=0; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 2"] [run: seed="wiki-world"; tick=200; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 9"]
Proposal: P19 seeks discoverable underground ore, crystal and water,
and fish, salt and pearls reached by boats.
Current demos/bembe/web/minds/economy.mjs distinguishes depth and medium;
verify access, depletion and regrowth before narrating them.
Pearls remain a specification subject here.
Planned sub-page: world/resources-and-ecology.md.
Preview prompt for Resources and ecology
Cover food, wood, stone, crystal, underground and ocean resources, depletion and regrowth. 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 ("world"), 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/world-resources-and-ecology.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.Preview prompt for Resources and ecology
Write the missing resource-access evidence for the BEMBE wiki: underground depth, boat or net access, extraction, depletion and regrowth; distinguish deposits from harvested stock and proposed pearls.
Read docs/bembe/WIKI/README.md and
docs/bembe/WIKI/CONTRIBUTING.md; consult
docs/bembe/WIKI/world.md, docs/bembe/SPEC/00-SEED-EXPANDED.md
P4, P15, P19 and P24, demos/bembe/web/world/terrain.mjs,
demos/bembe/web/minds/world.mjs and demos/bembe/web/minds/economy.mjs.
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 ("world"),
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.
Record commands, revision, parameters and interventions.
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/world-resource-access.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.Weather and disasters
Rain is recorded at tick 60; clear weather at tick 181. [run: seed="wiki-world"; tick=60; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 7"] [run: seed="wiki-world"; tick=181; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 8"]
A storm is recorded at tick 240; clear weather at tick 301. [run: seed="wiki-world"; tick=240; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 11"] [run: seed="wiki-world"; tick=301; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 12"]
Proposal: P15 asks weather to affect yields and moods.
P19 asks disasters to leave footprints: investigate flood losses on low ground,
drought and regrowth, quake damage and exposed deposits, blight and bushes.
demos/bembe/web/minds/world.mjs contains physical effects already;
these topics still need event evidence here.
Visible inundation needs separate rendering evidence.
Planned sub-page: world/weather-and-disasters.md.
Preview prompt for Weather and disasters
Cover seasons, weather, floods, drought, quakes and blight; distinguish physical effects from visual atmosphere. 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 ("world"), 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/world-weather-and-disasters.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.Preview prompt for Weather and disasters
Write the missing flood and disaster evidence for the BEMBE wiki: capture an event with seed and tick, affected coordinates and before/after resources or structures; distinguish physical damage from rendered inundation.
Read docs/bembe/WIKI/README.md and
docs/bembe/WIKI/CONTRIBUTING.md; consult
docs/bembe/WIKI/world.md, docs/bembe/SPEC/00-SEED-EXPANDED.md
P4, P15, P19 and P24, demos/bembe/web/world/terrain.mjs,
demos/bembe/web/minds/world.mjs and demos/bembe/web/minds/economy.mjs.
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 ("world"),
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.
Record commands, revision, parameters and interventions.
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/world-disaster-footprints.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.Fractal coasts
Proposal: P24 asks Mandelbrot and Julia boundaries for coasts and veins,
fractional Brownian motion for relief, and noisy coupled weather oscillators.
demos/bembe/web/world/terrain.mjs uses layered value noise and an oval mask;
fbm does not establish P24 acceptance.
Coastline dimension and continent-scale performance await measurements.
Preview prompt for Fractal coasts
Write the fractal-coast continuation for the BEMBE wiki; compare present value-noise terrain with proposed P24 Mandelbrot/Julia generators, and require measured coastline statistics before claiming acceptance.
Read docs/bembe/WIKI/README.md and
docs/bembe/WIKI/CONTRIBUTING.md; consult
docs/bembe/WIKI/world.md, docs/bembe/SPEC/00-SEED-EXPANDED.md
P4, P15, P19 and P24, demos/bembe/web/world/terrain.mjs,
demos/bembe/web/minds/world.mjs and demos/bembe/web/minds/economy.mjs.
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 ("world"),
order (70),
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.
Record commands, revision, parameters and interventions.
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/world-fractal-coasts.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.Evidence
Reproduction
Revision: 54f1d6d1a704228a1e55552e70c48a358e281582.
Pre-existing headless edits were present.
Both traces: branch 1, no peers, no god interventions.
The detail trace exports engine records.
Its last snapshot is line 25, tick 1200.
[run: seed="wiki-world"; tick=1200; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="line 25"]
node demos/bembe/headless/run.mjs --seed wiki-world --ticks 1200 --tick-ms 0 --log .zig-cache/wiki/world-wiki-world.jsonl
Exact log line 1200:
{"U":0.786,"tick":1200,"head":1215,"alive":39,"words":19,"petitions":0,"era":2}
[run: seed="wiki-world"; tick=1200; log=".zig-cache/wiki/world-wiki-world.jsonl"; locator="line 1200"]
Replay from the repository root:
node --input-type=module <<'JS'
import{open}from'node:fs/promises';
import{createDb,seedToU64}from'./demos/bembe/web/db.mjs';
import{engineTransport}from'./demos/bembe/headless/engine-node.mjs';
import*as minds from'./demos/bembe/web/minds/index.mjs';
import*as god from'./demos/bembe/web/god.mjs';
const seed='wiki-world',ticks=1200;
const log=await open('.zig-cache/wiki/world-wiki-world-detail.jsonl','w');
const db=createDb({transport:await engineTransport(),idSeed:seed});
const write=async r=>log.write(JSON.stringify(r)+'\n');
try{
await db.open({seed:seedToU64(seed)});
let view=await db.view({branch:1});
await db.commit({branch:1,expected_head:view.head,request_id:db.nextId(),actor:'genesis',items:minds.genesis(seed).items});
for(const power of['feed','rain','sun','bless','smite','gift','name','dream','answer','grant'])await db.grant({holder:'god',power,expires_tick:1000000,request_id:db.nextId()});
view=await db.view({branch:1});
const T=minds.terrain(seed);
await write({tick:0,kind:'terrain',w:T.w,h:T.h,start:T.start,fords:T.fords,river:T.river,counts:Object.fromEntries(T.kinds.map((k,i)=>[k,T.lists[i].length])),walkable:Object.fromEntries(T.kinds.map((k,i)=>[k,T.lists[i].every(([x,y])=>T.walkable(x,y))])),fertile:Object.fromEntries(T.kinds.map((k,i)=>[k,T.lists[i].every(([x,y])=>T.fertile(x,y))]))});
await write({tick:0,kind:'snapshot',view});
const seen=new Set();let weather;
for(let tick=0;tick<=ticks;tick++){
if(tick){
const out=minds.think(view,[],24);
const items=out.items.concat(god.expiryItems(view).filter(x=>!out.items.some(y=>y.col==='petitions'&&y.id===x.id)));
await db.commit({branch:1,expected_head:view.head,request_id:db.nextId(),actor:'minds',items});
view=await db.view({branch:1});
}
if(view.docs.world.now.weather!==weather){weather=view.docs.world.now.weather;await write({tick,kind:'weather',now:view.docs.world.now});}
for(const[key,event]of Object.entries(view.docs.chronicle||{}))if(!seen.has(key)){seen.add(key);await write({tick:event.tick,kind:'chronicle',key,event});}
if(tick&&tick%200===0)await write({tick,kind:'snapshot',view});
}
console.log(JSON.stringify({seed,ticks:view.docs.world.now.tick,head:view.head,chronicleRecords:seen.size}));
}finally{db.dispose();await log.close();}
JS
Limits of this shore
No disaster chronicle record appears in detail lines 1–25. This absence does not establish immunity. [run: seed="wiki-world"; tick=1200; log=".zig-cache/wiki/world-wiki-world-detail.jsonl"; locator="lines 1–25"]
Proposal: chronicle evidence pending for disasters and extraction (P19).
Proposal: package public evidence before publication; these cache paths are local review artifacts, not download links (P34).
Preview prompt for Limits of this shore
Write a public-evidence handoff for the BEMBE wiki world section; verify local record locators and propose an authorized retrievable evidence package without publishing cache contents implicitly.
Read docs/bembe/WIKI/README.md and
docs/bembe/WIKI/CONTRIBUTING.md; consult
docs/bembe/WIKI/world.md, docs/bembe/SPEC/00-SEED-EXPANDED.md
P4, P15, P19 and P24, demos/bembe/web/world/terrain.mjs,
demos/bembe/web/minds/world.mjs and demos/bembe/web/minds/economy.mjs.
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 ("world"),
order (80),
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.
Record commands, revision, parameters and interventions.
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/world-evidence-handoff.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.Proposals and gaps
Proposal: continue through the planned sub-pages (P4/P15/P19).
Proposal: the river needs journeys; deeper resources need access receipts; disasters need before/after footprints; fractal coasts need statistics. Their adjacent prompts define those gaps (P4/P19/P24).
Related entries: The bembe, Peoples, The chronicle and The laws.