# Project Concept

## Why (One Sentence)

Bicameral eliminates redundant rework in the SDLC by building a local-first
compliance layer that maps product decisions to the code implementing them
and surfaces alignment gaps before they become bugs.

## Vibe (Three Keywords)

1. **decision-aware** — every line of code is traced to the decision it
   satisfies; status (`reflected` / `drifted` / `pending` / `ungrounded`) is
   *derived*, not stored.
2. **local-first** — runs entirely in-process via embedded SurrealDB; no
   cloud, no network calls in the deterministic core.
3. **deterministic** — retrieval and status derivation are rule-based
   (BM25, tree-sitter, git, content hashes). LLMs are *callers*, never
   part of the ledger's truth function.

## Anti-Goals (What This Is NOT)

- **Not a cloud service.** No remote DB, no managed backend; the ledger
  lives next to the repo it tracks.
- **Not an LLM-powered ledger.** The deterministic core does not invoke
  any model. Compliance verdicts come from caller LLMs and are *cached*,
  not generated.
- **Not a code generator.** Bicameral observes and traces; it does not
  emit, refactor, or rewrite source.
- **Not a replacement for code review.** It surfaces *alignment* gaps
  (decision ↔ code), not correctness or design quality.
- **Not a one-size-fits-all framework.** It plugs in via MCP; downstream
  workflows (review, planning, dashboards) compose with it but are
  out-of-scope for the core ledger.

---
_Generated by QorLogic S.H.I.E.L.D. Bootstrap_
