The Board walkthrough
What this demonstrates
This is the operational Deckwright The Board, not a concept animation or a design mockup. The governed production pipeline surface: hierarchical context inheritance from board to stage to card, officers operating the product through permission-gated MCP tools, cards as units of deployable code, and a human-in-the-loop pipeline that can also be auto-deployed when the Captain chooses.
Capabilities demonstrated, with timestamps
- [00:00-00:54] The Mission Board as the top of the pipeline, with officers as in-product guides: deeply connected to the functionality, holding the tools, able to walk the user through any part of the system.
- [01:03-01:18] A default tech stack and previously attached context (the manifesto and cover image from the other two walkthroughs) present on the board.
- [01:18-01:59] Hierarchical context inheritance stated and shown: board context inherits everywhere; stages inherit board context and add their own; cards inherit stage and board context - keeping work tightly scoped and consistent.
- [02:13-03:08] The Chief Officer creates a demo stage and its task cards through an MCP command, with the MCP permission gate visible in the flow.
- [05:08] Each card represents a unit of deployable code.
- [06:01-06:24] The participation dial: the Captain can make choices and read documents at every step, or have the plan auto-deployed - shown as a compressed view of a full human-in-the-loop production pipeline.
What this walkthrough does not establish
- The demo stage is explicitly built with insufficient context (the narration says so); it shows the mechanism, not a production-quality specification.
- It does not show a card carried through build, review, and verification to deployed code within this video.
- It does not show the independent-review (Bosun) or verification gates executing on screen.
- The narration audio repeats a passage and ends abruptly; this transcript reflects the audio as recorded.
Timestamped transcript
[00:00] So once you have enough context collected to start developing, you come to this screen,
[00:07] which is the Mission Board.
[00:11] And as far as knowing when you have enough context, or really as far as knowing how to
[00:17] do any of the things that you can do in Deckwright, all you have to do is ask an officer.
[00:25] They're deeply connected to the functionality.
[00:29] They have all the tools.
[00:30] They understand the stack from top to bottom.
[00:33] They understand the process from top to bottom.
[00:36] So they'll give you feedback.
[00:38] If they feel like they have enough, if they feel like they need more, they can give you
[00:43] instructions and detailed descriptions of how to use any given part of the system.
[00:49] They can walk you through it.
[00:50] They can probably do a better job than I can.
[00:54] So this is the place that you come when you have gathered enough context.
[00:59] Now we don't have enough context, so we're just going to mock some stuff up.
[01:03] First thing you have is a default tech stack.
[01:06] It's just what I have installed to work with.
[01:10] This is your context, so we have the manifesto and the cover image are already attached.
[01:18] The way this works is context is inherited.
[01:22] So the top level context is inherited everywhere.
[01:26] The next level down is stages.
[01:29] Stages inherit board context and they have their own context.
[01:35] And within a stage, you have task cards and those task cards inherit the stage context
[01:43] and the board context and have their own context.
[01:45] But this keeps the scope of the work tightly focused and incredibly consistent from stage
[01:54] to stage, from card to card, because they're all inheriting back up the same pathway.
[01:59] So in this case, we're just going to have CO create some arbitrary random...
[02:06] Let's do a login.
[02:08] Let's make the stage for the login.
[02:10] So we'll say...
[02:13] Okay, CO, I want to do a demo here.
[02:17] I know we don't have enough context, really, but let's put together just a demo stage where
[02:26] we can work through the login process for a game like this.
[02:31] So give me the stage and give me the cards that would be in a stage like that.
[02:38] And this is an MCP command.
[02:42] I'm saying this to you, CO, but I'm also saying it for the people listening and watching on
[02:46] the walkthrough.
[02:47] Since it's an MCP tool, you're going to require the MCP permission, so you have it.
[03:02] And we'll just cut ahead after he creates it.
[03:07] Excellent.
[03:08] So this is stage one, and these are the cards, the various steps in the login process that
[03:24] the CO has just sort of mocked up.
[03:26] But they're going to be pretty useful because the officers are all very experienced software
[03:36] developers.
[03:38] So once you have enough context collected to start developing, you come to this screen,
[03:45] which is the Mission Board.
[03:49] And as far as knowing when you have enough context, or really as far as knowing how to
[03:55] do any of the things that you can do in Deckwright, all you have to do is ask an officer.
[04:03] They're deeply connected to the functionality.
[04:07] They have all the tools.
[04:08] They understand the stack from top to bottom.
[04:11] They understand the process from top to bottom.
[04:14] So they'll give you feedback, any given part of the system.
[04:19] They can walk you through it.
[04:20] They can probably do a better job than I can.
[04:24] Okay, CO, I want to do a demo here.
[04:28] I know we don't have enough context, really, but let's put together just a demo stage where
[04:36] we can work through the login process for a game like this.
[04:41] So give me the stage and give me the cards that would be in a stage like that.
[04:48] Once it's an MCP tool, you're going to require the MCP permission, so you have it.
[04:56] Excellent.
[04:57] So this is stage one, and these are the cards.
[05:04] The CO is just sort of mocked up.
[05:06] Okay, so let's take a look at this.
[05:08] Each of these cards represents a unit of deployable code that we want to execute.
[05:15] So let's open one up.
[05:48] Attempts to keep them from going off the rails.
[05:57] In this case, we're doing a really good job.
[06:01] If you don't want to participate to that level where you're making choices and reading documents
[06:06] and whatever, you can just have the plan auto-deployed.
[06:10] You can do that with this entire thing.
[06:12] So I'm about to show you in a really, really compressed way what a full human-in-the-loop
[06:20] production pipeline looks like.
[06:24] But you can also understand...