Status: mixed

The laws

Lore

Dawnfolk found a word for rain.

[run: seed="reed"; tick=399; log=".zig-cache/wiki/chronicle-reed.jsonl"; locator="line 438; chronicle/39900.text"]

This record names a rain concept in seed reed. It does not expose the salience calculation or establish that the proposed natural laws are implemented. Recording method and revision.

Proposal: imagine the mathematics as weather beneath the weather. A bemba need not see an equation to live within its consequences. An equation can be a lantern for the reader: enough light to distinguish a promise from an event. This is editorial framing for CIVILIZATION-SPACE §1 and expanded seed P24.

At seed laws-017, tick 1, the log records six living bembe, one word record and unity zero. [run: seed="laws-017"; tick=1; log=".zig-cache/wiki/laws-laws-017.jsonl"; locator="line 1"]

At tick 1200 it records thirty living bembe, twenty word records, era 3 and unity 0.785. These are observations of this world, not promises about another shore. [run: seed="laws-017"; tick=1200; log=".zig-cache/wiki/laws-laws-017.jsonl"; locator="line 1200"]

Proposal: P26 invites complexity to accumulate through local acts, memory and inheritance. That ambition makes the small beginning interesting without granting it an invented destiny. The explanations below remain proposed accounts wherever the log cannot demonstrate their mechanisms.

Preview prompt for Lore

Write the laws 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 ("laws"), order (8), 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/laws-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

Parameters and determinism

Proposal: read the seed as an address in a landscape of possible rules. CIVILIZATION-SPACE §1–2 defines 64 coordinates, collected into a parameter vector. A vector is an ordered list: hunger beside learning, learning beside weather, weather beside disagreement. The implementation reference is demos/bembe/web/minds/params.mjs.

Proposal: each coordinate has a milli-value p̂ from 0 to 1000. This is a thousand-step ruler for a fraction from zero to one. The physical value uses the parameter's lower and upper limits:

v = lo + floor((hi − lo) × p̂ / 1000).

Proposal: for a range 20–200 and a milli-value of 500, this gives 110. The example explains the formula; it is not a measured coordinate of our seed. Source: CIVILIZATION-SPACE §1; params.mjs, val.

Proposal: the prior letters describe how draws occupy the ruler. Current code shapes two seed-keyed integer hash draws u and u′, each from 0 to 1000. The specification expresses the corresponding shapes as fractions.

Prior	Current integer shape	Reading
U	`u`	Uses the first draw.
T	`floor((u+u′)/2)`	Averaging favours the middle.
L	`floor(u×u′/1000)`	Multiplication favours lower values.
H	`1000−floor((1000−u)(1000−u′)/1000)`	Mirroring favours higher values.

Proposal: units matter as much as coordinates. These are catalogue ranges, not sampled parameter values. Source: CIVILIZATION-SPACE §2; params.mjs, PARAMS.

Coordinate	Range	Role
`met_hunger`	1–4	Hunger increment per need update.
`learn_rate`	200–1800	Milli-scaled learning gain.
`memory_decay`	5–80	Milli-scaled decay coefficient.
`concept_threshold`	20–200	Base salience threshold.
`split_distance`	250–700	Milli-distance between clusters.
`quorum`	500–800	Milli-scaled voting threshold.

Proposal: inheritance requires distinguishing design from implementation. Section 1 describes copying and mutating a parent's vector at founding. The current tribeParams helper derives non-first tribe vectors from the world vector using tribe ids. Faction founding copies and mutates the parent's effective vector, stores it in fp:<parameter>:<tribe> cells, and rawParams reads those cells back. Thus the helper alone is not the inheritance path. This run does not trace a founding or measure inherited values (factions.mjs::splitStep, rawParams).

Proposal: current parameter mutation adds trunc(rate×(2r−1000)/1000) and clamps to 0–1000. Here r is an integer draw in 0–1000, and trunc rounds toward zero. The older §1 expression uses floor, which differs for negative fractions. Keep that distinction when explaining the implementation.

