Project organization
A Project Director proposes the smallest useful team and gives every role a bounded mandate tied to the project objective.
Roles exist because the work requires them—not because a fixed agent roster does.vbxns sits above individual agents. It gives each project a deliberate organization, a shared working state, authority boundaries, and a path from execution evidence to owner decisions.
Explore the modelEach layer has a job, an authority boundary, and evidence the next layer can inspect.
A Project Director proposes the smallest useful team and gives every role a bounded mandate tied to the project objective.
Roles exist because the work requires them—not because a fixed agent roster does.Approvals, pauses, scope changes, assignments, and escalations appear as explicit owner actions rather than invisible automation.
Consequential authority remains attributable.Tasks, dependencies, blockers, active runs, due dates, artifacts, and approvals occupy one legible operating state.
PostgreSQL is the approved authoritative state store.Role permissions, approval evidence, scope bindings, and state transitions constrain what can happen next.
Paused, blocked, and awaiting-approval are first-class states.Review is modeled separately from implementation so evidence and acceptance criteria can be evaluated without self-approval.
The separately authenticated reviewer boundary remains planned work.Reports compress project state into progress, risk, decisions, evidence, and unresolved constraints.
The current MVP is a controlled single-owner, single-pilot surface.Status is useful only when it changes the next decision. vbxns keeps operational state concise, attributed, and actionable.
vbxns is being built from the control plane outward: durable state, explicit authority, independent evidence, then broader execution capability.
Get started