Knowledge Packs

Stunspot’s Guide to AI Systems is available in multiple packaging formats for AI Projects, RAG systems, local search, and long-context workspaces.

The reports in /docs/ are canonical. Files in /knowledge-packs/ are derived packaging copies. If a pack and a source report disagree, the source report wins.

Use the By Part pack unless you have a specific reason not to.

It gives you five files: one per multi-volume canon part. This is the lowest-file-count option that still preserves major retrieval boundaries instead of collapsing everything into one omnibus file.

Before upload, check the platform’s current file-size, file-count, retention, privacy, and context limits. Upload only the units relevant to the task when possible.

Pack Types

Pack Files Best Use Link
By Part 5 Recommended default. Good broad coverage with low file count. Open By Part pack
By Volume 12 Use when you want smaller files and cleaner retrieval boundaries. Open By Volume pack
Omnibus 1 Use for archival, local search, local models, or platforms that handle large single-file knowledge sources well. Open Omnibus
Source Reports 37 Best for cloning the repo, precise indexing, citation, editing, and source navigation. Open Canon Map

Use and Recovery

  1. Choose the smallest pack that covers the task.
  2. Confirm that the platform accepted the complete file.
  3. Ask one task-specific question that should retrieve a named report or canon handle.
  4. Inspect the retrieved passage or cited report before relying on the answer.

If upload fails or retrieval is diffuse, step down from OmnibusBy PartBy VolumeSource Report. Adding more text is not a retrieval strategy; sometimes it is merely a larger haystack wearing an innovation badge.

For the complete load, probe, verification, and recovery procedure, see How to Use This Canon.

How to Choose

Use By Part when you want the best default Project/RAG upload format: five files, broad coverage, low upload friction.

Use By Volume when you want smaller files, cleaner retrieval boundaries, or more selective loading.

Use Omnibus when you want the entire canon as one searchable local file or archival artifact.

Use Source Reports when you are cloning the repo, building a precise RAG index, citing specific reports, or editing the canon.

Pack presence and report-heading coverage are checked by the repository’s deterministic validation gate. That establishes packaging completeness, not model retrieval quality or factual correctness.