Buyer Start Guide
What you actually bought, how to start, and how to know it works
This page is the shortest path for buyers. It explains what each package is, what should be inside it, what it does not include by default, and what to do in the first ten minutes so you can get to a real working outcome instead of digging through the whole project.
Package map
First ten minutes
Support path
AI-readable
First ten-minute path
1. Save the receiptKeep the purchase email. It tells support what was bought and which email address was used.
2. Open the matching manualUse the package page instead of guessing from repo docs or theory pages.
3. Confirm contentsCheck the bundle against the package matrix below.
4. Run one success checkEach package should get to one specific working result first.
5. Expand laterDo not scale up until the first small use works cleanly.
Verified package map
| Package | You should get | Best first action | Not included by default |
|---|---|---|---|
| AI Governance Toolkit | Decision record template, threshold worksheet, pilot checklist, review notes format. | Choose one real workflow and complete one threshold worksheet plus one decision record. | The full SCBE architecture, hidden weighting values, or managed deployment. |
| HYDRA Agent Templates | Role templates, packet examples, launch checklist, review checklist. | Run one small swarm with explicit role ownership and one clean handoff. | A fully autonomous multi-agent platform or every possible swarm formation. |
| n8n Workflow Pack | Workflow exports, environment variable map, connector notes, validation checklist. | Import one workflow, map its environment variables, and run one safe test. | Every external credential, managed hosting, or automatic production rollout. |
| Content Spin Engine | Source-to-channel matrix, transformation patterns, review checklist, output tracker. | Turn one strong source into two reviewed derivative outputs. | Finished marketing strategy, guaranteed distribution, or push-button truth checking. |
What buyers should not have to guess
- Which manual matches the package they bought
- Whether the package needs a key or is file-only
- What the first working outcome looks like
- Where support goes if the delivery is incomplete
Use with an AI assistant
This guide is written so you can hand it to an AI assistant and say:
I bought the SCBE package named here. Use the matching manual, tell me what should be in the bundle, and walk me to the first working result without diving into unrelated architecture docs.