Product evidence
Deckwright's public claims, each mapped to timestamped evidence in the three walkthrough videos. The videos show the currently operating product - the same system used to build Deckwright itself - not concept renders. Each video has a full timestamped transcript: Bench (9:28), Bridge (9:39), Board (6:33). A claim not listed here should be treated as asserted, not demonstrated.
Demonstrated claims
| Claim | Evidence | Location |
|---|---|---|
| Voice and gesture become structured, durable context - not a transcript | A full-canvas multi-modal capture session parses gestural content, semantic content, hesitation patterns, and captured motion, temporally coordinated, into a persistent payload delivered to an officer for execution | Bench 00:47-02:39 |
| Speech plus pointing directs real generation, without naming tools | Shapes indicated by gesture rather than name are generated, placed, and styled; an arc of seven size-graded triangles is produced from one spoken-and-gestured instruction | Bench 01:00-02:39 |
| Capture includes behavioral and runtime data, not just visuals | A live HTML page is loaded onto the Bench; inputs, scrolls, DOM hovers, mutations, dev-console errors, and network fetches are recorded, timestamped against user behavior | Bench 03:44-04:37 |
| Captured intent attaches to governed work | Canvas elements and whole recorded captures attach to the Board and cards as build templates; captured bugs and features attach to the production pipeline; a synthesized manifesto is attached from the Bridge and inherited downstream | Bench 03:04-03:44, 09:05 · Bridge 08:20-09:31 |
| Image generation is driven by spatial composition plus accumulated project context | A box-cover image is composed by voice while gesturing regions of the canvas; the result draws on previously developed project context and lands in one shot | Bench 05:06-08:58 |
| Multiple role-scoped officers develop context polyphonically | Five named officers in separate threads; research dispatched to the Librarian; the Chief Officer's reasoning forwarded to three officers for parallel additions; synthesis across all threads into one manifesto | Bridge 01:03-08:18 |
| Context can be injected without triggering replies | The all-hands "context" send mode seeds every officer's thread silently; officers see it at next startup instead of answering | Bridge 02:05-02:42 |
| Each project builds its own research corpus | The Librarian runs a formal MCP research project into the deck's stored corpus (the sea chest) | Bridge 04:02-05:10 |
| Context inherits hierarchically through the pipeline | Board context inherits to stages, stage context to cards; stated and shown on the operating Board with previously attached artifacts present | Board 01:03-01:59 |
| Officers operate the product through permission-gated tools | The Chief Officer creates a stage and its cards via an MCP command, with the permission grant visible in the flow | Board 02:13-03:08 |
| The Captain chooses the participation level | The pipeline runs human-in-the-loop with choices and documents at each step, or the plan can be auto-deployed | Board 06:01-06:24 |
Not demonstrated in these videos
- A card carried end-to-end through build, independent review, verification, and deployment on screen. The pipeline stages and gates are shown on the Board; the execution run is not filmed in these walkthroughs.
- The Bench running on iPad with Apple Pencil captured as a first-class stream. The iPad surface is released and in use, but these walkthroughs were filmed on desktop; the pencil-capture path is not on screen here.
- Multi-user collaboration on one deck.
- Performance under load, scale limits, or benchmark comparisons.
- External or third-party validation. The system's daily proving ground is Deckwright's own development; no external audit has been performed.
- Security posture beyond what is visible (permission gates on officer tool use).
For the current status of each capability - implemented, demonstrated, internally validated, externally validated, or planned - see the technical diligence brief.