The manual exists because toolkits fail at delivery, not code.
Most buyers do not abandon a toolkit because it is low quality. They abandon it because they cannot find the usable surface fast enough. A manual-first delivery path turns the purchase into a sequence: receive, open, follow, recover.
The repo-maze failure mode
When a product is "the repo", the buyer spends their first hour answering questions they should not need to answer: what folder matters, what is deprecated, what is safe, what is optional, what is marketing.
- High friction means low adoption, even if the tech is strong.
- Low adoption means the workflow never gets governed.
- Ungoverned workflows drift until something breaks in production.
Manual-first means the buyer path is part of the product
The SCBE AI Governance Toolkit is paired with a manual and a recovery route. This is not "documentation as an afterthought". It is the shortest route from checkout to a governed workflow running on a smaller surface.
- Manual: the only route the buyer needs on day one.
- Delivery: clear access steps that do not depend on tribal knowledge.
- Recovery: a support path when something is missing or broken.
If you want the whole repo
The full SCBE repo exists. The toolkit exists so you do not have to start there. Start with a smaller governed surface, then expand.