Commands

Cast

Ship to one recipient, deployed and tracked

Cast turns a research piece, briefing, proposal, or report into a private deployed site for one named recipient. Watermarked, capsule-sealed, revocable in one click. You see when it opens, which sections held attention, what got clicked.

How it works

From PDF to deployed surface in
one command.

Point Cast at a source artifact and a recipient. It runs a sixteen-step cascade: triple archaeology of the recipient and the artifact, three direction options, scaffold, implement, polish, verify, deploy. The recipient gets a private URL. You get a live activity timeline.

Triple Archaeology

Cast starts with /analyze: deep recipient archaeology (latent identity, decision authority, what would feel intrusive), source artifact archaeology (load-bearing passages, drop list, what gains from interactivity), and Cast positioning (privacy, watermark, lifetime, revocation triggers).

Output: a structured recipient_brief.json that all fifteen downstream steps consume

Bespoke per recipient

No template library. Each Cast is a fresh, bespoke surface scaffolded for one named recipient. The craft expresses differently every time. A briefing for an investor reads differently from a research deep-dive for a partner from a capability narrative for a regulated buyer.

Every Cast is its own project, peer in shape to every other shipped surface

Watermarked, revocable, audited

Per-recipient watermark baked into the build. Forensic by default (invisible to recipient, visible in the audit chain), visible-mode for high-stakes Casts. One-click revoke kills the URL. Every lifecycle event (composed, deployed, dispatched, opened, dwell, clicked, revoked) is capsule-sealed.

Capsule chain exportable on demand for regulated buyers

Live activity, not dead PDF

PDFs die on send. Casts come alive. Recipient opens, section dwell, click events, scroll completion all flow back into your relationship timeline. You learn which sections held attention, which got skipped, and when to follow up. The artifact becomes a feedback loop.

Devon spent 9 minutes on the unit-economics section, skipped methodology

Beyond the PDF email

Not "please find attached."
A deployed, branded, tracked surface bound to one recipient.

PDF Email
Dies on send: no open signal, no section dwell, no click events
Forwardable forever, no revocation, no expiry
No update path: a typo means resending the whole file
No audit chain: who saw it, when, and how is unrecoverable
Cast
Live activity timeline: opens, section dwell, clicks, scroll
Per-recipient watermark, one-click revoke, configurable expiry
Update in place: deploy a new version without breaking the URL
Capsule-sealed lifecycle, exportable for regulated audits

Any artifact worth tracking

Cast anything that should not die on send.

Anywhere you would attach a PDF to an email, a Cast is the better artifact.

Briefing Cast

Strategy memo, due-diligence pack, executive summary, board prep

Research Cast

Deep-dive findings, peer-reviewed synthesis, scholarly briefings

Dashboard Cast

Investor KPI console, quarterly update, live data with section drilldown

Persona Cast

Personalized landing surface for one family, one client, one prospect

Capability Cast

Sovereignty pitch for regulated buyers: defense, healthcare, finance, gov

Internal Cast

Team update, partner brief, advisor digest with revocation on departure

Ready to cast?

Open a Space in the Workspace and run /cast from the Conductor.

Get AskQP