# Episteme
<!-- generated by `orchestrator understand`; the PKG is source of truth, edits here are advisory -->

Code-true knowledge base for **synaptixs-spine** (brownfield), built by `orchestrator understand` from the Product Knowledge Graph + project profile.

<!-- spine-stamp -->
Generated from commit `34f63dcdb45eaab53c750763986fb7f58b6457fd` **plus uncommitted changes** by **Spine 3.25.0**.
Verify it still matches the code with `orchestrator understand --check`.
<!-- /spine-stamp -->

**Graph:** 12989 grounded nodes · 37532 edges.

> **epistēmē** (ἐπιστήμη) — knowledge grounded in evidence, as opposed to *doxa*, opinion. Everything here is derived from the code itself, not written by hand.

## New here? Read these first
_Where execution starts, then what the most code depends on._

1. [`scripts.agentic_eval`](../scripts/agentic_eval.py#L1) — where execution starts
2. [`scripts.audit_eval`](../scripts/audit_eval.py#L1) — where execution starts
3. [`scripts.bench_aggregate`](../scripts/bench_aggregate.py#L1) — where execution starts
4. [`scripts.codegen_ab`](../scripts/codegen_ab.py#L1) — where execution starts
5. [`scripts.codegen_benchmark`](../scripts/codegen_benchmark.py#L1) — where execution starts

## Files
- [architecture.md](architecture.md) — module map, node kinds, call hotspots
- [`areas/`](areas/) — 25 area pages: what each component is, what it depends on, and a map of its neighbours
- [`modules/`](modules/) — 50 module pages: every symbol, who calls it, and what it calls
- [`entities/`](entities/) — 7 table pages: columns, foreign keys both ways, and the code that reads or writes it
- [domain-model.md](domain-model.md) — tables, fields, foreign keys both ways
- [api-surface.md](api-surface.md) — every route and the code behind it
- [tech-context.md](tech-context.md) — languages, framework, db, tests
- [conventions.md](conventions.md) — observed house style + lint config
- [glossary.md](glossary.md) — domain terms
- [symbol-index.md](symbol-index.md) — every symbol, A–Z, and the page it's on
- [progress.md](progress.md) → `BACKLOG.md`

**Start at [architecture.md](architecture.md)** and click down: area → module → symbol → its source. Every relationship is rendered from both ends, so you can always walk back.

_Regenerate with `orchestrator understand .` — structural files are rendered from code, so edits are advisory._
