Internal · Demo support

Klariven demo control room

Internal preview surface. Static links only. No publishing, backend, accounts, analytics, OAuth, or platform APIs are implemented here.

Start here · recommended demo order

  1. Homepage
  2. Design partner page
  3. Operator surface
  4. Content review
  5. Watermark settings
  6. LinkedIn text-post preview
  7. LinkedIn carousel preview
  8. LinkedIn native video preview
  9. LinkedIn article preview

Product surfaces

Distribution readiness surfaces

Trust posture checklist

  • Review before publish
  • Human approval
  • Visible watermark
  • Signed provenance
  • AI disclosure separated from provenance
  • No auto-publishing claims
  • No platform-performance claims

Build readiness stage

Demo-ready Yes
Validation-ready Yes
Onboarding-ready No · production backbone required
Paid-release-ready No · production backbone required

Production backbone needed before real onboarding or paid release:

  • Backend service layer
  • Auth + customer accounts
  • Database / persistence
  • API layer
  • Platform connection / OAuth (only if native publishing is promised)
  • Analytics / event tracking
  • Payments / billing
  • Publishing / export workflow (only if real publishing is promised)

Founder voice workflow · Map 1 build path · production controls pending

Definition-only in this static preview. No voice upload, no voice cloning, no AI voice generation, no third-party voice provider integration. Voice remains part of the Media Engine workflow — not a standalone voice-cloning product.

  1. 01 Voice capture / upload — founder or customer records or uploads their own voice. Map 1
  2. 02 Consent confirmation — explicit consent captured before reuse. No third-party voice without explicit consent. Map 1
  3. 03 Approved voice profile — voice profile must be approved before reuse. Profile is not automatically used for publication. Map 1
  4. 04 Script-to-voiceover workflow — approved scripts can become voiceover assets. Human approval required before export or publishing. Map 1
  5. 05 Voice usage receipt — each voice use generates a receipt showing what script/asset used the voice and the approval state. Map 1
  6. 06 Revocation / deletion — founder or customer must be able to revoke or delete voice use. Production backbone required. Map 1

Future production data objects

  • VoiceProfile
  • VoiceConsentReceipt
  • VoiceoverAsset
  • VoiceUsageReceipt

Guardrails

  • No fake testimonials
  • No impersonation
  • No third-party voice without consent
  • No publishing without approval
  • Not a standalone voice-cloning product
  • No pricing change
  • Voice remains part of the Media Engine workflow

UGC Variation Pack production controls pending

Definition-only in this static preview. No video rendering, no AI creator generation, no avatar generation, no third-party video provider integration, no automated publishing, no upload controls. UGC Variation Pack lives under Media Engine — not a standalone UGC product.

  1. 01 Approved source message — pack starts from one approved product message; claims tied to approved product facts. Map 1
  2. 02 Hook variation set — 10–25 hook variations against the approved message. Map 1
  3. 03 Script variation set — 10–50 UGC-style ad scripts as drafts requiring review. Map 1
  4. 04 Creator persona matrix — founder/operator, expert/analyst, skeptical buyer, product walkthrough, problem/solution narrator. Do not imply these are real customers. Map 1
  5. 05 Angle matrix — pain-led, proof-led, speed/efficiency-led, trust/risk-led, comparison-led, use-case-led. Map 1
  6. 06 CTA variation set — demo, waitlist/design-partner, audit/review, learn-more, founder-message. Map 1
  7. 07 Authenticity direction — anti-studio aesthetic, natural lighting shifts, handheld framing, lived-in settings, subtle camera jitter, micro-expressions, lo-fi audio direction, direct-response human pacing. Directorial notes only, not synthetic content. Map 1
  8. 08 Platform-specific captions — LinkedIn, short-form video, founder post, ad test. Map 1
  9. 09 Claim-safety checklist — no fake testimonials, no impersonation, claims tied to approved facts, unsafe claims flagged before use, human approval before export or publishing. Map 1
  10. 10 Testing matrix — hook × persona × angle × CTA × platform × claim-risk level × approval state × test purpose. Map 1

Future production data objects

  • UGCVariationPack
  • ApprovedSourceMessage
  • HookVariation
  • ScriptVariation
  • CreatorPersona
  • ClaimSafetyCheck
  • TestingMatrix

Claim-safety guardrails

  • No fake testimonials
  • No impersonation
  • Do not imply synthetic creators are real customers
  • Claims tied to approved product facts
  • Unsafe claims flagged before use
  • Human approval before export or publishing
  • UGC remains part of the Media Engine workflow — not a standalone product
  • No pricing change

Open the UGC Output Workspace → — static output workspace showing the structured pack from one approved product message.

What exists today

  • Static preview pages: LinkedIn text post, document carousel, native video, article
  • Cloudflare Pages live preview at trelmir-klariven.pages.dev
  • Demo walkthrough path (5–7 minutes) defined in Validation Pack v1
  • Design Partner Validation Pack v1
  • Design Partner Outreach Pack v1

What does not exist yet

  • No backend
  • No accounts
  • No auth
  • No OAuth
  • No LinkedIn API
  • No automatic publishing
  • No analytics
  • No payment / billing
  • No persistence
  • No real export generation

Tomorrow · outreach checklist

  • Update LinkedIn profile
  • Re-check Cloudflare Pages preview
  • Send first 3 DMs manually
  • Track replies in the prospect sheet
  • Do not send email unless needed
  • Do not send Miernowski or Onel yet
  • Do not overclaim product state

First-send candidates

Mikkel Skarnager
Spektr · fintech compliance
Hook: stop asking AI to behave and start coding it to comply
Status: send-ready · DM-first
Elad Ferber
Synthpop · healthcare AI
Hook: four-part trust framework — defined authority + visible reasoning + explicit accountability + failure designed in
Status: send-ready · email-first
Rafael Broshi
Notch · regulated AI agents
Hook: auditable, controllable, safe in production
Status: send-ready · DM-first

Cloudflare Pages QA links

This control room is an internal launch-support surface. It does not create customer accounts, publish content, connect platforms, collect data, or trigger workflows.

Klariven · Internal · Demo support
← back to operator surface · ← back to homepage