Wakes vanish
Signals flap, paths drop, and the responsible lane never wakes. Work stalls until someone notices by hand.
Product education
How Wakehold
holds the work.
Agent fleets lose wakes when paths flap. They claim “done” without evidence. Handoffs drop context. Rules live in docs nobody opens mid-run. Wakehold is the control plane that keeps continuity, proof, owned packets, and policy at decision time - metered by tokens you buy once and burn as the fleet operates.
“Done” is a rumor
Agents and operators mark complete with no sealed evidence. Downstream teams inherit hope instead of proof.
Handoffs drift
Context stays tribal - chat logs, half-updated tickets, tribal knowledge. The next owner starts from scratch.
Rules stay offline
Policy lives in a wiki. Mid-run, nobody opens it. Guardrails arrive as postmortems instead of capsules.
End-to-end example
One lead scenario.
Four primitives.
A qualified sales lead is ready for a human closer. An account executive needs proof the research happened. Delivery needs an owned kickoff packet - not a Slack dump. Watch wake → receipt → packet → capsule in sequence, and what the operator sees at each step.
SCENARIO · SALES LEAD → CLOSER → DELIVERY
OPERATOR VIEW
-
01 · Wake
Lead signal becomes a durable wake
A form submit or CRM stage change fires. Wakehold accepts the wake, watermarks it, and routes it to the qualifier lane - even if the wake path flapped on the way in. Catch-up fills gaps so the lane isn’t left hanging.
Operator sees“Wake accepted · lane: qualifier · watermark set.” Token meter ticks once for wake processed.
-
02 · Receipt
Qualifier seals proof before claiming done
The qualifier agent researches fit and updates the opportunity. Wakehold seals a proof receipt with CRM record id, message id, and tracker reference. Without that seal, the run cannot honestly say “qualified.”
Operator sees“Proof receipt sealed · opportunity + tracker linked.” Token meter ticks for proof receipt sealed.
-
03 · Packet
Owned context moves to the closer - then delivery
Fit notes, expected outcome, and the sealed receipt travel as a work packet to the closer. When the deal wins, a second packet carries kickoff context to delivery. Ownership is explicit: each lane is the next owner, not a shared pile of threads.
Operator sees“Work packet transferred · owner: closer → delivery · receipt attached.” Token meter ticks for work packet transferred.
-
04 · Capsule
Policy arrives at decision time
Before the closer offers a discount - or delivery accepts the kickoff - a versioned policy capsule injects current rules: discount caps, evidence required, handoff constraints. Guardrails travel with the work instead of sitting in a doc nobody opens.
Operator sees“Policy capsule injected · version pinned · decision ready.” Token meter ticks for policy capsule injected.
Result: continuity held · proof sealed · handoff owned · policy applied
4 burns from the prepaid pool
Same pattern in other fleets
- Release - build green → QA packet → publish gate with policy
- Support - ticket wake → resolution receipt → escalation packet
- Service - field request → completion proof → billing handoff
- Finance - invoice exception → research receipt → AP packet
Primitives in depth
What each piece
is - and why it burns.
Four control-plane events. Each one exists because something real breaks without it. Each one burns tokens from your prepaid balance.
01
Wake continuity
Durable wakes when paths flap
What it is
A wake is the durable signal that work should start or resume on a specific lane. Wakehold watermarks, catches up after flaps, and routes so the responsible owner gets the call - even after a blip.
What breaks without it
Fleets miss the moment. Operators babysit queues. “We’ll retry later” becomes silent loss. Downstream lanes wait on work that never arrived.
What burns a token
Wake processed Accepting, watermarking, and routing a durable wake - including catch-up after a flapping path.
What you get back
A reliable wake trail: which lane, when, and with what watermark. Continuity you can operate against - not hope the network behaved.
02
Proof receipts
“Done” only with evidence
What it is
A proof receipt seals message, tracker, or system ids into a durable record. Operators and downstream agents can trust the outcome because evidence is attached - not asserted.
What breaks without it
Status becomes theater. Finance, support, and other lanes invent completion or re-do work. Incident reviews argue about whether anything actually shipped.
What burns a token
Proof receipt sealed Sealing evidence into a receipt so “done” is backed by ids you can inspect.
What you get back
An auditable seal: what happened, which systems confirm it, and a trail the next owner can verify without a scavenger hunt.
03
Work packets
Owned handoffs between lanes
What it is
A work packet carries intent, state, expected outcome, and related proof between agents or lanes. Ownership transfers cleanly: the next owner can act without reconstructing tribal context.
What breaks without it
Handoffs drop half the story. Agents re-ask the customer. Operators paste from Slack into tickets. Continuity dies at the boundary between teams.
What burns a token
Work packet transferred Moving owned context - intent, state, expected outcome - across agents or lanes.
What you get back
A clear owner, a complete packet, and a handoff you can meter. Less drift. Fewer “what was this about?” loops.
04
Policy capsules
Rules that show up mid-run
What it is
A policy capsule is a versioned operating rule set injected at decision time. Guardrails travel with the work - approval thresholds, evidence requirements, routing constraints - pinned to a version you can audit.
What breaks without it
Policy lives in a wiki nobody opens under pressure. Agents invent local rules. Compliance becomes a retrospective instead of a control.
What burns a token
Policy capsule injected Injecting a versioned capsule when a decision is due so rules arrive with the work.
What you get back
Decisions made against the policy that was current then - not against memory. Versioned guardrails you can explain later.
Who it’s for
Teams that run
more than one lane.
Wakehold fits operators and founders who already have agents (or soon will) and cannot afford lost continuity or invented completion.
Multi-agent fleets
Several agents or lanes must hand off without dropping context - or inventing that the last step finished.
Ops-minded founders
You need a control plane that holds proof and continuity when the work gets messy.
Multi-tenant operators
Customers, teams, or environments share a plane but must stay scoped. One fleet’s wake must not bleed into another’s packet.
Positioning
Where Wakehold
fits.
Wakehold is a control plane and ops layer for agent fleets. It meters wakes, receipts, packets, and capsules around the tools your agents already use.
- Bring your own models We do not host or sell model inference. Bring your own models and runtimes; Wakehold holds continuity and proof around them.
- Tokens, not seats Commercial model is prepaid tokens burned on control-plane events - not monthly seats for every human who glances at a dashboard.
Tokens on this page
How burns fit
the story.
You buy Wakehold Tokens as prepaid credits. Your fleet burns them when it processes wakes, seals receipts, transfers packets, and injects capsules. Packs and prices live on the pricing page.
Do I pay per agent seat?
No. Tokens meter control-plane work - not headcount. Spike the fleet, burn more; idle the fleet, burn less.
What exactly burns a token?
Four events: wake processed, proof receipt sealed, work packet transferred, policy capsule injected. See the walkthrough above for the sequence.
Where do I see packs and prices?
On Pricing: Spark, Current, and Surge packs. Checkout will run through Paddle; email [email protected] until that flow is live.
Do unused tokens expire?
Draft policy: unused tokens don’t expire for 12 months from purchase. Beyond that, contact us. Not final until Terms are locked.
Full pack details and burn definitions → Pricing
Multi-tenant by design
Wakehold scopes customer, team, and environment boundaries so one fleet’s wake doesn’t bleed into another’s packet. Tokens meter usage across the plane you operate. For isolation and proof-trail notes, see Security.
Proof trail, not vibes
Receipts seal evidence. Packets carry ownership. Capsules pin policy versions. Together they give operators a trail they can inspect - paid for with the same token pool that meters the work.
Next step