Operational guides that follow the pipeline.
From first-site setup through advanced automation configuration, each playbook follows the IGNY8 pipeline. Written for operators, not administrators — the focus is on decisions that affect authority outcomes, not button-click sequences.
From first site to advanced automation.
Each playbook walks a real operational task, in pipeline order.
First-site setup
Connecting a site, reading its authority profile, and generating the SAG blueprint.
Cluster strategy
Choosing sectors, building clusters, and prioritising the mesh.
Automation configuration
Stage toggles, batch sizes, and budget ceilings for the pipeline.
Decisions, not button clicks.
A playbook is about the choices that move authority, not the location of a setting.
For operators
Written for the person commissioning a strategy, not administering a tool.
Pipeline-ordered
Each playbook follows the pipeline from research to publishing.
Outcome-focused
The focus is on decisions that affect authority, not interface mechanics.
Every playbook follows the pipeline.
The structure is consistent, because the pipeline is consistent.
| Stage | What the playbook covers |
|---|---|
| Setup | Connecting the site and reading its profile |
| Strategy | Choosing sectors and building clusters |
| Production | Configuring content, linking, and schema |
| Operation | Running automation and reviewing outcomes |
- The decisions that matter at each stageDecisions
- Why each choice affects authorityRationale
- A consistent, pipeline-ordered structureStructure
Teaching the interface
A tutorial that walks the buttons teaches where things are, not what to do with them.
- Walks the buttons in order
- Teaches where settings live
- Says what to click, not why
- Goes stale when the UI changes
Teaching the decisions
A playbook teaches the choices that move authority — the interface is incidental.
Pipeline-ordered. Operator-written. Decision-focused.
Where how-to guides usually fall short.
A guide that teaches clicks teaches nothing about authority.
| Anti-pattern | Why it fails | The playbook approach |
|---|---|---|
| Button-click walkthroughs | Teach the interface, not the strategy | Playbooks teach the decisions that move authority |
| Guides written for administrators | Miss the operator's actual job | Written for operators commissioning a strategy |
| Steps in no particular order | No mental model of how the work flows | Each playbook follows the pipeline, stage by stage |
| Advice with no rationale | Operators cannot adapt it to their case | Every choice is explained by why it affects authority |
Setup, strategy, production, operation.
Each playbook moves through the pipeline in the order an operator actually works.
- 01SetupConnect the site and read its authority profile.
- 02StrategyChoose sectors, build clusters, prioritise the mesh.
- 03ProductionConfigure content, linking, and schema for the run.
- 04OperationRun automation, set the budget, review the outcomes.
Run your first playbook.
Connect a URL and follow the first-site setup playbook from the start.