Sapphire Balconies
Managed AI, draft for discussionBrandedAI

Your people build. We make it run the second time, safely.

"As individual intelligence increases, coherence infrastructure must scale in parallel or the system will fragment."The Coherence Scaling Principle, BrandedAI

23 October: what we found, and the shape it becomes

Drawing 1 of 8
Today Seats bought one at a time. Each wired by its owner. Evan Selwyn Gerald Konrad own account own account own account own account Inboxes SharePoint HubSpot Report Manual pull every day.Column renamed, it stops. No view ofseats, cost, connections After set-up One company workspace. Approved connections. Everything on a register. Sapphire Claude workspace, Sapphire sign-in Evan Selwyn Gerald Konrad + seats Prototype registerowner, stage, source, outputs Roles, spend caps, usageseen by Dave, run by John Microsoft 365 HubSpot Warehouse, scoped Read only, under each person's own permissions. Writes off. Everything else blocked. Report on a stable feedchange check tells the owner Nesting, operationalowned, tested, run unaided Outputs land in project folders, procurement and the warehouse, never in a personal chat.
wired by the userapproved, read onlySapphire owned

The architecture

Drawing 2 of 8

Hover a block to isolate it. Blue-filled boxes exist today as reported on the call or seen in the sprint; white boxes are set up in the foundation; dashed boxes are proposed or conditional on a decision.

Guard rails Sign-in and roles Spend caps Keys in one vault Consents reviewed Connection allow-list What AI may read Register, change rule Code and cloud Sapphire owned People Evan, builder Selwyn, builder Gerald, Konrad Rhianna, operator Dave, owner John, admin Entra ID sign-inthe Microsoft login Sapphire Claude workspace Team or Enterprise, owned by Sapphire, no training on content Projects Nesting (Evan), Checks (Selwyn),Ask Sapphire, each builder's own Skills and instructions Rules packs, approved prompts,pushed to all seats by the owner Code execution What Evan's prototype already uses Admin console roles, caps, usage, connectors Prototype register playing, candidate, operational: owner, inputs, source, outputs, limits Approved connections read only, each person's own permissions Microsoft 365: pilot onlynamed group after review HubSpotdeals, tickets, contacts Warehouse views (proposed)design now, build if approved Everything else: blockedGoogle, Slack, GitHub, personal MCP Sapphire Azure, AI-Development area already provisioned by John for the sprint; Sapphire owned Nesting engineexact-number step, fixed calculationreused from the sprint Feeds and checks: proposedHubSpot report feed, column check,parameter table reads Where results go Project folder, SharePoint Procurement sheet order Warehouse tables Inputs 2D drawing pack Master matrix Parameter table BrandedAI runs the loop Weekly, 20 minuteswith whoever is building. Findings in writing. Monthlyseats, spend, connections, reviews, advisories Quarterly, Evan and Daveusage, cost per seat, results, next candidates
flowread only connectionSapphire owned, exists or set up onceconfigured in the first stageproposed or conditional

Why it fragments, on a sheet

Drawing 3 of 8

Every rectangle is one prototype someone is building. Raise the number of people building, then switch the infrastructure on and off. An illustration of the principle on a 2 mm sheet, not a measurement of Sapphire's estate.

Overlaps
0
Off the sheet
0

From prototype to tool

Drawing 4 of 8
Playing Anyone, any idea, own project in thecompany workspace. One row on the register. Nothing else changes. Candidate Weekly 20 minutes with BrandedAI.Written review: what it does, what it needs,what it must not be used for yet. Operational Owner, runbook, outputs where the nextperson looks, change check on its feed. Run unaided by someone other than the builder. Gate 1 1 Inputs named, and where they come from 2 Parameters out of the chat, into a table 3 Run on a job with a known answer Gate 2 4 Named owner and a one-page runbook 5 Release check passed, outputs saved where agreed Evan's nesting HubSpot report

Scroll moves the two live cases along the line. Playing stays free of process; the gates are what the foundation builds and the monthly service runs.

First outcome: nesting, from Evan's prototype

Drawing 5 of 8
In 2D drawing pack Master matrix Claude reads the drawings with Evan's rules pack and theparameter table Sapphire edits Shows lines pickeda person confirms each Nesting engine, Sapphire Azure exact-number step, fixed calculation Out Blank list by family Nest options, tonnes Sheet order to project folder, procurement Validation comes first Evan's own route on two completed jobs against sheets actually bought, one he used and one he chooses, with real parameters, against tolerances he sets first. A pass commissions the build. Acceptance: Rhianna or Konrad runs a new job unaided, twice, within Evan's tolerances. Savings baseline signed by Evan.

What safe means here

Drawing 6 of 8
Outputs Data scope Connections Workspace Identity IdentitySapphire sign-in only, roles, leavers out the same day, revocation tested Workspace, keys, codeSapphire owned; keys in one vault, rotated; repos scanned; consents reviewed ConnectionsBlocked unless approved; read-only; Microsoft 365 as a named pilot after a permission review Data scopeWritten scope of what AI may read, enforced by SharePoint permissions, told to staff OutputsA person checks anything that acts on company data; register and change check Owned by Dave and John, watched by BrandedAIadvisories monthly, one incident scenario rehearsed a quarter, one-page incident route
Hidden instructions in emailPhishing now carries text aimed at AI inbox assistants, for example to change supplier bank details. A person approves anything that moves money or data.
App identities on Microsoft 365October attacks signed in through third-party app identities across thousands of tenants. John reviews Entra app consents and audit logs as part of set-up.
Keys stored elsewhere are a targetThe Railway breach in October took customers' stored API keys. Sapphire's keys go in one vault, one per tool, rotated, and desktop apps are kept current.

The plan

Drawing 7 of 8
Weeks 1 to 2 Weeks 3 to 4 Weeks 5 to 6 Monthly, optional Seats and workspaceJohn, Dave Foundation: register, sign-in, caps, connectors joiners, leavers, spend Keys, consents, code, cloudHardening add-on; John, RAMSAC vault, consents, GitHub, ownership, SharePoint review, M365 pilot, incident route rotation, access review HubSpot reportSelwyn or Elston, Andrew stable feed, change check, 10-day run monthly check NestingEvan builds, we wire and test Validation: two jobs vs sheets bought Operational: rules, run unaided, baseline next candidates Peoplelicence holders 90-minute session, playbook weekly 20 min, clinic Decision points go or close accept; monthly pilot follows

An illustrative, dependency-led sequence: dates are set at kick-off once inputs and diaries are confirmed. The validation in weeks 1 to 3 decides whether the nesting line continues; if it fails, the findings are handed over and that line closes. The monthly service is optional and agreed afterwards.

What Evan and Dave will be able to see

Drawing 8 of 8
Sheets bought vs needed boughtneeded two completed jobs,from 2D inputs,signed by Evan A run anyone trained can do new job sheet order unaided, twice, lines it pickedshown for a person to confirm A report that runs every day ten consecutive working days,and a message when thesource changes One view of the estate seat, plan, payer spend this month, cap connections, what it can read tools, owners, stage week one, kept current monthly
Sapphire Balconies

Individual intelligence is already rising at Sapphire. This is the coherence infrastructure that scales with it.

Draft for discussion. BrandedAI, October 2026.