How it works — the 5-step buyer journey
1. Approve the step listThe buyer reviews the one-page step list and presses Approve. No run can start without that human Approve — approve-before-approval is BLOCKED. SAMPLE
2. Verify run prepChecklist before the first run: template loaded, approved controls mapped, stop key armed. A validation gate BLOCKS anything missing steps, step text, or controls. SAMPLE
3. Execute steps exactlyThe agent copies text exactly as written and presses only approved controls, step by step. Any reword attempt is BLOCKED by name. SAMPLE
4. Guards stay onUnapproved control press, sign attempt, or unexpected input → BLOCKED and flagged to a human. GuardPilot never guesses and must never sign. SAMPLE
5. Counts-only logSteps done, blocks, flags — no report text retained. Completion sends a counts-only notification via mock phone/SMS. Audit is counts and events only. SAMPLE
Live demo console (sample data)
Everything below is SAMPLE DATA. Adapters are mocks: mock Epic mock phone/SMS — no real EHR, phone, or billing is connected.
Practice (tenant): Step lists, runs, and the audit trail are filtered per practice — zero cross-tenant records. Switch practices to prove isolation.
Approved step lists (this practice)
Run console
Approve a step list, then start a run.
Per-step event log (active run)
No active run.
Notification outbox (mock phone/SMS — counts only, no report text)
Outbox empty.
Audit trail (this practice only — counts and events, never step text)
No audit events yet.
Pilot pricing
| Plan | Price | Includes |
|---|---|---|
| Pilot | $1,750 fixed | One practice, one buyer-approved step list (buyer approves the one-page list before build), up to 3 workflow runs/day in pilot, counts-only audit logs, keyboard stop key, runbook + verification checklist handoff. untested hypothesis |
| Monitoring plan | $199/mo | Guard-event reports, step-list change reviews, next-business-day email support. untested hypothesis |
Billing is not connected. Next step: a 30-minute pilot scoping call — contact placeholder: pilot@example.com (replace before any real outreach).
Support, privacy & terms (summary)
- Support path: monitoring-plan customers get email support with a next-business-day response target. This demo has no support desk.
- Privacy: the demo stores nothing — all state is in-memory sample data that vanishes on reload. A real pilot would process only the admin data needed for the approved step list, inside the practice's tenant, and its audit logs would be counts-only.
- Terms: pilot scope is fixed in writing before work starts. GuardPilot never signs; unapproved controls are never pressed; unexpected input stops the run and flags to a human; no report text is retained.