# Cross-Surface Resolution Packet - 2026-07-09

Generated UTC: `2026-07-09T21:38:00Z`

## Verdict

Clone-proven, not production-applied.

The mapped rich proposal packet handles canonical claim/source/evidence/claim-edge rows. This companion packet handles the one currently safe non-claim write: updating strategy anchor `47f128a0-36c5-4b60-97d4-48c32fa48bc7` after Claim D exists.

## Safe Write

- Table: `public.strategy_node_anchors`
- Anchor: `47f128a0-36c5-4b60-97d4-48c32fa48bc7`
- From node: `52bc4264-330e-489d-920c-a493fd2d985a` (`Multi-agent public intelligence`)
- Old claim: `d0000000-0000-0000-0000-000000000005`
- New claim: `e6ce4e36-15d2-53bc-8b74-dda0efc095c1`
- New meaning: active Leo policy is justified by the boundary claim that internet finance is a candidate mechanism, not Teleo's telos.

## Clone Proof

Disposable database: `teleo_cross_surface_rehearsal_20260709`

Sequence:

1. Created disposable clone from live `teleo` using `pg_dump | psql`.
2. Applied mapped base packet in clone: `7` claims, `15` sources, `11` claim edges, `17` claim evidence rows.
3. Ran cross-surface preflight:
   - anchor still pointed to old claim `d0000000-0000-0000-0000-000000000005`
   - Claim D existed
   - approval source existed
   - telos anchor already existed
   - governance gate rows existed
4. Ran cross-surface authorized commit in clone.
5. Postflight read back anchor pointing to Claim D with weight `0.85`.
6. Ran cross-surface delete rollback.
7. Ran mapped base packet delete rollback.
8. Clone returned to zero generated mapped rows and original anchor state.
9. Production stayed unchanged: generated rows remained `0/0/0/0`, and production anchor still points to old claim with weight `0.7`.
10. Dropped disposable DB and removed host/container temp packet files.

Cleanup readback:

- `disposable_db_exists`: `0`
- host tmp removed: yes
- container tmp removed: yes
- `leoclean-gateway.service`: `active`
- `MainPID`: `3252143`
- `NRestarts`: `0`

## Constraint Found And Fixed

The first clone attempt failed because `public.strategy_node_anchors` rejects a row with both `claim_id` and `source_id` set. The packet was corrected so the anchor points only to Claim D. The approval source remains required as provenance and is linked through Claim D's evidence rows from the mapped base packet.

## Explicit Deferrals

These approved fragments are not safely writable through the current schema:

- `governance_gate:quality-gate`: row exists, but there is no claim-to-governance-gate edge/anchor table.
- `governance_gate:evidence-bar`: row exists, but there is no claim-to-governance-gate edge/anchor table.
- `concept_map:distributed_market_intelligence`: no first-class concept-map table exists.
- `rio:capital-deployment-layer`: no exact Rio strategy node or claim target exists.
- `rio:active strategy v1 / internet-finance capital product`: no exact Rio active strategy node exists.

## Evidence

- Packet JSON: `docs/reports/leo-working-state-20260709/cross-surface-packet.json`
- Authorized commit SQL, not executed in production: `docs/reports/leo-working-state-20260709/cross-surface-apply-authorized-commit.sql`
- Delete rollback SQL: `docs/reports/leo-working-state-20260709/cross-surface-delete-rollback.sql`
- Successful clone rehearsal log: `docs/reports/leo-working-state-20260709/cross-surface-clone-rehearsal-current.log`
- Failed-source-id constraint log: `docs/reports/leo-working-state-20260709/cross-surface-clone-rehearsal-failed-source-id-constraint.log`

## Claim Ceiling

This proves the strategy-anchor companion write is schema-compatible, reversible, and safe in a disposable clone after the mapped base packet exists. It does not prove production has been updated, because production commit was intentionally not executed.
