CEG 0.1 landed — RATCHET's §5.7 + §11.2.1 calibration-package coordination

[emooreatx]

Top-line

CIRISRegistry just published CEG 0.1 at FSD/CEG/. Supersedes FSD-002. RATCHET is the calibration-package authority for LensCore's open-vocabulary detectors — this issue captures the coordination items.

Reading discipline — §0.5 fractal-self

CEG README's anti-Cartesian-default callout. RATCHET advisory flags are emitted against entities that are already relational composites; flags are inputs to NodeCore's moderation flow, never autonomous state changes. Please anchor RATCHET reviewer feedback against this frame.

What RATCHET owns (CEG §5.7)

Advisory anti-Sybil / Counter-RII flags (NEVER autonomously modify ledger state):

• ratchet:flag:out_of_distribution_voting
• ratchet:flag:coordinated_voting_cluster
• ratchet:flag:density_anomaly
• ratchet:flag:expertise_attestation_anomaly
• ratchet:flag:counter_rii:{layer}
• ratchet:flag:harassment_pattern

Critical enforcement: ratchet:flag:* cannot be sole evidence for slashing:*. WA quorum is the load-bearing gate.

What's load-bearing for RATCHET (calibration-package authority)

§11.2.1 axis-vocabulary discipline

RATCHET ships the hash-pinned calibration packages that operationalize:

• LensCore §5.5.3 detection:correlated_action:{axis} axes
• LensCore §5.5.5 detection:distributive:access:{resource_type} types

For each axis, the calibration package MUST document (pinned via emissions' evidence_refs[]):

1. Measurement procedure
2. Threshold function
3. Statistical floor
4. Evidence-shape requirement
5. Polarity semantics

§15.2 R2 — version-transition discipline

The first test was the correlated_action_v{N+1}:from:emergent_deception_v{N} chain at RATCHET deployment. Version-transition windows are an adversarial straddle surface (per CEG 0.1 red-team review): adversaries can spread correlated action across the v{N} → v{N+1} window so neither calibration sees the full pattern. RATCHET should document in-flight transition discipline.

§13.5 discipline pattern

Wire format resists self-declaration primitives. RATCHET flags compose with cross-attestations (other RATCHET instances + LensCore detector emissions + NodeCore moderation flow) to produce the verdict. No single RATCHET instance is sole evidence for downstream action.

What changed from FSD-002 v1.4.3 → CEG 0.1

[Same as Agent issue.] RATCHET-specific:

• §11.2.1 axis-vocabulary discipline now load-bearing for RATCHET-calibrated detector emissions
• §15.2 R2 acknowledged as a known bet — RATCHET-side mitigation pending
• ratchet:flag:* polarity column populated (signed)

0.2 roadmap (RATCHET-relevant)

1. TupleHash128 + domain-separation labels canonical-bytes redesign — general
2. Multi-party witness directory admission — does not affect RATCHET directly
3. Full OpenAPI export
4. Machine-readable FSD/CEG/dimensions.json — useful for axis-vocabulary lookup

RATCHET 3.0 adoption plan

• CCP-conformance: ensure all ratchet:flag:* emissions follow §4 envelope shape
• Document operational definitions for all LensCore detector axes per §11.2.1 five-point spec
• Calibration-package version-transition discipline per R2 — document the in-flight straddle defense
• Pin calibration-package hashes via evidence_refs[] on all RATCHET emissions
• Document that ratchet:flag:* is never sole evidence for slashing:* — surface this in RATCHET-side documentation
• Adopt the §0.5 fractal-self frame in RATCHET-side documentation

Coordination

Calibration-package work coordinated with LensCore (consumer). Spec changes route through CEG §11.2 at CIRISRegistry.

[emooreatx]

CEG 0.1 → 0.2 wire-break (FYI/correction to prior issue)

CIRISRegistry just shipped CEG 0.2 (commit 4b27130) — one wire-break vs 0.1: §5.2 attestation-ladder prefixes renamed to mechanism-only, per §1.3.1 T2 honestly applied. L-numbers name a ladder-position (verdict-shape), not a mechanism; only mechanism belongs in the wire prefix.

What changed

Was (CEG 0.1)	Now (CEG 0.2)
attestation:l1:self_verify	attestation:self_verify
attestation:l2:hardware	attestation:hardware_rooted
attestation:l3:registry_consensus	attestation:registry_consensus
attestation:l4:license_validity	attestation:license_validity
attestation:l5:agent_integrity	attestation:agent_integrity

The L1-L5 ladder is now consumer-side composition per new §8.1.9 Policy I — Attestation-Ladder Composition. Reference composition function shipped; different consumers may order/weight rungs differently.

Why

CIRISVerify v3.7.0 had caught the principle correctly; CEG 0.1 inherited the FSD-002 v1.0 L-numbered shape without re-examining against the T2 gate. Same anti-pattern shape as v1.2's detection:emergent_deception → detection:correlated_action rename. §13.1 records the deprecation.

Migration

• Consumers SHOULD accept deprecated attestation:l{N}:* during 0.1 → 0.2 transition
• Producers MUST emit only mechanism form going forward
• Deprecated form rejected at admission once §11.2 amendment formally retires it (target: CEG 0.3)

RATCHET-specific impact

No direct impact — RATCHET owns §5.7 advisory flags, not §5.2. Just FYI for the rename.