◆ Cross-category trail
AI-Native Operating Model
How the full engineering system enables AI-native work. This trail borrows articles from Engineering and Agentic Engineering & Q — each keeps its primary home; here they read as one story.
10 guided reading paths, each an ordered ascent through one subject. The elevation strip shows a trail's length and shape — pick one and follow it end to end.
How the full engineering system enables AI-native work. This trail borrows articles from Engineering and Agentic Engineering & Q — each keeps its primary home; here they read as one story.
A seven-part series exploring Osprey Strike from problem space to production — what emergency callout management is, the domain landscape that shapes it, how the system solves it, and why the architecture looks the way it does.
The operating map for Q and OpenClaw: trust boundaries, lanes, event routines, and remote development boxes.
A three-part series on Conduit — why we built a static-site dev-log aggregator that runs on per-project publishers and an LLM, how its architecture splits responsibilities between project repos and the consumer site, and what running it actually looks like in practice.
A new-hire's path through how Constructured actually ships software: the philosophy, the required tools (beads, timbers, just, the gates), the recommended ones (codex, worktrees, RTK), and the day-to-day workflow from spec to merge.
A user-first guide to working with Q from Slack: what Q can do in the observer sandbox, how its tool access works, what it remembers, and where operator-only details begin.