teleo-infrastructure/docs/reports/leo-working-state-20260709/local-canonical-postgres-rebuild-canary-20260713.md

Local Canonical Postgres Rebuild Canary

Generated UTC: 2026-07-13T08:34:54.016399+00:00

Status: pass

Result

• Total command time: 3.809726s
• Named database ready: 0.781077s
• pg_restore: 1.026398s
• Manifest capture and parity comparison: 1.229484s
• Cleanup: 0.088110s
• Dump bytes: 13,462,116
• Dump SHA-256: 8a217e32bf6c83cb2b629e5ca5f91fc57f759e5010d9c40babe0d13c9a450822
• Source manifest SHA-256: d077f859b5f8ece908c61958a90914272ddc6fb9930df3b97d2ad2ac85b8e39a

Parity

• Manifest tables: 39/39
• Total rows: 52,164/52,164
• Table mismatches: 0
• Column, constraint, function, index, policy, schema, sequence, trigger, type, and view hash mismatches: 0
• Application role mismatches: 0
• Performance threshold failures: 0

Key restored rows:

Object	Rows
public.claims	1,837
public.sources	4,145
public.claim_evidence	4,670
public.claim_edges	4,916
public.reasoning_tools	17
kb_stage.kb_proposals	26

Isolation And Cleanup

• Docker image: postgres:16-alpine
• Network mode: none
• Postgres data directory: tmpfs, no persistent Docker volume
• Named-database readiness used an actual psql -d teleo connection
• Production database touched: false
• Container absence after cleanup: true
• Independent label-filtered orphan check: no containers found

Command

.venv/bin/python ops/run_local_canonical_postgres_rebuild.py \
  --dump /private/path/teleo-canonical.dump \
  --source-manifest /private/path/source-manifest.jsonl \
  --output /tmp/teleo-canonical-rebuild-receipt.json

This proves fast exact recovery from the canonical snapshot. It does not claim that the whole database can yet be semantically recompiled from raw documents and reviewed change records alone.