# Proposal Readiness Live Canary

## Outcome

The updated read-only bridge was executed from the local branch against the
live VPS Postgres container without deploying it or writing to the database.
All three currently approved proposals classify as intent-approved but not
contract-applyable.

## Live Readback

| Proposal | Type | Readiness | Apply payload | Contract applyable |
| --- | --- | --- | --- | --- |
| `14fa5ecc-ac7a-41c1-807d-a2e85b936617` | `attach_evidence` | `approved_needs_apply_payload` | `false` | `false` |
| `ac036c9d-20a0-4ffe-881f-57d6b7bacf22` | `attach_evidence` | `approved_needs_apply_payload` | `false` | `false` |
| `a64df080-8502-42e2-98f4-9bbdecb8da73` | `attach_evidence` | `approved_needs_apply_payload` | `false` | `false` |

`production_worker_enabled` is deliberately `null`: proposal readback cannot
prove service enablement, strict payload validity, authorization, or apply.

## Boundary

This is a live read-only database canary of the proposed bridge code. It proves
the classifier produces the correct readiness boundary for current rows. It is
not deployed-runtime proof and it does not normalize, restage, approve, or apply
any proposal.
