teleo-infrastructure/docs/reports/leo-working-state-20260709/deterministic-context-contract-live-canary-20260713.md
2026-07-13 12:20:30 +02:00

40 lines
1.6 KiB
Markdown

# Deterministic Context Contract Live Canary
## Canary
The proposed `kb_tool.py` was streamed to `python3 - --local` on the VPS and ran
two read-only `context` queries against the real `teleo-pg` Postgres database.
The proposed file was not installed during this canary.
For schema-sensitive contracts, the bridge read the current columns from
`information_schema.columns`; it did not rely on the fallback code constants.
## Source Intake Contract
The document/intake query returned:
- reply target `170`, hard maximum `220`;
- required lead: local compiler proven; live VPS/chat intake not shipped;
- build-local compiler capability tier;
- retained artifact plus URL/storage path plus content hash;
- pending-review candidate packet before canonical apply;
- exact current `public.sources` columns and explicit rejection of invented
author/title/publisher/publication-date columns.
## Mixed Packet Contract
The heterogeneous-packet query returned:
- facts/disputes -> claims plus sources/evidence;
- reusable framework -> `reasoning_tools`;
- operating rule -> `behavioral_rules`;
- evaluative gate -> `governance_gates`;
- agent position -> `beliefs`;
- exact supported `approve_claim` collections and exact current columns;
- explicit guards against reasoning-tool/belief edge endpoints, unshipped
fields, per-row `applied_at`, and unsupported writes in the apply sequence.
## Safety Readback
After both queries, canonical counts remained `1837/4145/4670/4916/26`.
`leoclean-gateway.service` remained active/running on PID `3166667` with zero
restarts; the deployed checkout remained clean at `ee06d0d`.