Docs

Guides

Deploy hot issue now

For a fix that must land now, or when the loop itself is broken: you and one agent edit the branch live, with every gate still running.

Planned
Hot issue
Principal

Before you start

  • You are the Principal. Hot mode is yours to enter.
  • The change is urgent and small: one objective, a few files.

The flow

Deploy hot issue now · the flow
OUTSIDE VINAYA · PRODUCT MANAGEMENT · defines the what, hands specs to engineering
Engineering need
No product project behind it:tech debt, orchestration fixes,bugs found while working
STAGE 1 · THINKING · architect and planner
Hot Issue
No planner. Issue opened hot,light briefsame gates, still recorded
#1001
hot
Fix flaky CLI test nowopened · no tranche
STAGE 2 · EXECUTING AND RETROSPECTING · the loop, the gates, closure and the record: all automatic
Hot ModeDEV + ONE AGENT
DIRECT CHAT · LIGHT BRIEF · DEV DRIVESANY CHAT SURFACECLI · desktop app · IDENo loop, no engine.Sandbox is the agent's own setting.The gates still apply.
Claude Code· atta-labs/shop · mainsonnet 5.5
Claude Code · atta-labs/shop · main
The CLI test fails one CI run in five. Open it hot.
Claude
Two tests share TMPDIR. One objective, one file, a test plan. Hot Issue #1001 written.
Reply… · ⌘⏎ to send
Claude CodeSANDBOXED
CodexSANDBOXED
macOSsandbox: Seatbelt
Linux / Unixsandbox: seccomp
GATES · at every step, the doors to GitHub · same for planned and hot · cannot be skipped
Ring 0 · commit + push hooks
last door before GitHub
Ring 1 · CI on the PR
same checks, merge blocked while red
Ring 2 · audits
after merge, always on
BEFORE CLOSURE · REPLAN, RECOVER, MERGE
Ready? → Review and merge
Gates green on the pull request.Required reviews report.The Principal merges. Nobody else does.MERGED → ARCHIVE · REFUSED → EXECUTE / REPLAN
RETROSPECTING · on every merge, automatic
Archivist
Closes each task on mergeRecords what shipped and why
Retrospective record
What shipped and why
STAGE 4 · SELF-IMPROVEMENT · the Log teaches the process
Report: what the Log says
Written from every run of the deploy. Example figures.
34 mintime per task
19 of 52second rounds
418problems caught
WHERE THE TIME GOES
Developer 84% · Reviewers 16% · most extra rounds come from one gate · a vague Surface doubles the rounds
Improver
Reads the report, proposes what to changeBACK TO LINEAR / JIRA · THE PRINCIPAL APPROVES
Project: run the doc gate before pushFix · cuts an expected 0.7 rounds per task
Project: surface check at planning timeFix · catches vague briefs before dispatch
Project: resume preview in StudioNew feature · shows what a ruling will change

Steps

  1. 1

    Open a hot Issue

    Write a light Issue marked hot: one objective, the files, and the facts you read. You do the readiness check yourself, and it is recorded in the Issue. No Planner.

  2. 2

    Work with one agent, live

    Pair with one agent in any chat surface. There is no loop and no rounds: you drive, the agent edits.

  3. 3

    Commit and push

    Commit and push as usual. Ring 0 runs on your machine; the pull request runs Ring 1. The gates are the same as for any task.

  4. 4

    Ask for review when you want it

    Review runs once, on demand: the same two reviewers judge the pull request against the hot Issue's objective. A push after that voids their verdicts and review runs again.

  5. 5

    Merge

    Merge when the gates are green. The Issue closes on merge, with the record kept beside the work.

What you get

  • One pull request, merged by you, through the same gates as everything else.
  • The same Log: every gate run and review is recorded.

What's next

Hot mode

The full definition

Gates

What runs on every commit and pull request

The whole process

Every flow on one diagram, from product work to merge and back.