feat(tick): community.bsl c07-c08 — the DG-2 readout (PUBLISH, the 2026-08-18 sitting) - #693
Merged
Merged
Conversation
…26-08-18 sitting) DG-2 was adjudicated at the 2026-08-18 sitting (the #564 docket, delegated provenance, morning-reviewable): PUBLISH contestation + dominant-tendency. Task 9's Steps 4-5 land, un-stopped: - c07-contestation (carrier): the normalized Shannon entropy of the published simplex (entities/consciousness.py:274-291) — per-component 1e-10 guard (the (/ 1c 10000000000) quotient), divided by (log (* 1.0c 3)) — the divisor COMPUTED through the pack's new (intrinsic log :params (real) :returns real :cost 40) declaration (the FIRST content declaration of log — the spec's ":cost provenance" paragraph: the first declarer sets the number, pinned by the conformance vectors thereafter). THE 1-ulp DIVISOR DIVERGENCE, recorded (D210): libm's log(3) is 1.0986122886681096, one ulp BELOW CPython's glibc math.log(3) — the engine's pinned soft-float crossing is this port's law, the mirror divides by the engine's value, and the conformance pins are bit-exact against the PORT's arithmetic (on the landed vectors the per-component p*log(p) ulp differences cancel; a future world whose vector does not cancel re-opens with a written tolerance policy). - c08-dominant-tendency (carrier): the argmax with the ruled tie order LIBERAL > REVOLUTIONARY > FASCIST at 1e-6 (entities/consciousness.py:167-191, epsilon :189) — the same shape consciousness/p8-dominant-worldview runs over the class surface. - §8a row 1's copies-agree test LANDED: dominant_tendency_ties_match_the_class_surface_rule over the new ninth content world (community-tie-conformance.bscn — the landed consciousness-ternary world PLUS one carrier, three equal-weight orgs, one SETTLER-kind community over the tied member; the class side is the landed tv-tie-all-true witness) — both readouts pick LIBERAL. - The consciousness.bsl amendment (Step 5's theory-line edit, gated until the answer): "ONE DECLARED HOME" becomes "TWO DECLARED HOMES, parity-guarded", with its own frozen-anchor correction (:177-192 → :167-191, epsilon :189) — one comment line, as ruled. - The skip gate holds for the readout: a no-org community is written NOTHING (honest-null, proven in world 3). - Golden pins re-measured for the pack's intentional growth (this crate's own goldens, never a §6.5 ceremony): worlds 1-4's after-hashes and the arc's tick-3 pair moved (c07/c08 write the two new fields on non-skipped communities); the seam/collision/empty pins did NOT move (their communities are all skip-gated — the readout writes nothing there, measured); the tie world's pin is new (9 content worlds now). - Fuel (per-world, max+1, over all nine worlds incl. the tie world's co-load): c07 900, c08 336. Fired arithmetic: world 1 is 32 = 30 + c07:1 + c08:1; the collision world is 39 = 37 + the two readout rules on the shared carrier. - D210/D211 move from gated to landed in the register; D225 records the readout's landing. Gates: rust:check (incl. the citation sentinel), qa:regression (byte-identical 12 + E5b), qa:vault-regression-ci (both goldens byte-identical), check:quick, the grammar-sync pytest, manifest-sync (the tie row), the corpus digest re-pinned at 84 content files. No Python engine source touched. Co-Authored-By: Kimi Code <noreply@moonshot.cn>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
Changes are coherently scoped to the DG-2 readout landing, with deterministic pins and conformance coverage updated to match the new content behavior.
Pull request overview
This PR lands the DG-2 (2026-08-18) ruling to publish Community’s readout fields by adding c07-contestation (normalized Shannon entropy) and c08-dominant-tendency (ruled argmax + tie-break order) to community.bsl, along with a new “tie world” conformance scenario and updated golden/hash pins to keep the tick corpus deterministic and regression-guarded.
Changes:
- Add Community readouts
c07(contestation vialog(3)divisor) andc08(dominant tendency with ruled tie order) and declare thelogintrinsic in content. - Introduce a new tie conformance world to pin “copies-agree” behavior across class-surface and community-surface tie-breaks; wire it into content sets and golden tests.
- Update scenario declarations, corpus digests, goldens/hashes, and reference docs to reflect the landed DG-2 behavior and the
logintrinsic/divisor contract.
File summaries
| File | Description |
|---|---|
| rust/crates/babylon-tick/tests/tick_goldens.rs | Adds the tie world golden and re-pins community world hashes impacted by c07/c08. |
| rust/crates/babylon-tick/tests/community_conformance.rs | Updates conformance expectations for contestation/dominant and adds DG-2 readout + tie-world assertions. |
| rust/crates/babylon-tick/tests/community_arc_conformance.rs | Updates fired-count arithmetic to include c07/c08 when packs are co-loaded. |
| rust/crates/babylon-tick/content/scenarios/community-tie-conformance.bscn | New scenario that pins the “copies-agree” tie behavior across both readout surfaces. |
| rust/crates/babylon-tick/content/scenarios/community-solidarity-seam-conformance.bscn | Declares the new community readout fields in the seam scenario. |
| rust/crates/babylon-tick/content/scenarios/community-floor-conformance.bscn | Declares the new community readout fields in the floor scenario. |
| rust/crates/babylon-tick/content/scenarios/community-empty-conformance.bscn | Declares the new community readout fields in the empty scenario. |
| rust/crates/babylon-tick/content/scenarios/community-degenerate-conformance.bscn | Declares the new community readout fields in the degenerate scenario. |
| rust/crates/babylon-tick/content/scenarios/community-decay-arc-conformance.bscn | Declares the new community readout fields in the arc scenario. |
| rust/crates/babylon-tick/content/scenarios/community-cost-modifier-conformance.bscn | Declares the new community readout fields in the cost-modifier scenario. |
| rust/crates/babylon-tick/content/scenarios/community-conformance.bscn | Declares the new community readout fields in the main conformance scenario. |
| rust/crates/babylon-tick/content/scenarios/community-carrier-collision-conformance.bscn | Declares the new community readout fields in the collision scenario. |
| rust/crates/babylon-tick/content/scenarios/community_conformance.py | Updates the mirror/oracle script to use the engine-pinned LOG3 divisor and removes “DG-2-gated” labeling. |
| rust/crates/babylon-tick/content/rules/consciousness.bsl | Updates the dominant-worldview material-basis note to reflect the second parity-guarded home and correct frozen anchor lines. |
| rust/crates/babylon-tick/content/rules/community.bsl | Adds (intrinsic log ...) and implements c07 + c08 readout rules under DG-2 PUBLISH. |
| rust/crates/babylon-tick/content/content-sets.toml | Registers a new community/tie content set (scenario + prelude + rules + consumers). |
| rust/crates/babylon-bsl/tests/content_corpus_digests.rs | Re-pins digests for updated content and adds the new tie scenario digest. |
| docs/reference/bsl-language.rst | Documents DG-2 readout landing and log/divisor divergence, and notes current membership-kind implementation status. |
Review details
- Files reviewed: 18/18 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
This was referenced Aug 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The DG-2 adjudication at the 2026-08-18 sitting (#564 docket, delegated provenance, morning-reviewable) came back PUBLISH contestation + dominant-tendency — Community port plan Steps 4-5 land, un-stopped:
entities/consciousness.py:274-291), per-component 1e-10 guard, divisor computed through the pack's new(intrinsic log :params (real) :returns real :cost 40)declaration — the first content declaration oflog. The 1-ulp divisor divergence is recorded (D210): libm'slog(3)is one ulp below CPython's glibcmath.log(3); the engine's pinned soft-float crossing is this port's law.entities/consciousness.py:167-191).community-tie-conformance.bscn) — both readouts pick LIBERAL.tests/baselines/**unmoved): worlds 1-4's after-hashes + the arc's tick-3 pair moved; seam/collision/empty pins did not (skip-gated).Local gates at commit time
rust:check,qa:regression, vault regression,check:quick, grammar-sync, manifest-sync, digest — all green.