Auto-Commit

Commits are not a separate step in Jorv Builder. Every Mission Board card lifecycle event (a feature being marked done, an audit auto-closing, a Ralph Loop iteration ending) auto-commits the dirty working tree and auto-pushes. You don't have to remember to git add . && git commit.

Why?

The classic AI-assisted workflow has a quiet failure mode: the AI makes changes, the user moves on, and at some point the working tree contains hours of unsaved work that no one remembers. Or the user remembers, but the commit that finally lands bundles ten unrelated changes under one vague message.

Jorv Builder inverts this. Every meaningful event becomes a commit. Each commit's message is brain-generated, anchored to the card or iteration it belongs to. Your git history reads like a narrative of the work, not a backup log.

When commits happen

A card transitions to Done (mark_feature_done)
An audit card auto-closes
A Ralph Loop iteration ends (commits to the loop branch only, not main)
An audit finding is triaged
Inline doc edits via Quick Edit are flushed (after a 30-second idle window, or rolled into the next card-lifecycle commit)

Push behaviour

Auto-push is on by default. Each commit is pushed to its upstream branch immediately.

To disable per-project, add to .orbit/config.json:

{ "autoPush": false }

Stragglers

Sometimes the working tree gets dirty without tying to any card — e.g., you ran a build script that wrote artifacts, or you tweaked a file outside any conversation with Orbit. After 5 minutes idle, those changes surface as a single "Uncommitted Changes" card on the Mission Board's Review lane. Open it via Brainstorm and Orbit helps you triage: commit, split into multiple cards, or revert.

Push failures

If auto-push fails (offline, auth expired, branch divergence), the Mission Board HUD icon turns red — the canonical critical signal. Click the icon to acknowledge and open the board, then run git push manually to see the actual error.

See Troubleshooting: Push failures.