030-bedrock-backend
Hosted model platform backend: AWS Bedrock
A remote decision backend under `integrations/rustev-bedrock/` for Amazon Bedrock over two wires on the `bedrock-runtime` endpoint, Converse and the OpenAI-compatible Responses API, signed with SigV4 over Rustev's existing hyper and rustls stack. A versioned binding document puts wire, region, model or inference profile, declared destination regions, residency policy, parameters, structured output mode, price table and reserved members for later operations into the artifact identity. A host-supplied `ModelPolicy` (deny wins, no default allowlist) is evaluated at bind time and again at runtime start. Wave 1 serves `classify`, `proposition` and `rubric` as `Label` outputs, because neither wire documents token log-probabilities; `rank`, `generate`, `extract` and Guardrails screening are added by their own specs into members reserved here. Amends spec 001 only by adding a cloud SDK dependency family to the boundary check. Approved (A-26) under the 2026-10-16 delivery work order; implementation is complete, with a recorded live exchange on each wire. The work order authorizes paid Bedrock smoke and probe calls on synthetic or spec 023 admitted data within R-29's total testing cap across all providers (USD 10 since A-75 raised it from USD 5); the owner supplies AWS credentials, whose absence blocks only the live stage. Approval makes no quality, residency-compliance or production claim.
Read the full pinned specification ↗Relationships
depends on
depended on by
Claimed units
- establishes
{ "kind": "directory", "path": "integrations/rustev-bedrock/" } - 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": "scripts/acceptance/" } } - extends
{ "nature": "additive", "spec": "001-boundaries-and-authority", "unit": { "kind": "directory", "path": "tools/rustev-boundaries/" } } - extends
{ "nature": "additive", "spec": "031-public-api-and-release-family", "unit": { "kind": "directory", "path": "tools/rustev-release/" } } - extends
{ "nature": "additive", "spec": "012-jev-integration", "unit": { "kind": "directory", "path": "integrations/rustev-jev/" } }
Source headings
- 030: Hosted model platform backend: AWS Bedrock
- 1. Purpose
- 2. Territory
- 3. Behavior
- 3.1 Position, authority and provenance
- 3.2 The binding document
- 3.3 Residency and inference profiles
- 3.4 Model policy
- 3.5 Credentials, signing and transport
- 3.6 The Converse and Responses wires
- 3.7 Operations and output kinds
- 3.8 Served identity
- 3.9 Cost and spend
- 3.10 Failure taxonomy
- 3.11 Reachability probe
- 3.12 Operations added by later specs
- 3.13 Boundary check extension
- 3.14 Exchange records, replay and live smoke
- 3.15 How the binding principles are kept
- 4. Out of scope
- 5. Observable negative cases
- Facts relied on
- Acceptance
- Verification
- Implementation record
- Decisions at approval
Frozen anchors
No frozen anchors declared.