# Implementation Mapping (Web -> Backend -> Runtime)

## Web Repo Responsibilities

1. Wallet-first UX and membership flow orchestration.
2. API contract and schema definitions.
3. Policy/legal/public messaging consistency.

## Backend Responsibilities

1. Intent/verify/quote/confirm/notify endpoints.
2. Deterministic state transitions and persistence.
3. Chain verification and policy hash enforcement.

## Runtime/Kernel Responsibilities

1. Membership and entitlement gates at activation points.
2. Fail-closed behavior for uncertain states.
3. Evidence receipt generation and retention.

## Required Integration Contract

1. Backend API shape follows `docs/api/secret-system.openapi.yaml`.
2. Policy/offer/entitlement payloads validate against schemas.
3. Runtime consumes entitlement state and policy hash from backend evidence.