Leo Source Composition Clone Checkpoint

Result

Status: pass, 34/34 checks, zero harness errors.
Tier: live VPS, no-send, disposable full-data clone.
Full receipt: leo-source-composition-clone-checkpoint-current.json.
Receipt SHA-256: 897f2b48a5b85a32a069e154f246140421a16942acd85e32e4b8edc1d6738278.
Production behavior changed: no.

What Ran

Leo received a previously unindexed operating document and a contradictory post for AURORA-A1CF3DF21D. The model first searched the current clone KB, then extracted two atomic claims, retained both supplied source-content hashes, linked evidence from both sources, and represented the conflict bidirectionally. Extraction changed no database rows.

The harness normalized the packet into strict proposal b84244ce-53c8-5172-8c5e-38814f4f4e95, staged it as pending_review, performed a separated operator review to approved, and ran guarded apply to applied. All mutation occurred only in disposable clone leo-compose-20260711-03.

Exact clone deltas were:

kb_stage.kb_proposals: +1
kb_stage.kb_proposal_approvals: +1
public.claims: +2
public.sources: +4
public.claim_evidence: +4
public.claim_edges: +2
public.reasoning_tools: +0

Restarted Reasoning

A new isolated GatewayRunner child reused the same private persisted session, recalled composition-memory-live-20260711-03, searched without generated IDs, found and opened the applied proposal, read JSON evidence for both claims, read the canonical contradiction edge, and returned every exact proposal, claim, source, and edge ID in its final state receipt.

The transcript contained seven terminal calls. Every call had a result, none was rejected or nonzero, all seven matched nonce-bound wrapper receipts, and the two bounded/truncated transcript results reconciled to successful wrapper receipts. The GatewayRunner exposed no delivery adapter or send tool.

Production And Cleanup

Production remained byte-for-byte stable across the guarded fingerprints:

gateway: PID 2999690, NRestarts=0, start time unchanged;
canonical counts: claims 1837, sources 4145, evidence 4670, edges 4916, reasoning tools 17, proposals 26;
every tracked production table MD5 unchanged;
review/apply gate schema unchanged and still absent from production;
live KB wrapper and bridge-skill hashes unchanged.

All three composition containers, their anonymous volumes, private credential files, run directories, temporary profiles, and GatewayRunner children were removed and independently verified absent.

Claim Ceiling

This proves source extraction, hash-bound normalization, guarded canonical composition, conflict-aware reasoning, and isolated handler/session survival on a current full-data VPS clone. It does not prove Telegram-visible delivery, production DB mutation, scheduled DB-to-identity recomposition, arbitrary-source coverage beyond this case, or GCP parity.

2.9 KiB Raw Blame History