What Is Vyasa
Vyasa governs AI work. If assistants are workers, Vyasa is the project manager plus quality assurance plus compliance officer plus audit trail — for a hospital review flow as naturally as for a software release.
The split that explains everything
| Vyasa (governs) | Assistant (works) |
|---|---|
| Reads your workflow, prepares scoped context | Reads context, produces output |
| Enforces gates, scopes, and status rules | Works strictly inside its staging area |
| Validates output, challenges it when risky | Self-checks, then submits |
| Advances or rolls back work items | Never touches item status |
| Records every action | Leaves completion claims |
Vyasa never does the work itself. It makes work governable.
The loop in one picture
Five words (the whole vocabulary that matters today)
- Workflow — your team's recipe for how work flows (stations, powers, checks). Built per case, per industry.
- Node — one piece of work. Its own status, files, history.
- Session — one supervised sitting on one node, with a time limit and a lock.
- Gate — a checkpoint where you say yes or no with full evidence.
- Assistant — any worker: coding agent, writing agent, reviewer. Governed, never unsupervised.
What it is not
Not an IDE, not a coding assistant, not a model, not a PM-tool replacement. It sits above workers and directs them. It governs any work with steps and standards — documents, reviews, checks, releases — not just code, not just Python.
Next: Modular Workflows — how any workflow is built from the same parts.