God
Lore
Dawnfolk asked the sky: "What is love?"
[run: seed="reed"; tick=1601; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 1794; chronicle/160100.text"]
This is a recorded petition in seed reed. Its English wording is engine
narration, not proof of concept-composed speech or an answer from God.
Recording method and revision.
Proposal: picture a hand above the island, able to put food on the ground or change the sky. Below it, a bemba has a life of its own. The distance between those two lives is the subject of this section: what is offered, what is asked, and what anyone can know about an answer. This is narrator framing for expanded seed P9 and P15, not a creature's testimony.
In seed god-silence, the first recorded tick had six living bembe
and one word. The recorder counted no open petitions. These are
the narrow facts of that moment, rather than a description of what
the six believed. [run: seed="god-silence"; tick=1; log=".zig-cache/wiki/god-god-silence.jsonl"; locator="line 1"]
{"U":0,"tick":1,"head":12,"alive":6,"words":1,"petitions":0,"era":0}
By tick 300 in the same run, the recorded living count was nine and the word count fifteen; open petitions were counted as zero at that tick. No player acts were supplied. This establishes change during this interval of player silence, without establishing a stance, a prayer, or the cause of that change. [run: seed="god-silence"; tick=300; log=".zig-cache/wiki/god-god-silence.jsonl"; locator="line 300"]
{"U":0.21,"tick":300,"head":311,"alive":9,"words":15,"petitions":0,"era":0}
Proposal: silence need not be imagined as an empty world. It can be the space in which a people continues living while its questions go unheard. P9 asks for remembered answers and different responses to their absence. These two recorded moments offer no access to anyone's private meaning.
Proposal: an act and an interpretation are separate things. Rain can be a change in the world; gratitude is a response attributed to someone within it. P9 asks peoples to develop different models of god. Leave room between the falling water and the belief that someone sent it.
Preview prompt for Lore
Write the god 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 ("god"), order (4), 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/god-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
Acts and mandates
Proposal: Cover blessing one, many, area or all, smiting, weather, terraform, targeting and receipted authority. Source: demos/bembe/SPEC.md §1; docs/bembe/SPEC/00-SEED-EXPANDED.md P15, P21, P33. Planned sub-page: god/acts-and-mandates.md.
Proposal: the following reads present code, awaiting act-level
evidence under P15 and P21. demos/bembe/web/god.mjs::buildAct
builds physical transactions; demos/bembe/web/minds/god.mjs::handle
processes reactions. An applied message distinguishes an effect
already committed from a fallback effect applied by the minds.
The requested minds/god.mjs source lives under web/minds/.
| Act | Proposal: current code reading, unobserved here; P15/P21 |
|---|---|
| Feed | Integer tile coordinates create a bush with amount 30 and a scent memory lasting 12 ticks. |
| Rain | Sets world weather to rain; the reaction adds rain memories and can grant matching petitions. |
| Sun | Sets world weather to clear; the reaction can grant matching sun petitions. |
| Smite | Requires a living target; patches it to dead, bones, idle and grieving, records fear, and reduces trust by 12. |
| Bless one | Selects a living target and patches joy, fear, hunger and faith. |
| Bless many | Selects an explicit list or a disk of living bembe around a centre. |
| Bless all | Selects living bembe in the supplied view, not across every network node. |
| Gift | Adds equal bounded amounts of food, wood and stone to a tribe's accounts. |
| Answer | Uses petition decision helpers, not a buildAct power case. |
| Name | Changes a living target's name after filtering and truncation. |
| Terraform | Writes a terrain override, removes resource nodes at the tile, and handles displaced bembe. |
| Weather | Sets a weather kind and records a bounded-duration override memory. |
| Wonder | The interface's Wonder builds place, a completed wonder structure. |
Proposal: feed's bush is an opportunity to eat, not a patch to every
stomach. In the minds' food reaction, nearby bembe receive joy,
faith and fear changes; some hungry bembe are redirected toward
the tile. The direct hunger change there is zero. P15's consequences
need a trace of the food being used, not just its arrival.
Proposal: smite is a death, not a temporary fright. The reaction
invokes killNow, adds witness reactions and grief, and empties
nearby trees or bushes within its stated range. P9 requires
remembered cruelty. Chronicle strings in this source are literals
until a run retrieves them; they are not observed speech here.
Proposal: blessing defaults to one. Many accepts at most 24 listed
living IDs, or uses squared Euclidean distance around a centre.
Its radius defaults to six and is clamped to one through twelve.
All uses aliveBembe(view), excluding bones. P21's area blessing
is partly represented by a disk; a painted brush needs evidence.
Proposal: the physical blessing adds three tribe-specific joy steps, subtracts twenty fear and ten hunger, and bounds the values. Faith rises fifteen without explicit scope, otherwise four. The early blessing reaction handles touched tribes and returns before the older single-target switch case. Do not combine both paths into an invented total. This is a P21 implementation reading.
Proposal: gift defaults to 25 of each resource, clamped to 1–500. The builder uses the requested tribe or the first tribe. Its inbox message carries no tribe field; the minds locate a nearby tribe using fallback coordinates. P15 evidence should check both the account receiving resources and the people reacting.
Proposal: naming accepts letters, numbers, spaces, apostrophes and hyphens, trims the result, and takes at most sixteen JavaScript string units. Empty results are refused. The minds add a response for the living target. Under P9, a cheerful source literal does not prove that a particular bemba accepted a particular name.
Proposal: authority normally belongs to god. Terraform and place
fall back to gift authority, weather to rain authority; a matching
current specialized mandate can be used instead. Bless-many and
bless-all normalize to bless. P15 asks for receipted acts:
constructed items alone do not prove engine acceptance.
Preview prompt for Acts and mandates
Cover blessing one, many, area or all, smiting, weather, terraform, targeting and receipted authority. 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 ("god"), 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/god-acts-and-mandates.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.Stances and petitions
Proposal: Explain remembered acts, silence, atheism and faction-specific responses; quote only observed petitions. Source: docs/bembe/CIVILIZATION-SPACE.md §8; docs/bembe/SPEC/00-SEED-EXPANDED.md P9. Planned sub-page: god/stances-and-petitions.md.
Proposal: a petition has a sender, tribe, kind, concept, text,
options, status, answer, creation tick and deadline. Prayer need
not create such a record. The pray job in minds/life.mjs can
change individual faith and fear, make offerings, or speak toward
god. P9 invites a distinction between practice and pending request.
Proposal: minds/tribe.mjs checks shortages, drought, night fear,
grief, questions and later power requests. It stops new petitions
at four open for a tribe or fourteen overall, and for an atheist
tribe. A separate concept-weighted scheduler in concepts.mjs
does not prove that every request comes from born concepts.
P9 and P15's fuller request model remains an evidence target.
| Kind | Proposal: active petition source reading; P9/P15 |
|---|---|
| Need | Food shortage together with a hungry fraction can open a food request. |
| Wish | Drought or fearful night can produce rain or light requests. |
| Grief | Death, civilization era and chance can open a question about someone who ended. |
| Question | The existing question table supplies eligible questions and options. |
| Power | River, outside and out have distinct technology or era conditions. |
Proposal: answerItems sets granted, denied or answered status
and stores at most eighty string units of answer. In
web/app.mjs::decide, a grant requests a mandate before committing
the decision; the default mandate lifetime is 300 ticks. P15's
mandate requirement does not make every wish physically come true.
Proposal: minds/god.mjs::answer can update beliefs, invoke answer
shock, change trust and affect selected members. Questions, grief
and powers follow different branches. Some reactions inspect
words such as yes or denied as well as status. P9's interpretation
is not an unrestricted natural-language conversation here.
Proposal: web/god.mjs::translate combines word fidelity with
exposure count, revealing or masking tokens deterministically.
This display confidence is not proof that god understood intent.
P9's phrasing should be investigated with the original petition
beside the displayed text, rather than through a gloss alone.
Faith and stances
Proposal: P9 has three distinct scales to investigate: one bemba's
faith, a tribe's beliefs.god, and world trust. They occupy
different records and update paths. Average faith cannot speak
for every member; trust is not the narrator's verdict on god.
| Stance | Proposal: concepts.mjs::regime boundaries; P9 |
|---|---|
| Devout | Tribe god belief greater than 40. |
| Doubting | Tribe god belief from −40 through 40 inclusive. |
| Atheist | Tribe god belief less than −40. |
| Bargaining | Requested by P9; not a fourth result of this classifier. |
| Rival-god | Requested by P9; not a fifth result of this classifier. |
Proposal: faithEvent weights answers and unsolicited good acts
against ignored petitions and cruelty, using tribe parameters.
Its result is bounded to −100 through 100. Daily faithDay
relaxes tribe belief toward a piety-derived prior. P9's silence
is not a universal countdown from devotion to atheism.
Proposal: answerShock remembers the last answer tick, caps
silence at twenty days, and uses a tribe-specific surprise gain.
Devout and doubting tribes receive different extra updates.
Selected atheist members' faith can move in opposite directions
according to god-axis lean. P9 asks for divergent tribes in runs;
reading these branches does not satisfy that demonstration.
Under a silent god
Proposal: petitionUpkeep distinguishes unanswered requests from
self-resolved ones. An expired request without an answer can
reduce trust above −30, lower its sender's faith, and register
an ignored event. A need resolved by world conditions expires
with answer self, avoiding that penalty. P9 needs both sequences.
Proposal: neglect bookkeeping uses temporary petx memory;
petition records can later be removed. expiryItems separately
marks overdue open requests expired using the world tick.
P9's remembered absence needs a sequence, not just a final count.
Proposal: the silence run cannot demonstrate these transitions. Its samples contain no faith, tribe belief or prayer jobs. Zero open petitions at tick 300 means neither that nobody ever asked nor that belief ceased. P9 leaves the deeper question open.
Preview prompt for Under a silent god
Explain remembered acts, silence, atheism and faction-specific responses; quote only observed petitions. 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 ("god"), 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/god-stances-and-petitions.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.Wonders and objects
Proposal: Cover the proposed catalogue, discovery, naming, histories and consequences of objects beyond understanding. Source: docs/bembe/SPEC/00-SEED-EXPANDED.md P21–22. Planned sub-page: god/wonders-and-objects.md.
Proposal: terraform translates land to meadow, water to shallow, forest to grove, raise to hill and lower to beach; recognized terrain kinds are also accepted. Coordinates must lie inside the seed's terrain. P15 requires the override to become visible; a written terrain cell alone is not a picture of a changed shore.
Proposal: water conversion deletes structures at the tile and marks the reaction cruel when that happens. Living occupants move to nearest eligible land by Manhattan distance; no destination means refusal. A grove can add a tree below 300 resource nodes. P15 evidence needs occupants and structures before and after.
Proposal: Weather supports rain, clear, storm and drought, with
sun normalized to clear. Duration defaults to 200 ticks, clamped
to 1–400, and a god:weather memory records the override.
Plain Rain and Sun do not build the same duration item.
In the minds, good weather can answer matching need petitions;
drought and storm add memories. P15 asks for yields and moods:
this packet's run measured neither.
Proposal: Wonder creates a level-one structure with progress 100 and a built tick, using the target's tribe or the first tribe. The builder refuses at 160 structures; the minds process nearby witnesses and a sky-act cue. P21 asks for properties, discovery, names and histories. A generic wonder does not establish reactor heat, danger, pilgrimage, or a named discovery.
The node of origin
Proposal: P17 asks an act to carry origin across the horizon. The sending node need not be the node receiving the act. This is provenance, not a new deity inferred by the narrator. The single-island run here cannot establish that journey.
Proposal: headless/http.mjs validates origin.node and
origin.at, can attach local origin when queuing, and includes
origin in responses and logs. An accepted act writes a god
chronicle item whose text contains JSON with label and origin:
the schema has no dedicated chronicle origin column. This P17
implementation path awaits a cited receiving receipt.
Proposal: headless/sync.mjs commits the built items without
adding the HTTP origin-bearing chronicle item. Ordinary JSONL
mode also omits provenance from its samples. P17 must therefore
be investigated per transport, rather than asserted uniformly.
Proposal: a transported field does not demonstrate cultural inference. P17 also asks another tribe to update its god model after a blessing or a ship from blessed people. That needs both the sending receipt and receiving people's records, keeping machine provenance distinct from the people's interpretation.
Preview prompt for The node of origin
Cover the proposed catalogue, discovery, naming, histories and consequences of objects beyond understanding. 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 ("god"), 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/god-wonders-and-objects.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
The reproduction command for the quoted records was:
node demos/bembe/headless/run.mjs --seed god-silence --ticks 300 --tick-ms 0 --log .zig-cache/wiki/god-god-silence.jsonlIt exited zero and printed:
{"game":"BEMBE","ticks":300,"U":0.21,"tick":300,"head":311,"alive":9,"words":15,"petitions":0,"era":0,"interrupted":false}The quoted log records are exactly line 1 at tick 1 and line 300 at tick 300. They are samples, not chronicle quotations. The run used the local WASM engine, ordinary single-island mode and branch 1, without an acts file, peers or injected intervention. Zero tick delay sets wall-clock pacing; 300 is the recorded tick.
The checkout reported 54f1d6d1a704228a1e55552e70c48a358e281582.
Uncommitted changes already existed, including headless files;
this revision alone does not identify the complete executed tree.
Reproduction must retain that limitation.
The cache log is a local review artifact, not a public download. Mixed status separates the two cited samples from proposed behavioural accounts. Cache contents must not be published implicitly by rendering this page.
The reed excerpt records a petition to the sky; the separate
god-silence sampler records only counts.
Proposal: P9, P15 and P21 still need direct act and reaction records. A petition alone establishes neither an answer nor its consequences.
Proposals and gaps
Proposal: the preserved prompts extend the four planned subjects: acts and mandates; stances and petitions; wonders and objects; beyond the world. Every unobserved act remains within these evidence gaps, including successful effects and refusals. P15/P21 contributions should show accepted transactions and reactions, with before-and-after values for numerical claims.
Proposal: P9's five-stance design remains separate from the current three-way classifier. Compare two tribes under one act, recording priors and answer histories. P9's requested 5,000-tick silence was not tested by the 300-tick sampler cited here.
Proposal: the ordinary recorder cannot settle silent belief, timed weather, or origin. The additional prompts below target those gaps separately. The overview prompt is also this page's continuation prompt. The editorial catalogue preserves all live prompts.
Silence evidence
Proposal: under P9, retrieve prayers, ignored and self-resolved
petitions, and individual and tribe faith before narrating absence.
Keep the aggregate god-silence samples as limited observations.
Preview prompt for Silence evidence
Write evidence for silence, prayers, expired versus self-resolved petitions and faith changes in the BEMBE wiki, retaining the limits of the god-silence aggregate samples. Read docs/bembe/WIKI/README.md, docs/bembe/WIKI/CONTRIBUTING.md and docs/bembe/WIKI/god.md; consult docs/bembe/SPEC/00-SEED-EXPANDED.md P9, demos/bembe/web/god.mjs and demos/bembe/web/minds/god.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 ("god"), 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/god-silence-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.Weather evidence
Proposal: P15 needs timed Weather and plain Rain/Sun examined separately, with yields, moods, expiration and petition reactions. The presence of a memory item alone does not measure duration.
Preview prompt for Weather evidence
Write evidence for timed Weather versus plain Rain and Sun in the BEMBE wiki, recording duration, yields, moods and petition reactions against P15. Read docs/bembe/WIKI/README.md, docs/bembe/WIKI/CONTRIBUTING.md and docs/bembe/WIKI/god.md; consult docs/bembe/SPEC/00-SEED-EXPANDED.md P15, demos/bembe/web/god.mjs and demos/bembe/web/minds/god.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 ("god"), 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/god-weather-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.Origin evidence
Proposal: P17 needs a sending node, receiving island, accepted receipt and receiving tribe's model, with transport identified. One provenance field cannot establish the whole journey.
Preview prompt for Origin evidence
Trace an act from its sending node to its receiving island under P17 for the BEMBE wiki, distinguishing HTTP and TCP provenance and recording the receiving tribe god model. Read docs/bembe/WIKI/README.md, docs/bembe/WIKI/CONTRIBUTING.md and docs/bembe/WIKI/god.md; consult docs/bembe/SPEC/00-SEED-EXPANDED.md P17, demos/bembe/headless/http.mjs, demos/bembe/headless/sync.mjs, demos/bembe/web/god.mjs and demos/bembe/web/minds/god.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 ("god"), 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. 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/god-origin-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.Beyond the world
Proposal: Explain the out concept, sandbox marks, knowledge requests, advisors and land rights; label grant-dependent proposals. Source: docs/bembe/SPEC/00-SEED-EXPANDED.md P12–14. Planned sub-page: god/beyond-the-world.md.
Proposal: the answer code can change an out belief and emit a final event. It does not establish that a sandbox directory was created or that a people reached an external world. P12–P14's grant-dependent designs remain beyond this packet's observations.
Preview prompt for Beyond the world
Explain the out concept, sandbox marks, knowledge requests, advisors and land rights; label grant-dependent proposals. 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 ("god"), 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/god-beyond-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.