feat: add typed tier assurance guardrails

SCOPE.md

@@ -15,7 +15,8 @@ adapting, and implementing pricing models across the product lifecycle. See
 - Generic pricing core under `adaptive_pricing_core/`, including:
   canonical pricing schema and validation, boundary evaluation, comparable
   customer LTV, customer-tuning solver, provider-publication primitives, Stripe
-  mapping, and governance models.
+  mapping, governance models, and typed customer assurance claims backed by
+  tenancy-posture minimums.
 - Generic framework documentation and research (`INTENT.md`, `docs/`,
   `research/`, `registry/`).
 - Project-specific proving grounds under `projects/<slug>/`, with Coulomb
@@ -36,6 +37,12 @@ adapting, and implementing pricing models across the product lifecycle. See
   they still require supplemental operational or contract logic.
 - Autonomous customer-visible pricing rollouts or irreversible pricing changes
   without human approval.
+- Treating a tier's assurance wording as authorization, placement state, or a
+  substitute for current service/provider posture evidence. The tier records
+  the commercial minimum; operational owners declare and enforce what exists.
+- Plan-derived tenant guardrail ceilings until `ADAPTIVE-WP-0010` establishes a
+  jointly accepted contract with `tenant-engine`. No ceiling schema or feed is
+  implemented yet.
 - Project-specific deployment material in generic doc paths (use
   `projects/<slug>/`).
 
@@ -44,20 +51,35 @@ adapting, and implementing pricing models across the product lifecycle. See
 - **Phase:** framework plus executable core. The repo is no longer just docs and
   research around a single MVP; it now contains reusable pricing-core modules
   and one concrete deployment.
-- **Implemented milestones:** `ADAPTIVE-WP-0003` through `ADAPTIVE-WP-0008`
+- **Implemented milestones:** `ADAPTIVE-WP-0003` through `ADAPTIVE-WP-0009`
   are finished. The repo now has canonical pricing models, explainable boundary
   validation, comparable-customer LTV simulation, customer-tuning, provider
-  shadow publication, and governance workflows.
+  shadow publication, governance workflows, and typed tier assurance claims.
 - **Generic runtime surface:** reusable implementation lives under
-  `adaptive_pricing_core/`.
+  `adaptive_pricing_core/`. Assurance claims are optional and default empty;
+  when present, the schema validates typed `{I,A,E,P,R,V}` minima, the boundary
+  engine checks wording and coupled floors, and governance requires one-time
+  approval when a tier definition adds, changes, or removes a claim.
 - **Deployment surface:** Coulomb Social remains the first proving ground under
   `projects/coulomb-pricing/observatory/`, including the dashboard/API, data
   loaders, tuning pilot, Stripe shadow-publication flow, and governed
   recommendation surfaces.
+- **Current commercial posture:** all current Coulomb pricing models remain
+  silent on isolation, availability, retention, and performance assurances.
+  The claim machinery is a preparatory guardrail; it does not invent a live
+  customer promise.
+- **Tenancy posture:** root `tenancy.yaml` declares the observatory as a local,
+  unauthenticated, single-user design-time tool (`I0/A0/E0`, `P/R: n/a`,
+  `V0`). Exposing it as a shared service is a new scope decision requiring a
+  fresh posture assessment before deployment.
 - **Execution boundary:** Stripe support is currently a provider abstraction and
   local shadow-state publisher, not live Stripe API management.
+- **Next proposed seam:** `ADAPTIVE-WP-0010` explores plan-derived tenant
+  guardrail ceilings, but its interface and ownership contract with
+  `tenant-engine` are not yet agreed and no implementation has started.
 - **Coordination:** State Hub integration (`ADAPTIVE-WP-0001`) remains the repo
-  workflow backbone for orientation, workplan tracking, and brief sync.
+  workflow backbone for orientation, workplan tracking, generated
+  `WORK-RECORDS.md`, and brief sync.
 
 ## Getting Oriented
 
@@ -67,6 +89,7 @@ adapting, and implementing pricing models across the product lifecycle. See
 - Customer tuning: `docs/CustomerTuningSolver.md`
 - Provider publication: `docs/StripePublication.md`
 - Governance workflow: `docs/GovernanceWorkflows.md`
+- Tenancy posture declaration: `tenancy.yaml`
 - Implementation roadmap: `docs/ImplementationRoadmap.md`
 - Agent instructions: `AGENTS.md`
 - Workplans: `workplans/`