# Building Terminal Graph, a Spatial Development Environment > [!question] Lingering Questions > - Does Terminal Graph's canvas UI have a documented accessibility/keyboard-navigation story? Check https://kaidan.dev. > - What does Terminal Graph's v1.0/GA release and blueprint-marketplace maturity look like as a follow-up story? > [!tip] Article Ideas > - none beyond the fleeting-queue watch item above > [!link] Cross Reference > - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — a case study in primitive-first product design under conflicting beta feedback > - [[3. Resources/MOCs/Visual Thinking MOC]] — canvas/graph-based spatial UI as an alternative to fixed-panel developer tooling > [!quote] Vocabulary > - **blueprints** — Terminal Graph's planned mechanism for exporting a whole node/connection workflow as one importable file, so a team can share a process without teaching it step by step ## Bib capsule Caidan Williams, interviewed on "Building Terminal Graph, a Spatial Development Environment," (YouTube), 2026 — https://www.youtube.com/watch?v=fUJRKhjen_I ## Author's thesis (Adler Q1+Q2) Caidan Williams, a partner at Internet Development Studio (indev), built Terminal Graph — a canvas-based development environment where terminals, browsers, file editors, and notes live as connected nodes on an infinite Figma-like surface, with Unix-pipe-style data flow wired between them. It's a genuinely novel entry in the "AI coding tool" wave: rather than a fixed three-panel layout (file tree / chat / diff), it treats the workspace itself as a graph the developer composes and rewires, with no direct prior art for the node-to-node data piping according to Williams's own search. Built solo in two weeks and validated through Williams's own daily use, it's now being productized around a "blueprints" workflow-sharing mechanism, while indev — bootstrapped, not VC-backed — needs product revenue to reduce client-work dependency. ## Key arguments (≤3) 1. **Data flow between nodes is the actual differentiator**, not the canvas UI itself — plenty of tools have a canvas; few pipe data between arbitrary node types. 2. **Primitive-first design is a deliberate response to conflicting feedback** — rather than picking a winner among contradictory beta-user requests, Williams builds composable primitives users can combine their own way. 3. **Blueprints are the next lever for adoption** — packaging a whole workflow as one importable file removes the friction of teaching a process step by step. ## Claim atoms ### Data flow between nodes is Terminal Graph's key differentiator > [!quote] > "I do truly think that the data flow is the most unique aspect that separates itself from others." **Where/why**: Mid-interview, responding to "what sets it apart from other apps." The clearest one-sentence positioning claim in the episode. #xref ### Build primitives, not an everything app, when feedback conflicts > [!quote] > "I'm trying to make sure I'm not building like an everything app... The way that I'm trying to focus on building this is I want to build the primitives such that other people can build out what they need with it." **Where/why**: Said describing how he filters contradictory beta-user feedback. Directly actionable design-philosophy statement, reusable for any product-prioritization discussion. #xref #aphorisms ### Blueprints let teams share whole workflows as one importable file > [!quote] > "You download terminal graph. You import it and just click run and it just does the thing... there wouldn't be the need to like have that kind of like friction of teaching somebody this process." **Where/why**: Introduced as the next focus area after core node/connection functionality. Ties to the onboarding-speed question raised elsewhere in the episode. #xref #articleseed ## Permanent candidates - **Primitive-first design absorbs conflicting user feedback without scope creep** — when feedback conflicts, building composable primitives instead of point features lets users resolve the conflict themselves. Promoted below. ## Processing checklist - [ ] Check kaidan.dev for Terminal Graph's current beta status and accessibility story - [ ] Watch for the blueprint-marketplace and v1.0 release as a follow-up - [x] Connect into the relevant MOC — [[3. Resources/MOCs/Product & Startup Instincts MOC]] ## Links - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — primitive-first design as a founder instinct under conflicting feedback - [[3. Resources/Readwise/Podcasts/Building Terminal Graph, a Spatial Development Environment, with Caidan Williams]] — source document