What should happen after someone buys a package
This page locks down the buyer experience: receipt, delivery link, manual, access notes, and the recovery path if something does not arrive. Not every product needs a key. Every product should have a manual and a clear support contact.
Standard delivery sequence
Minimum delivery packet fields
| Field | Required | Notes |
|---|---|---|
| Product name | Yes | Matches the package card and the manual title. |
| Version | Yes | Lets the buyer and support talk about the same build. |
| Download link | Yes | The buyer needs a direct route to the files or assets. |
| Manual link | Yes | Points to the package-specific page in this manual hub. |
| Access key / invite | If applicable | Only include it when the product actually uses hosted access or private assets. |
| Support contact | Yes | [email protected] |
| What to verify | Yes | A one-line success check so the buyer knows they are done. |
Practical rule
If a package is file-only, do not pretend it needs a key. If a package uses private or hosted access, do not bury the key in a generic message. State it directly in the delivery note.
Non-open-source delivery check
Public source stays on GitHub. Paid delivery packets stay outside the public site repo and should be sent through buyer-only links. Current package builds are generated locally from python scripts/package_products.py in the SCBE-AETHERMOORE repo, and Stripe fulfillment can point buyers at private URLs through SCBE_TOOLKIT_DOWNLOAD_URL and SCBE_TRAINING_VAULT_DOWNLOAD_URL.
Current customer delivery surfaces
| Surface | Customer purpose | Public link |
|---|---|---|
| Training Bus proof | Shows the Operator Agent Bus and latest constrained-decoding gate result. | Open proof |
| Offer delivery proof | Shows the package delivery readiness checks and buyer-packet path. | Open offers |
| SCBE project manual | Documents buyer-only download URL configuration and recovery handling. | Open SCBE manual |
Universal buyer checklist
- Save the receipt email. This proves which product was bought and which email address should receive delivery.
- Open the matching manual. Use the package manual before exploring the repo or the architecture docs.
- Confirm the bundle contents. The package should include the files or templates named in the manual.
- Check whether a key is actually required. Many file-based packages do not need one.
- Run the success check. Each manual ends with a quick verification target.
Support and recovery
Use these subject lines so delivery issues can be triaged quickly:
- SCBE Delivery Issue — bundle link missing or expired
- SCBE Access Key Help — hosted package, private endpoint, or invite problem
- SCBE Package Support — the files arrived but the package is not working
- Open the support page — fastest route for setup trouble, AI trouble, or broken links