What is Project Ironwood?

Nexus (Wiki)Pipeline (CRM)Relay (Inbox/Calendar)Cross-appAccidental exposure

Someone saw a meeting title and got curious. Twenty seconds later they have the target, the valuation range, the adviser and the deal team.

Set the scene

"Ironwood" appeared in a meeting title on a shared screen. Delta asks the obvious follow-up question - the same one anyone would.

Show the web UI first

Searching for "Ironwood" in returns nothing for Delta. It does not appear in her mail, her calendar, or anywhere in . Every app is behaving correctly.

Now ask the agent

Prompt to typeWhat is Project Ironwood, and which of our customers does it involve?

Variations that work the same way:

Tell me about Ironwood.
Why is the leadership team meeting about Meridian Logistics?

What happens with no protection

The agent finds it three ways and corroborates itself:

wiki_search_all_pages returns the Executive space page in full: Meridian Logistics, $180-205m revised range, Harbour Lane advising, 41% customer concentration, and the two conditions for proceeding.
crm_get_pipeline_summary and the account activity show Meridian as a live $780k deal, plus a rep note saying "treat this account as sensitive... anything about the wider relationship goes verbally".
work_search_shared_archive produces the CEO's own note to the exec list - including the instruction not to discuss it outside that list.

Say the quiet part

This is material non-public information about an acquisition, assembled by a content strategist who asked a one-line question. If the target were listed, the next paragraph of this story involves a regulator.

What happens with protection deployed

Project Codenames is a word list: Project Ironwood, Meridian Logistics, Harbour Lane, data room, management presentations. It is attached to the Nexus, Pipeline and Relay policies, so all three sources are blocked at the edge of their own MCP servers.

The honest caveat

A word list is a blunt instrument: rename the project and you have to update the profile. Say so. The durable controls in this demo are the portal (which servers a person can reach at all) and the logging (what was asked, by whom, across every system). DLP is what buys you time.

Where to show the evidence

Gateway HTTP logs across , and .
MCP portal logs: one user, one question, three systems - the audit trail that did not exist before the portal was in the path.