009-remote-adapter-protocol
Remote adapter protocol
Increment 3 (design roadmap 17.1, ordinal 009): what every decision backend reached across a network must guarantee, and a versioned, transport-neutral protocol (`rustev.remote/1`) for backends served by another process. Covers capability description and negotiation at setup, attempt identity and idempotency, one total time budget per attempt, cancellation that never claims more than the remote side confirmed, validation of responses into `RawOutput` without inventing mass, a closed error taxonomy mapped onto spec 003's failure classes, explicit served-model identity (unknown is a value, never an omission), cost reporting, retained exchange records for audit and replay, and privacy options passed through and recorded. Protocol messages live in `rustev-contract`; every network implementation lives under `integrations/`. Amends no approved behavior. Approved (A-08); implemented.
Read the full pinned specification ↗Relationships
depends on
Claimed units
- establishes
{ "kind": "directory", "path": "integrations/rustev-remote-http/" } - extends
{ "nature": "additive", "spec": "002-decision-contract-and-pure-core", "unit": { "kind": "directory", "path": "crates/rustev-contract/" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Cargo.toml" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Cargo.lock" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "file", "path": "Makefile" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "directory", "path": "tools/rustev-boundaries/" } }
Source headings
- 009: Remote adapter protocol
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 Authority and provenance
- 3.2 Capability description and negotiation
- 3.3 Attempt identity and idempotency
- 3.4 One total budget and cancellation
- 3.5 Response validation into RawOutput
- 3.6 Error taxonomy
- 3.7 Model and served identity
- 3.8 Cost and privacy
- 3.9 Exchange records and replay
- 3.10 The rustev.remote/1 documents
- 3.11 HTTP binding
- 4. Out of scope
- 5. Limits of the approved vocabulary
- 6. Observable negative cases
- Acceptance
- Implementation record
- Verification
- Resolved questions
- Open questions
Frozen anchors
No frozen anchors declared.