Governframe — what using it looks like

Three scripted scenes: a team member's session connecting to the hosted layer, a knowledge-base query answered from the team's own docs, and the admin's isolation/audit view. Click through — nothing here calls a live system.

Scene 1 — a team member connects their own Claude session

Illustrative example: a designer on a 9-person agency team opens Claude Code and points it at the team's Governframe MCP endpoint using their own existing subscription. No account or credential is shared with Governframe — the session is theirs.

connect mcp://agencyname.governframe.app --as jordan

Connected. Signed in as Jordan (Design), team "Agencyname" (Team tier, 9/15 seats). Your own Claude session — Governframe never sees your account credentials.

tool_roster.load() → curated for role: Design

brand-kb.search client-brief.lookup asset-memory.recall prod-db.query — not granted to Design role billing.export — admin only

Illustrative example: the roster is curated per role by the team's own admin — Jordan sees the tools relevant to design work, not the full catalog. This is the "don't want everyone using it willy-nilly" framing the offer is built around.

Scene 2 — a KB query answered from the team's own data

Illustrative example: Jordan asks a question that used to mean pinging a teammate or searching six old Slack threads.

what's our current file-naming convention for client deliverables, and did we change it after the Meridian project?

brand-kb.search("file naming convention", scope=team) → 3 hits, ranked

Yes — updated after Meridian (2026-03). Convention is now <client>_<deliverable>_<v#>_<YYYYMMDD>. Source: "Ops SOP v4," updated by Priya, last edited 4 months ago. The pre-Meridian convention (no date suffix) is flagged deprecated in the same doc.

Illustrative example only — this is the hosted memory/KB slice of the offer (Starter tier and up), not a real team's real documents.

Scene 3 — the admin's isolation & audit view

Illustrative example: the team lead's dashboard. This is the honesty-load-bearing screen — it shows what isolation actually is at this price tier, not an inflated claim.

Client / workspace	Seats active	Data boundary	Last audit event
Agencyname (this team)	9 / 15	Logical per-tenant separation	2026-07-28 — KB query, Jordan (Design)
— other Governframe teams —	—	Not visible from this workspace	—

Isolation note (shown to every buyer, not buried): this is logical per-tenant separation at Starter/Team pricing — not dedicated infrastructure and not a SOC2/VPC-level compliance certification. Teams that need that level should ask before buying.

Audit log (illustrative example, last 24h): 14 KB queries · 2 tool-roster changes by admin · 0 cross-tenant access attempts · 1 seat added (Jordan, Design)

All names ("Agencyname," "Jordan," "Priya," "Meridian project"), all figures, and all messages on this page are illustrative example data built to be plausible against Governframe's real pricing and real seat ranges (see the pitch site) — not a real client, not a real conversation, not a real audit log.