Command Center
Messy Notes To Verdicts
Technical receipts
Runtime Proof
Priority claims
Needs attention
Selected claim
Current posture
Agent roles
Court walkers
WitnessFinderVisits evidence nodes connected to the claim.
ProsecutorFollows contradicts edges and records risk.
DefenderFollows supports edges and records context.
JudgeWrites the verdict node and confidence.
BailiffCreates validation task nodes from weak verdicts.
Jac/Jaseci proof
How this uses Jac
Graph nodesClaim, Evidence, Trial, Verdict, Task.
Typed edges:supports, contradicts, cites, produced_verdict, creates_task.
Witness FinderTraverses sources and creates Evidence to Claim links.
Prosecutor / DefenderTraverse contradiction and support edges to build cases.
Judge / BailiffJudge writes Verdict; Bailiff writes Task and creates_task edge.
by llm()Gemini refines structured verdict rationale when the key is available.
Runtime honestyNative Jac CLI is shown when installed; otherwise the app labels the serverless Jac contract runtime.
Demo graph stateVercel uses warm in-memory graph state; local dev persists to data/store.json.
Why Jac?
Graph traversal is the product
Jac matters here because the problem is not chat. A claim deserves belief only after walkers inspect connected evidence, contradiction edges, source reliability, verdict history, and generated tasks.
Object-spatial graph
Role walkers
Typed mutations
by llm() verdict polish
Claims
Claims
Claim Table
| Claim | Status | Confidence | Evidence | Tags |
|---|
Courtroom
Active Trial
Object-Spatial Memory
Evidence Graph
Claim
Support
Contradiction
Verdict
Task
Action Generation
Actions
| Task | Claim | Owner | Due | Status |
|---|
Evidence Intake