teleo-infrastructure/docs/reports/leo-working-state-20260709/production-apply-packet-current.md

Production Apply Packet - Mapped Rich KB Subset - 2026-07-09

Generated UTC: 2026-07-09T20:32:38Z

Scope

This packet is the guarded production apply package for the mapped supported subset of two Cory-approved rich KB proposals:

• 14fa5ecc-ac7a-41c1-807d-a2e85b936617
• ac036c9d-20a0-4ffe-881f-57d6b7bacf22

The packet does not execute production apply by itself. It contains preflight, rollback rehearsal, optional authorized commit SQL, postflight, and exact delete rollback SQL.

It intentionally does not mark the original rich proposals applied, because this is still a mapped subset. Eight non-claim/cross-table fragments remain unresolved.

Packet Files

• production-preflight.sql
• production-apply-rollback-rehearsal.sql
• production-apply-authorized-commit.sql
• production-postflight.sql
• production-delete-rollback.sql
• production-apply-packet.json
• production-apply-packet-summary.json
• live-preflight-rollback-current.log
• clone-commit-delete-rollback-current.log

Target Row Counts

claims:         7
sources:        15
claim_edges:    11
claim_evidence: 17

Required existing claims are present in production:

• 7da4851c-0aac-4084-a99f-baeeeb3aa23e
• c0000000-0000-0000-0000-00000000000c
• d0000000-0000-0000-0000-000000000005

Live Production Preflight

Read-only preflight against live teleo passed:

id                                      status    proposal_type    reviewed_by_handle
14fa5ecc-ac7a-41c1-807d-a2e85b936617  approved  attach_evidence  m3ta
ac036c9d-20a0-4ffe-881f-57d6b7bacf22  approved  attach_evidence  m3ta

missing_required_existing_claims: 0 rows

expected_claims  expected_sources  expected_claim_edges  expected_claim_evidence
7                15                11                    17

generated_claim_rows  generated_source_rows  generated_edge_rows  generated_evidence_rows
0                     0                      0                    0

Live rollback rehearsal inserted all target rows inside two transactions and ended with ROLLBACK. A second preflight still showed 0/0/0/0 generated rows in production.

Disposable Clone Commit Proof

Created disposable DB teleo_packet_rehearsal_20260709 from live teleo.

Clone preflight before commit:

generated_claim_rows  generated_source_rows  generated_edge_rows  generated_evidence_rows
0                     0                      0                    0

Clone authorized commit rehearsal:

generated_claim_rows  generated_source_rows  generated_edge_rows  generated_evidence_rows
7                     15                     11                   17

The commit created DB-side superseded_by references through the generated supersedes edge behavior:

id                                      superseded_by
7da4851c-0aac-4084-a99f-baeeeb3aa23e  cd8daac8-039c-5349-9c50-02f622e73b03
d0000000-0000-0000-0000-000000000005  e6ce4e36-15d2-53bc-8b74-dda0efc095c1

Production currently has those superseded_by values blank, so this is an apply-side mutation to expect if the commit SQL is ever authorized.

The packet delete rollback now handles that by nulling exact superseded_by references to generated claims before deleting generated claim rows:

DELETE 17
DELETE 11
UPDATE 2
DELETE 15
DELETE 7
COMMIT

Clone generated-row count after delete rollback:

generated_claim_rows  generated_source_rows  generated_edge_rows  generated_evidence_rows
0                     0                      0                    0

Production preflight after clone rehearsal remained 0/0/0/0.

Cleanup:

disposable_db_exists
0

Claim Ceiling

The packet is production-ready as a reviewed artifact for the mapped subset, but it has not been executed on production. Executing production-apply-authorized-commit.sql would create canonical rows and DB-side supersession pointers for the mapped subset. It still requires explicit production apply authorization and a decision to either defer or separately model the eight non-claim/cross-table fragments.