# Working Leo Integrated Packet Rehearsal - 2026-07-10

Generated UTC: `2026-07-10`

## Verdict

Integrated production-order clone rehearsal passed. Production was not modified.

This rehearsal composes every currently prepared Working Leo DB packet in dependency order, then rolls the whole stack back in reverse order:

1. `mapped-rich-base`
2. `cross-surface-anchor`
3. `rio-strategy-context`
4. `governance-concept-schema`
5. `helmer-7powers`

Rollback order:

1. `helmer-7powers`
2. `governance-concept-schema`
3. `rio-strategy-context`
4. `cross-surface-anchor`
5. `mapped-rich-base`

## Clone Proof

Disposable database: `teleo_integrated_rehearsal_20260710`

After all five apply packets ran in the clone, the expected integrated generated footprint was:

- `12` claims
- `28` sources
- `18` claim edges
- `34` claim evidence rows
- `1` reasoning tool
- `2` Rio strategy nodes
- `5` Rio strategy anchors
- `1` concept map
- `1` claim-concept-map link
- `2` claim-governance-gate links
- `1` Helmer proposal ledger row marked `applied`
- `1` cross-surface strategy anchor update

After all rollback packets ran in reverse order:

- mapped base generated rows returned to `0/0/0/0`
- Helmer generated rows returned to `0/0/0/0/0`
- Helmer proposal ledger returned to `approved`
- cross-surface anchor `47f128a0-36c5-4b60-97d4-48c32fa48bc7` returned to old claim `d0000000-0000-0000-0000-000000000005` with weight `0.7`
- Rio generated nodes/anchors returned to `0/0`
- generated governance/concept schema tables were absent again

Production readback after the clone proof:

- mapped base generated rows remained `0/0/0/0`
- Helmer generated rows remained `0/0/0/0/0`
- Helmer proposal ledger remained `approved`
- generated governance/concept tables were absent
- no production apply SQL was executed

Cleanup readback:

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

## Evidence

- Integrated manifest JSON: `docs/reports/leo-working-state-20260709/working-leo-integrated-packet.json`
- Integrated manifest summary: `docs/reports/leo-working-state-20260709/working-leo-integrated-packet.md`
- Integrated clone proof log: `docs/reports/leo-working-state-20260709/working-leo-integrated-clone-rehearsal-current.log`
- State image: `docs/reports/leo-working-state-20260709/leo-db-state-25-integrated-apply-rehearsal.svg`

## Claim Ceiling

This proves the prepared packet set composes in one disposable clone and can be rolled back cleanly in reverse dependency order. It does not prove production has been updated. Production apply still requires explicit authorization, and the live Telegram canary should be rerun after any production apply.
