The chronicle
Lore
Three seeds, three windows: enter through the words they left behind. The quotations below are exact log lines; labels are editorial.
Preview prompt for Lore
Write the chronicle 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 ("chronicle"), order (7), 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/chronicle-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.One world: reed, from egg to era five
Grass, an egg, then another: the chronicle opens quietly. Its genesis sentence dates itself to tick zero, collected at tick one. [run: seed="reed"; tick=0; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 2"]
The opening
{"wiki":"chronicle","id":"0","observed_tick":1,"body":{"tick":0,"kind":"genesis","actors":["m0_1"],"text":"An egg stirred in the grass. Then another."}}[run: seed="reed"; tick=0; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 2"]
Gupu, a bemba still in an egg
{"wiki":"bembe","id":"m0_6","observed_tick":1,"body":{"name":"Gupu","x":24,"y":35,"tx":24,"ty":35,"age":0,"gen":0,"parent":"","tribe":"t1","alive":true,"stage":"egg","hunger":15,"energy":85,"joy":65,"clean":80,"social":60,"fear":0,"faith":20,"mood":"calm","job":"idle","carry":"","words":0,"traits":{"curious":73,"diligent":70,"pious":52,"bold":68}}}[run: seed="reed"; tick=1; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 10"]
A first word before the hatch
{"wiki":"chronicle","id":"100","observed_tick":1,"body":{"tick":1,"kind":"word","actors":["m0_3"],"text":"The first word was spoken: \"to\". It means wood."}}[run: seed="reed"; tick=1; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 3"]
Gupu becomes young: the hatch
{"wiki":"bembe","id":"m0_6","observed_tick":39,"body":{"name":"Gupu","x":24,"y":35,"tx":24,"ty":35,"age":40,"gen":0,"parent":"","tribe":"t1","alive":true,"stage":"young","hunger":15,"energy":85,"joy":75,"clean":80,"social":60,"fear":0,"faith":20,"mood":"glad","job":"idle","carry":"","words":0,"traits":{"curious":73,"diligent":70,"pious":52,"bold":68}}}[run: seed="reed"; tick=39; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 54"]
Another birth
{"wiki":"chronicle","id":"9300","observed_tick":93,"body":{"tick":93,"kind":"birth","actors":["m0_2","m93_1"],"text":"Tefu became two. Zote was born."}}[run: seed="reed"; tick=93; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 113"]
A garden completed
{"wiki":"chronicle","id":"20600","observed_tick":206,"body":{"tick":206,"kind":"build","actors":["m0_2","m0_3"],"text":"Dawnfolk finished a garden."}}[run: seed="reed"; tick=206; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 238"]
Gupu reaches adulthood
{"wiki":"bembe","id":"m0_6","observed_tick":303,"body":{"name":"Gupu","x":25,"y":27,"tx":25,"ty":34,"age":304,"gen":0,"parent":"","tribe":"t1","alive":true,"stage":"adult","hunger":32,"energy":74,"joy":57,"clean":47,"social":91,"fear":0,"faith":12,"mood":"calm","job":"gather","carry":"wood:1","words":15,"traits":{"curious":73,"diligent":70,"pious":52,"bold":68}}}[run: seed="reed"; tick=303; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 337"]
The era number supplies a second clock; each first step is dated below.
| Seed | Tick | Era | Living bembe | Exact sample and citation |
|---|---|---|---|---|
| reed | 1 | 0 | 6 | {"U":0,"tick":1,"head":12,"alive":6,"words":1,"petitions":0,"era":0} [run: seed="reed"; tick=1; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 1"] |
| reed | 377 | 1 | 10 | {"U":0.208,"tick":377,"head":388,"alive":10,"words":15,"petitions":0,"era":1} [run: seed="reed"; tick=377; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 414"] |
| reed | 766 | 2 | 16 | {"U":0.51,"tick":766,"head":779,"alive":16,"words":16,"petitions":0,"era":2} [run: seed="reed"; tick=766; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 824"] |
| reed | 1112 | 3 | 32 | {"U":0.714,"tick":1112,"head":1127,"alive":32,"words":19,"petitions":0,"era":3} [run: seed="reed"; tick=1112; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 1213"] |
| reed | 1434 | 4 | 51 | {"U":0.836,"tick":1434,"head":1449,"alive":51,"words":20,"petitions":1,"era":4} [run: seed="reed"; tick=1434; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 1591"] |
| reed | 1966 | 5 | 98 | {"U":0.904,"tick":1966,"head":1983,"alive":98,"words":20,"petitions":1,"era":5} [run: seed="reed"; tick=1966; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 2259"] |
The first recorded question
{"wiki":"petitions","id":"p1121_1","observed_tick":1121,"body":{"from":"m1067_1","tribe":"t1","kind":"question","concept":"kind","text":"Are you kind?","options":["Yes","Sometimes","No"],"status":"open","answer":"","tick":1121,"due":1571}}[run: seed="reed"; tick=1121; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 1223"]
A word’s coiner becomes bones
{"wiki":"chronicle","id":"225500","observed_tick":2255,"body":{"tick":2255,"kind":"death","actors":["m0_3"],"text":"Kopu grew still and became bones."}}[run: seed="reed"; tick=2255; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 2657"]
A request after that death
{"wiki":"petitions","id":"p2301_1","observed_tick":2301,"body":{"from":"m1849_3","tribe":"t1","kind":"grief","concept":"death","text":"Why did Kopu have to end?","options":["They are at rest","They are gone","They live in you"],"status":"open","answer":"","tick":2301,"due":2681}}[run: seed="reed"; tick=2301; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 2717"]
The last sample
{"U":0.975,"tick":3000,"head":3021,"alive":187,"words":23,"petitions":2,"era":5}[run: seed="reed"; tick=3000; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 3615"]
The window closes here. Its next morning remains unwritten.
Born words
Keys supply glosses; form holds the word, by its recorded coiner.
wood to
{"wiki":"words","id":"wood","observed_tick":1,"body":{"form":"to","uses":2,"born":1,"by":"m0_3","fidelity":20}}[run: seed="reed"; tick=1; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 4"]
good lu
{"wiki":"words","id":"good","observed_tick":4,"body":{"form":"lu","uses":1,"born":4,"by":"m0_1","fidelity":21}}[run: seed="ember"; tick=4; log=".zig-cache/wiki/chronicle-ember.jsonl"; locator="line 7"]
food si
{"wiki":"words","id":"food","observed_tick":3,"body":{"form":"si","uses":1,"born":3,"by":"m0_4","fidelity":19}}[run: seed="tide"; tick=3; log=".zig-cache/wiki/chronicle-tide.jsonl"; locator="line 6"]
food te
{"wiki":"words","id":"food","observed_tick":4,"body":{"form":"te","uses":1,"born":4,"by":"m0_1","fidelity":26}}[run: seed="reed"; tick=4; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 15"]
food li
{"wiki":"words","id":"food","observed_tick":5,"body":{"form":"li","uses":1,"born":5,"by":"m0_2","fidelity":16}}[run: seed="ember"; tick=5; log=".zig-cache/wiki/chronicle-ember.jsonl"; locator="line 9"]
water ni
{"wiki":"words","id":"water","observed_tick":33,"body":{"form":"ni","uses":2,"born":33,"by":"m0_2","fidelity":22}}[run: seed="tide"; tick=33; log=".zig-cache/wiki/chronicle-tide.jsonl"; locator="line 40"]
Preview prompt for Born words
Present exact word forms, glosses, speaker or tribe, seed and event tick; distinguish a gloss from a quote. 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 ("chronicle"), 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/chronicle-born-words.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.Born concepts
Read each pairing literally, before imagining its cultural weight.
Concept entry
{"wiki":"chronicle","id":"39900","observed_tick":399,"body":{"tick":399,"kind":"concept","actors":["m0_1"],"text":"Dawnfolk found a word for rain."}}[run: seed="reed"; tick=399; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 438"]
Concept entry
{"wiki":"chronicle","id":"33800","observed_tick":338,"body":{"tick":338,"kind":"concept","actors":["m0_1"],"text":"Dawnfolk found a word for plenty."}}[run: seed="tide"; tick=338; log=".zig-cache/wiki/chronicle-tide.jsonl"; locator="line 360"]
Concept entry
{"wiki":"chronicle","id":"72600","observed_tick":726,"body":{"tick":726,"kind":"concept","actors":["m0_1"],"text":"t1 joined dark and plenty."}}[run: seed="tide"; tick=726; log=".zig-cache/wiki/chronicle-tide.jsonl"; locator="line 755"]
Concept entry
{"wiki":"chronicle","id":"239100","observed_tick":2391,"body":{"tick":2391,"kind":"concept","actors":["m0_1"],"text":"t1 joined (dark⊕long_dry) and death."}}[run: seed="tide"; tick=2391; log=".zig-cache/wiki/chronicle-tide.jsonl"; locator="line 2453"]
Preview prompt for Born concepts
Trace cues and concept birth through records; a count alone does not prove causality. 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 ("chronicle"), 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/chronicle-born-concepts.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.Petitions: words turned toward the sky
These English text fields preserve requests and options, not independently
recovered translations or evidence of eventual answers.
Petition
{"wiki":"petitions","id":"p1601_1","observed_tick":1601,"body":{"from":"m503_1","tribe":"t1","kind":"question","concept":"love","text":"What is love?","options":["Sharing food","Staying together","Nothing useful"],"status":"open","answer":"","tick":1601,"due":2051}}[run: seed="reed"; tick=1601; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 1795"]
Petition
{"wiki":"petitions","id":"p2041_1","observed_tick":2041,"body":{"from":"m246_1","tribe":"t1","kind":"wish","concept":"rain","text":"Rain, please. The ground is cracking.","options":[],"status":"open","answer":"","tick":2041,"due":2281}}[run: seed="ember"; tick=2041; log=".zig-cache/wiki/chronicle-ember.jsonl"; locator="line 2068"]
Petition
{"wiki":"petitions","id":"p2561_1","observed_tick":2561,"body":{"from":"m0_1","tribe":"t1","kind":"question","concept":"death","text":"Why do we end?","options":["So others may begin","I do not know","It is a gift, not a loss"],"status":"open","answer":"","tick":2561,"due":3011}}[run: seed="ember"; tick=2561; log=".zig-cache/wiki/chronicle-ember.jsonl"; locator="line 2595"]
Petition
{"wiki":"petitions","id":"p1361_1","observed_tick":1361,"body":{"from":"m0_1","tribe":"t1","kind":"question","concept":"love","text":"What is love?","options":["Sharing food","Staying together","Nothing useful"],"status":"open","answer":"","tick":1361,"due":1811}}[run: seed="tide"; tick=1361; log=".zig-cache/wiki/chronicle-tide.jsonl"; locator="line 1397"]
Petition
{"wiki":"petitions","id":"p2221_1","observed_tick":2221,"body":{"from":"m0_1","tribe":"t1","kind":"grief","concept":"death","text":"Why did Bepi have to end?","options":["They are at rest","They are gone","They live in you"],"status":"open","answer":"","tick":2221,"due":2601}}[run: seed="tide"; tick=2221; log=".zig-cache/wiki/chronicle-tide.jsonl"; locator="line 2275"]
Mechanism
The hatch label follows demos/bembe/web/minds/life.mjs:285–286:
Gupu’s recorded stage changed from egg to young.
[run: seed="reed"; tick=39; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 54"]
Proposal: investigate cue salience and composite birth under CIVILIZATION-SPACE §4–4.1; these entries do not establish causality.
Proposal: expanded seed P8 and P12 request concept-composed petitions; English fields alone cannot establish their completion.
Evidence
Reproducing these windows
Revision: 54f1d6d1a704228a1e55552e70c48a358e281582.
Working tree: headless changes already present.
Node: v24.12.0; existing demos/bembe/web/bembe.wasm; branch 1.
No acts, peers, node configuration or resumed checkpoint were supplied.
Completed: interrupted:false.
Base commands (the observation import described below was added):
node demos/bembe/headless/run.mjs --seed reed --ticks 3000 --tick-ms 0 --log .zig-cache/wiki/chronicle-reed.jsonl
node demos/bembe/headless/run.mjs --seed ember --ticks 3000 --tick-ms 0 --log .zig-cache/wiki/chronicle-ember.jsonl
node demos/bembe/headless/run.mjs --seed tide --ticks 3000 --tick-ms 0 --log .zig-cache/wiki/chronicle-tide.jsonlAdd --import=data:text/javascript,<URL-encoded-hook> before the runner path.
The in-memory hook appends committed documents; it changes no simulation decisions.
Omit bembe for ember and tide. Locators count all lines from one.
observed_tick dates collection; body.tick or body.born dates events.
import {registerHooks} from 'node:module';
registerHooks({load(url,ctx,next){const r=next(url,ctx);if(!url.endsWith('/headless/run.mjs'))return r;
let s=String(r.source).replace('const debug = createDebug','const wikiSeen = new Set(); const debug = createDebug');
s=s.replace('await write(sample()); completed++;',`await write(sample());
for(const col of ['chronicle','words','petitions','bembe'])for(const [id,body]of Object.entries(view.docs[col]||{})){
const key=col+'/'+id+(col==='bembe'?'/'+body.stage:'');if(wikiSeen.has(key))continue;wikiSeen.add(key);
await write({wiki:col,id,observed_tick:view.docs.world.now.tick,body});}completed++;`);
return {...r,source:s};}});Histories and receipts
These samples and documents contain no transaction receipts. Cache logs remain local evidence.
Preview prompt for Histories and receipts
Build histories dated in ticks, with receipts and a quote index cross-linking all nine sections. 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 ("chronicle"), 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/chronicle-histories-and-receipts.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: preserve the complete evidence for public retrieval under expanded seed P7 and P34. The prompt catalogue includes these continuations.
Preview prompt for Proposals and gaps
Write a public evidence companion preserving exact quoted JSONL lines and updating the prompt catalogue through an authorized handoff. 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 ("chronicle"), 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/chronicle-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.Proposal: investigate ember’s missing concept-kind entries under CIVILIZATION-SPACE §4; ordinary word births do not explain their absence.
Preview prompt for Proposals and gaps
Write a bounded investigation of the absence of concept-kind chronicle entries in seed ember through tick 3000; distinguish ordinary word birth from cue and composite birth. 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 ("chronicle"), 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/chronicle-ember-concepts.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: compare English petitions and generated speech against expanded seed P8 and P12 before making claims about translation or composition.
Preview prompt for Proposals and gaps
Write an evidence-led comparison of logged petition text and concept-generated speech against expanded seed P8 and P12. 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 ("chronicle"), 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/chronicle-petition-composition.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.