How to Use This Canon
Stunspot’s Guide to AI Systems is designed to work in two ways:
- as a human-readable field manual for practical AI systems design;
- as model-readable reference material for AI Projects, RAG systems, long-context workspaces, and agentic design workflows.
The canonical source reports live in /docs/.
Bundled upload formats live in /knowledge-packs/.
Quick Start
Use the Guide in one of four ways:
| Use Case | Best Format |
|---|---|
| Reading and browsing the canon | /docs/ |
| Uploading to an AI Project or RAG workspace | /knowledge-packs/by-part/ |
| Uploading when smaller files or cleaner retrieval boundaries are preferred | /knowledge-packs/by-volume/ |
| Local search, archival use, or full-corpus import | /knowledge-packs/omnibus/ |
Most users should start with the By Part pack. It gives broad coverage with low upload friction while avoiding both extremes: one giant file or dozens of separate reports.
Use It as Project Knowledge
For ChatGPT Projects, Claude Projects, NotebookLM-style tools, or other AI workspaces, upload the relevant knowledge pack.
Recommended order:
- Start with
/knowledge-packs/by-part/. - Upload only the parts relevant to your task when possible.
- Use
/knowledge-packs/by-volume/when you want smaller files or more precise retrieval boundaries. - Use
/knowledge-packs/omnibus/only when the platform handles large single-file knowledge sources well.
The goal is to give the model enough canon context to reason well without forcing the retrieval system to chew one giant undifferentiated brick.
Use It as RAG Substrate
For custom RAG systems, the best source is usually the canonical report structure in /docs/.
Use individual reports when you want:
- precise chunking;
- better source attribution;
- cleaner retrieval boundaries;
- easier updates;
- report-level metadata;
- stronger citation and traceability.
Use bundled packs when your platform is simpler and expects fewer files.
Use It as an Architecture Reviewer
The Guide is especially useful when asking an AI system to review, critique, or improve an AI design.
Use it to evaluate:
- prompt systems;
- RAG pipelines;
- model-routing plans;
- agent workflows;
- tool/action boundaries;
- eval plans;
- governance models;
- product architecture;
- adoption plans;
- vendor strategy;
- operational readiness.
Minimal Loading Strategy
Do not load the whole canon by default.
Load the smallest useful unit:
| Task | Suggested Loading |
|---|---|
| Prompting / model steering | Volume 1 |
| RAG / knowledge systems | Volumes 1–2 |
| Model selection or serving | Volumes 1, 3, 4 |
| Agents and tool use | Volumes 1, 5, 7, 9 |
| Multimodal systems | Volumes 6, 8, 9 |
| Security and failure analysis | Volumes 7, 9, 10 |
| Product and adoption | Volumes 8 and 11 |
| Governance and operations | Volumes 9–10 |
| System doctrine / design review | Volume 12 |
| Broad AI architecture review | By Part pack or By Volume pack |
Load more only when the task actually needs it.
Choosing Between Pack Formats
Source Reports
Use /docs/ when cloning the repo, building a serious RAG index, citing specific reports, or editing the canon.
By Part
Use /knowledge-packs/by-part/ as the recommended default for most AI Projects and RAG workspaces. It preserves major canon structure while keeping file count low.
By Volume
Use /knowledge-packs/by-volume/ when the By Part files are too large, when you want smaller upload units, or when cleaner retrieval boundaries matter more than file-count simplicity.
Omnibus
Use /knowledge-packs/omnibus/ when you need the entire canon as one file for local search, archival use, or a platform that handles large single-file knowledge sources well.
For most hosted RAG and Project systems, the omnibus is not the best default.
Special note: NotebookLM has a powerful RAG/knowledge-graph infrastructure and can usually handle the omnibus file well.
Suggested Instruction
When loading the Guide into an AI system, give the model a clear usage frame:
Analyze, design, critique, or improve the requested AI system using Stunspot’s Guide to AI Systems as governing reference material, not decorative background reading. Retrieve and apply the Guide’s vocabulary, doctrine, design patterns, failure modes, interface logic, evaluation standards, and operational assumptions as the frame through which the system is understood. Do not merely summarize the Guide. Use it to improve the precision, realism, safety, and build-awareness of the work.
Reading Paths
For human reading paths, start with the Canon Map.
For upload formats, start with the Knowledge Packs page.