Three books, and between them ten artifacts specified precisely enough to implement: the shape a routing policy takes, what a capability contract must declare, what a delivery guardrail has to decide before an agent may act. None of it is a library you install. All of it is a shape you can build in the stack you already run.
Most engineering books hand you either a philosophy you cannot act on or an implementation that assumes your infrastructure looks like the author's. Neither survives contact with a regulated institution, which already has a stack, already has constraints, and cannot adopt someone else's opinionated framework wholesale.
So the series specifies shapes rather than implementations. A schema states what a thing must declare and what must be true of it, and leaves how you store, serve and enforce it to you. That is deliberately less convenient than a library and considerably more portable, because a shape can be honoured by a Kubernetes CRD, a config service, or a table in a database you already run.
The infrastructure layer. Out 24 August 2026.
The application layer. Out 5 September 2026.
The operations layer. Out 15 September 2026.
Each book additionally carries a compliance crosswalk aligning its material to TOGAF, DMBOK, the EU AI Act and the NIST AI Risk Management Framework, which is the artifact most readers reach for first when someone asks how the architecture maps to a standard the institution already reports against.
There is no repository to clone and no package to install. Specifying a shape rather than shipping an implementation is a deliberate trade: it costs you the convenience of working code and buys portability into a stack that was never going to match the author's anyway. If what you need is a library, this is the wrong purchase.
The systems are presented through a deliberately fictional regulated bank so the method can be shown end to end without exposing a client. Nebula Financial is a teaching device, not a case study being passed off as a deployment. The patterns behind the artifacts are implemented in Maxim, which is live, and in client engagements which are confidential. Where a claim rests on a real system, it says so; where it rests on the fiction, it says that too.
Book 1 is out 24 August 2026, Book 2 on 5 September, Book 3 on 15 September. This page describes what they specify. It is not a substitute for them, and nothing here should be read as the schemas themselves.
No, and it does not claim to. What it specifies are schemas, contracts and templates: the shape a routing policy takes, what a capability contract must declare, what a delivery guardrail has to decide. Those are implementable in whatever stack you run, which is the point of specifying a shape rather than shipping an implementation that assumes your stack looks like someone else's.
They are presented through a deliberately fictional regulated bank so the full method can be shown end to end without exposing a client. The patterns behind them are what the author implements in Maxim, which is a live product, and in client engagements which are confidential. Nebula Financial is a device for teaching, not a case study being passed off as real.
No. The books are layered rather than sequential: infrastructure, application, operations. A platform team standing up model routing needs the first, a team building agents needs the second, a team running them in production needs the third. The Cross-Book Navigation Guide on the series resources page exists to route you to the one that matches the problem you actually have.
The licensing of the series text and its free companion materials is set out with those materials rather than asserted here, and it differs between the paid book text and the free companions. If you intend to adapt a schema into a commercial product, ask and you will get a straight answer rather than a link to a licence page that does not quite address it.
All three are forthcoming. LLM Systems in Production is out 24 August 2026, Prompt Systems and Agent Orchestration on 5 September 2026, and DevOps for AI-Native Platforms on 15 September 2026. The already-published Enterprise Playbook on AI governance for the Middle East is a separate book and available now.
If you already know which layer is your problem, go straight to that book. If you do not, the free Readiness Self-Assessment will tell you which of the four governance layers is lowest, and that is usually the same place the engineering is thinnest.