Three roles. One workspace. Every deck on brand.

Your designers open the governor IDE and define your brand in three layers. Tokens carry the raw values, the colour ramps, the fonts, the spacing units. Slot types define the typed contract every slide reads from: headline, metric, logo, quote, chart, body text. Slide templates carry the HTML scaffold, the per-template CSS, and the slot placeholders. A deck template wraps every slide with the chrome the brand wants to see on every page.

Every layer versions. Every change writes an audit log entry. Past decks render the way they rendered the day they shipped, even after the templates move on.

The brand work your designers do once is the brand work the whole company uses for the next year.

Codexroom runs a Model Context Protocol server. Your agent (Claude, Cursor, your internal stack) connects through OAuth. The user authorising the grant picks the scopes. A common grant looks like read on tokens, read on assets, read on templates, write on decks, write on shares. That grant lets the agent compose and send, and stops it from changing the brand.

The agent then has a typed set of tools: list the tokens, search the data room for the right case study, list the slide templates that fit a sales pitch, create the deck, validate it, and create a share link with a watermark.

A single prompt produces a watermarked link.

Example. A sales lead in Claude Desktop says, "Build me a 12-slide pitch for Acme, lead with the healthcare case study, password the share, expire it Friday." The agent calls Codexroom seven times. The reply is a link.

The Acme rep opens the link. The viewer renders the deck slide by slide in a sandboxed iframe. The recipient's name sits in the bottom-right of every slide. The recipient sees this share only. The link expires Friday. After Friday, the page says the link is unavailable.

Set any of five gates per share before you send it: password, IP allowlist for the office or VPN, origin allowlist for an embed inside a partner portal, country allowlist for regulatory boundaries, email verification with a 6-digit code, and a view cap that closes the share after the recipient opens it the agreed number of times. Each gate runs server-side, fails closed, and writes every rejection to the audit log.

Underneath, three invisible channels combine to fingerprint the HTML. If the file ever leaves the viewer, the forensics tool decodes it back to the share that produced it.

Every open writes an event. Every slide view writes an event. Every completion writes an event. Your analytics page shows a per-share session timeline and a per-slide engagement chart across every recipient. The deck that gets skipped on slide 4 is the deck you fix first.