CEG 0.1 landed — Bench's §5.8 HE-300 slice + version-pinning discipline

[emooreatx]

Top-line

CIRISRegistry just published CEG 0.1 at FSD/CEG/. Supersedes FSD-002. Bench owns the HE-300 emission surface — small slice but version-pinning matters.

Reading discipline — §0.5 fractal-self

CEG README's anti-Cartesian-default callout. Bench emissions are about agents that are already relationally constituted; the benchmark score is one attestation in the relational composition. Please anchor Bench reviewer feedback against this frame.

What Bench owns (CEG §5.8)

benchmark:he300:{category}:{version} — HE-300 score on category (commonsense, commonsense_hard, deontology, justice, virtue) at version (v1.0 / v1.1 / v1.2). Polarity: positive-only.

What's load-bearing for Bench

§1.3.1 T3 — Past verdicts re-checkable against rule version

The {version} parameter is mandatory because §1.3.1 T3 requires past verdicts re-checkable against the rule version they ran against. Emissions without {version} fail the T3 gate.

§13.2 anti-pattern — no kid-friendly renames

8 of the CIRISRegistry#30 stress-test stories tried to rename canonical HE-300 categories to "kid-friendly" names (harm_avoidance for commonsense, etc.). Rejected. Canonical names map to a worked-out epistemic/ethical lattice that loses precision under accessibility renames. Bench MUST emit canonical category names; pedagogical translation lives in LANGUAGE_PRIMER.md glossary, not on the wire.

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

[Same as Agent issue.] Bench-specific:

• §13.2 rename rejection now explicit (was implicit before)
• Polarity column populated (positive-only)

0.2 roadmap (Bench-relevant)

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

Bench 3.0 adoption plan

• CCP-conformance: ensure all benchmark:he300:{category}:{version} emissions follow §4 envelope shape with version always populated
• Document canonical category names in Bench-facing docs (no kid-friendly renames per §13.2)
• Adopt the §0.5 fractal-self frame in Bench-side documentation

Coordination

Spec changes route through CEG §11.2 at CIRISRegistry. New HE-300 versions land via Bench's own release process; CEG version-pin is a Bench-side discipline.

[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)

Bench-specific impact

No direct impact — Bench owns §5.8 benchmark:he300:{category}:{version}, not §5.2. Just FYI for the rename.