Security in plain terms
Your job is to know what’s private, what’s shared, what stays sealed, and which steps I won’t take on my own — not to configure any of it.
Written in your agent’s voice: this is how it talks to you in your workspace.
None of this is a setting you turn on; it’s wired into the workspace.
Private to each person, shared across the team
Two kinds of content, and the line between them decides almost every security question you’ll have.
Private.
Each person’s own outputs, their session history, and what I’ve learned about them belong to that person alone.
I don’t read another person’s private space, and I won’t open it on request.
The line that holds it is the user-data boundary: a private space is keyed to whoever signed in, and nothing keyed to one person opens for another.
That private space has a concrete home: your own Drive, organized as six drawers I file into for you — your sessions, your meeting transcripts, what you brought in, what I made for you, the knowledge of a domain that is yours alone, and the living documents I keep current. Your sessions, transcripts and inputs always live there and never in the shared repository. Only you and the system account can open it.
Shared.
The methodology, each domain’s knowledge, and the corrections that make me better are meant to reach the whole team.
When one person fixes something and it lands in the shared space, the next person’s work inherits the fix.
That’s where the system compounds — one person’s improvement reaches everyone.
The rule of thumb: personal work is private, the methodology and the improvements are shared.
The full data boundaries live in the governance rules.
Sealed inside your workspace
Your whole workspace is a third zone, walled off from every other company running on the same system.
Nothing crosses in.
Another company’s data, credentials, and knowledge never reach you, and yours never reach them.
The wall is the sealed credential boundary: each workspace signs in under its own keys, and I can never act on your data using anyone else’s.
If the keys for a request don’t belong to your workspace, the work fails loudly rather than quietly reaching across the line.
For you, that means your client data, your team’s corrections, and your competitive edge stay yours — they can’t leak sideways into another company’s system.
So the three zones stack: private to a person, shared across your team, sealed inside your workspace.
I won't take a step you can't take back
Inside the workspace, every change is recoverable — a logbook records each one, so "undo that" works.
Anything that leaves the workspace is not recoverable: a sent email, an updated the CRM record, a published document.
So I draft those and hand the final step to you.
I never send the email, never commit the record, never publish the document on my own — you do.
This is the same outbound gate you met in the Orient-3 module; here it’s the security reason behind it.
I act only as whoever signed in
I read who you are from your authenticated sign-in, not from the name on the computer — and that can’t be faked by editing a file or flipping a setting.
This matters because access depends on identity: your role decides what you can change, and your private space is keyed to you.
There’s a stop built in.
If the credentials acting on a request ever belong to someone other than the person signed in, I halt rather than act under a confused identity.
For you that’s a clear failure you can fix, never a silent action under the wrong name.
Your move: name the zone
When a question looks like security — can this person see that, is this safe to put here — it almost always reduces to which of the three zones the work belongs in.
You don’t have to reason it out alone.
Ask me:
"Is this private to me, shared with the team, or does it stay sealed in our workspace?"
Name the zone, and the boundaries above enforce the rest.
The one thing to remember
Personal work is private, the methodology and improvements are shared, your workspace stays sealed from every other, and I never take an irreversible step on my own.
I act only as whoever signed in, and stop if that ever blurs — you place the work in the right zone, and the system holds the walls.
Next: designing roles across your team