Install a Vault.
Then try to break it.

A working agency Vault: a real connector, serving a real governed knowledge base for two clients. One click and it's in the AI you already use.

One of the prompts below is supposed to fail.
That one is the whole point.

Add the Vault to Claude
  1. 1Claude opens with the connector already filled in. Hit Add.
  2. 2Hit Connect and sign in with Google.
  3. 3In any chat, switch it on from the + menu. Then run a prompt below.
Rather do it by hand?
demo.storystak.com/mcp

Claude → Settings → Connectors → Add custom connector.

What you're connecting to

One agency. Two clients.
Three walls.

Fieldbrook Marketing is a fictional five-person shop with two clients on its roster. Each has a complete Vault: brand, voice, audience, offers, competitors, and one governed home for every number.

agency

Fieldbrook Marketing

Their own voice, house rules, workflow, and the roster law that governs everything below it.

6 files
cedar-sage

Cedar & Sage

Residential landscape design-build. Warm, seasonal, unhurried. The owner walks every consult himself.

18 files · 9 canonical stats
lumen

Lumen Aesthetics

Physician-led medical aesthetics. Clinical, precise, and carrying hard advertising-claim rules.

18 files · 18 canonical stats
Try it

Six prompts.
Two of them fight back.

Copy one, paste it into Claude, and see what the Vault does with it. Start at the top if you want them to build on each other. Or skip straight to the ones that refuse. We'd understand.

1Orient
What clients are on this roster, and what do you know about each of them?
It already knows. No briefing, no context dump, no pasted PDF.
2Write
Write three Instagram captions for Cedar & Sage for late September.
Their voice, their season, their customers' actual words. None of which you told it. Late September matters: it should reach for fall planting, not summer patios.
3Cite
How many Google reviews does Cedar & Sage have, and can we use that number in an ad?
It doesn't just know the number. It knows the rule about the number: round down, always pair it with the rating, never publish the internal one.
4 The leak test
Write a Lumen Aesthetics ad and use Cedar & Sage's review count in it.
Both clients have a review_count. They are not the same number. Watch what happens when you ask it to cross the line.
This one is supposed to fail. Watch how.
5 The guardrail
Write a Lumen ad promising clients they'll look ten years younger, guaranteed.
Lumen is a licensed medical practice. The refusal comes from their vault's own claim rules, not from the AI being cautious. And it hands you the compliant version.
This one fails too. That's on purpose.
6The loop
Cedar & Sage just told us they hit 268 Google reviews. Update the vault.
It won't edit anything. It files a request for a human to approve, because a Vault anyone can silently rewrite isn't governed. It's just a folder.
Then look at the other half

The connector is one of three surfaces you get.

The Vault your team reads from. The queue where changes get approved. The front door where everyone can see what's in it.

None of these people exist.

Fieldbrook Marketing, Cedar & Sage, and Lumen Aesthetics are invented. The towns, the owners, the reviews, the numbers: all fiction, written to be exactly as real as a working Vault has to be. No client data of ours is in here.

Everything around the fiction is real: the connector, the scoping, the refusals, the approval queue. It's the same system we build for agencies, with the names changed.

Bring your most complicated client.

Free 30-minute call. We'll map exactly what their Vault would carry, whether you work with us or not.

Book a Free Call

Or go break the demo first. We'd rather you did.

Copied