01
Wake continuity
Durable wakes, watermarks, and catch-up when wake paths flap. The right lane wakes — even after a blip.
right work · right timeFeatures
What Wakehold
gives the fleet.
The operating layer between your AI workforce and your business systems: a harness for continuity and proof, Workflow Runs for the whole path, and Records for what the work knows — without replacing the systems you already use.
The harness
Four primitives.
One ops layer.
The harness is the control plane around agents you already run. Wakes, proof, packets, and policy keep work honest when paths flap and handoffs cross lanes. For a step-by-step sales-lead walkthrough, see How it works.
02
Proof receipts
“Done” only with evidence — message, tracker, or system ids on the record.
evidence · not vibes03
Work packets
Owned handoffs of context between agents and lanes — intent, state, and expected outcome in one packet.
clean handoff · no drift04
Policy capsules
Versioned operating rules at decision time — guardrails that travel with the work.
rules · in contextWorkflow Runs
The durable thread
for the whole path.
Wakes and proof receipts catch moments. A Workflow Run is the board that holds the whole path: where things stand, what finished with evidence, and which systems are involved — a bridge across the tools where your business already lives, not a replacement for them.
One path.
Several steps.
Work that spans people and tools gets a durable thread — not a pile of chat and tickets. You see the path, the open steps, and the proof already on record.
Moments vs.
the whole path.
Wakes, receipts, and packets are moments. A Workflow Run holds them together so continuity doesn’t stop at a single handoff.
You design
the path.
Name the steps for your company. Self-serve — not a fixed industry template gallery we ship as “the” playbook.
Several systems.
One thread.
Link the systems you already use — ATS, calendar, docs, HRIS, or your own stack. Updating one doesn’t quietly finish another. Side paths can move without finishing the main path.
Connect work.
Don’t replace SoRs.
Wakehold does not replace your CRM, ERP, CMMS, accounting, or document stores. It holds the operational thread between them — stages, proof, and references — so agents and operators share one picture of the path.
EXAMPLE · HIRING A TEAMMATE
PATH VIEW
Someone applies. Your team screens, interviews, decides, and brings them on. The Workflow Run holds that path — with proof for what finished and links to the tools involved.
Applied
Screened
Interviewed
Offer out
Started
What “finished” means
- Screened only counts when the scorecard (or ATS note) is on the record.
- Offer out only counts when the signed offer document id is on the record.
- Started only counts when the start-date confirmation is on the record.
Side path · background check
While interviews run, background check can move on its own timeline. A clear background check does not mark the person as started. An accepted offer does not close the background check for you.
Same hire, several tools
ATS candidate id, interview calendar event, offer document, HRIS profile — all on one thread. Updating the calendar doesn’t invent an offer. Creating the HRIS profile doesn’t invent “screened.”
Result: path held · proof required · tools linked · side path separate
You name the steps
Same idea elsewhere
- Release — build green → QA handoff → published
- Onboarding — kickoff → configured → trained → go-live
- Claims — intake → review → decision → payout
- Course launch — outline → draft → reviewed → live
Simple rules
- You name the steps.
- A step isn’t done without evidence.
- One thread can link to more than one tool.
- Side paths (like a background check) don’t sneak-finish the main path.
- Your approval habits stay yours — Wakehold keeps the path honest.
Records
What the work
knows.
Runs tell you where the work is. Records tell you what the work knows. Receipts tell you what actually happened. Evidence records keep identity and relationship on the plane — while file bytes stay in the object stores and file systems you already use.
A record id.
A clear type.
Each evidence record carries a durable identity, a type, and metadata your team can search — so “the offer letter” or “the scorecard” is a first-class object, not a buried attachment.
Tied to the
business object.
Search and browse by the business object and workflow relationship — which run, which step, which candidate or case — so operators and agents see the same operational picture.
Your store.
Our pointer.
Bytes stay in your object store or file system (for example S3, SharePoint, or Drive). Wakehold holds identity, metadata, workflow relationship, and signed or local content URLs — it does not replace your document store.
On the path
when it matters.
When a Workflow Run step needs evidence, the record is what the gate can point at. “Offer out” can require the signed offer record — not a vibe that someone sent something.
Coming soon
On the roadmap.
Not claimed as shipped.
These ideas extend the operating layer. They are labeled clearly so we never invent product that isn’t ready yet.
Target · roadmap only
- Federated search — search once across systems an agent is authorized to see
- Tool & permission registry — broad visibility, narrow authority
- Exception / missing-info UI — know what’s expected but not found
- Search-exhaustion proof — record systems searched and misses as first-class UX
- Cost / model governance — beyond token metering of control-plane events
- Runtime marketplace — louder agent-runtime independence beyond “bring your own”
Next step