Guidebook + GitHub template
The Two-Space Method
Beyond the wall: the wall is not the model. It is a missing foundation.
A practical operating system for AI-assisted software development. Written for product owners, analysts, designers, and other non-developers who already tried prompting an app into existence and watched it fall apart after two weeks.
The book
Why pure vibe coding collapses, two spaces, written briefs, two human gates, and the ops layer you still have to own. Grounded in a live enterprise multi-tenant SaaS that is still in production.
The kit
A GitHub template: standing files, docs tree, brief and investigation templates, CI hard gate, Day One script, and an on-ramp if the repo already has code.
Who it is for
- You can run a terminal command when someone writes it out.
- You cannot debug a stack trace from scratch, and you should not have to.
- You already hit the wall: the agent forgets last Tuesday, breaks last week’s work, and sounds sure the whole time.
What you will run instead
- Design space and Build space stay separate.
- The written brief is the interface. Investigations do not ship code.
- The agent opens the pull request. You merge.
- Location carries status. Findings beat claims. Scar tissue becomes a rule or a runbook.
Not the O’Reilly engineering book. This is the operator foundation and kit. One bundle. One price. Not an HPS product page.