The Geidi Trinity
Every project — born governed, catalogued automatically, and speaking one shared language.
- 3→1 — Three specialised systems, one queryable knowledge graph
- 100% — Of projects catalogued & born governed — nothing falls through
- 2 — Live MCP endpoints — your AI reads the estate with nothing pasted by hand
The knowledge lives in people’s heads
What does that service even do? — the honest answer is usually “ask whoever built it.”
Every new project restarts the same plumbing before any real work begins. Each one speaks its own dialect, so people and AI trip over the same words meaning different things. Projects sprawl across several platforms with no single inventory. If I change this, what breaks? is unanswerable without reading the code. And AI assistants are blind to all of it unless someone hand-feeds them context every time.
Three systems, one map
This is not one product. It is three that cover a project’s whole life — idea, inventory, shared language — with a single map over the top.
- Projects are born governed. A plain-English description becomes a specification, a scaffold, a repository and a task board, with the house rules already in the code and a build gate that enforces them.
- Everything is catalogued. Owner, lifecycle, where it runs, what it connects to — discovered from each repository’s own manifest rather than hand-maintained.
- One vocabulary per team. A shared dictionary, isolated per product, so a word means the same thing to people and to AI across projects.
- Change has evidence. Ask what a change touches and get a real answer across data, back end and front end, instead of a guess.
- Your AI can read the estate. Agents get live, governed access to the same knowledge — no copy-paste, no stale context.
It checks itself, and shows the gaps
The map is derived twice, from independent sources, and disagreement between them is surfaced rather than smoothed over.
Where something is not mapped, it reads as unknown — never as a false all-clear. That is the property that makes the rest of it usable: a green light is only worth having if the system is willing to show you an amber one.
Why the three belong together
Separately, each is useful and each has a familiar failure. A generator produces projects nobody tracks. An inventory goes stale. A glossary becomes a document no one reads.
Connected, they close each other’s gaps: projects register themselves at birth, so the inventory cannot fall behind; they seed their own vocabulary, so the glossary is never a separate chore; and the inventory feeds the map that answers what a change will break.
Where it fits
- Engineering leads who need the whole estate at a glance.
- Product managers onboarding to an unfamiliar project.
- Audit, compliance or cost work across many services.
- Developers who move between projects and keep hitting vocabulary clashes.
- Organisations where “how it all fits together” lives in one or two heads.
See your estate as one map
The walkthrough runs on your own projects — from a plain-English idea through to a live, queryable map.