The 3-stage pipeline

codingassist.bot is built around a 3-stage pipeline. Each stage is independently observable, independently replayable, and bounded by a strict input/output contract. Nothing in the pipeline is non-deterministic — given identical inputs, you get identical verdicts.

Stages at a glance

Stage 1 — Context

The Context stage builds a single, typed bundle from three independent sources:

• Diff — hunks, renames, symbol moves
• Ticket — acceptance criteria parsed from Jira/Linear/GitHub Issues
• CodeGraph — semantic neighbours retrieved from a vector index over the repo

The output is an immutable ReviewContext record, content-addressed by SHA-256.

Stage 2 — Analysis

The Analysis stage fans out the ReviewContext to six reasoning planes (Intent, Contract, Semantic, Tests, Security, Performance). Each plane:

1. Receives the same immutable bundle
2. Runs in isolation — no cross-plane reads
3. Emits a typed signal: { plane, severity, finding[], confidence }

There is no master prompt. Each plane is a standalone evaluator; the LLM call (when used) is bounded to the plane's input schema.

type PlaneSignal = {
  plane: "intent" | "contract" | "semantic" | "tests" | "security" | "perf";
  severity: "info" | "warn" | "error";
  findings: Finding[];
  confidence: number; // 0..1
};

Stage 2-bis — Sandbox (optional)

For findings that need code execution (e.g. test-coverage delta), Stage 2-bis runs the proposed change in an ephemeral sandbox. Sandboxes are language-scoped and disposable.

Stage 3 — Orchestration

The Orchestration stage receives the six signals and produces:

• A verdict (auto-merge / auto-approve / human review / escalate / declined)
• A confidence tier (T1–T5)
• A signed audit record that can be replayed

Orchestration applies tenant-defined policies — for example, "always escalate when the Security plane reports error severity" or "auto-merge T1 only on main".

Determinism guarantees

What's next?

• AC verification — how Stage 1 binds ACs to code
• Findings & severity — what each plane emits
• POST /v1/reviews — drive the pipeline from your code