CC 0.7 §2.6.4: EphemeralResponse enters Tier-1 (§2.9) — Standards Action

[emooreatx]

Ratifies the wire-vocabulary row for MessageType::EphemeralResponse, which CIRISEdge shipped in v18.2.0 without this amendment (the typed request/response correlation that made Edge::send a working API — it had been returning Err on success). CIRISConformance's test_520_wire_vocabulary drift gate caught it correctly: wheel-only, not in manifest.

The placement is derived from this manifest, not chosen:

• Tier 2 is structurally unavailable. §3.1: "CIRISEdge holds no Tier-2 kind range by design… This is intentional, not an omission." The substrate's own reply mechanism has no Private-Use code point to ride.
• §3.3's ethical-primitive test is the EXIT test toward Tier 2, and what exits must carry "the schema, its canonicalization, AND the convenience API into the range steward's own repo." This variant has none of those to carry: edge never parses the payload and the canonicalization is the outer envelope's.

So §2.9 states it as Tier-1 by exclusion rather than implying an ethical weight it does not have. Count 25 → 26.

Interop severity, for the record: an unratified variant is refused at parse by a conforming peer with an unknown-variant error enumerating the accepted set — so the pre-amendment consequence was fail-closed non-delivery of typed ephemeral replies against older peers, never a silent acceptance.

The conformance gate derives its accept-set from the §2 table (not a hand-copied list), so it goes green on the hash re-pin with nothing else to update.

Tracked as CIRISEdge#527.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FejjcCbAbRFpLkmcgCDLEY

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.