Launch a Space

A Space is the home for one effort. This playbook sets one up from nothing: a goal with a real measure, the people, a template agent working in it, and a job that reports into it so the Space tells you where things stand.

Steps

1. Create the Space. Open Spaces and choose New Space. Give it a Name, such as "Customer rollout", and select Create Space. Edit the description at the top of the home to one sentence on what done looks like.
2. Let the agent interview you. The empty home shows three starter sentences; choose one or type your own in Ask in Customer rollout…. The agent asks for the goal and its measure, where the work and data come from, where the knowledge lives, and who handles what. It then proposes the mission, goals with their queries, instructions, and routines, and makes each change through an approval card.
3. Add the team. In the rail, Team → Add opens the members dialog. Add people or groups, and set the Space's default agent. Add files and Drive folders from Files → Add so everyone can read them.
4. Bring in a template agent. On Agents, choose Templates and Use it on the one that fits, for example Pipeline Keeper. On its Settings → Access, make it available to this Space. Members turn it on for themselves from its About tab; its jobs then run for each of them.
5. Let a job report in. Ask the agent: "Every Friday, post a short status against the goal into this Space." It creates the routine with this Space as its destination, off. Run it once, read it, and turn it on. The Space's rail counts its runs under Routines, and the daily review records each goal's standing once a goal exists.

What waits for your approval

Everything the agent changes in the Space during setup: goals, instructions, membership, routines. Routines it proposes start off and are enabled only after you say so. Your own edits on the home save directly. Later, each job's actions ask the person they are for.

Limits

• A goal's figure comes from a saved query over data in Meridian. A goal measured in a system that is not connected records a state word only.
• The agent can contribute in a Space but never manage it. Goal and instruction changes it suggests reach a manager as a Task.
• Members' personal accounts stay personal. A job that reads HubSpot runs for each member with their own HubSpot access.
• Spaces are flat. There is no parent Space or roll-up across Spaces yet.