Nodes
Lore
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"]
This genesis record comes from the local reed run on branch 1. It gives the
proposed network a concrete life to preserve; it supplies no remote-node or
migration evidence. Recording method and revision.
Proposal: imagine a horizon with more than one morning behind it.
The near shore is only the place from which Eris looks.
Other islands have their own clocks and unfinished histories.
P2 of docs/bembe/SPEC/00-SEED-EXPANDED.md asks for this
network of separately running worlds. The horizon here is
an illustration of that intention, not an observed crossing.
In seed nodes-015, the first sample recorded six living bembe
and no words. That is one local world's first recorded tick.
[run: seed="nodes-015"; tick=1; log=".zig-cache/wiki/nodes-nodes-015.jsonl"; locator="line 1"]
Proposal: a node is the keeper behind an island: a process
responsible for its clock and saved state. An island is the
world it keeps; a projection is the view another keeper receives.
A bemba belongs in the world, not in a hardware diagram.
This distinction comes from docs/bembe/NODES.md §1,
narrowed for V1 by docs/bembe/V1-NODES.md §1.
Preview prompt for Lore
Write the nodes 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 ("nodes"), order (6), 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/nodes-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.Islands on the horizon
Proposal: P2 asks connected nodes to reveal their islands.
V1 makes the meeting modest: a greeting names the keeper
and its worlds; a projection supplies one island's view.
A distant shore should carry an age as well as a name.
A last sighting is not proof of its present condition
(docs/bembe/V1-NODES.md §1.2–1.5).
Proposal: seeing is different from sailing.
docs/bembe/NODES.md §5 designs transfers of bembe, words,
beliefs, and cargo. V1's opening comparison excludes ship frames.
A projected bemba has not thereby migrated into Eris's island.
The planned sub-page is nodes/islands-on-the-horizon.md;
its path is a contribution target, not a live destination.
Preview prompt for Islands on the horizon
Explain ownership, HELLO, PROJ, peer loss and remote god acts; distinguish projections from migration. 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 ("nodes"), 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/nodes-islands-on-the-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.What lives on when Eris is off
Proposal: P30 imagines the desktop as a window onto independent
node processes. Closing that window should leave remote islands
advancing on their owners' clocks. Turning the laptop off stops
its local computation. Continuity depends on other machines
remaining powered, their services running, and their stores
recoverable (docs/bembe/SPEC/00-SEED-EXPANDED.md P30;
docs/bembe/NODES.md §7).
Proposal: “lives on” describes separate keepers, not immortality.
A disconnected projection cannot certify the unseen island's
next dawn. A checkpoint preserves a past state without producing
another tick. P32 requests replicas and recovery elsewhere;
this page's local observation demonstrates neither
(docs/bembe/SPEC/00-SEED-EXPANDED.md P29–32).
Mechanism
Server, small and micro
Proposal: P3 distributes work among one server, several small
nodes, and several micro nodes. These V1 defaults come from
docs/bembe/V1-NODES.md §2. They are design budgets,
not measurements or claims of deployment.
| Proposed V1 kind | Islands | Tick | Peer poll | RAM cap | Disk cap |
|---|---|---|---|---|---|
| Server | 8 | 500 ms | 5000 ms | 12288 MiB | 49152 MiB |
| Small | 3 | 600 ms | 5000 ms | 3072 MiB | 12288 MiB |
| Micro | 1 | 2000 ms | 15000 ms | 768 MiB | 6144 MiB |
Proposal: default island counts differ from the maximums of
32, 4, and 1. A micro node keeps one island at a slower default
clock; its name does not rank the worth of its inhabitants.
Self-guards and service limits are separate layers of care
(docs/bembe/V1-NODES.md §2–3; code context:
demos/bembe/headless/node.mjs and headless/run.mjs).
Proposal: V1's server collects logs and offers releases.
P32 additionally assigns it long memory in shared storage.
Collecting accounts of events is different from replicating
the island records that produced them (docs/bembe/V1-NODES.md
§1.3, §1.5, §6; expanded seed P32).
Planned sub-page: nodes/server-small-and-micro.md.
Preview prompt for Server, small and micro
Compare node kinds, long memory, storage, capacity and clocks without claiming deployment or uptime. 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 ("nodes"), 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/nodes-server-small-and-micro.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.HELLO and projections
Proposal: V1 HELLO is GET /hello. Its response introduces
identity, kind, version, time, islands, peers, and doctor status.
Island summaries include head, tick, population, era, tribe count,
and word count (docs/bembe/V1-NODES.md §1.2).
Proposal: GET /proj/<node>/<n> supplies an owned island's
view, hash, head, tick, fixed epoch 1, empty changes list,
and latest twenty chronicle entries. The head names a committed
version; the tick names simulation time. They are different
coordinates (docs/bembe/V1-NODES.md §1.2; code context:
demos/bembe/headless/http.mjs, snapshot publication).
Proposal: V1 projections are bounded full views, not P31's
future compact summaries. A view over 1 MiB is refused.
Polling requests a projection when the remote head advances;
an equal head with a different hash is an integrity fault
(docs/bembe/V1-NODES.md §1.2, §1.5).
Proposal: V1 uses plain LAN HTTP with source-address restrictions
on writes. The older NODES.md §4 proposes mutually pinned
TLS Sessions. V1's opening comparison defers TLS and keys;
its pins are allowed IPv4 addresses. These designs must not
be combined into an unsupported security promise
(docs/bembe/V1-NODES.md §1.4; code context:
headless/http.mjs, transport summary).
Proposal: a remote God act is a request to the owner, not
a local edit to a projection. V1 specifies expiry, origin,
request identifiers, and applied or refused receipts.
A queued response is not yet an applied act; retries reuse
the identifier for replay (docs/bembe/V1-NODES.md §1.4–1.5).
No remote act was attempted in this page's run.
The laptop’s tiny island
Proposal: P31 asks for 128 MB RAM, one CPU core, and 1 GB disk:
at most one tiny island plus summaries of watched worlds.
Larger islands should use network compute. This research target
is distinct from V1's 768 MiB VM micro budget
(docs/bembe/SPEC/00-SEED-EXPANDED.md P31).
Proposal: the tiny home should let the laptop participate
without carrying the archipelago. The older desktop sanctum
in NODES.md §7 supplies that image, but its larger budget
does not establish P31 compliance. P30 now requests a native
GPUI window; the older Tauri-shell design is not that application
(docs/bembe/SPEC/00-SEED-EXPANDED.md P30–31).
Proposal: compact projections, smaller worlds, measurements,
and archival remain P31 research requirements. P32 adds island
migration, sharded storage, default replication factor two,
and replica recovery. A projection file alone demonstrates
none of these (docs/bembe/SPEC/00-SEED-EXPANDED.md P31–32).
Planned sub-page: nodes/the-laptops-tiny-island.md.
Preview prompt for The laptop’s tiny island
Explain the proposed 128 MB, one-core, 1 GB budget and remote compute, distinct from V1 VM micro caps. 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 ("nodes"), 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/nodes-the-laptops-tiny-island.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.Care and recovery
Proposal: P29 gives every keeper a doctor. V1 §5 names
the checks and four report states: healthy, repaired, degraded,
and failing. Healthy describes one report's checks, not every
possible future failure (docs/bembe/V1-NODES.md §5).
Proposal: this care map condenses V1 §5. No check or repair
below was exercised by the sampler. Code context:
demos/bembe/headless/doctor.mjs and headless/run.mjs.
| Proposed check | Measurement | Specified remedy or limit |
|---|---|---|
| Chain | Image name, parse, restored head and hash | Quarantine bad image; choose older valid image; fail if none |
| Disk | Store, logs, filesystem space | Archive at 90%; stop ticks at hard 97% |
| RAM | Resident memory against cap | Report excess; no memory repair |
| Peers | Recent contacts | Reset backoff and re-poll |
| Clock | Peer wall-clock skew | Report beyond five seconds |
| Logs | Writable directory and retention | Recreate, reopen, prune past retention |
| Version | Own version against peers | Warning, not fatal mismatch |
| Ticks | Last commit and recent refusals | Restore and restart; repeated restarts can fail |
| Boot | Version confirmation | Attempt rollback on next start |
Proposal: checkpoints preserve past worlds, not second live
keepers. V1's runner normally retains eight images, while
disk-pressure care can archive images past keep-three.
Recovery may re-live ticks since the last image
(docs/bembe/V1-NODES.md opening comparison, §5–7;
docs/bembe/NODES.md §3).
Proposal: at the hard disk limit V1's HTTP service should remain
reachable while ticking stops. Reachability and an advancing
world are different questions. Current headless/run.mjs has
different stopping paths for finite runs and offline mode;
the service scenario is not this finite sampler's result
(docs/bembe/V1-NODES.md §5, §7).
Planned sub-page: nodes/care-and-recovery.md.
Preview prompt for Care and recovery
Explain logs, doctor, checkpoints, rollback and resilience limits. 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 ("nodes"), 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/nodes-care-and-recovery.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.Updates without losing the shore
Proposal: V1 §6 gives P29's frequent updates a verification
chain: fetch metadata, check size and SHA-256, unpack a matching
version, then swap current and previous release pointers.
A rejected download is not an installed release
(docs/bembe/V1-NODES.md §6).
Proposal: a new boot remains unconfirmed until ten completed
rounds. A subsequent start finding that version unconfirmed
attempts rollback unless the previous release is also known bad.
A boot confirmation shows startup progress, not an exhaustive
world test (docs/bembe/V1-NODES.md §6; code context:
demos/bembe/headless/update.mjs). No update was performed here.
Evidence
Exact local records
The first record reported six living bembe, no words, no open petitions, and era zero at tick 1. [run: seed="nodes-015"; tick=1; log=".zig-cache/wiki/nodes-nodes-015.jsonl"; locator="line 1"]
{"U":0,"tick":1,"head":12,"alive":6,"words":0,"petitions":0,"era":0}
At tick 60 the sample reported ten words; it does not identify their forms or speakers. [run: seed="nodes-015"; tick=60; log=".zig-cache/wiki/nodes-nodes-015.jsonl"; locator="line 60"]
{"U":0,"tick":60,"head":71,"alive":6,"words":10,"petitions":0,"era":0}
The last record reported eleven words, six living bembe, no open petitions, and era zero. Counts at different ticks do not identify whether the same individuals survived. [run: seed="nodes-015"; tick=120; log=".zig-cache/wiki/nodes-nodes-015.jsonl"; locator="line 120"]
{"U":0,"tick":120,"head":131,"alive":6,"words":11,"petitions":0,"era":0}
Reproduction and limits
The command exited 0; its final sample matches log line 120. [run: seed="nodes-015"; tick=120; log=".zig-cache/wiki/nodes-nodes-015.jsonl"; locator="line 120"]
node demos/bembe/headless/run.mjs --seed nodes-015 --ticks 120 --tick-ms 0 --log .zig-cache/wiki/nodes-nodes-015.jsonl{"game":"BEMBE","ticks":120,"U":0,"tick":120,"head":131,"alive":6,"words":11,"petitions":0,"era":0,"interrupted":false}Evidence context: revision
54f1d6d1a704228a1e55552e70c48a358e281582, with pre-existing
working-tree modifications including headless code.
The revision alone does not identify those changes.
The command used the single-world sampler, branch 1,
with no acts, peers, listener, node configuration,
or persistent store directory. Zero timer delay was an
experiment parameter, not a measured service rate.
Evidence artifact: .zig-cache/wiki/nodes-nodes-015.jsonl,
120 sample records. Locators are one-based exact lines
containing the cited tick. This local cache is review evidence,
not a public download. Code context is
demos/bembe/headless/run.mjs, run() and sample().
The nodes-015 quotations are numerical samples. The separate
reed genesis excerpt above is a verified local chronicle record.
Proposal: obtain a remote island's chronicle with node identity and receipts before presenting any network event as witnessed.
Proposals and gaps
Continuation
Proposal: greeting, seeing, acting, migrating, and surviving failure each need distinct traces. The preserved overview block serves as the continuation prompt. Other preserved blocks cover the four planned sub-pages, which remain contribution targets, not live links (wiki README, Information architecture).
The additional gaps below have their own prompts, preserved in the editorial catalogue.
Update and rollback evidence
Proposal: obtain exact verification, swap, boot, and rollback
records before describing a successful upgrade (V1 §6).
Seed nodes-015 provides no update trace.
Preview prompt for Update and rollback evidence
Write update and rollback evidence for the BEMBE wiki, using docs/bembe/V1-NODES.md §6 and docs/bembe/SPEC/00-SEED-EXPANDED.md P29. Read docs/bembe/WIKI/README.md, docs/bembe/WIKI/CONTRIBUTING.md and docs/bembe/WIKI/nodes.md. Return exactly one UTF-8 Markdown document, no enclosing code fence or commentary. Begin with --- delimited front matter in this exact order: title (nonempty quoted string matching H1), section ("nodes"), 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 plain-text 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 claim must cite [run: seed="<seed>"; tick=<event tick>; log="<path>"; locator="<line or record key>"] matching runs or begin Proposal:. Never invent runs, quotes or receipts; separate specification, code and observation. Include a verbatim observed chronicle quote when verified, otherwise state Proposal: chronicle evidence pending. Record reproduction command, revision, parameters, interventions and island identity; preserve retrievable evidence. Use a bemba for one, bembe for many, BEMBE for the game. Include a continuation prompt and one per remaining gap repeating this complete output contract with concrete paths. Submit docs/bembe/WIKI/contrib/nodes-updates-and-rollback.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.Continuity and replicas
Proposal: observe remote ticks across desktop shutdown for P30; separately demonstrate migration and replica recovery for P32. A cached projection is not evidence of either.
Preview prompt for Continuity and replicas
Write evidence of what continues while Eris is off for the BEMBE wiki. Read docs/bembe/WIKI/README.md, docs/bembe/WIKI/CONTRIBUTING.md, docs/bembe/WIKI/nodes.md, docs/bembe/NODES.md §7, docs/bembe/V1-NODES.md §7 and docs/bembe/SPEC/00-SEED-EXPANDED.md P30–32. Distinguish remote ticks, local shutdown, migration and replica recovery. 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 matching H1), section ("nodes"), 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 plain-text 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 claim must cite [run: seed="<seed>"; tick=<event tick>; log="<path>"; locator="<line or record key>"] matching runs or begin Proposal:. Never invent runs, quotes or receipts; separate specification, code and observation. Include a verbatim observed chronicle quote when verified, otherwise state Proposal: chronicle evidence pending. Record reproduction command, revision, parameters, interventions and island identity; preserve retrievable evidence. Use a bemba for one, bembe for many, BEMBE for the game. Include a continuation prompt and one per remaining gap repeating this complete output contract with concrete paths. Submit docs/bembe/WIKI/contrib/nodes-continuity-and-replicas.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.Chronicle and public evidence
Proposal: obtain a verbatim node chronicle entry with island, seed, tick, and record locator, then preserve a retrievable public review artifact under an authorized scope (wiki README, Evidence rule). Sample counts are not creature speech. Extend the local genesis excerpt with a witnessed remote event.
Preview prompt for Chronicle and public evidence
Write the missing node chronicle excerpt and public evidence handoff for the BEMBE wiki. Read docs/bembe/WIKI/README.md, docs/bembe/WIKI/CONTRIBUTING.md, docs/bembe/WIKI/nodes.md, docs/bembe/V1-NODES.md §1.2 and docs/bembe/NODES.md §9. Distinguish exact chronicle text from sample counts; do not invent a speaker or translate unrecorded words. 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 matching H1), section ("nodes"), 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 plain-text 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 claim must cite [run: seed="<seed>"; tick=<event tick>; log="<path>"; locator="<line or record key>"] matching runs or begin Proposal:. Never invent runs, quotes or receipts; separate specification, code and observation. Include a verbatim observed chronicle quote when verified, otherwise state Proposal: chronicle evidence pending. Record reproduction command, revision, parameters, interventions and island identity; preserve retrievable evidence. Use a bemba for one, bembe for many, BEMBE for the game. Include a continuation prompt and one per remaining gap repeating this complete output contract with concrete paths. Submit docs/bembe/WIKI/contrib/nodes-chronicle-evidence.md or a pull request adding that file. Emit each continuation or gap prompt as a standalone HTML comment: concatenate "<" with "!-- prompt: " to open, then the full prompt text, then concatenate "--" with ">" to close. Do not fence these comments. Use exactly the seven front matter fields; JSON strings use double quotes and status is one bare enum value. Never copy placeholder values into the final document.