What each connected system unlocks
You met the live connections in Orient-2 — this is the deep-dive on each: what it is, and the exact work it unlocks.
Written in your agent’s voice: this is how it talks to you in your workspace.
I’m connected to the systems this company already runs on, with a live line into each — so you ask in plain words and I reach the system, instead of pasting data into a box.
This module walks them one at a time, gives you the words to use, and shows the move for when something you need isn’t connected yet.
Your mailbox — Gmail
The connection is to your Gmail, so your inbox, sent mail, and threads are live material I can work in — every message and attachment, going back years.
I read and search it, and draft replies — but a draft stays a draft until you send it, because outbound is always yours.
Say: "Read every thread with this client and tell me where it stands," or "Draft a reply to that last message and hold it for me."
Your calendar — Google Calendar
The same Google line reaches your calendar, so I can see what’s on it, find open time, and put events on it.
I check availability and book — and when a thing affects other people, I draft the invite and leave the send to you.
Say: "Find 45 minutes with Pierre and Patrick next week and draft the invite," or "What’s on my calendar Thursday?"
The company directory
The directory isn’t a separate system to connect to — it lives in the workspace itself, as the roster of everyone on the team with their names, roles, and addresses.
It’s why a name is enough: I look up who they are instead of asking you for an address.
Say: "Who owns the website?" — or just name people inside any request, "send this to Pierre," and I resolve them.
The company's documents — Google Drive
The connection reaches the team’s files on Google Drive, so I find, read, and create without you hunting for a folder.
The work itself — deals, invoices, content — lives as named artifacts in the plugins, and Drive is where finished documents land.
Your own Drive is your private cabinet. Every person has a dedicated Drive the system organizes into six drawers: Sessions/ (your conversations with the system), Transcripts/ (your meetings — Meet notes and recordings arrive here on their own), Inputs/ (documents you bring in), Outputs/ (documents a private domain made for you), Knowledge/ (the domain knowledge of a domain that is yours alone), and Artifacts/ (living documents the system keeps current, like your task list). Sessions, transcripts and inputs are always here and never in the shared repository. Only you and the system can see it. You never file into it by hand — the system does the filing, and you find things by asking.
Say: "Find the proposal we sent this client in April," or "Pull up the latest invoice for this account," or "Open the transcript of Tuesday’s meeting."
Publishing — Google Docs
When a finished file needs to become a real document, I publish it to Google Docs through /publish.
It lands as a named, formatted doc you can share — no copy-paste, no reformatting.
Say: "Turn this thread into a one-page summary and publish it," or "Publish this draft as a Google Doc and give me the link."
When something isn't connected yet
Not every system you use is wired in on day one — and the move when you hit one is short.
You ask for it by name, the way you’d ask for anything else, and I tell you whether the line exists.
Say: "Can you reach our accounting system?" — if the answer is no, that’s not a dead end.
A live connection is part of the workspace’s wiring, so adding one is the system builder’s job — the platform team, the people who can change the whole workspace.
I route the request to them, they wire the system in, and from then on it answers in plain words like the rest.
You name the system you want to reach; if it’s there, I use it; if it’s not, the request goes to the system builder who connects it.
See the live list anytime
The connections aren’t a fixed list to memorize — they grow as the system grows, and the current set is read live from this workspace.
Say: "What systems are you connected to?" and I read this workspace and show you exactly what’s wired in right now.
The one thing to remember
I’m connected to your mailbox, your calendar, the directory, and your documents on Drive — and I publish finished files to Google Docs — so name the outcome and I find the route.
When the system you need isn’t connected yet, you name it and the system builder wires it in — your job is to name the system, never to operate the wiring yourself.
Sources
- tool-execution — connected-system operations go through one tool layer, the boundary that makes them auditable.
- communication-safety — the draft-only boundary on outbound mail: I draft, you send.
- The live workspace catalog (
/sw-catalog) — the current, authoritative list of connected systems for this workspace.
Next: back to your track — or ask for any module by name.