Content Threads

Every piece of Ship With Intent content belongs to at least one of five threads. The threads aren't categories — they're lenses. The same insight might be relevant to software leadership and game development. The same failure pattern might appear in both organizational alignment and novel writing. The threads organize without siloing.

Intent Engineering

The core thread. Intent Engineering is the practice of using AI as a structured thinking partner — not a ghostwriter, not a search engine, not a faster autocomplete. The distinction matters: using AI well isn't about prompting technique. It's about knowing what you're trying to accomplish before you start talking to the machine.

Intent Engineering applies the same thinking patterns across software, games, and novels. The practice is portable. A specification for a game feature uses the same principles as a specification for a novel chapter or a content piece. The thread documents what those principles are and how they hold up across domains.

Free content delivers the concepts and narratives. Paid content delivers the actual prompts, AI outputs, and iteration documentation — the working artifacts behind the ideas.

Full-Spectrum Delivery

What it actually takes to ship software that works in production. Not architecture astronautics. Not theoretical best practices. The concrete, unglamorous decisions about maintainability, deployment, monitoring, and resilience that determine whether something survives contact with real users.

This thread is grounded in twenty years of working at every layer of the stack. Every principle is tied to a specific engineering failure or decision point — not generic advice, not "best practices" divorced from context.

The Human Layer

The thesis behind Ship With Intent: most technical teams fail not because of engineering, but because of misalignment between people and mission. AI accelerates failure when organizations can't align humans first.

This thread covers mission alignment without cult-speak, metric substitution and its consequences, and why the most expensive engineering failures come from building the wrong thing the right way. The tone is direct about organizational dysfunction. The value is honesty, not diplomacy.

Building a Game

Poopborne — documented in real time. This thread follows indie game development with process visibility as a first principle. Process-visible means showing the actual state: what's working, what broke, what got redesigned, what the code looks like when you're figuring it out. Not a highlights reel.

Intent Engineering applied to game design means the same specification-driven approach used in enterprise software applies to game mechanics, level design, and player feedback loops. The thread documents what that looks like in practice, including the parts that don't work yet.

Writing a Novel

The novel Agentic — using AI to develop thematic depth, character motivation, and narrative structure. This thread applies Intent Engineering to fiction. The AI doesn't write the novel. It operates within a system that loads craft rules, character voice guides, and plotline context in layers, then drafts chapters that can be audited against the specification.

Same transparency principle as Building a Game: show the draft, not just the finished page. The struggle is the content.

Why Five Threads

The threads exist because the publication's audience isn't monolithic. Engineering leaders care about organizational alignment and delivery. Indie developers care about game design and AI workflows. Writers care about craft and process documentation. Some readers care about all of it.

Five threads let each piece reach its natural audience while the publication maintains a coherent identity. The connecting tissue is the practice: Intent Engineering works the same way regardless of which domain you're applying it in.