Repository navigation
antiRea v2.8.0
An additive, advisory-only release with five new modules: the combined room guard that 2.7.3 excluded at its frozen gate, rebuilt under a new pre-registered pin with the occupancy leg it lacked (RECOMB-06), and a four-module evidence layer ported from the neighbour-dissection candidates CS-02, BS-01, CAP-01 and KT-01, each past its own frozen Step 0. Nothing on the default path changes: no existing module imports a new one, and all 758 pre-existing tests pass unmodified.
- Room guard - RECOMB-06 (
createRoomGuard, NEW, advisory, population-only): pressure v2 over 30 s ticks - the original three paths (burst: join velocity vs the room's own trailing baseline with newness and inactivity legs; sustained: 30-minute concentration; churn: fast-leave cycling) OR the occupancy leg declared up front in the new registration (estimand and FAST 0.50/600 s + DRIP 0.34/3,600 s laws verbatim fromcreateSeatOccupancySignal). One gate change declared before any number existed: the squat gate is 900 s, taken from CAND-273-1 for the same statistic, because its physical floor is ~660-720 s; the results file records the descriptive 600 s comparison openly (690 s does not meet it). Lab record (RECOMB-06, seeded simulation, 20,161 ticks per cell): pressure never high in five legitimate cells (steady, raid of existing accounts, scheduled showtime, karaoke prime time, and KARAOKE-SILENT with 60% of seat sessions silent, old and new; legitimate occupancy peaked 0.02-0.10 against the 0.34 DRIP threshold); FLOOD high at +60 s (gate 120 s), DRIP at +1,950 s (gate 45 min), CHURN at +30 s (gate 15 min) via the original paths; SQUAT high at +690 s (gate 900 s) via the occupancy leg alone, the original paths silent at every tick; SQUAT-DRIP flagged by the DRIP law 5,100 s before the last bot seated (gate >= 1,800 s of warning). Output is a room state plusrecommendStepUpForNewJoinsfor NEW joins only - no output names an identity and seated members never receive a consequence. Declared open (registration, header, LIMITATIONS, and a pinning unit test): hole A1 - a squatter emitting even 1-2 activity events escapes the occupancy leg's zero-activity definition. - Config provenance - CS-02 (
createConfigProvenance,configProvenanceHash,canonicalSerializeConfig,resolveEffectiveConfig, NEW): pins a signal's effective configuration to a SHA-256 hash over a canonical serialization of{ kind, version, options }(defaults resolved, undeclared fields excluded, keys sorted at every level, -0 normalized, unhashable values throw). Lab record (Step 0 probe over the 43 declared options of the 7 kinds shipped in 2.7.4): cross-process determinism 100%, default-equivalence 100%, mutation sensitivity 100%, 0 collisions, ~0.005 ms per pin against a 1 ms gate. The shipped port reproduces the probe's seat-occupancy digest byte-for-byte (pinned as a test vector). - Verified-neutral facts - BS-01 (
classifyWebBotAuthVerdict,classifyHostVerificationFact, NEW): the frozen semantics of identity verification as code. Over the shipped verifier's outcome space (17 failure reasons extracted mechanically from source, plus FCrDNS and published-range channels - 26 rows), verified, no-claim and every unverified outcome carry an evidence delta of exactly 0; only two spoof rows carry "EVIDENCE": the conclusive cryptographicinvalid_signaturedetail and an FCrDNS contradiction.replay_detectedsurfaces as a side event, not an identity fact; unknown reasons and future detail strings default to unverified, so hosts never key enforcement on a detail string. Facts optionally carry the CS-02 hash of the producing verifier's configuration (the BS-01 spec hook). Lab record: conformance exact on all 26 rows, spoof set exactly 2, delta 0 on both the verified and unverified sides. - Step-up proof - CAP-01 (
issueStepUpProof,createStepUpProofVerifier,stepUpChallengeHash, NEW): a three-part Ed25519 token binding one identity, the CS-02 hash of the configuration whose step-up it answers, the hash of the host's challenge config, a single-use nonce, and a lifetime capped at 3,600 s (60 s verification skew). The verifier requires a nonce-consume hook at construction and calls it exactly once per token that reaches the replay step - after structure, key, signature, claims, temporal and binding checks, never earlier. Lab record: 19/19 conformance cases exact, the hook firing exactly 4 times across the suite; the shipped port re-runs that law as unit tests. - Evidentiary roles - KT-01 (
evidentiaryRoleOf,auditEvidencePack,decorateSignalResult,EVIDENTIARY_ROLE_TABLE,ENFORCEMENT_TIER_EVIDENCE_RULES, NEW): every evidence channel's role written as law - CONVICTING only with its own passed gates, otherwise CORROBORATING; the BS-01 fact is the one conditional row (spoofed convicts, anything else corroborates).room-guardjoins the shipped signals as CONVICTING under the same rule via RECOMB-06. Pack audit is mechanical: an unknown channel or a mis-claimed role is invalid, and a pack with no fired CONVICTING item is ineligible for consequences however many corroborating items fire. Lab record: role table complete over all shipped kinds and pin channels, decoration fidelity verified against the real factories'evaluate()outputs, audit invariant exact on 10/10 frozen packs, tier restatement covering tiers 0-3 with tier 3 forbidden for inferred evidence. - Not in this release: the C27+C35 pin conversion (advisory to tiered consequences) remains behind the 2026-11-16 farm gate and a production stratum-assignment mechanism - the evidence layer above is its foundation, not its activation. Five dissection candidates (CS-01, CS-03, AN-01, AN-02, AN-03) have not run their Step 0 and ship in no form.
- Suite: 812 tests (810 pass, 0 fail, 2 pre-existing RSA-PSS skips), up from 758 in 2.7.4 - 35 new tests across the five modules at release, plus a 19-test verification battery added the same day (full RECOMB-06 lab-population replay through the shipped guard, property tests, evidence-pipeline integration and BS-01/KT-01 drift guards), zero pre-existing expectations changed.