.N..AO
.N..AO
All work
Case 03 / 04·Early development · beta targeted Q2 2026

AI Code Review · Go · Python · TS

TRIBUNAL.

The missing code review layer — AI that reviews what the AI wrote. Detects AI-generated code in PRs, analyzes context blindness, and briefs human reviewers.

AI EngineerFull-StackForward Deployed

License

MIT

Detect

~2ms / file (Go)

Analyze

~5s high-risk section

Runtime

Docker Compose

Interactive lens

PROBLEM → SOLUTION

Drag the handle right to reveal the solution over the problem.

← ProblemSolution →

Problem

AI tools write syntactically impressive code that is often semantically dangerous — migrations that ignore table scale, retries against non-idempotent APIs, config flips with wide blast radius. Linters catch syntax; they miss operational context. Human senior review does not scale with Copilot volume.

Solution

TRIBUNAL acts as an automated senior engineer in CI: DETECT AI authorship, ANALYZE context blindness against topology/incidents/runbooks, BRIEF the human reviewer so review time drops from roughly 30 minutes to about 30 seconds per change with full operational context.

Drag right to reveal the solution · 12%

01Result

Three-phase pipeline: detect → analyze → brief

02Result

Flags scale, idempotency, cascade, incident-pattern, and race-condition blindness

03Result

Posts human-readable briefings into the PR review flow

Execution flow

HOW IT RUNS

End-to-end flow from trigger to decision output.

  1. 01

    Step 1 of 6

    PR event from GitHub / GitLab / Gitea

  2. 02

    Step 2 of 6

    Go interceptor: webhook, changed files, 3-signal AI authorship detection

  3. 03

    Step 3 of 6

    Go context graph: topology, incidents, dependencies

  4. 04

    Step 4 of 6

    PostgreSQL context layer for persistent correlations

  5. 05

    Step 5 of 6

    Python semantic analyzer (Claude) + briefing generator

  6. 06

    Step 6 of 6

    Output

    TypeScript PR overlay: check runs, annotations, risk heatmap

Capabilities

WHAT IT CATCHES

Signal 01

Scale blindness — e.g. migrations on multi-billion-row tables with zero-downtime constraints

Signal 02

Idempotency blindness — retries against non-idempotent payment/API calls

Signal 03

Cascade blindness — config/flag changes spanning dozens of services

Signal 04

Incident pattern blindness — repeating known failure modes

Signal 05

Dependency and race-condition blindness in shared libraries and concurrent code

Pin a layer

STACK MATRIX

Click a layer to isolate it — MIT · Go · Python · TypeScript

Live signal

CORE LOGIC

tribunal.corestreaming…
1 

TRIBUNAL fills the gap between perfect syntax and catastrophic semantics. It specializes in what AI-generated diffs did not know — service scale, incident history, dependency blast radius — and briefs humans so review capacity can keep up with AI authorship.

[ VERIFY ]

Open the
source.

Claims should survive a read of the repo.

BRIEF0%Source