836 B
836 B
Implementation Mapping (Web -> Backend -> Runtime)
Web Repo Responsibilities
- Wallet-first UX and membership flow orchestration.
- API contract and schema definitions.
- Policy/legal/public messaging consistency.
Backend Responsibilities
- Intent/verify/quote/confirm/status endpoints.
- Deterministic state transitions and persistence.
- Chain verification and policy hash enforcement.
Runtime/Kernel Responsibilities
- Membership and entitlement gates at activation points.
- Fail-closed behavior for uncertain states.
- Evidence receipt generation and retention.
Required Integration Contract
- Backend API shape follows
docs/api/secret-system.openapi.yaml. - Policy/offer/entitlement payloads validate against schemas.
- Runtime consumes entitlement state and policy hash from backend evidence.