Guides
Draft ≠ commit
In HiveBase, a hold must not hide the draft — it only blocks promotion, publish, or other commits that change the outside world.
Draft ≠ commit means AI-produced work can be fully visible while still blocked from promotion, publish, or other commits that change systems outside HiveBase. A review hold freezes commit, not visibility. You should always be able to see what was drafted, why it was held, and what would ship if you approve.
Why it matters
Without this split, “held for review” can accidentally hide cascade output — the team loses the draft and only sees silence. With it, reversible preparation can proceed and leave a trail; consequential publish stays gated.
| Stage | What it is | Default behavior |
|---|---|---|
| Draft | Proposed text, plan, or internal artifact | Visible; often reversible |
| Commit / promote | Publish, send, merge, or write-back that changes the outside world | Held when risk or policy requires it |
Product law
Holds must never be implemented by deleting or hiding drafts. They only block the step that makes the change durable outside HiveBase.
Related product surfaces
- First governed run — practice draft → hold → commit
- Trust, safety & autonomy — automatic vs asks-first
- Action receipt — what runs leaves a record
- One-way door — when commit stays held
- Action Receipts — marketing overview of the trust spine