Keeping your work organised
GNexusOS gives you three ways to keep things apart, and they are not interchangeable. Picking the heaviest one first is the usual mistake.
| Level | Cost | Use it when |
|---|---|---|
| One workspace, no projects | None | Always, to begin with |
| Projects and clients | A dropdown click | Two jobs start contaminating each other |
| Separate workspaces | A whole second setup | Material genuinely must not mix |
Start with nothing
Stay in the default workspace until something actually hurts. Structure you added before you needed it is structure you now have to maintain, and it hides things.
Projects, when the signals appear
Three signals, any one of which means it is time:
An agent quotes the wrong job back at you. It mentions one client's details while writing to another. Memory and artifacts are shared across the default workspace, so this is the system working as designed — you just gave it one bucket.
You cannot find a file. Thirty unrelated artifacts in one list is thirty.
You want to know what one job cost or produced. Artifacts belong to the context they were made in, so the workspace panel can answer that question only if the context exists.
Use clients when work is done for someone and projects for your own strands. A client holds projects underneath it, and archiving a client archives them with it.
Removing either is restorable — they are archived, not destroyed, with a ↩ Restore control. So the cost of being wrong here is near zero, which is another reason not to agonise upfront. See Your workspace and files.
A second workspace is a bigger decision than it looks
A separate workspace means a separate set of agents, a separate memory vault, separate providers to configure, and a relaunch every time you switch.
Worth it: a client who contractually requires their material kept separate; a sandbox for experiments where you do not mind breaking something.
Not worth it: organising your own work. Projects do that with a fraction of the friction.
The question to ask is not "are these different?" but "would it be a problem if an agent could see both?" If the answer is no, use projects.
Memory is the part worth tending
Everything else here is tidiness. Memory is different, because memory is what your agents treat as true.
Write down what you would otherwise re-explain. A client prefers bullet
points. A decision was made in March and why. One of the two spreadsheets is
the real one. Use /remember the moment you notice yourself saying something
for the second time.
Write the reason, not just the rule. "Send Acme reports as PDF" ages badly. "Send Acme reports as PDF — their system rejects .docx attachments" survives the day their system changes, because the next reader can tell the rule has expired.
Date anything that will go stale. Memory has no sense of time. A note saying "we are migrating to the new platform" is misleading a year later.
Do not put credentials in it, ever. Memory is shared with the agents that can read it. Keys belong in Connections, where they are held in your operating system's secure storage and can be revoked.
Read your anomaly flags. When the system finds a memory entry that does not match what happened — or one that reads as though it were written to influence a later decision — it raises a flag in System Config → Memory. These are worth more attention than almost anything else on screen, because a bad note quietly affects every future task. See Memory.
Pruning
Delete finished tasks you will not refer to. DEL is a soft delete; the
task moves to the DELETED filter and RESTORE brings it back. Nothing
is lost by being tidy.
Purge rarely, and read the warning. PURGE removes the record for good.
Any artifact it made is moved to a DeletedArtifacts/ folder rather than
destroyed, so the file survives even when the record does not — but the
record itself does not come back. The app plays a warning sound first,
because this is the one step with no undo.
The workspace is an ordinary folder. You can tidy it in Finder or File Explorer like anything else. Nothing is in a proprietary format and nothing breaks if you move a file you made.
Before you reorganise anything
Take a backup first. System Config → Backup → BACKUP NOW takes a minute and means a reorganisation you regret is reversible. See Workspaces and backups.
A structure that holds up
- One workspace, no projects, until something hurts.
- Add a project the first time two jobs collide — not before.
- Promote to clients only when you are doing work for more than one.
- Reach for a second workspace only when mixing would be a real problem.
- Put a note in memory every time you explain something twice.
- Back up before any of the above.
