Keep one client's context out of every other client's build

Start with two current client engagements. Check their repository folders, shared documents, agent conversations, access lists, and environment bookmarks. Clear names help, but a name is not an access boundary. Identify any catch-all note that includes both clients' private material. Split it into client-specific records and decide what belongs in an internal portfolio summary instead.

Before an agent session, verify the selected client, local directory, repository, branch, and task. Do not paste one client's brief into another client's conversation to reuse the structure. Copy an empty template instead. End with a client-specific handoff and store it in the correct place. Review collaborator access when an engagement or role changes. These manual habits are useful even with software isolation because files, email, local agent history, and external repositories have their own access rules. A project system cannot undo sensitive material pasted into the wrong external conversation.

Create a distinct workshop for the client when the people and access boundary need to be separate. Add the client's projects inside that workshop, rather than making every task its own workshop. Keep private documents, decisions, links, and delivery notes in the intended record. Check the current workspace memberships and project-sharing settings before inviting anyone.

Scope agent access to the work it needs. Read-only access is different from permission to propose changes or write routine updates. Have the agent select the correct project and read its brief before editing. Hark's working sessions are project-bound; changing projects requires an explicit switch. That does not mean Hark controls every file on the agent's machine or clears the tool's existing conversation. Check the local repository and conversation context too.

Use cross-client oversight for status, blockers, and responsibilities without copying detailed private rationale into a public summary. When sharing a client room, choose appropriate sections and inspect the actual visible content. Do not assume a familiar template has inherited the correct links. Verify repositories, environments, and recipients individually after creating each engagement. Keep credentials outside the project notes and direct authorized people to the service that manages access.

An agency can standardize a checklist for scope, test evidence, handoff gaps, and client questions. Reuse that blank structure while creating client-specific content in the right record. Before each milestone, compare the project name, repository, and shared links with the delivery. A copied staging URL can be as misleading as a copied decision.

When staff change, review workshop membership and external repository access separately. Give the incoming builder a current brief and one bounded task, then ask them to identify missing information. Keep portfolio readers' access narrower than the access needed to implement a client project whenever appropriate. Product isolation supports a boundary; it is not a compliance certification or a substitute for contractual review. The client documentation workflow explains how to keep each isolated record resumable, while this setup keeps the record attached to the correct engagement throughout the work.