Vinaya plans the work, checks every change before it merges, and measures every deploy, so the process gets better each time.

What Vinaya brings

Ship all day. Break nothing.

You deploy all day, and agents write most of the code. Vinaya puts every deploy, from a hot fix to a whole feature, through the same plan, the same gates and the same record.

  • Deploy complex workComplex workA feature with product specs: one milestone, several tranches, many tasks.
  • Deploy medium workMedium workAn engineering need with several tasks: one standalone tranche.
  • Deploy a backlog issueSimple taskA single fix found while working: one backlog Issue.
  • Deploy a hot issueHot issueUrgent: a light brief, no Planner, the same gates and the same record.
How Vinaya does it

From product to production

Product decides what to build. Vinaya takes it from there, in four stages, every one written down in the Log.

Product

  1. DecidingScope closed
  2. Defining
Checkout v2
SpecLedgerSpecRefundsSpecMobile paySpecCharge onceSpecFraud checksSpecWeb checkout

VinayaShipping

  1. ThinkingArchitect and Planner prepare the mission.
  2. ExecutingEach task runs in a loop, and every gate runs.
  3. RetrospectingOn every merge the work is closed and archived.
  4. Self-improvingThe Improver learns and proposes projects.

Product

  1. DecidingProposal accepted
  2. Defining
Checkout v2.1
SpecPartial refundsSpecLedger exportsSpecMobile pay retriesSpecRefund webhooksSpecFraud rules
1

Thinking

The Architect sets the milestone and its tranches. A Planner reads the real specs and the real code and writes each task as an Issue.

  1. ArchitectSets the milestone and its tranchescheckout-v2· 3 tranches
  2. PlannerReads the real specs and the real code52 tasks· each one an Issue
2

Executing

Each task runs in a loop: a Developer builds, fresh Reviewers check, every gate runs. A blocked task pauses for a ruling.

  1. DeveloperBuilds the taskcode+203−67
  2. ReviewersFresh agents check it✓ review approved · security pass
  3. GatesRing 0 · Ring 1 · Ring 2✓ every rule green
Built into the harness

Studio

Open Studio

Log and follow your agents. And learn from it to self-improve.

3

Retrospecting

On every merge the work is closed and archived: each task, then its tranche, then the milestone.

  1. Merged and archivedThe Archivist closes each task on merge☞ checkout-v2 landed on main
  2. Tranches and milestone closedThe Tranche Archivist closes each finished tranche3 tranches archived·milestone closed
4

Self-improvement

Built into the harness: the Log becomes a report, the Improver reads it and proposes projects. The Principal approves them, and they go back to product.

  1. The reportWhat the Log adds up to34 min per task·19 of 52 second rounds·418 caught
  2. The Improver proposesMost extra rounds come from one gateRun the doc gate before push
  3. A person approvesAnd it goes back to productLinear · a new Project
Gates

Every stage is gated

Checks that refuse unsafe work, from your machine to the merge and after it. No agent can skip them.

0
checks in three rings
0
are generic, for every process
0
are Vinaya’s own
See all 37 checks
  1. Ring 0 · your machine25 checks at commit and push, before work leaves the session✓ commit · push
  2. Ring 1 · the code host12 checks on the pull request and on every Issue write; merge waits until they passPR #473 · ready for your approval
  3. Ring 2 · after mergeAudits turn drift from any writer into findingsmerged · audited
Roles

Who does what

Agents do the work, each with only the tools its role needs. A person holds the decisions.

  • ArchitectThinkingSets the milestone and names its tranchesAgent
  • PlannerThinkingReads the code first, writes each task as an IssueAgent
  • OperatorExecutingStarts, watches, resumes and cancels tasks; never plans or rulesAgent or person
  • DeveloperExecutingBuilds one task in a sandbox, through the controller’s toolsAgent
  • Reviewer and SecurityExecutingJudge the change, fresh each round, never talking to each otherAgents
  • Archivist and Tranche ArchivistRetrospectingClose the task, then the tranche, after mergeAgents
The Principal

Five decisions stay with a person

Any engineer can hold the seat. Every decision is written to the Log under their name.

  • Approve the planBefore any task is dispatched
  • Rule at a pauseWhen a task cannot continue safely
  • Ask for review on a hot IssuePer Issue, the Principal’s call
  • MergeOnly once every gate is green
  • Adopt an improvementThe Improver proposes, the Principal approves

Run it on your own repository

Set up once. The process is ready in your agent when you finish.

Get startedRead the docs