root a21a34b057 docs: close 2 cross-runtime parity gaps + document unified log

Companion to lakehouse 98b6647. Architecture comparison decisions
tracker now captures:

  - Go validatord direct header read (fixes 6847bbc): closes the
    case where Langfuse-off middleware passthrough silently dropped
    forwarded X-Lakehouse-Trace-Id
  - Rust IterateResponse trace_id echo (fixes 98b6647): closes the
    asymmetry where Go's response carried the join key and Rust's
    didn't
  - Unified longitudinal log demonstrated end-to-end: both daemons
    co-writing /tmp/lakehouse-validator/sessions.jsonl, distinct
    daemon tags, one DuckDB query covers both

24/24 parity assertions (validator 6/6, extract_json 12/12,
session_log 4/4, materializer 2/2) hold against live :3100 + :4110.
Both runtimes deployed with today's full stack.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-02 06:25:21 -05:00

469 B

Raw Blame History

Materializer parity probe — Bun vs Go

Date: 2026-05-02T11:24:21Z Bun: /home/profit/lakehouse/scripts/distillation/build_evidence_index.ts Go: ./bin/materializer

Identical data/_kb/ source → both runtimes' materializer. Match = JSONL byte-equal after normalizing provenance.recorded_at (per-run wall clock) + sorted line order (dedup ordering).

Tally: 2 match · 0 diff (out of 2 stems)

No divergences — on-wire JSON parity holds.

469 B Raw Blame History

Materializer parity probe — Bun vs Go

469 B

Raw Blame History