022-jev-production-transport
Production transport and served identity for the Jev adapter (amends 012)
The separately reviewable spec 012 amendment that backlog item RUSTEV-010 and spec 012 R-3 require before production use: a Jev binding is production-eligible only when its transport pins a model version and every answered exchange proves the served identity against that pin. Defines the qualification of TypeSafe's direct API with a pinned version, the evidence under which Gateway pinning could be accepted instead, and the transport, TLS, timeout, connection, privacy and cost-reconciliation facts a production binding records. Development evidence with `served: unknown` is never relabeled as production evidence. Approved (A-21) with the additions of tracking issue #76 child C3 (section 3.8). Approval authorizes implementation of the no-network stage; live stages stay inside R-29's testing cap, and no deployment is authorized.
Read the full pinned specification ↗Relationships
depends on
amends
Claimed units
- extends
{ "nature": "amending", "spec": "012-jev-integration", "unit": { "kind": "directory", "path": "integrations/rustev-jev/" } } - 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": "scripts/acceptance/" } }
Source headings
- 022: Production transport and served identity for the Jev adapter (amends 012)
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 Production eligibility
- 3.2 Direct transport with a pin
- 3.3 Gateway pinning as an alternative
- 3.4 Transport facts of a production binding
- 3.5 Cost reconciliation
- 3.6 Evidence and requalification
- 3.7 Qualification stages
- 3.8 Additions from the tracking issue (C3)
- 4. Out of scope
- 5. Observable negative cases
- Acceptance
- Verification
- Implementation record
- Questions settled at approval
Frozen anchors
No frozen anchors declared.