An interactive map of the ten Agentic AI Foundation projects and the links between them. Every documented line on the map is a link one project's own documentation states, with the quote and the file it comes from; examples and open seams are labelled as such.
A community map by James Wolfe, AAIF Ambassador, built from each project's own documentation.
- 10 projects in five layers: context, agents & apps, protocols, gateways, and run & train. The list matches aaif.io/projects; stages come from the technical committee table.
- 16 documented links, 1 example and 2 open seams. A documented link is stated in a project's docs. An example is a mention only. An open seam is an overlap no document settles.
- 5 flows that step through how the projects work together: a coding agent at work, through the gateway, agents talking to agents, train then serve, and an app calls a model.
- Docs and repository for each project, one click from its panel.
bunx serve .Then open the address it prints. The page reads data/*.json, so it needs to be served; opening index.html as a file will not load the data.
Needs a recent Bun: CI uses 1.4.4, and Bun 1.3 can't read bun.lock.
bun install
bun scripts/verify.tsThe script clones each source repository (shallow, into .cache/repos) and runs three tiers of tests:
| Tier | Checks |
|---|---|
| 1 · Sources | Every source repository is reachable, every source file exists, and every quote still appears in its file. |
| 2 · Stages | Every stage matches the technical committee table, and the map has exactly the projects the table lists. |
| 3 · Data | The data files are consistent: unique ids, links between real nodes, flow steps that name real links, complete project records. |
It prints every test and exits non-zero if any fails. CI runs it on pushes to main, on pull requests and once a week; when the weekly run finds drift, it opens an issue labelled drift.
- Share a path: these are some of the paths to discover relationships between the projects: the five flows on the map. Share yours: open a path issue.
- Propose a link: open a link issue with the quote and the source file URL, or send a pull request.
See CONTRIBUTING.md.
-
AGENTS.mdgives any coding agent the rules for this repository. -
.agents/skills/add-aaif-linkis an Agent Skill for adding a link the verify script can prove. -
recipes/recheck.yamlis a goose recipe that runs the verify script and proposes fixes for any drift:goose run --recipe recipes/recheck.yaml
-
recipes/review-pr.yamlis a goose recipe that reviews a pull request against AGENTS.md and CONTRIBUTING.md, with verify and typecheck, in its own worktree. Report only:goose run --recipe recipes/review-pr.yaml --params pr=<number>
Works with goose. goose reads AGENTS.md first. When the weekly verify opens a drift issue, run recheck.yaml: goose finds the current wording in the project's own repository, updates the data file and re-runs verify. Pull requests are reviewed with review-pr.yaml before they're merged. Neither commits or comments; you review and merge.
| File | Holds |
|---|---|
data/projects.json |
Projects: stage, docs, repository, origin and date joined (only where a cited source states them), and map position |
data/links.json |
Links: ends, kind, quote, source repository and path |
data/flows.json |
Flows: ordered link ids with one caption each |
Code and data files: MIT. Quotes belong to their projects and are reproduced short, with their source file linked.