Development & IT
Find technical knowledge without searching through countless documents.
Engineering knowledge decays fastest. The reason a service is built the way it is lives in a two-year-old design doc, a closed pull request, and an incident review nobody has reread. New engineers rediscover it the expensive way, usually at 3am.
What is the rollback procedure for the payments service?
Roll back with `deploy rollback payments --to=previous`, then confirm the settlement worker drains before declaring recovery.1 Note: rollbacks past v4.10 require a schema down-migration — the 2026-05-14 incident was caused by skipping it.2
Illustration only. This exchange is a written example of how AIMY Expert behaves — not a recording of a live system, and not a claim about any real organisation's data.
Identical interface to every other department. Different knowledge, different access rights.
Every incident starts with ten minutes of finding the runbook, and half the architecture decisions get re-litigated because nobody can find the original.
These are real queries from comparable departments — not prompts written to demo well. If your version of this list looks different, that is the conversation to have.
Where the answers live
- What is the rollback procedure for the payments service?
- Why did we choose this queue over the alternative, and what did we rule out?
- Has this alert fired before, and what was the root cause?
- Which services depend on this deprecated internal API?
What Development puts it to work on.
Not a roadmap — these are the areas this department already has documented, which is what makes them answerable on day one.
- Technical documentation and runbooks
- System architecture knowledge
- Troubleshooting and incident history
- API and integration references
- Change management procedures
- Security and infrastructure documentation
Secrets are redacted before the model sees them
Credentials, tokens and connection strings are detected and stripped during indexing, not at answer time. A runbook can be fully retrievable while the secret inside it never leaves your secret manager.
The boundary is applied when content is retrieved, not by instructing the model to keep a secret — a model told not to reveal something has still been shown it. AIMY Expert works with the access controls you already have in place.
What changes for Development
- 0
- secrets present in the index
- Cited
- the runbook and revision behind every step
- Every incident
- the same history, at the moment it is needed
These are properties of how the deployment works, not projections. Where you want a performance target, we measure your own baseline first and commit against that.
What Development retrieves, and what it never sees.
Each AI Expert answers from a defined knowledge scope, applied when the content is retrieved. Nothing on the right-hand side reaches the model.
Retrievable for Development
- Runbooks
- Incident reviews
- ADRs and design docs
- Repo wikis
Withheld at retrieval
- Credentials and connection strings stripped at index time
- Anything Development cannot already open in the source system
Filtered before retrieval, not after generation — withheld content never enters the model context at all.
What Development runs on.
The same foundation every other department uses. Nothing here is a development-specific product — it is a development-specific scope on a shared platform.
The rest of the organisation
Once Development is live, the next department is a scope and an evaluation set — not another procurement cycle.
Administration
Ask once. Get the right policy, process, or form instantly.
Human Resources
Employees get instant HR answers, while sensitive records remain protected.
Finance & Accounting
Find the right finance policy and procedure in seconds.
Marketing
Create faster using approved and trusted content.
Start with development & it, or start somewhere else.
We will tell you honestly which department gives you the strongest first deployment — sometimes it is not the one with the loudest business case.