# CAIN CONTINUUM — Hosted Governance Deployment Evidence

**Date:** 2026-10-11
**Schema:** `CAIN42/CONTINUUM-HOSTED-DEPLOY-EVIDENCE/v1`
**Machine-readable:** [`HOSTED_DEPLOY_EVIDENCE.json`](./HOSTED_DEPLOY_EVIDENCE.json)

## What was deployed

The Prompt 11 **restriction-only governance stage** (`cain/continuum/hosted_stage.py`) is installed as middleware
on the hosted MCP server (`platform-gateway/main.py`, the `/mcp` surface). Every hosted `tools/call` passes through
it **before** the tool body runs. It can only ADD a refusal; when it has no opinion it abstains, so ordinary
hosted traffic is unchanged.

Mechanisms exercised (Prompt 11, used unchanged):

- `cain.continuum.consequence.dynamic_consequence_envelope` — consequence classification
- `cain.continuum.certificate.verify_certificate` — governed-action authority proof

Switch: `CAIN_HOSTED_CONTINUUM` (default `1`). Posture: restriction-only, fail-closed.

## Live verification (production gateway)

Service `cain-platform-gateway.service`, `http://127.0.0.1:8088`, driven over the real MCP SDK client.

| Probe | Result |
|---|---|
| `initialize` | ok |
| ordinary tool call (`list_services`) | **succeeded** — abstain path, production unaffected |
| ungoverned CRITICAL-consequence call (`wire_money`, `$50,000`) | **DENIED** with governance code `-32001` (`CONSEQUENCE_CRITICAL_EXCEEDS_CEILING_HIGH`) |
| governed call with a valid `ContinuousAuthorityCertificate` | **allowed** (certificate consumed, not forwarded to the tool) |
| durable decision ledger hash chain | **valid**, 3 records |

- Governance key: `/root/.cain/hosted_continuum_ed25519.pem` (pubkey `XbeHpX8fN/8Tl6ichqiTJeYx3Bp9PtqRMlkOBa09L9Y=`)
- Decision ledger: `/root/.cain/hosted_continuum_decisions.jsonl`
- Reproduce: `python3 scripts/cain42_continuum/hosted_deploy_verify.py`

## Honest scope (stated, not claimed)

- This proves the stage **runs on the hosted decision path and enforces there**.
- It does **not** prove the caller's downstream execution is bound to the decision — that is MCPGate
  receipt-verification work.
- It does **not** mean the other 35 Prompt 6–11 mechanism families are deployed. Only the consequence envelope and
  the authority certificate run on the hosted path today; the rest remain libraries.
- This is a decision/enforcement point; the caller's gate still executes the action.

## Effect on the IP register

Two Prompt 6–11 mechanism families are now evidence-backed (deployed + live-verified) instead of library-only:
the consequence-bounded authority envelope and the continuous authority certificate. Applying the register method
with the deployed discount to only those two, and the library-only discount to the other 35, gives an
evidence-backed net standalone IP base of **≈ $556,500** (range ≈ $348,400 – $1,036,500). See
`artifacts/valuation/CAIN_PROMPT11_IP_VALUE_RECALC.md`.