Built to stay current, by people who build AI.
Two principles run through every book in the AI+ library: it stays current with the field, and it’s written by the people who build AI. Here’s what each means in practice.
A subscription, not a snapshot.
Most AI training is shipped once and walks away. Six months later the tool it taught is deprecated; a year later half the examples are wrong. Every book in the AI+ library is reviewed and updated every quarter.When the field moves — a new model class, a regulatory shift, a framework that supersedes the last one — the books move with it.
The mechanism: each title is written in two layers. The durable layer— frameworks, principles, professional judgement, the way to think about AI — survives every model release. PRISM for prompting. TRUST for evaluating output. The AI Safety Checklist. The perishable layer— tools, vendors, regulatory citations — is tagged at write-time so it refreshes without rewriting the book. When the next model ships, your library updates underneath it; the principles your team learned still apply.
Localised editions are reviewed by in-region experts before release. The Tanzanian civil-servant edition is reviewed by Tanzanian civil servants, not a Western desk approximating the context.
Written by engineers who ship AI for a living.
Every AI+ title is authored by practitioners at Straits AI Group — the AI engineering firm behind 100+ university deployments across 15+ countries. We build production AI systems first, then write about what we’ve learned doing it. No consultant repackaging, no journalism without the engineering, no theory dressed up as expertise.
Then every profession-specific title is verified by working practitioners in that field. Doctors read the doctor book. Auditors read the auditor book. Civil servants read the civil-servant book. By the time you receive a title, the engineering authority and the professional reality have both signed off.
We publish under the Straits Institute for Applied AI imprint, the publishing arm of Straits AI Group. The institute exists because the books our engineers were writing — in client engagements, in implementation reviews, in deployment briefings — were too valuable to stay client-private.