Proposal: replay needs the same implementation, state and ordered interventions as well as the seed. CIVILIZATION-SPACE §12 requires determinism; one execution does not verify a replay. A seed is an initial condition, not the whole experimental record.

Proposal: Explain seed distributions, units, mutation, integer arithmetic and replay limits for readers. Source: docs/bembe/CIVILIZATION-SPACE.md §1–2, §12. Planned sub-page: laws/parameters-and-determinism.md.

Preview prompt for Parameters and determinism

Explain seed distributions, units, mutation, integer arithmetic and replay limits for readers. 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 ("laws"), 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/laws-parameters-and-determinism.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.

Salience: when experience becomes nameable

Proposal: salience measures the insistence of an experience upon attention. CIVILIZATION-SPACE §4 supplies an alphabet of observable cues. A cue is a model input; an English gloss is a label for readers. The label alone cannot tell us what a bemba believes.

Proposal: let Δn[q] count new events and σ[q] denote salience. Learning rate η and seed direction π[q] give:

gain = floor(η × (1000+π[q]) × Δn[q] / 1000000).

Proposal: the seed direction changes gain rather than supplying an event. Current conceptStep subtracts floor(σ[q]×δ/1000) only when (tick & 7) === 0. Gain is then added, subject to transaction room. This cadence differs from reading the older §4 equation as decay every tick. Source: CIVILIZATION-SPACE §4; concepts.mjs, conceptStep.

Proposal: vocabulary size raises the primary-concept threshold:

θ_effective = θ × (1 + floor(vocabulary_size/16)).

Proposal: the source rule requires sufficient salience and an unknown concept. Current code also requires transaction room and a word count below 124. It permits at most one primary birth per tribe per tick. The general MAX_WORDS constant is 128; these are distinct limits. Source: CIVILIZATION-SPACE §4; concepts.mjs; data.mjs.

Proposal: composites require experiences that recur together. Association lift is floor(1000×co(q,r)×N/(n[q]×n[r])) for a meaningful denominator. Both lift and co-occurrence count must reach their parameter thresholds. The v2 definition also requires disjoint leaf sets and a composition depth no greater than three. Source: CIVILIZATION-SPACE §4.1.

Proposal: borrowing qualifies any claim that naming requires a local event. Section 4.1 permits a concept observed elsewhere to enter through another people's words. Our log records counts, so it cannot identify local birth or borrowing for a particular word.

Logistics and conservation

Proposal: a ledger totals places, not merely the village store. Section 6.1 counts stores, resource nodes, carried loads, food offerings and ship cargo in Z_r. Its v2 identity is:

ΔZ_r = Regrow_r + Γ_r + Terra_r − Eat_r − Build_r − Decay_r − Salt_r − Lost_r.

Proposal: each term names an entrance or exit from the counted inventory. Current economy.mjs, conserve, computes the residual against this identity. This entry has not measured that residual.

Term	Meaning in CIVILIZATION-SPACE §6.1
Regrow	Replenishment.
Γ, `Gamma`	Gifts entering inventory.
Terra	Net creation or removal through world changes.
Eat	Food consumption.
Build	Construction consumption.
Decay	Spoilage or rot.
Salt	Salt used in preservation.
Lost	Disaster losses and a dead bemba's carried load.

Proposal: gathering and trade move goods within the ledger. A unit carried and then deposited must not become two units. Offerings remain within food inventory; their transfer is not automatically a sink. Lore lies outside this conserved-goods equation. Source: CIVILIZATION-SPACE §6–6.1.

Proposal: conservation means accounted change, not perpetual abundance. The standard runner used here omits the flows field envisaged by §6.1. Rising population therefore cannot establish a conservation pass.

Proposal: Explain logistic growth and conserved stocks using formulas, assumptions and measured limits. Source: docs/bembe/CIVILIZATION-SPACE.md §6; docs/bembe/SPEC/00-SEED-EXPANDED.md P24. Planned sub-page: laws/logistics-and-conservation.md.

Preview prompt for Logistics and conservation

Explain logistic growth and conserved stocks using formulas, assumptions and measured 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 ("laws"), 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/laws-logistics-and-conservation.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.

