Develop context
Express, question, research, challenge, and refine what should exist.
The context development platform
Make waves.
Talk, point, and gesture on an open canvas where prototypes flow into production. Deckwright keeps decisions, constraints, and context intact across every agent and surface. Built for taste-driven founders, design studios, and maker teams iterating great ideas into verified, shipped software.
Prototype → production
BYOM
Use existing code
Desktop + iPad
The Bench · actual product
Emplace context
Promote durable decisions into governed scopes that inherit and compound.
Execute against context
Specify, approve, build, review, test, and verify against the same source of truth.
Code is regenerable from context. Context is not regenerable from code.
One context stream acrossthree surfaces.
The Bridge develops thinking. The Bench shapes prototypes. The Board governs work. Artifacts move between them without forcing the crew to reconstruct the project at every handoff.
Surface one: The Bridge
Develop ideas polyphonically.
Talk to one officer, several officers, or the whole crew. Forward reasoning between specialized roles, inject context without triggering a reply, and prune inaccurate material from future startup context while preserving the record.
Watch the full Bridge walkthrough ↗
Surface two: The Bench
Prototype out loud.
Desktop + iPad · full Apple Pencil support
The open canvas where prototypes take shape: talk and gesture them into being, generate imagery in the loop, work live surfaces and HTML in place - and attach any of it directly to mission cards as real, buildable context.
Watch the full Bench walkthrough ↗
Surface three: The Board
Turn decisions into governed work.
Mission cards carry context - specifications, files, stack details - as scoped payloads on a Context Inheritance Chain. LLMs hallucinate when they lack information. Inheritance makes sure each agent starts with all of it.
Watch the full Board walkthrough ↗
Context Inheritance Chain
Mission
Broadest mission truth
product promisevisual language
Stages
Stage context
Cards
Task Card context
Production
Polyphonic context development
Do not ask one model to be everyone.
The crew is not a stack of interchangeable chatbots. Chief Officer, Scribe, Librarian, Secretary, and Mapmaker have distinct briefs, authority, tools, and best-fit models. The Captain controls how their reasoning crosses streams.
FORWARD
Take one officer’s response and route it to another officer - or several - for expansion, criticism, or synthesis.
WHISPER
Inject context into an officer’s stream without asking for a response or spending an inference turn.
PRUNE
Remove inaccurate material from future officer context without destroying the historical audit trail.
DECIDE
The Captain determines what is challenged, combined, discarded, or promoted into project truth.
Forward · actual Bridge interaction
Context becomes an asset
Prototype loose,keep the gold.
Lean into the LLMs as idea generators and detail verifiers. Use cross-officer tools to accelerate prototyping. Escalate selected context to the production pipeline, as the source from which formal specs and deployed code are built.
Brownfield, not only greenfield
Attest an existing codebase into the system.
Deckwright can reverse-engineer architecture, conventions, dependencies, product patterns, and constraints so officers enter an existing repository with inherited understanding rather than a cold file tree.
- Architecture and technology map
- Existing conventions and product patterns
- Known constraints and verification targets
The specification gate
Spec writing as distributed authorship - not voting.
No single officer writes the whole truth. Each contributes the axis its role is qualified to own; the Chief Officer coordinates the questions; the Captain makes the decision.
Scope ceiling
The outer boundary: what the work may and may not become.
Visible behavior
What the user will actually see, do, and experience.
Observable proof
The evidence that makes success visible and inspectable.
Passing test
The executable, visual, or adjudicated contract fixed before build.
Governance · actual Board
Hand builds
A task-scoped builder receives the approved Bridge Packet, file scope, code map, tools, and specification. It cannot approve its own work.
Bosun reviews
A separate reviewer examines the diff against the specification and plan, then returns a passing, conditional, or failing verdict.
Secretary verifies
The verification pool executes the predeclared target and records observable evidence rather than accepting a narrative claim.
Captain decides
Human authority remains at consequential approval and deployment gates. Failed proof loops back into the system.
The asset test
Keep the code and lose the context: you own a black box. Keep the context and lose the code: you can rebuild.
Deckwright treats code as the current executable form of a richer asset: the intent, decisions, constraints, specification, proof, and rationale that produced it.
See the product move
Full walkthroughs.
These are not concept films. They show the live Bench, Bridge, and Board - including forward, attach, inheritance, attestation, and production controls.
09:40 · video
The Bridge
Orchestrate officers, forward ideas, prune noise, and promote decisions.
Watch full walkthrough ↗
09:29 · video
The Bench
Talk, gesture, generate, manipulate, and attach visual context.
Watch full walkthrough ↗
06:34 · video
The Board
Govern stages, inherited context, specifications, cards, and code attestation.
Watch full walkthrough ↗One proving ground
Deckwright is being built with Deckwright.
The same capture layer and gated production pipeline shown here are used to design, implement, and evolve Deckwright itself. This is not a mock interface or a separate demo path. Deckwright's own codebase is the proving ground for the system.
The thinking behind the system
Read the architecture.
The product is visual. The thesis underneath it is structural: context as the durable asset, the Captain as decider, and metaphor as a working harness.
Platform overview
Why Deckwright?
An instrument for software: creative expression above, a production-grade engine below.
Read article → CaptureWe record what you meant.
Why voice, gesture, pencil, timing, surface state, and runtime behavior belong in the specification.
Read article → Agent coherenceWhy a ship?
The nautical metaphor is not decoration. It is the first layer of the system’s coordination harness.
Read article → ProductionThe production pipeline.
How context, specification, handoff, independent review, human gates, and verification fit together.
Explore pipeline →You are not the prompter
You are the decider.
Talk and gesture the vision into being. Let the crew develop it. Promote what survives. Execute against context that does not lose the plot.