Claude Code AI company template ships after folder-wipe near miss

The template is a record of specific failures rather than a general framework. Writing files is deliberately withheld from the planning, marketing and quality-control roles; only product-development can write, and only within a folder defined by written rules. Quality control runs on an isolated copy under a different role from the one that produced the work, and it can block publication until fixes and re-verification clear it.

The author is explicit that the rules are mostly prose that the AI is asked to follow, not hard technical limits. External publishing, billing, contracts and account operations are left to the human, with approvals logged in a file. In the two-company setup, a settings.json deny on absolute paths stopped Write, Edit and Bash echo, but a Node script could still write when Bash was auto-allowed, so the author describes deny as a brake rather than a wall and suggests separate Windows users, virtual machines or containers for anything that must truly stay out of reach.

The stated environment is Windows 10 with Git Bash and Claude Code 2.1.296. Unverified areas include Mac and Linux, long-term operation and how well the planning exploration works in practice, and the author notes there is no track record of revenue from this setup.