Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
emooreatx merged 1 commit into from
Aug 21, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion manifests/WIRE_VOCABULARY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Signatures are hybrid throughout: Ed25519 (mandatory) + ML-DSA-65 (`signature_pq

## 2. Tier 1 — constitutional `MessageType` variants (closed; CC §4.5.1 / Standards Action)

25 variants. Each row: **delivery class** · one-line contract. Body structs live in the named consumer crates; edge stays domain-agnostic.
26 variants. Each row: **delivery class** · one-line contract. Body structs live in the named consumer crates; edge stays domain-agnostic.

### 2.1 Attestations (signed standing claims)

Expand Down Expand Up @@ -116,6 +116,14 @@ The integrity primitive here is **`sha256(body)` itself**, not an inner signatur
| `BlobChunkBody` | Ephemeral (response) | Carries chunk bytes; persist `put_blob_chunk` atomically verifies `sha256(bytes) == chunk_sha256` or returns `ChunkMismatch`. |
| `BlobChunkMiss` | Ephemeral (response) | Chunk-level typed refusal sharing the `ContentMiss` `MissReason` vocabulary. |

### 2.9 Substrate reply correlation

Tier-1 by exclusion, not by ethical weight: the §3.3 ethical-primitive test decides what leaves for Tier 2, and what leaves must carry a schema, a canonicalization, and an API into a range steward's repo. This variant has none to carry — edge never parses its payload, and its canonicalization is the outer envelope's. It is also not expressible as Tier 2 for a structural reason: **edge holds no `kind` range** (§3.1, by design), so the substrate's own reply mechanism has no Private-Use code point available to it. Tier-1 is where it lives.

| Variant | Delivery | Contract |
|---|---|---|
| `EphemeralResponse` | Ephemeral (response) | Carries a typed handler's response bytes back to the `Edge::send` waiter that requested them, correlated by `in_reply_to` = the request's `body_sha256`. Distinct from `OpaqueResponse`, which is the *app*-tier reply on a steward's `kind` range; this is the substrate's own. Excluded from the durable-ACK matcher exactly like `OpaqueResponse` — its `in_reply_to` is request/response correlation, never a durable-send acknowledgement. Edge is domain-agnostic to the payload: it moves the bytes the handler returned and parses none of them. |

---

## 3. Tier 2 — app-tier opaque channels (Private Use; delegated to range stewards)
Expand Down
Loading