dd2d03a3ea
Some checks are pending
CI / lint-and-test (push) Waiting to run
- Compose prepared KB packets in production dependency order with rollback order - Prove full disposable clone apply/rollback while production stays unchanged - Retain missing packet SQL, integrated manifest, state image, and tests `docs/reports/leo-working-state-20260709/current-truth-index.md` `docs/reports/leo-working-state-20260709/helmer-7powers-production-apply-packet-summary.json` `docs/reports/leo-working-state-20260709/helmer-7powers-production-apply-rollback-rehearsal.sql` `docs/reports/leo-working-state-20260709/helmer-7powers-production-postflight.sql` `docs/reports/leo-working-state-20260709/helmer-7powers-production-preflight.sql` `docs/reports/leo-working-state-20260709/leo-db-state-25-integrated-apply-rehearsal.svg` `docs/reports/leo-working-state-20260709/production-apply-authorized-commit.sql` `docs/reports/leo-working-state-20260709/production-apply-packet-summary.json` `docs/reports/leo-working-state-20260709/production-apply-packet.json` `docs/reports/leo-working-state-20260709/production-apply-rollback-rehearsal.sql` `docs/reports/leo-working-state-20260709/production-delete-rollback.sql` `docs/reports/leo-working-state-20260709/production-postflight.sql` `docs/reports/leo-working-state-20260709/production-preflight.sql` `docs/reports/leo-working-state-20260709/working-leo-current-state-20260709.md` `docs/reports/leo-working-state-20260709/working-leo-execution-plan-current.md` `docs/reports/leo-working-state-20260709/working-leo-integrated-clone-rehearsal-current.log` `docs/reports/leo-working-state-20260709/working-leo-integrated-packet-current.md` `docs/reports/leo-working-state-20260709/working-leo-integrated-packet.json` `docs/reports/leo-working-state-20260709/working-leo-integrated-packet.md` `scripts/working_leo_integrated_packet.py` `tests/test_working_leo_integrated_packet.py`
45 lines
1.5 KiB
Markdown
45 lines
1.5 KiB
Markdown
# Working Leo Integrated Packet
|
|
|
|
Production apply status: `not_executed`.
|
|
|
|
## Apply 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`
|
|
|
|
## Expected Counts After Apply
|
|
|
|
- `claim_concept_map_links`: `1`
|
|
- `claim_edges`: `18`
|
|
- `claim_evidence`: `34`
|
|
- `claim_governance_gate_links`: `2`
|
|
- `claims`: `12`
|
|
- `concept_maps`: `1`
|
|
- `cross_surface_anchor_updates`: `1`
|
|
- `helmer_ledger_rows_marked_applied`: `1`
|
|
- `reasoning_tools`: `1`
|
|
- `rio_strategy_anchors`: `5`
|
|
- `rio_strategy_nodes`: `2`
|
|
- `sources`: `28`
|
|
|
|
## Dependency Notes
|
|
|
|
- mapped-rich-base must precede cross-surface-anchor, rio-strategy-context, and governance-concept-schema.
|
|
- cross-surface-anchor must roll back before mapped-rich-base so Claim D still exists while the anchor is restored.
|
|
- rio-strategy-context and governance-concept-schema must roll back before mapped-rich-base because their rows reference mapped base claims.
|
|
- helmer-7powers is independent but included in the integrated rehearsal because it is an approved full-coverage KB packet.
|
|
|
|
## Not Done
|
|
|
|
- Production canonical rows/schema remain unapplied until explicit production apply authorization.
|
|
- GCP parity remains unproven until account auth allows read-only GCP service/DB readback.
|
|
- Live Telegram canaries remain regression proof for current VPS behavior and should be rerun after any production apply.
|