The curated knowledge base for software development on the Apollo V4 platform: the 68080 CPU, the SAGA chipset, ApolloOS and the ApolloCrossDev toolchain.
It is written for two audiences at once: developers, and the AI coding agents they work with. AI models know classic AmigaOS, AROS and the 68000–68060 well, but not Apollo V4. This knowledge base fills that gap so AI-assisted code uses the platform correctly and to its full potential.
Four pillars of knowledge, each with reference files, best practices and pitfalls:
| Pillar | Contents |
|---|---|
core/ |
68080 CPU and the SAGA chips: Isabelle (video), Arne (audio), Anni (DMA), Maggie (3D) |
hardware/ |
The V4 boards: shared knowledge in v4-generic/, and per model: Standalone (SA), UniCorn (UNI, A6000), IceDrake (ICE), Manticore (MC), Firebird (FB) |
os/ |
Running on V4 under ApolloOS R10, AmigaOS 3.9 and 3.2; OS takeover; ApolloOS internals (libraries, devs, filesys, commands, datatypes) |
toolchain/ |
ApolloCrossDev setup, options and syntax |
Each pillar has best-practices/ (how to write optimal code using all Apollo
V4 features) and pitfalls/ (known traps and how to avoid them).
Cross-cutting folders:
| Folder | Contents |
|---|---|
guides/ |
Step-by-step how-tos |
examples/ |
Small, compiling, tested code |
conventions/ |
Team coding style and process |
lessons/ |
Project retrospectives |
Supporting folders: templates/ (templates for knowledge base files, code
repositories and seed content), sources/ (original official documents),
tools/ (CI scripts), and later skills/ and evals/.
Each file shows its owner, its status (draft, reviewed, verified,
deprecated), where its facts come from (the core developer, measurements,
official documentation or source code) and which core revision, target OS,
execution mode (os-friendly or os-takeover) and V4 model it applies to.
-
Add the knowledge base as a submodule in the repository root:
git submodule add https://github.com/ApolloTeam-dev/ApolloKnowledgeBase.git ApolloKnowledgeBase
-
Copy
templates/repo/AGENTS.mdandtemplates/repo/CLAUDE.mdto the repository root and fill in the placeholders. -
To pick up the latest knowledge base changes:
git submodule update --remote ApolloKnowledgeBase
AI agents working in that repository then find and follow the knowledge base automatically.
Everyone in the Apollo community can contribute. Read CONTRIBUTING.md for
the file format and review process. The most valuable contributions are:
- Places where ApolloOS, the 68080 or SAGA differ from what developers (and AI models) expect
- Measured optimization techniques, for the pillars'
best-practices/ - Bugs you hit and how you fixed them, for the pillars'
pitfalls/ - Lessons from your projects: AI agents offer to draft one at the end of a
project and submit it as a pull request (see
CONTRIBUTING.mdsection 7)
AI agents: start with AGENTS.md.