← Verity Auto docs

๐Ÿค– Meet Your AI Teammate

Verity Autonomy, explained without the jargon ยท it works inside GitHub, where your project lives

How much freedom does it get?

What's waiting in your project?

Safety dials

A "turn" = the teammate waking up (it wakes every 30 minutes), doing one batch of work, and writing down what it did.

The journey of one piece of work

The safety rails (always on โ€” you don't have to configure anything)

๐Ÿ›‘

The big red button

Put a special circuit-open sticker anywhere in your project and the teammate refuses to even start. Works instantly, no code needed.

๐Ÿ’ธ

A daily allowance

It has a spending cap per day (you set it). Hit the cap โ†’ it stops until tomorrow. Every dollar is written in a ledger you can read.

โœ‹

Permanent checkpoints

Some moments always wait for a human โ€” shipping to real users is one you can never turn off.

๐Ÿ˜ต

Two strikes, then it asks

If it fails at the same task twice, it stops retrying, marks it "needs a human," and moves on. No infinite loops, no burned money.

๐Ÿ“

Everything is written down

Every action is signed by the bot and leaves a note: what it did, what it cost, how long it took. Nothing happens silently.

๐Ÿ”’

Limited hands

Each job (planner, builder, reviewerโ€ฆ) only gets the specific tools it needs. The reviewer literally cannot press the merge button โ€” only deterministic safety code can.

Questions people actually ask

Where does it live? Do I need a server?

No server of your own. It runs either on a schedule from any computer (yours, or a tiny cloud machine), or inside GitHub Actions โ€” GitHub's built-in robot runner โ€” which means GitHub hosts it for you. Either way it wakes up, takes one turn, and goes back to sleep.

How do I give it work?

Write your idea as a GitHub issue and put the verity:request sticker (label) on it. That sticker means "a human approved this idea." It never invents its own work, and it ignores requests written by itself.

How do I approve something it finished?

It leaves you a comment that says exactly what to do: add the verity:approved sticker. Next time it wakes up, it sees your sticker, uses it up (one approval = one go-ahead), and continues.

What does "trust it with small stuff" actually mean?

A plain checklist, not AI judgment: the change only touches safe areas (docs, tests), it's under 150 lines, and all automated checks pass. Pass every item โ†’ it ships itself. Fail any item โ†’ it waits for you. Sensitive areas (login code, deploy scripts, its own settings) can never qualify.

What if it goes off the rails?

Pull the big red button (the circuit-open sticker), or just turn the mode back to "off". Both stop it at its next wake-up. Plus the allowance, the two-strike rule, and a 45-minute timer per turn are always running in the background.

What does it cost?

It pays per AI call, like any AI assistant. You set the daily cap (default $25/day) and can check the bill anytime with one command โ€” it keeps an honest spreadsheet of every run.

Your getting-started prompt โ€” paste this into Claude Code in your project folder