Belief dispersion and the split gate

Proposal: a bemba's belief position is tribe belief plus personal lean, clamped to −100–100. The coordinate mean is rounded down. Source: CIVILIZATION-SPACE §7–7.1; factions.mjs, position and dispersion.

d(x,y) = clamp(floor(1000 × Σ |x_k−y_k| / 800), 0, 1000).

Δ_t = floor(Σ d(x_i, mean_t) / member_count).

Proposal: distance measures separation; dispersion averages distance from a tribe's centre. For four coordinates, 800 is the greatest possible sum of differences. Current tribe comparisons may use a union of axes; dist clamps the result.

Proposal: clustering chooses the axis of greatest summed squared deviation. Members above its median form one group; the remainder form the other. The gap g measures distance between their coordinate means. Source: CIVILIZATION-SPACE §7.1; factions.mjs, cluster.

Proposal: the normal council path attempts a split after reconciliation fails. Population alone is insufficient; these gates must be read together. Source: CIVILIZATION-SPACE §7.1; factions.mjs, council and splitStep.

Gate	Requirement
Dispersion	`Δ_t ≥ floor(D_s/2)`
Gap	`g ≥ D_s`
Viable groups	At least ten members each.
Tribe slots	Fewer than four tribes.
Founding age	At least 400 ticks, or two days.
Reconciliation	Failed motion on the normal council path.
Safeguards	No pacing marker or unfinished faction change; sufficient transaction room.

Proposal: the sample log contains neither a council event nor split measurements. A future trace must expose those gates at the event tick before claiming a witnessed division.

Unity: five windows onto one island

Proposal: §9.1 replaces §9's older four-term formula. Current unity.mjs, unityRaw, uses five milli-scaled terms:

U_raw = clamp(floor((H + T + Λ + B + Π)/5), 0, 1000).

Term	Current definition, following CIVILIZATION-SPACE §9.1
H	Sum of `floor(s_t²/1000)`, where `s_t=floor(1000×alive_t/N)`.
T	1000 for one tribe; otherwise `floor(2000×tied_pairs/(m(m−1)))`.
Λ	1000 for one tribe; otherwise mean pairwise milli-Jaccard similarity of concept leaf sets.
B	1000 minus internal dispersion for one tribe, or mean intertribal distance for several.
Π	Peace elapsed since the last recorded hurt, capped at 1000 after five days.

Proposal: a tied pair has a tie cell at least one. Shared concepts are compared by leaf sets, not word sounds. With no living population or no tribes, current unityRaw returns zero. Source: CIVILIZATION-SPACE §9.1; unity.mjs.

Proposal: only at a day boundary does the stored index move:

U_next = clamp(U_old + floor((U_raw−U_old)/4), 0, 1000).

Proposal: other ticks retain the old value; a day is 200 ticks. The standard sample divides the stored milli-value by 1000 for display. Negative differences round down, so this is not symmetric rounding. Source: CIVILIZATION-SPACE §9.1; unityStep; headless/run.mjs, sample.

At tick 600 the run records unity 0.512. [run: seed="laws-017"; tick=600; log=".zig-cache/wiki/laws-laws-017.jsonl"; locator="line 600"]

Proposal: the log omits the five components, so it cannot explain their separate contributions. Unity is a model index, not a moral verdict. Section 9.1 and unityRewards define joy floor(U/50), lore multiplier (2000+U)/2000, and birth multiplier (1000+floor(U/4))/1000. Quorum stays at least 500; power and wonder also have era gates. This run does not isolate those effects.

Evidence

The bounded run completed with exit code 0:

node demos/bembe/headless/run.mjs --seed laws-017 --ticks 1200 --tick-ms 0 --log .zig-cache/wiki/laws-laws-017.jsonl

Checkout HEAD: 54f1d6d1a704228a1e55552e70c48a358e281582. The working tree already contained edits, including headless files; this is not a clean-commit reproduction claim. The command used standard single-world JSONL mode with no --acts, node configuration or peers. The runner begins with branch 1 and grants the initial covenant; sample rows do not expose branch identity. No node identity or intervention receipt is claimed.

