Gamebooks

the agentic game plan for investigation and response

A Gamebook is Mate’s investigation process - built for AI agents. SOAR playbooks are deterministic and brittle. Unbounded AI SOC agents are hard to trust. Gamebooks are the sweet spot: a structured investigation process where AI agents reason and pivot dynamically within every step, and are fully customizable to align with your processes.

Get a demo

The Evolution of Automation

Different philosophies. Different outcomes.

Legacy Soar

Human-Authored Playbooks

Fully deterministic investigation.  Brittle and breaks when things change. Needs ongoing  maintenance

Low Adaptability High maintenance
SOAR + AI

AI-Authored
Playbooks

Same playbook architecture. 
AI-assisted authoring reduces maintenance but all other problems remain.

same architecture,  AI authored
agentic investigation

Glass Box AI

Dynamic, but unbounded - inefficient and hard to trust. Does not follow your playbooks. Not customizable.

dynamic, but
hard to trust
Gamebooks

Designed Intent

Follows your SOPs. Dynamic & agentic in each step, with boundaries. Extendible and open.

dynamic, trusted customizable and aligned with your SOPs

Deterministic where it can. intelligent where you need it.

A football team doesn't script the whole game before kickoff, but it has a game plan: what to achieve, how to read the field, which rules never break. A Gamebook works the same way: investigative intent, not vendor API calls.

What a Gamebook Knows

What must be investigated
Which evidence is needed
Which conditions change the investigation
Which actions are permitted
When agents must escalate, stop, or request approval

how gamebooks work

Gamesbooks are deterministic about intent.

A gamebook defines how to investigate, what evidence is required, which actions are permitted, and what approval boundaries apply.

Agents are dynamic about execution.

Gamebooks activate agents. Agents decide which skills to invoke next, which evidence to pursue, and when new context requires a pivot.

Tool use is abstracted

Tools are queried as a separate flow, with access restrictions for their current task. An Endpoint Profile Collection Flow might collect information from the sources available in that environment: CrowdStrike, Microsoft Defender, Device42, An MDM platform or a custom data lake. Tools can easily be changed by replacing Flows, without breaking investigation processes.

customize, build
Make them Your Own

Building agentic workflows is hard. With Mate you get elite gamebooks out of the box, and bring your own knowledge in two ways, no rip and replace:

two ways to make game books your own
Migration

Bring your playbooks

Mate translates your SOAR playbooks into Gamebooks. Brittle API calls get replaced. Your custom logic stays.

Extension

Describe what you need

Gamebooks are extendable by design. Write the investigation in plain language. Use your Workflows, 3rd Party Tools, 1st Party Tools and Best of Breed Agents. Mate tests it against past cases, runs it in shadow mode, then waits for your sign-off.

Migration

Gamebooks work through changes

Your reality keeps changing.  Gamebooks keep working because they are driven by intent and Mate’s context graph, not hard coded API calls and individual knowhow.

Extension

Ownership - On Us

Building and testing agents is no longer your problem. When you customize a Gamebook, it runs through Mate's evals and tests before it goes live. This used to be your problem if it broke. Now it's ours.

SOAR playbooks vs. Mate gamebooks

what happens when
SOAR playbook
MATE GAMEBOOK

6 of 12 nodes need rewriting.
New vendor, new APIs, new playbook.

Zero changes needed.
Same Gamebook. New connector swapped in automatically.

0 of 12 nodes work.
Different tools, different infrastructure, different assumptions. Rebuild from scratch.

No automation rebuilt.
Different stack, same investigative logic.

Pre-built.
Active from day one. Mate ships Gamebooks for core investigation domains.

The playbook runs.
The reasoning behind it left with Sarah.

No single-author dependency.
Knowledge lives in the graph, not in one person's head.