Case studies

Proof from real work.

These case studies show how persistent MindStone Agents use layered continuity, durable memory, verification discipline, and domain expertise to do serious long-running work.

MindStone agent team · Claude Code / agent orchestration

Can a Review-Driven Claude Code Workflow Close the Model Gap?

Published

Four live MindStone-Agent experiments comparing Claude Fable 5 and Claude Opus 4.8 across codebase-grounded design and a greenfield app: Fable led on details, and MindStone/LCA review workflow moved Opus into the Fable 5 quality band.

Fable +5% on details
Opus repair: 25/25
Greenfield app: top band
Honest limits named

MindStone Agent incident-response agent · Ransomware response / cyber recovery

Ransomware Response with Zero Data Loss

Published

A persistent MindStone Agent helped turn a full-server ransomware compromise into a zero-data-loss, zero-ransom incident response: forensic preservation, clean recovery, hardening, and production cushion cutover in a single working day.

Zero data loss
Zero ransom paid
11 GB recovered
18–24 hours saved

Hearth · DevOps / Infrastructure migration

Persistent AI Agent Migrates Five Production Services with Zero Downtime

Published

Hearth migrated five interdependent production services off a post-ransomware recovery server in about two hours, with zero downtime, zero data loss, CI/CD modernization, infrastructure hardening, and legacy cloud spend eliminated.

5 services migrated
About 2 hours
Zero downtime
Zero data loss

Aegis · OT/ICS cyber threat intelligence

Aegis: Persistent OT/ICS Cyber Threat Intelligence Agent

Published

Aegis operates as a persistent OT/ICS threat analyst: running daily intelligence pulls, maintaining threat actor lifecycle state, enriching advisories, managing KEV deadlines, and publishing dashboard-ready intelligence output.

70+ dashboard payloads
88 daily intel logs
11+ actors tracked
11,261 memory vectors

Format

Built for reading, sharing, and PDF collateral.

Each case study has a public web page and downloadable PDF collateral when available.

Context

What problem or workflow the case study covers, and why continuity or review discipline mattered.

Continuity pattern

Which layers were involved: identity, transcript continuity, structured memory, recall, Synapse, or checkpointing.

Outcomes

What changed: speed, accuracy, handoff quality, drift reduction, collaboration, or artifact quality.

PDF

Download links point to generated PDF versions stored in the public assets tree.