new_repo — the enclosure (prototype)

The clean, from-scratch, born-instrumented, contained codebase that replaces the old rot. This is the working prototype of the Living Code-Graph architecture specified in SPEC.md — the "enclosure": the boundary that holds the code, governs who touches it, and watches it.

The three pieces (and how they form the enclosure)

| package | role | status | |---|---|---| | packages/code_pipeline | Observability — the born-instrumented execution-graph tracer (nodes = functions pinned to (file, commit), edges = calls, every branch via sys.monitoring), into a new auto-timestamped DB. Retired + replaced the split-brained dz_debug. | built, 15/15 tests | | routed_vm → moved to jazz-forge/crank_pi | The enclosure, physical — persistent OVS fabric + Incus, in Python, systemd-backed. Extracted 2026-07-08 into crank_pi (the Pi node stack) where it belongs; this repo keeps only the observability layer. | moved | | packages/wayback | Ground truth — a read-only git×telemetry visualiser: what the codebase is over time vs what it stubs against (the anti-degeneration lens). | built |

The idea (see SPEC.md for the full normative version)

- Observe everything (code_pipeline): degeneration becomes a visible diff, not a silent swap. - Contain everything (routed_vm + the tiers in SPEC): no agent is handed the whole spec or raw code — only its slice, via MCP. - Together: you can see the whole from the controller, while nothing can be overwhelmed by the whole.

Dev

~/code/.venv/bin/pip install -e packages/code_pipeline
python packages/code_pipeline/tests/test_graph.py     # 15/15

Provenance

Refactored + generated 2026-07-01/02. dz_debug retired (its Logger folded into code_pipeline.log). Not a jazz package — its own tree, prototyping the monorepo shape (task #27).