AI Ecosystem Inventory Map
Next: Decide where repository and file density needs summarising or filtering. · Write the Outcome, including the per-item maps the record leaves out. · Commit the c25 experiment edits left in the qmap working tree.
last activity Apr 28
A session map shows one agent. Security teams also need the company-wide picture: which agents were active, which code and files they touched, and which tools they called.
A company-wide inventory map works on invented data from a small team to a global enterprise, plus a focused map for each kind of item. Judging density is still open.
Documents
With file names, on their own page →Start here
Documents
Pages
- /experiments/c25.ai-ecosystem-inventory-map/ (local dev)
- /experiments/c25.ai-ecosystem-inventory-map/item-maps.html (local dev)
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The same inventory map scales from a handful of agents to thousands of things.
From a demo to a global company · came from Mark Parson
- 2
Grouped by repository, each repo's files sit inside it, with the agents alongside.
Repositories hold their files · came from Mark Parson
- A second page maps a single item, an agent, model, MCP server, API key, repo or session, with everything around it. New in this cycle
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
From the record: no recorded conversation behind this one.
qmap-c25-D1 Use qmap's existing shapes and carry meaning in tags (agent, repository, file, MCP server, tool, sub-agent) before inventing new ones. — Mark Parson
The same inventory map scales from a handful of agents to thousands of things.
From the record: no recorded conversation behind this one.
qmap-c25-D1 Use qmap's existing shapes and carry meaning in tags (agent, repository, file, MCP server, tool, sub-agent) before inventing new ones. — Mark Parson
Grouped by repository, each repo's files sit inside it, with the agents alongside.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Mapped a company's whole AI ecosystem
The record names nobody; credited from git authorship (the 2026-04-28 c25 commit). The planning came from design c43.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 15
The full record 0 decisions · 0 key-change entries · 625 words · 15 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c25 →