Exact quotation of the final log record:

{"U":0.785,"tick":1200,"head":1215,"alive":30,"words":20,"petitions":0,"era":3}

[run: seed="laws-017"; tick=1200; log=".zig-cache/wiki/laws-laws-017.jsonl"; locator="line 1200"]

The artifact contains 1200 lines and remains under .zig-cache/wiki/ for local review. It is not a public download. Proposal: authorized evidence packaging is still needed for publication under README's Evidence rule. Claims with inaccessible artifacts must be treated as proposed during publishing review.

The laws-017 log contains no chronicle sentences, salience, resource flows or belief coordinates. The separate reed excerpt records a rain concept, without exposing its calculation.

Proposal: obtain the salience and flow records needed to test the equations.

Proposals and gaps

Fractals and movement

Proposal: P24 asks for each natural law's formula, parameters and expected statistic. The following are illustrative candidate definitions, not formulas specified verbatim by P24 or fitted to this run.

Proposed law	Candidate mathematical lens	Evidence needed
Logistic growth	`dN/dt=rN(1−N/K)`	Population and resource curves; carrying capacity K.
Logistic map	`x_next=a x(1−x)`	A discrete recurrence, distinct from continuous growth.
Fractal coasts	`z_next=z²+c`	Mandelbrot or Julia boundaries; coastline dimension across scales.
Relief	Fractional Brownian fields	Spatial correlations and specified roughness.
Lévy flights	Truncated heavy-tailed step lengths	Full movement samples, cutoffs and boundary handling.
Power laws	`P(size=s) ∝ s^(−α)` on a stated range	Settlement or wealth samples and alternative fits.
Coupled-oscillator weather	`dφ_i/dt=ω_i+Σ K_ij sin(φ_j−φ_i)+noise`	Coupling, seeded noise and measured temporal correlations.

Proposal: carrying capacity is environmental support, not simply a representation cap. P24 also requests Lotka–Volterra-style flows, requiring explicit interacting quantities and coefficients. No overshoot, collapse or predator–prey cycle is claimed here.

Proposal: a winding coast does not establish a fractal generator. A long journey does not establish a Lévy distribution. Unequal stores do not establish a power law. Each needs a scale range, enough observations and comparison with other explanations.

Proposal: Explain fractal fields, coasts and Lévy movement; distinguish proposed laws from implemented mechanics. Source: docs/bembe/SPEC/00-SEED-EXPANDED.md P24–25. Planned sub-page: laws/fractals-and-movement.md.

Preview prompt for Fractals and movement

Explain fractal fields, coasts and Lévy movement; distinguish proposed laws from implemented mechanics. 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 ("laws"), 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/laws-fractals-and-movement.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.

Power laws and complexity

Proposal: P26 requests a small beginning: sense, move, take, give, remember and signal. It proposes later needs for meaning, beauty and knowledge as culture accumulates. Acceptance asks for differing need orders across seeds and individual histories at 100000 ticks. This packet's 1200-tick run tests neither condition.

Proposal: a vocabulary count is not evidence of an evolved need for meaning. A continuation must expose the need representation and its transition in a real history. Sources: expanded seed P26; CIVILIZATION-SPACE §3–5.

Proposal: Explain heavy tails, word frequencies and local rules; state what data would test a distribution. Source: docs/bembe/SPEC/00-SEED-EXPANDED.md P24–26. Planned sub-page: laws/power-laws-and-complexity.md.

Preview prompt for Power laws and complexity

Explain heavy tails, word frequencies and local rules; state what data would test a distribution. 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 ("laws"), 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/laws-power-laws-and-complexity.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.

Continuing the evidence

Proposal: parameter replay, conservation residuals and natural-law statistics remain within the preserved subject prompts. Salience histories, split gates, unity components, weather, evolving needs and chronicle provenance need the dedicated continuations below. The four planned sub-pages remain contribution targets rather than live links. The editorial prompt catalogue preserves these continuations.