Progress is unclear
Each system shows its own status. Nobody has a single answer for what finished across the path.
Product education
How Wakehold
holds completion.
Wakehold follows critical work across the systems where it happens, checks every required milestone against evidence, and shows exactly what is complete, waiting, or missing. Wake continuity, proof receipts, work packets, and policy capsules are how that record is held.
Completion lacks evidence
Teams mark steps complete without sealed evidence. Downstream work starts from assertions instead of receipts.
Handoffs drift
Context stays in chat logs and half-updated tickets. The next owner reconstructs the story by hand.
Rules stay offline
Policy lives in a wiki. Mid-run, nobody opens it. Guardrails arrive as postmortems instead of capsules.
End-to-end example
Project Atlas onboarding.
Four control-plane events.
A new customer is moving from signed agreement to confirmed launch. The work crosses CRM, identity, documents, email, and calendar. Wakehold keeps the milestones and evidence on one durable path. The four burns below are the four illustrated events — later milestones may create additional receipts or handoffs.
Example · Project Atlas · Customer onboarding
Operator view
-
01 · Wake
The signed agreement starts a durable run
The CRM records the signed agreement. Wakehold accepts the event, watermarks it, and routes it to the onboarding lane. Catch-up prevents a temporary delivery failure from silently losing the start of work.
Operator sees“Wake accepted · lane: onboarding · watermark set.” Token meter ticks once for wake processed.
-
02 · Receipt
Workspace ready only counts with evidence
Configuration finishes. Wakehold seals a receipt containing the workspace ID, configuration record, and linked agreement reference. The milestone remains open until the required evidence is attached.
Operator sees“Proof receipt sealed · workspace + configuration record linked.” Token meter ticks for proof receipt sealed.
-
03 · Packet
Context transfers to enablement
The launch date, approved scope, user roster status, and workspace receipt move as an owned packet to the enablement lane. The new owner receives the current state and remaining requirements without reconstructing the history.
Operator sees“Work packet transferred · owner: enablement · receipt attached.” Token meter ticks for work packet transferred.
-
04 · Capsule
Access policy arrives before invitations
Before administrator invitations are sent, a versioned policy capsule supplies the current access rules, approval thresholds, and evidence requirements. The decision records which policy version applied.
Operator sees“Policy capsule injected · access policy version pinned · decision ready.” Token meter ticks for policy capsule injected.
Result: Continuity held · evidence sealed · handoff owned · policy applied
Four illustrated burns — later milestones may add more
Same pattern elsewhere
- Hiring — applied → screened → offer sent → offer accepted → started
- Release — build green → QA packet → publish with policy
- Onboarding — kickoff → configured → trained → go-live
- Claims — intake → review → decision → payout
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 completed event 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.
What breaks without it
Fleets miss the moment. Operators babysit queues. 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.
02
Proof receipts
Finished only with evidence
What it is
A proof receipt seals message, tracker, or system ids into a durable record. Sealed means those ids are attached and inspectable. Verified (when your workspace uses review) means a reviewer confirmed the evidence matches the required fact.
What breaks without it
Status gets ahead of reality. Finance, support, and other lanes rework or invent completion.
What burns a token
Proof receipt sealed Sealing evidence into a receipt so a finished step 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 check.
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.
What breaks without it
Handoffs drop half the story. Agents re-ask the customer. 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.
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 — 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. Compliance becomes a retrospective instead of a control.
What burns a token
Policy capsule injected Injecting a versioned capsule when a decision is due.
What you get back
Decisions made against the policy that was current then — not against memory.
Who it’s for
Teams whose work
crosses systems.
Built for teams whose work crosses systems, owners, and agents—and where “done” has financial or operational consequences.
Multi-agent fleets
Several agents or lanes must hand off without dropping context — or claiming a step finished without evidence.
Ops-minded founders
You need one place that holds progress and proof when the path gets messy.
Multi-tenant operators
Customers, teams, or environments share one product but must stay scoped.
Positioning
Where Wakehold
fits.
Wakehold is the environment where completion is defined and shown: tenant controls, workflow definitions, evidence rules, visibility, support, and admin. Included usage is a token pool for completed control-plane events; events past that pool are additional usage.
- The environment You get the workspace that holds paths, evidence rules, and who owns the next step — not a meter by itself. Early access is priced as usage; the environment is included.
- Usage 10,000 tokens cover about 2,500 four-event sequences (wake, receipt, packet, capsule). Later milestones, receipts, and handoffs are additional events. Model inference stays on your runtime.
Tokens
How burns fit
the story.
Usage is a prepaid token pool for completed control-plane events. The environment those events run in — definitions, evidence rules, visibility, support, and admin — is described on Pricing.
Do I pay per agent seat?
No. Tokens meter control-plane work — not headcount. More completed events burn more; idle fleets burn less.
What exactly burns a token?
Each completed control-plane event burns tokens (default: 1 token per event): wake processed, proof receipt sealed, work packet transferred, policy capsule injected. The Project Atlas walkthrough above shows four illustrated burns; later onboarding milestones may create additional receipts or handoffs.
What about retries?
A retry that successfully re-processes an event burns again. Attempts that never complete a burn event do not consume tokens.
What happens at zero balance?
Control-plane events that require tokens pause until you top up. Existing records and proof already on the ledger remain readable.
Do unused tokens expire?
Unused tokens don’t expire for 12 months from purchase. Beyond that, contact us. See the Terms of Service.
Where do I buy packs?
On Pricing: Spark, Current, and Surge, each with the Wakehold environment. Checkout uses Paddle (Merchant of Record). If checkout does not complete, email [email protected].
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. For isolation and proof-trail notes, see Security.
Proof trail you can inspect
Receipts seal evidence. Packets carry ownership. Capsules pin policy versions. Together they give operators a trail — paid with the same token pool that meters the work.
Next step