Operator · Sandbox · Slice 101

Demo state summary

Current production status as of Slice 100. Use this page before and during every demo session. No backend calls are made from this page.

What is live and production-verified

What is not yet live

Demo · Start here

Start here — live demo path

Follow this path for every live demo. Each step must be approved before the next runs. Do not skip gates.

Supporting surfaces

Product · Workflow

Input → Output → Outcome

What a founder puts into Klariven, what the workflow does with it, what comes out, and what the outcome is for their next campaign. Every step requires operator approval — nothing auto-advances.

Every lane requires operator approval before advancing. No copy is generated from unapproved claims. No content ships without a review gate. This workflow is the same whether the demo is run live or shown from the Slice 97 verified ZIP.

Demo · Example scenario

Demo scenario

A neutral fictional B2B SaaS example — concrete enough to make the workflow legible. Use this when explaining Klariven to a founder or buyer who asks "what would this look like for a real product?"

Meridian is a fictional product used only to make the workflow concrete. No real customer data, no real campaigns, no real publishing. The same workflow structure applies to any founder-led B2B product with a real buyer, a real pain, and real proof points.

Demo · Honesty posture

What this demo proves / what it does not prove

Be explicit about this with every founder, buyer, or design partner. The sandbox demo proves the workflow and product narrative — not production-readiness for live publishing or multi-tenant accounts.

Demo · Artifact proof

Verified artifact proof

Slice 97 production smoke session — verified 2026-05-04. Use these IDs to retrieve the demo ZIP at any time.

Buyer docs confirmed inside ZIP

Retrieve demo ZIP

Demo · Pre-session checklist

Demo checklist

Run before every session. Expected: all 6 workflow pages 200, R2 binding live, bucket found.

Pre-demo health check

Artifacts to have open before the call

• □ Opportunity intelligence shell — open app-entry.html#opportunity-intelligence in a browser tab. Confirm "Future · Not live" label is visible.
• □ Design partner application — open design-partner.html. Confirm apply form and trust pills render.
• □ Demo ZIP retrieved — run the retrieve command above. Have the extracted ZIP folder open so buyer docs can be shown live.
• □ EXPORT_MANIFEST.json open — open in a text editor. Show not_live_capabilities and provenance_note fields.
• □ REVIEW_CHECKLIST.md open — confirm all 8 review sections visible, "Klariven does not auto-post" present.
• □ Intake page ready — open intake.html in a fresh tab if running a live workflow demo.

15-minute demo structure

1. Opening (2 min) — what Klariven is, what it is not, review-gated position
2. ProductTruth Intake (3 min) — structured intake, not a prompt box; each field is a verified claim
3. Founder Voice (2 min) — real writing samples, not a tone preset; voice profile requires approval before scripts run
4. Script Output + UGC Ad Pack (4 min) — 6 channels from one approved truth; hooks, pain-agitate-solve, CTA
5. ZIP walkthrough (2 min) — open buyer docs live; show EXPORT_MANIFEST.json not_live_capabilities
6. Close (2 min) — design partner ask; one real business event, one package, one feedback call

Demo · Honesty guards

Known limitations Must disclose

These limitations must be disclosed proactively in every design partner conversation. The EXPORT_MANIFEST.json not_live_capabilities field documents them inside every ZIP.

What cannot be claimed in any conversation or demo

• ✗"Grok-powered" or "xAI enrichment is active" — Grok is not wired. UX shell is preview only.
• ✗"Automatic publishing" or "auto-posts" — Klariven never auto-posts. This is a design principle.
• ✗"Full MP4 video generation" — video composition manifest is produced; MP4 rendering is not live.
• ✗"Real-time market intelligence" or "competitor monitoring" — not connected.
• ✗"AI-generated images in the current ZIP" — OPENAI_API_KEY not set; images use fixture data in smoke session.
• ✗"Autonomous campaign execution" — every step requires operator approval.

Known blockers and remaining unlocks

What is safe to show openly

• EXPORT_MANIFEST.json not_live_capabilities list — show it; it is an honesty signal
• Opportunity intelligence UX shell — clearly labeled "Future · Not live"
• Review gate at every step — no step advances without approval
• REVIEW_CHECKLIST.md 8-section review — shows "review before anything ships"
• Design partner application form — live D1 lead capture, no fake submissions

Operator · Commands

Operator commands

All commands run from the repo root. Requires wrangler authenticated and jq / python3 available.

artifact-runbook.sh

leads.sh

Generate a new ZIP package (full chain)

Operator · Gate

Completion gate

What must be true before moving beyond controlled design partner outreach to broader launch.

Unlocks needed before broader launch

Reference documents

• Design Partner Readiness Packet — docs/operations/klariven_design_partner_readiness_packet.md
• Demo Script — docs/operations/klariven_design_partner_demo_script.md
• Outcome Narrative — docs/operations/klariven_outcome_narrative.md
• Production Artifact Runbook — docs/operations/klariven_production_artifact_runbook.md
• Design Partner Lead Ops — docs/operations/klariven_design_partner_lead_ops.md
• Launch Packet Index — docs/operations/klariven_launch_packet_index.md

This page is an internal operator surface. No Grok or xAI calls are made. No D1 writes occur. No backend calls are made from this page. All data shown is static and sourced from verified Slice 97 smoke results.