Book Summary
Book 3 of The Agentic Frontier. The domain playbook. The Amazon listing names industry chapters across banking, insurance, healthcare, logistics, legal, cybersecurity, manufacturing, and telecom, media, and HR. Kindle and Kindle Unlimited.

The book

The Agentic Frontier: Volume 3 is Book 3 of 3 in The Agentic Frontier by Vatsal Shah. The Kindle edition was published on 11 September 2026. Language: English. ISBN-13 978-9334485745. ASIN B0H8KZZZCZ.

The full listing title is: The Agentic Frontier: Volume 3: The Domain Playbook: Enterprise Vertical Systems & 100 Production Agentic Deployments.

Open the Kindle edition on Amazon.

What is inside

The description on the Amazon page says the book spans 10 industry chapters and 100 production case studies. The chapters it names:

  1. Financial services and banking — sentiment loops, AML swarms, commercial credit underwriting, ISO 20022 and SWIFT parsing.
  2. Insurance — vehicle-damage appraisal, parametric underwriting, fraud graphs, claims settlement.
  3. Healthcare and life sciences — clinical triage, biomedical GraphRAG, trial matching, diagnostic consensus.
  4. Logistics and freight — route optimization, port rerouting, customs parsing, cold-chain tracking.
  5. Legal and regulatory — contract reasoning, compliance auditing for the EU AI Act, GDPR, and SEC, and M&A document review.
  6. Cybersecurity — quarantine pipelines, red-teaming, IAM isolation, SOC triage.
  7. Manufacturing and robotics — IoT anomaly detection, defect classification, digital-twin simulation.
  8. Telecom, media, and HR — network-slice balancing, voice agents, and skill-graph intelligence.

Who it helps

Read the chapter for the industry you are in. Volume 2 is the architecture. This volume is the domain map.

Enterprise architect. Pick the vertical and copy the systems the listing names for that industry.

Chief AI officer. Use the chapter list as the meeting map: which industries the listing covers, and which systems sit in each.

Engineering lead. Hand one chapter to the team that owns that domain.

Operator. Use a single named system, such as claims settlement or SOC triage, as the first deployment conversation.

How to use it

  1. Pick the vertical. One industry, not the whole book.
  2. Name the system. One item from that chapter's list.
  3. Bring the architecture. Use Volume 2 for the loop, the memory, and the tool boundary.
  4. Keep the case count on Amazon. The listing says 100 production case studies. This page does not restate a result the listing has not itemized here.

What you leave with

  • A vertical to start from.
  • The systems the listing names in that vertical.
  • A reason to read Volume 2 before you build.
  • A series that ends here: Book 3 of 3.

The series on this site

Questions about using this in a team workflow: contact me.

Vatsal Shah

Vatsal Shah

AI Leader · Solution Architect · TPM

I design autonomous AI systems, enterprise architectures, and publish deep technical content for global organisations.