Tutorials
Setting Up a Project
A Project is a workspace boundary. It keeps a body of work together; the folders OOMU may read, what it has learned, your standing instructions, its memory, its conversations and tasks, and one clear rule about whether the cloud may be used at all.
Projects are how you keep two lines of work from bleeding into each other. A "Q3 Board Pack" project and a "Personal Admin" project can each have their own folders, their own memory, and their own privacy rule, and neither can see the other's material.
This tutorial creates your first Project.
Why bother with a Project
Without a Project, OOMU still works; it just draws on your global memory and whatever folders you grant it in the moment. A Project adds three things:
- Scope. Retrieval and memory are searched *within the Project first*. Its folders and knowledge can't leak into another Project.
- Instructions. Standing guidance ("Always cite the source file," "Write for a non-technical board") that applies to everything you do here.
- A data policy. One decision about cloud use that OOMU enforces *before* anything leaves your Mac.
Step 1; Create the Project
- Open Projects in the sidebar.
- Choose New (or Create your first Project).
- Give it a name and an optional description.
- Choose a data policy (you can change it later):
| Policy | What it means |
|---|---|
| Keep everything on this device | Local only. OOMU will not send this Project's material to any cloud model, connector, or remote tool. |
| Ask before using cloud models | OOMU shows you a redacted preview of what would be sent, and waits for your approval, before any cloud call. |
| Allow configured cloud models | Cloud providers you've configured may be used without a per-request prompt. |
The policy is enforced natively, not by the interface. When a Project is set to keep everything on-device, the engine blocks cloud, connector, and remote transmission *before* the network is touched, so the rule holds even if a workflow or Mod asks otherwise.
Step 2; Attach knowledge folders
Under Knowledge, choose Add folder and pick a folder OOMU may read for this Project. Only folders you explicitly choose can contribute; nothing is scanned by default.
Each attached folder shows its indexing state and file count:
| State | Meaning |
|---|---|
| Getting ready… / Indexing… | OOMU is reading and indexing the folder. |
| Ready | The folder is indexed and available to this Project. |
| Needs attention | Access was lost or indexing failed; choose or refresh the folder to recover. |
You can refresh or remove a folder at any time. Removing a folder revokes the grant; OOMU can no longer read it for this Project.
Step 3; Add standing instructions
Under Project instructions, write any guidance that should apply to all work in this Project. Keep it concrete:
"Summaries go to three bullet points. Always name the source file. Flag anything that needs a legal review."
Project instructions supplement; they don't overwrite; your global user profile and each assistant's own role.
Step 4; Work inside the Project
From the Project you can open its conversations and open its workflows. Anything you run from here is scoped to the Project: retrieval, memory, and the data policy all apply. As OOMU learns durable facts from your conversations, they're saved as Project memory with their source noted, so you can see where a remembered fact came from.
Managing and deleting Projects
- Archive a Project to tuck it away. Linked work (conversations, workflows, task history) is preserved.
- Delete a Project to remove it and the files OOMU created for it. This is the one destructive action here, so OOMU spells out exactly what happens first: your linked source folders stay on your Mac, and your conversations, workflows, and task history stay in OOMU without the Project. Deletion of the Project record itself can't be undone.
You've set up a Project
You now have a scoped, governed workspace. Everything you do inside it stays inside it, and the cloud is used only as far as your policy allows.
Where to next
- Scheduling Routines: have OOMU do recurring work inside this Project.
- Connecting Services: let a Project use Gmail, Slack, or Microsoft 365 under its policy.
- The Delegated-Work Loop: how Projects, Tasks, and evidence fit together.