Content generation guidelines

Purpose

The Brokenhouse website is the human-readable surface of a deeper agentic startup readiness model. It should explain the structure, intent and judgement behind the playbook without publishing the full assessment method.

The public content should help a CTO, founder or technology leader understand:

• what decision is being made
• why the decision matters
• what themes need attention
• how the stage connects to the next one
• where deeper guidance exists

It should not publish detailed agent prompts, evidence rubrics, internal scoring logic, client examples or proprietary assessment heuristics.

Source relationship

The operational source material lives in agentic-saas. That repository owns the gates, controls, skills, templates and detailed assessment knowledge.

The website owns curated public artefacts:

• playbook pages
• public references
• public blueprints
• content generation guidelines
• blog and service positioning

Public playbook rules

Each public playbook page should:

• read as a CTO-facing guide
• make the stage decision clear
• explain the reason the gate exists
• include enough context to be useful without becoming a checklist dump
• link to related public references
• avoid exposing the deeper assessment method

The page should show the outline of the underlying operating model, not the machinery.

Reference rules

Public references should explain the topic and why it matters. They can provide enough context for the reader to recognise the problem and start a useful conversation.

Public references should be tagged as Startup when they are specific to the startup journey, or Common knowledge when they are reusable CTO guidance placed into the startup flow.

Public references should not include:

• full control checklists
• evidence collection instructions
• internal agent workflows
• detailed risk scoring instructions
• proprietary prompts
• sensitive client examples

Blueprint rules

Public blueprints describe how website content is curated. They are not the operational source of truth. Their job is to make the content model visible enough to be trusted without exposing the private assessment layer.

Future playbooks

This playbook is for a startup moving from POC to Production. Future CTO playbooks may target different situations, such as entering a mature company, assessing current-state drift and bringing an organisation back into line.

Those playbooks may overlap with the startup playbook, but they should have their own structure, gates and public content model.