Workspace
The plans, sheets, forms and boards you and COORDINATOR build together. Everything you make in a session has somewhere to live, and it stays alive between them.
Plans that stay alive between sessions
Most AI hands you an answer and forgets it. That's fine for a question and useless for a training block, because the block is the thing you keep coming back to. A plan gets written, then adjusted after a bad week, then adjusted again when someone's schedule moves, and it's the same document the whole way through.
A workspace is where those documents live. Anything you make in a session lands there: the program, the roster, the intake form, the board you sketched a circuit on. COORDINATOR can read from them and write into them, so the plan it's reasoning about is the plan you actually gave someone.
That's the difference between a chat transcript and a system of record. You stop rebuilding the same thing from scratch on Sunday night.
Seven shapes, one workspace
Pick the shape that fits the work instead of forcing everything into a document.
Plans, protocols & notes
The twelve-week block, the movement standards, the return-to-run protocol, the notes from a consult. Write it with COORDINATOR in the room: highlight a paragraph, say what you want changed, and take the version it proposes or put it back the way it was.
Rosters, loads & tracking
Client rosters, session logs, load tracking, renewals, testing results. A sheet is a real spreadsheet your COORDINATOR can read from and write into, so the numbers it reasons over are the same numbers you keep.
Intake & check-ins
Send an intake form or a weekly check-in, collect the responses in one place, and have COORDINATOR turn them into a starting block or a flag on someone's week. No more chasing answers across text messages.
What the data is doing
Turn the numbers you already keep into a chart you can read at a glance, then ask what changed. Useful the moment a client asks why you moved their week.
Session boards & sketches
Lay out a small-group circuit, a station rotation, or a movement breakdown on an open canvas. Draw it the way you'd draw it on the gym wall, and keep it where the rest of the plan lives.
Present it, or make it interactive
Build a deck for an onboarding call or a workshop, or spin up a small interactive tool when a document isn't the right shape. Same workspace, same COORDINATOR, no second product to learn.
It proposes. You decide.
Ask for something in a session and COORDINATOR builds it as a draft. A draft is exactly that: it sits in the session until you save it into your workspace or export it out. Nothing appears in your workspace because a model decided it should.
Inside an artifact, editing works the same way. Highlight a paragraph, a few rows, or a slide, say what you want, and you get a proposal you can accept or revert. It tells you what it changed before it changes it, and the version history keeps the receipt.
Artifacts also work the other direction: pull one into a session as context and COORDINATOR answers against that plan instead of guessing at it. Pin the ones you use constantly, lock the ones that shouldn't move.
Your work leaves when you do
Export any artifact to Google or Notion, or download it as Markdown, Word, CSV, HTML, or PowerPoint. Your programming isn't held hostage by the tool it was written in.
In a group, every artifact carries its own audience: private to you, the specific people you pick, or the whole group. You set it, and you can change it whenever you want.