Internalplatform
Proof Point Studio
Short product reels recorded from real, running software.
Internal tooling, not a product. An agent reads a repository’s own documentation and proposes value-ranked demo capabilities. It builds each one into a real interactive page, records it, and assembles the footage into a short reel.
- Internal tooling
- Provenance-gated
- Playwright recorded
- Real software only
- Agentic orchestration
- Architecture & developer experience
- Data science & evaluation
The problem
Marketing a proof-first practice with slideware undercuts the claim. But recording real software is laborious, and the moment it becomes laborious it stops happening.
The approach
The pipeline runs four typed, one-directional stages, so each can be inspected on its own. A scout proposes capabilities, each with a claim tied to its supporting evidence. A builder renders the chosen one into a real branded page, and Playwright records it headful at portrait resolution. An assembler cuts cover, demo, outro and voiceover together.
How Proof Point Studio fits together
Scout
Proposes capabilities, each claim tied to its evidence
Builder
Renders a real interactive page
Recorder
Playwright, headful, 1080×1920
Assembler
Cover, demo, outro and voiceover
What Proof Point Studio does
Footage of real software
Each reel shows real software doing the real thing, such as an eval scorecard resolving or an agent run executing. Most vendors can't post footage like that.
Four one-directional stages
Scout, builder, recorder and assembler, each inspectable on its own.
A claim tied to its evidence
Every proposed capability carries a claim bound to the evidence behind it, before it is ever recorded.
Recorded, not staged
Playwright drives Chromium headful at 1080×1920 against the real interactive page.
What’s inside Proof Point Studio
- Scout: an agent reads the target repository’s agentic docs and proposes value-ranked capabilities. Each carries a narrative arc and a claim bound to its evidence
- Builder: renders a scene spec into a real interactive web page, not a mockup
- Recorder: Playwright drives Chromium headful at 1080×1920
- Assembler: cover, demo, outro and voiceover into one file, reusing Content Engine for assembly, captions and the claim-provenance gate
The most persuasive content for a proof-first brand is not a typeset claim — it’s real software doing the real thing: an eval scorecard resolving, an agent run executing, a before/after on a live dashboard. That footage is unfakeable, which is exactly why most vendors can’t post it.
Where Proof Point Studio stands today
- One real reel end to end: a live refine run, a real interactive scorecard demo, recorded at 1080×1920 and assembled
- Ships its own agent instructions and skills, so the pipeline is agent-driven by design
The Proof Point Studio tech stack
- TypeScript
- ESM
- strict
- pnpm
- tsx
- vitest
- Playwright
- Claude
- ffmpeg
- Content Engine