One system, mapped and prioritised
Most commonI take one system, place it against the seven layers and the twelve solutions on this site, and tell you where it actually breaks and in what order to fix it.
What happens:
- A scoping call, then access to whatever you can share: design docs, prompt assembly code, tool definitions, retrieval config. Reading code is useful but not required.
- I map the system to one of the four architectures and name the six primitives, which on its own usually surfaces components nobody owns.
- Every boundary gets the same question: what crosses it, and do you trust it.
- Findings written up, each with the failure it enables, the pattern that answers it, and what that pattern will cost you in latency, engineering and false positives.
- A walkthrough call with the engineers, not just the manager who commissioned it.
A written report you can hand to a customer or a board, ordered so the first three items are the ones that hold even when an injection succeeds.
Teams with one system going live, or one already live that nobody has reviewed with this specific lens.
Not a penetration test and not a compliance certificate. I am reading your architecture, not attacking your production environment.