Claw ed3ccf7c53 docs: Phase G0 kickoff plan + scrum-style independent review
7-day day-by-day plan for the smallest end-to-end ingest+query path
in Go: D0 ops setup → D1 skeleton + chi + /health × 5 binaries → D2
storaged S3 → D3 catalogd Parquet manifests → D4 ingestd CSV→Parquet
→ D5 queryd DuckDB → D6 gate-day end-to-end → D7 cleanup + retro.

Plan was reviewed by opencode/claude-opus-4-7 via the gateway
(same path the production overseer correction loop uses post-G0).
9 findings (2 BLOCK + 5 WARN + 2 INFO):

- 2 BLOCK fixed inline:
  - cgo build dependency surfaced on D0 not D5
  - DuckDB CREATE SECRET (S3) plumbed from SecretsProvider on D5.1
- 4 of 5 WARN fixed inline:
  - storaged binds 127.0.0.1 only + 2 GiB body cap
  - queryd uses TTL-cached views + etag invalidation, not refresh-per-call
  - gateway reverse-proxy stubbed on D1.10 (501), promoted on D6
  - ADR stubs go in at start of D4/D5, finalized on D7
- 1 WARN deferred (orphan GC on two-phase write — punted to G2)
- 1 WARN accepted with note (shared-server.go refactor — G1+ follow-up)
- 2 INFO fixed inline (go mod tidy timing, ADR-after-fact inversion)

Disposition table appended to the doc itself for auditability —
matches the human_overrides.jsonl pattern from the Rust auditor.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-28 06:47:15 -05:00

golangLAKEHOUSE

Go reimplementation of the Lakehouse — a versioned knowledge substrate for staffing analytics + local AI workloads.

Status

Pre-Phase G0. Documents seeded; Go module declared; implementation has not started. See docs/PRD.md for direction and docs/SPEC.md for the component-by-component port plan.

Phase G0 prerequisites (must be done before any code lands)

  1. Install Go 1.23+ on the dev box. Not currently present at /usr/local/go or elsewhere on the build machine. Standard install:
    curl -L https://go.dev/dl/go1.23.linux-amd64.tar.gz | sudo tar -C /usr/local -xz
    echo 'export PATH=$PATH:/usr/local/go/bin' >> ~/.bashrc
    
  2. Ensure cgo toolchain is present (gcc + libc-dev) — required by the DuckDB binding per ADR-001 §1.1. apt install build-essential on Debian-based systems.
  3. Initialize the dependency tree with go mod tidy once cmd/gateway/main.go declares its first imports.

Layout

docs/                         Direction + spec + ADRs
cmd/                          (forthcoming) main packages — one per service
internal/                     (forthcoming) shared packages
web/                          (forthcoming) HTMX templates + static
scripts/                      (forthcoming) cold-start, smoke, distill
tests/                        (forthcoming) golden files, integration tests

Reading order

  1. docs/PRD.md — what we're building and why
  2. docs/SPEC.md — how, per-component
  3. docs/DECISIONS.md — ADRs, starting with ADR-001 (foundational)
  4. docs/RUST_PATHWAY_MEMORY_NOTE.md — historical reference for the Rust era's pathway memory state (not migrated)

Predecessor

The Rust Lakehouse this rewrite supersedes lives at git.agentview.dev/profit/lakehouse. It remains the live system until this Go implementation reaches feature parity (per docs/SPEC.md §7).

Description
Go reimplementation of the Lakehouse — versioned knowledge substrate for staffing analytics + local AI workloads
Readme 3.2 MiB
Languages
Go 79.4%
Shell 20.1%
Just 0.3%
Dockerfile 0.2%