Every time you use AI to build something, it makes silent calls: which approach, which trade-off, which direction. Most never get written down. Then a new session picks a different direction, and now nothing is consistent.
VJS catches those calls and turns them into binding decisions:
The AI hits a choice: "build this ourselves or use the library?"; "how to format this document?"
The orchestration agent checks if that type of choice was already decided. If yes: follows the ruling instantly - no deliberation, same answer every time, for the life of the project.
If not: an AI court deliberates and issues a ruling. It gets committed to the repo.
The court has three tiers - a County Court (one judge), an Appeals Court (three), and a Supreme Court (five, expanding to nine for foundational questions) as a single apex. Benches are always odd-numbered and decide on a symmetric, two-sided case file with no access to the orchestration agent's preference.