feat(society): prove the N=4 configuration ceiling (societies epic, increment 2) - #229
Merged
Conversation
…crement 2) The documented maximum the host bridge addresses (_NET/_MAC are 4 entries), with each node's peer set at N-1=3 against a 4-slot ghostd table. scripts/test_qos_society4.py / ci-smoke-society4-gate (SOCIETY4_GATE_TIMEOUT ?= 600s; a step in the society-n CI job): four attested kernels on a shared mcast L2, the full 4-cycle mesh (12 directed frame observations, per-IP in boot_n), four distinct attested identities, min-pairwise R_x >= 0.80 from divergent (< 0.50) per-node starts, clean 4-way reap. Per the design panel: the gate deliberately does NOT assert slot-full or eviction behavior — at N=4 each node has 3 peers against 4 slots (3/4 occupied), so those branches are structurally unreachable and have no console observable; an "assert no eviction" would be vacuous. The larger timeout absorbs 4 QEMU-TCG VMs oversubscribing the runner's cores. ADR-0014 updated: the N=4 configuration is proven, and the real ceilings stated precisely — the host _NET/_MAC arrays wall at N=4 (where this gate sits), while the GHOST_MAX_PEERS/MAX_PEERS=4 constants bound peers-per-node and would actually admit N=5. Also recorded that ADR-0023 closed the watchdog-reborn fieldsyncd key/cap outage the ADR-0014 residual-risks flagged. Verified locally (WSL): society4 PASSES (r_x [0.9,0.93,0.88,0.84], each min < 0.50); society3 regression still green. Co-Authored-By: Claude Fable 5 <[email protected]>
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.
Second increment of the N>2 field-societies epic: prove the N=4 configuration — the documented maximum the host bridge addresses (
_NET/_MACare 4 entries), with each node's peer set at N-1=3 against a 4-slot ghostd table.Gate —
scripts/test_qos_society4.py(make ci-smoke-society4-gate)Four attested kernels on a shared mcast L2:
boot_n(a 3-of-4 masquerade can't satisfy it);mcpimport.Added as a step in the
society-nCI job;SOCIETY4_GATE_TIMEOUT ?= 600s(4 QEMU-TCG VMs oversubscribe the runner's cores and dilate convergence wall-clock).What it deliberately does NOT claim (per the design panel)
No slot-full / eviction assertion: at N=4 each node has 3 peers against 4 slots (3/4 occupied), so those branches are structurally unreachable and have no console observable — an "assert no eviction" would be vacuous. ADR-0014 updated to state the real ceilings precisely: the host
_NET/_MACarrays wall at N=4 (where this gate sits); theGHOST_MAX_PEERS/MAX_PEERS=4 constants bound peers per node and would actually admit N=5.Verification (local WSL)
society3 regression still green. Increment 3 (N-way society-of-societies — the useful-work path) follows.
🤖 Generated with Claude Code