First verified change

The story follows one builder on the Just me profile, after setup has finished and a model account is connected. The single-person record uses Claude with an API key. The builder is also the receiver: the person who accepts or rejects the result.

Seven steps take a goal to a decision #

Enrolling a repository keeps your work as it is #

Enrolling records the repository's current revision and a digest of any uncommitted changes and of its agent instructions. Uncommitted work is kept, never reset. The repository gains one .hyper folder holding its workspace binding.

A commission fixes the goal and its terms before work starts #

A commission is what the task must achieve and the terms it runs under. Its card shows the objective, the source at an exact revision, the recipe that builds and checks the change, the budget, the receiver and the verifier. Only pressing Enter commissions it, and a missing budget reads "not set", never $0. Changing a commission later creates a new one with a new id; a run keeps the terms it started under.

You approve the exact effect, not a summary #

Rocket! reads the repository, plans and edits, and asks before an effect that is not already allowed. The review shows the exact effect itself: the command or edit, its target and its arguments. It flags network use, writes outside the workspace, protected paths and destructive commands. The model's own summary of the effect is explanation only.

You answer with y to allow once, n to deny or e to edit. a arms Allow always, which applies only after you confirm with Enter, so one key never widens what is allowed. Changing the target or the command after you answer voids the approval. The part of Hypervibe that carries out the effect checks the approval and your current authority again at that moment, and text in instructions or files grants nothing.

Detaching or a crash does not run work twice #

Closing the view detaches it, and Rocket! keeps working. A session is Rocket!'s resumable journal: an append-only record of the work plus an index. If the engine is killed, hyper session resume reopens that journal and continues the same session with exactly one attempt. The lane that shows the session outlives the processes behind it. Every effect carries an operation id, so when a reply is lost, Hypervibe looks the effect up by that id instead of running it again.

A verifier that did not write the change checks it #

When Rocket! proposes a candidate, the exact change at one revision, Reactor runs the commission's recipe on it. The verdict is bound to that candidate and its base revision, and it comes from a verifier other than the producer. Rocket! cannot rewrite the candidate once it is submitted, and a timeout reads inconclusive.

You decide on the Result card #

The Result card shows the candidate and its diff, the verdict, the evidence, the limitations and the cost. A pass alone reads "awaiting acceptance", and nothing on the card says done.

Result · commission c-0117 · make the date parser accept ISO weeks
Candidate   a41f9c2 · 2 files · +18 −4
Verdict     ✓ pass · recipe unit-tests · verifier is not the producer
Evidence    14 of 14 required checks passed
Limits      performance not measured
Cost        settled $0.48 · estimated $0.14 · 2 lines Unknown
Acceptance  … awaiting acceptance
A accept · N reject · Enter review

A then Enter accepts. N opens a list of reasons with no default; you pick one, add a short note if you like and confirm with Enter. Choosing "needs revision" leads to a revised commission with a new id.

One receipt shows what the run cost #

The run's receipt joins every attempt, model call and build or verification job. While usage is still being settled the card reads "cost pending", and a cost that is not known reads Unknown, never $0.

Where to go next #

• Read a receipt defines every verdict, decision and cost line.
• Rocket! covers sessions, tools and approvals.
• Reactor covers builds, jobs and independent verification.
• Work and quality explains commissions and acceptance in more depth.