CI / lint-and-test (push) Waiting to run

Details

- Add broad Cory-style outcome scenarios to the open-ended benchmark so regular-use ambiguity is tested, not only exact ID canaries.

- Add a clone-proven cross-surface strategy anchor packet that updates the mapped rich proposal anchor only after Claim D exists.

- Retain VPS Docker DB, claim/body metadata, and cross-surface proof reports with ruff plus 37 focused tests passing.

`docs/reports/leo-working-state-20260709/cory-expected-working-leo-outcomes-20260709.md`

`docs/reports/leo-working-state-20260709/cross-surface-apply-authorized-commit.sql`

`docs/reports/leo-working-state-20260709/cross-surface-clone-rehearsal-current.log`

`docs/reports/leo-working-state-20260709/cross-surface-clone-rehearsal-failed-source-id-constraint.log`

`docs/reports/leo-working-state-20260709/cross-surface-delete-rollback.sql`

`docs/reports/leo-working-state-20260709/cross-surface-packet.json`

`docs/reports/leo-working-state-20260709/cross-surface-postflight.sql`

`docs/reports/leo-working-state-20260709/cross-surface-preflight.sql`

`docs/reports/leo-working-state-20260709/cross-surface-resolution-current.md`

`docs/reports/leo-working-state-20260709/current-truth-index.md`

`docs/reports/leo-working-state-20260709/leo-db-state-17-cory-outcome-benchmark.svg`

`docs/reports/leo-working-state-20260709/leo-db-state-18-db-vs-workspace.svg`

`docs/reports/leo-working-state-20260709/leo-db-state-19-claims-body-metadata.svg`

`docs/reports/leo-working-state-20260709/leo-db-state-20-cross-surface-anchor.svg`

`docs/reports/leo-working-state-20260709/working-leo-current-state-20260709.md`

`docs/reports/leo-working-state-20260709/working-leo-definition-20260709.md`

`docs/reports/leo-working-state-20260709/working-leo-execution-plan-current.md`

`docs/reports/leo-working-state-20260709/working-leo-open-ended-benchmark-spec.json`

`scripts/kb_cross_surface_resolution_packet.py`

`scripts/working_leo_open_ended_benchmark.py`

`tests/test_kb_cross_surface_resolution_packet.py`

`tests/test_working_leo_open_ended_benchmark.py`

2026-07-09 23:39:51 +02:00

3.7 KiB

Raw Blame History

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:

Created disposable clone from live teleo using pg_dump | psql.
Applied mapped base packet in clone: 7 claims, 15 sources, 11 claim edges, 17 claim evidence rows.
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
Ran cross-surface authorized commit in clone.
Postflight read back anchor pointing to Claim D with weight 0.85.
Ran cross-surface delete rollback.
Ran mapped base packet delete rollback.
Clone returned to zero generated mapped rows and original anchor state.
Production stayed unchanged: generated rows remained 0/0/0/0, and production anchor still points to old claim with weight 0.7.
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.

3.7 KiB Raw Blame History