09904d5222
J's "let's go" instruction: leave OPEN list behind, push the Go substrate forward into actual deployment shape. This commit marks the first time the Go side has run as long-running daemons rather than per-harness transient processes, and the first time the shared cross-runtime longitudinal log has carried a Go-emitted entry alongside the Rust ones. What landed: scripts/cutover/start_go_stack.sh — the persistent-stack runbook. Brings up all 11 daemons (storaged → catalogd → ingestd → queryd → embedd → vectord → pathwayd → observerd → matrixd → gateway, plus chatd-if-not-already-up) in dependency order via nohup + disown. Anchored pkill per feedback_pkill_scope (never bare "bin/"). Logs land in /tmp/gostack-logs/<bin>.log, one per daemon. Verified live state: - All 11 services healthy on :3110 + :3211-:3220 - gateway → embedd proxy returns nomic-embed-text-v2-moe vectors - chatd reports 5/5 providers loaded - No port collision with Rust gateway on :3100 - Daemons stay up after exit of the start script (production shape, not harness-transient) audit_baselines.jsonl crosses the runtime boundary: - 7 Rust-emitted entries (last: ca7375ea 2026-04-27) - 1 Go-emitted entry (ee2a40c 2026-05-01T07:53:54Z) appended via ./bin/audit_full -append-baseline - Same envelope shape, same metric set, same drift comparator semantics — operators running either runtime grow the same log What this DOES prove: - Substrate parity at deployment shape (not just unit tests) - Cross-runtime artifact write-side compatibility (was previously proven on read side via audit_baselines roundtrip) - The deploy machinery works end-to-end for the persistent case What this does NOT prove (still ahead): - Real coordinator traffic against the Go stack (no nginx flip yet; devop.live/lakehouse/ still serves through Rust) - Go-side production materializer (Phase 2 is observer-only) - Replay tool parity (Phase 7 is observer-only) - The 5-loop product gate against actual humans reports/cutover/SUMMARY.md now logs three new rows: - audit-FULL with 12/12 phases ported - First Go-emitted audit_baselines entry - Persistent Go stack live Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
65 lines
5.2 KiB
Markdown
65 lines
5.2 KiB
Markdown
# G5 cutover prep — verified-parity log
|
|
|
|
What works on Go gateway, what's been side-by-side compared to Rust,
|
|
what's safe to flip. Append a row when a new endpoint clears parity.
|
|
|
|
| Endpoint | Date | Rust path | Go path | Verdict | Notes |
|
|
|---|---|---|---|---|---|
|
|
| `embed` (forced v1) | 2026-04-30 | `/ai/embed` | `/v1/embed` | ✅ PASS 5/5 cos=1.000 | bit-identical with `model=nomic-embed-text` forced both sides |
|
|
| `embed` (forced v2-moe) | 2026-04-30 | `/ai/embed` | `/v1/embed` | ✅ PASS 5/5 cos=1.000 | bit-identical with `model=nomic-embed-text-v2-moe` forced both sides — both Ollamas have the model |
|
|
| `audit_baselines.jsonl` | 2026-05-01 | `data/_kb/audit_baselines.jsonl` | `internal/distillation` `LoadLastBaseline` / `AppendBaseline` / `BuildAuditDriftTable` | ✅ PASS round-trip | Live Rust file (7 entries) parses + round-trips byte-equal; lineage drift table fires correctly on zero-baseline metrics. See `audit_baselines_roundtrip.md`. |
|
|
| `audit-FULL` (phases 0/3/4) | 2026-05-01 | `scripts/distillation/audit_full.ts` | `cmd/audit_full` + `internal/distillation` `RunAuditFull` | ✅ PASS metric-equal | Go-side run against live Rust root: all 8 ported metrics (p3_*, p4_*) byte-equal to the last Rust-emitted `audit_baselines.jsonl` entry. 6/6 required checks pass. 4 phases (1, 2, 5, 6, 7) deferred — depend on broader Rust-side pieces (materializer / replay / run-summaries) not yet ported. See `audit_full_go_vs_rust.md`. |
|
|
| `audit-FULL` (phases 0/1/2/3/4/5/7 — observer mode) | 2026-05-01 | `scripts/distillation/audit_full.ts` | `cmd/audit_full` + `internal/distillation` `RunAuditFull` | ✅ PASS 12/12 | Skips reduced from 4 → 1: phase 1 invokes `go test`, phases 2/5/7 read existing artifacts as observers (no live materializer/replay invocation). Only phase 6 (TS-only acceptance harness) remains skipped. `p2_evidence_rows=1055` matches Rust `summary.json` `collect.records_out=1055` byte-equal. Updated `audit_full_go_vs_rust.md`. |
|
|
| `audit_baselines.jsonl` write side | 2026-05-01 | `data/_kb/audit_baselines.jsonl` (Rust-emitted, 7 entries) | Go-emitted entry #8 via `cmd/audit_full -append-baseline` | ✅ Mixed-runtime log | First Go-side entry written to the shared longitudinal log: `git_commit=ee2a40c5...` (golangLAKEHOUSE SHA, distinguishable from prior Rust SHAs like `ca7375ea`). All 10 metric fields match Rust shape exactly — drift comparator fires correctly across the runtime boundary. |
|
|
| Full Go stack (persistent) | 2026-05-01 | per-binary on :31xx | 11 daemons (storaged/catalogd/ingestd/queryd/embedd/vectord/pathwayd/observerd/matrixd/gateway/chatd) | ✅ All 11 healthy | First time the Go stack runs as long-running daemons rather than per-harness transient processes. Brought up via `scripts/cutover/start_go_stack.sh`; gateway proxies `/v1/embed` correctly through to embedd; all 5 chatd providers loaded. Live alongside the Rust gateway on :3100 (no port conflict). |
|
|
|
|
## Wire-format drift catalog
|
|
|
|
The Go gateway is *not* a literal nginx-swap drop-in for the Rust
|
|
gateway. Anything that flips needs a wire-shape adapter. Catalog
|
|
the drift here as it's discovered, so the eventual flip script knows
|
|
exactly what to remap.
|
|
|
|
### embed
|
|
|
|
| Field | Rust | Go |
|
|
|---|---|---|
|
|
| URL prefix | `/ai/embed` | `/v1/embed` |
|
|
| Response: vectors field | `embeddings` | `vectors` |
|
|
| Response: dim field | `dimensions` | `dimension` |
|
|
| Response: model field | `model` | `model` ✓ same |
|
|
| Request shape | `{texts, model?}` | `{texts, model?}` ✓ same |
|
|
| L2 normalization | unit vectors (‖v‖ ≈ 1.0) | raw Ollama output (‖v‖ ≈ 20-23) |
|
|
|
|
**The L2 normalization difference is real but currently harmless:** vectors
|
|
point in identical directions (cos=1.000) but Go has raw magnitudes. Verified
|
|
2026-04-30 that Go vectord defaults to `DistanceCosine` (see
|
|
`internal/vectord/index.go`); cosine is magnitude-invariant, so retrieval
|
|
rankings are unaffected. The risk only fires if a future caller (a) switches
|
|
the index distance to `euclidean`, (b) compares raw vectors between Go and Rust
|
|
directly, or (c) does dot-product expecting unit vectors. Adding a
|
|
normalization step in `internal/embed/embed.go` would make the cutover safer
|
|
and is cheap — but not blocking.
|
|
|
|
## Repro
|
|
|
|
```bash
|
|
./scripts/cutover/embed_parity.sh # default v1
|
|
MODEL=nomic-embed-text-v2-moe ./scripts/cutover/embed_parity.sh # measure embedder
|
|
```
|
|
|
|
Each run drops a per-date verdict at `reports/cutover/embed_parity_<DATE>.md`.
|
|
|
|
## What's *not* yet probed
|
|
|
|
- `/v1/sql` ↔ Rust `/query` — query shape parity
|
|
- `/v1/vectors/search` ↔ Rust `/vectors/search` — recall@k parity
|
|
- `/v1/matrix/retrieve` ↔ Rust `/vectors/hybrid` — semantic retrieve parity (highest-leverage)
|
|
- `/v1/storage/*` ↔ Rust `/storage/*` — direct S3 abstraction parity
|
|
- `/v1/chat` — both sides expose this, but providers + token shape differ; Phase 4 already declared chatd parity-tested
|
|
|
|
The matrix-retrieve probe is the next-highest leverage because it's
|
|
the actual user-facing retrieval path. Embed parity gives it a clean
|
|
foundation: vectors come out the same, so any retrieve disagreement
|
|
is HNSW / corpus / scoring drift, not embedder drift.
|