How updates reach you, and what stays sealed
Two things move at the boundary of your workspace: improvements coming down from the platform, and data that must never go sideways to anyone else.
Written in your agent’s voice: this is how it talks to you in your workspace.
Your workspace started as a copy of a template the platform team maintains, and from the moment it was yours, nothing reaches it without a decision.
A platform improvement reaches you only when someone decides to bring it in
When the platform team strengthens a rule, fixes a check, or ships a better command, that change does not appear in your workspace on its own.
The system carries a rule for this, workspace propagation — it is encoded, so the platform never auto-pushes anything to a live workspace.
Someone brings each change in by hand, after answering three questions:
- Does it fit how you work? A change built for a different kind of business may not belong in yours.
- Does it clash with your own tuning? Your voice, your conventions, your commands were set up for you, and a blind copy would clobber them.
- Whole, adapted, or skipped? Whole-file rarely, a targeted edit usually, nothing at all often.
That decision sits with whoever holds the system-owner grant on your workspace — the platform team for the machinery, your own people where it touches how your organization runs.
The platform is a starting point, not a master copy that keeps stamping itself over your work.
When you want to know whether a recent improvement is worth pulling in, say: "Show me what changed in the platform since our deployment, and tell me which of it is worth bringing into our workspace."
Your workspace is sealed, and the seal is mechanical
No other workspace can read yours, and you cannot read theirs.
This is the isolation the whole system rests on, and it is not a policy someone has to remember to honor — it is wired in by the sealed-credential boundary.
Here is how it holds:
- Each workspace signs in as itself and reaches only its own data, so there is no path by which one borrows another’s access.
- A missing credential fails loudly and stops, rather than quietly reaching for a different workspace’s sign-in — the failure is the safeguard.
- Your data stays inside your box. Your client records, your emails, your outputs reach no one outside it.
That seal is also why the platform stays safe at scale: revoke one workspace and the rest are untouched, audit yours and only your operations appear.
Some of the system is identical everywhere, some is yours
The shared machinery — the rules, the checks that enforce them, the commands, the core settings — starts identical across every workspace, because that sameness is what makes the system reliable the same way for everyone.
An improvement to that machinery is a candidate to flow down to you.
Your own calibration stays put and is never overwritten: your voice and style, any rule that names your own people or data, anything built for your situation, the commands and settings that hold your paths and permissions.
When you are unsure which a thing is, the test is one question: does it describe how the platform works for everyone, or how your organization works in particular?
The first flows down; the second stays.
Say: "Is this shared platform machinery, or our own calibration?" and I will tell you which side of the line it sits on.
The one thing to remember
Nothing reaches your workspace without a deliberate decision, and nothing of yours leaves it at all — the platform’s machinery is shared and gets stronger for everyone, while your data is sealed inside a box no other workspace can open.
Next: security and data boundaries