Ten clients in one workspace, answers that never cross.
Give each client its own scoped space. Nexus extracts the people, organisations and projects per client and keeps every query bounded to one account, so you build a memory that compounds across ten engagements without an answer ever leaking from one client into another.
Run Nexus- 1
Describe the task
Nexus can hold ten client engagements in one workspace without ever crossing the wires. Each client gets its own scoped space, and Nexus extracts the people, organisations, projects and concepts from that client’s notes into that space alone. When you ask a question inside a client, the answer is drawn only from that client’s graph and cited back to its notes, so context compounds across every engagement without a single fact bleeding from one account into another.
The cleaner you scope each space, the safer the wall between clients. Tell Nexus which notes belong to which client, which entity types matter for that engagement, and to answer only within the active space, and it holds that boundary on every query, a person who appears in two clients stays two separate scoped nodes, never one shared leak.
Index the notes for Client Aurelia into its own scoped space at space://clients/aurelia. For every note: - Extract the key entities: people, organisations, projects, and concepts - Keep everything scoped to this client, do not link it to any other client space - Cite the source note and date for every claim when I query When I ask a question, answer only from the Aurelia space and say so if a fact isn’t in it, rather than reaching into another client’s graph.
- 2
Give Nexus context
In a Nexus workspace, create one space per client and point each run at only that client’s notes. Nexus reads them into that space, so the same job title or generic project name in two engagements resolves to two separate nodes, one per client, and a query never has to guess which account you meant.
Give each space a short client glossary if the engagement uses its own codenames or stakeholder acronyms. Scoping the glossary per client keeps “the Atlas project” at Client Aurelia from colliding with a differently-meant “Atlas” at another account.
Required contextOne source location per client, the notes, transcripts or folder for each engagement, kept separateA list of entity types that matter, people, organisations, projects, conceptsOptional contextA per-client glossary of codenames and stakeholder acronyms, so aliases resolve inside the right spaceA Connected-mode team vault per client, so a small engagement team shares one scoped graphA priority list of stakeholders, so the key people at each client surface first when you queryclients/aurelia notesclients/meridian notesaurelia-glossary.md - 3
What Nexus creates
Nexus indexes each client into its own scoped space and keeps every query bounded to the active one. You get ten compounding client memories that never touch: ask inside a space and Nexus answers only from that client’s graph, cites the source note and date, and tells you plainly when a fact simply isn’t in that space rather than borrowing one from another account.
From Nexus: Indexed 10 client engagements into 10 scoped spaces, with no cross-space links.
10Client spaces3,410Entities across all spaces0Cross-client links createdSpaces indexed10 clientsClient space Entities Notes indexed Scoped clients/aurelia 412 188 Yes clients/meridian 357 141 Yes clients/harborline 298 119 Yes Sample scoped answer, Aurelia only2 sourcesClaim Source note Date Renata owns the Atlas migration aurelia-kickoff.md Feb 2025 Go-live slipped to Q4 aurelia-status-may.md May 2025 "A stakeholder named Renata appears in both the Aurelia and Meridian spaces, but they resolved to two separate scoped nodes, no cross-link. Want me to confirm they are different people, or keep them firmly separate as-is?"
- 4
Follow-up prompts
Prove a query stayed in its space
Because every answer cites its source note, you can confirm a response was drawn only from the active client, each citation names a note that lives in that space and no other. It is the audit trail that lets you promise a client their context never touched another account.
Answer only from the Aurelia space: who are the decision-makers on the Atlas project? For every name, cite the source note, and confirm each note belongs to the Aurelia space.
Add a new engagement without touching the rest
When you win a new client, create a fresh space and point Nexus at just their notes. It indexes into that space alone, leaving every existing client graph untouched, so onboarding an eleventh account never disturbs the first ten.
Index the notes for the new client at space://clients/northwind into its own scoped space. Keep it fully separate from every existing space, and summarise the entities extracted, cited to their source notes.
Roll up one client on demand
When you prep for a client meeting, ask Nexus for a summary of just that space, the people, projects and open threads, in one place, without a single fact from another engagement creeping in.
Give me a rollup of the Aurelia space: key people, active projects, and open decisions, each cited to its source note. Draw only from Aurelia and flag anything you cannot support from that space.
- 5
Tips and troubleshooting
One space per client, always
The wall between clients is the space boundary. Indexing two engagements into one space is what lets facts cross. Keep a strict one-space-per-client rule and the isolation holds by construction, not by hoping a query stays polite.
Same-named people stay separate by default
A common first name or a generic “the CFO” can appear across clients. Nexus keeps them as distinct scoped nodes rather than merging, which is exactly what you want, never let a per-client glossary reach across spaces.
Uncited means not-in-this-space
Ask Nexus to answer only from the active client and it will say when a fact isn’t there rather than borrowing one. Treat an uncited claim as a prompt to check the space, not as a quiet cross-client guess.
Ready to try it yourself?
Give each client its own scoped space, name the entities that matter, and ask your questions inside one account at a time, every answer drawn from, and cited to, that client alone.
Run Nexus