A model answers the prompt. VectorCourt governs the verdict.
File hard decisions as cases. VectorCourt challenges the evidence, constrains unsupported answers, surfaces blind spots, and returns a signed verdict artifact.
Sometimes the right verdict is: this filing cannot support the question.
A model gives you advice. VectorCourt turns the verdict into accountable work. It records what evidence supported the verdict, what was inferred, what was missing, and what would change the verdict later.
The sharper your question, the sharper the verdict. Include constraints, scale, and context — or the Council will ask before answering.
Free: 1 deliberation per month · Pro users get priority + 10/day
What happens next: VectorCourt returns a structured verdict or puts the submission into the queue when the deliberation needs longer.
Architecture-audit filings can trigger the Nemesis scaffold pass: a fail-closed check for unsupported load-bearing claims, missing required facts, and adversarial blind spots.
Good inputs for this mode
Click an example to load a full prompt into the form, then edit it to match your case.
Genesis text-only intake contract
Text only for now — no files or images. Genesis expects a grounded brief, not just a request for WOs.
What exists today
What is only intended
Who the user or customer is
Success condition
Major constraints
Runtime or deployment assumptions
What is explicitly out of scope
Desired backlog depth
Genesis will ask for clarification before WO synthesis if this minimum contract is weak.
0 / 10000 soft · 24000 hard
Optional project slug for replay and save. Auth is required if you want Genesis to compare this dry-run against the latest approved backlog for that project or bind this review to shared project state.
Genesis might fit better
This text looks more like a backlog brief than a decision for the Council to challenge.
Genesis dry-run
Project state
Synthesis
Budget tier
Draft backlog
Clarification
Contradictions
Warnings
Why Genesis stopped
What to add next
Sequenced backlog
Sequence and budget
Execution order
Budget estimate
Backlog replay
Project binding
Prior approved run
Backlog movement
Execution calibration
Assumption drift
Contradiction drift
Persistence
Write path
Named shared workledger project
How it works
01
File the case
Submit the decision, context, constraints, and what kind of output you need.
02
The Clerk checks the filing
VectorCourt may cap, defer, or refuse the verdict if the evidence cannot support the requested answer.
03
The Council argues
Adversarial branches test assumptions, surface blind spots, and separate observed facts from synthetic inferences.
04
You get a verdict artifact
A structured decision record with confidence, reversal conditions, evidence gaps, and signed provenance.
05
Verdicts become work
Convert findings into governed work — repair WOs, investigation WOs, or Preheat Candidates. The verdict trail stays attached from decision to execution.
Clarification-first, not fully covered: Robotics and automation · Manufacturing design · Logistics optimization · Process engineering · Policy and governance · Safety-critical system design
Physical, regulated, and safety-critical areas require missing operating, failure, validation, and authority facts before VectorCourt will frame a verdict as supported.
For architecture audits, VectorCourt separates Council seats from protocol phases: Nemesis is the scaffold-hole pass, not a public debater.
Pairs with Hiveram release bundles — point The Council at a release and find the failure mode your testing surface missed. Shaped by NeuroRouter context engineering.
VectorCourt can also validate against stored NeuroRouter vector state: does this change contradict a locked decision, or violate a persisted constraint?