1.1
The gate and tools
Every tool declares a risk class, an input schema, an idempotency key for writes and a verify step. How the gate runs one governed path for every action.
Fig.0 · Documentation
How Qvrone works
One governed harness and two divisions. Start with the harness: everything in Business Automation and the Software Factory runs through it.
Harness. What every action runs through, in both divisions.
1.2
Rules and decision tables
Write the tables that allow an action, refuse it or ask you first. Checked before the tool runs; the model never overrules a rule.
1.3
Approvals
Approvals are bound to the exact tool, arguments and policy you saw, and work once. How to approve, decline and read why a replay was refused.
1.4
Ledger and audit
Each tool call is recorded with the authority and policy decision that let it run. Read the ledger, verify the signed audit chain and export it.
Business Automation. Your operations, run by agents you can audit.
2.1Live
Conversations and bookings
Chat and voice agents that answer, book, remind and reschedule. A booking counts as done only after it is read back.
2.2Certifying
Business Tier 1 connectors
WhatsApp, Gmail, Google Calendar, Google Sheets, Razorpay, Zoho CRM and Zoho Books: the rules each ships with and what certification checks.
Agents and hands. Bubbles that keep working, and hands for any system.
3.1Early access
Bubbles
Persistent named agents with their own conversations, memory and responsibilities. Watch progress, stop a run, and give work in a conversation.
3.2Prototype
Symbolic computer use
How the gate reads the accessibility tree, confirms each proposed click, spends a one-use receipt and verifies the effect, and why it stays approval-gated.
3.3Prototype
Agent and paired computers
A shared, governed computer per workspace with a leased screen per agent, and pairing your own machine with a signed key.
3.4Coming
H2H and devices
People reaching people through their agents, and the Pendant and Hub: ears, hands and a key, with no agent stored on the device.
Software Factory. Requests in, verified and reviewed pull requests out. You merge.
4.1Early access
Specs and bars
A request becomes a task spec with acceptance checks and a bar that is fixed before any code is written, then a compiled plan.
4.2Early access
Sandboxed runs and evidence
Plans run in an isolated sandbox. Every run keeps its artifacts and an evidence packet: diff, tests, sabotage log and verdict.
4.3Early access
Review and delivery
Changes are reviewed, then delivered as a pull request through the GitHub App, with CI results reconciled back into the review.
4.4Coming
Security lane
Scheduled route audits, dependency scans and secret scans become findings, then a fix pull request that waits for your approval.
Platform. Workspaces, data and where Qvrone runs.
5.1
Workspaces and isolation
Each workspace's data is fenced by row-level security inside the database, with separate roles for requests, workers and migrations.
5.2Coming
Qvrone over MCP
Call Qvrone's governed tools from Claude, ChatGPT or Codex, under the same gate, approvals and ledger.
These guides are still being written. Until they are, ask us and a person answers, usually the same day.
Ask us instead