Owner authority
The owner approves the organization, consequential scope, and governed actions. Authentication and session boundaries fail closed.
The owner can direct work but cannot manufacture independent review.Autonomy with a visible permission ceiling.
Governance is not a final checkbox. vbxns places authority, independence, and evidence inside the execution model so the project cannot quietly outrun its mandate.
Explore the modelA visible chain of responsibility.
Each layer has a job, an authority boundary, and evidence the next layer can inspect.
Bounded builders
Builders operate within assigned scope and permissions. Active ownership cannot shift while a run is in progress.
Scope changes invalidate stale approval before work begins.Independent reviewers
Reviewers evaluate completion evidence and acceptance criteria through a distinct responsibility boundary.
A builder's confidence never counts as an independent verdict.Consumable approvals
Approval is bound to the task scope and assignment that existed at decision time, rather than treated as an evergreen toggle.
Changed work requires renewed authority.Append-only evidence
Governed changes record trusted actor identity, correlation context, and previous/new state in an audit history that cannot be rewritten.
State and audit evidence commit together.Safe escalation
Blocked work, missing information, policy boundaries, and operational risk move toward the owner instead of being hidden or guessed away.
Unapproved commercial, legal, customer-data, and production actions remain prohibited.Approval and review are different controls.
Status is useful only when it changes the next decision. vbxns keeps operational state concise, attributed, and actionable.
Owner approvalAuthorizes work
Completion evidenceProves output
Independent reviewEvaluates output
Audit eventPreserves context
Missing authorityFail closed
Unapproved actionDoes not proceed
Make trust a system property, not a promise.
The current pilot is intentionally bounded while reviewer isolation, recovery, observability, and deployment controls continue to mature.
Get started