Several workers in one repository at once

More than one agent or person is changing the same repository in the same period, in worktrees or in sequence.

Context

Each worker is individually reasonable. The cost appears between them: two tasks touching one file from different assumptions, a task record that travels with a branch into a checkout that never claimed it, a handover nobody can tell is stale.

Fits when

Work is divided by paths and it matters that the division is checked rather than agreed
Sessions hand work to each other and the handover has to survive the branch moving
You need to know which checkout a task record belongs to

Does not fit when

One person works one repository at a time and nothing is ever handed over
Coordination is the point and you want a scheduler; this tool reports overlap, it does not resolve it

Both lists are required. An entry declaring only what it fits is refused by the generator and by majordomus doctor.

What you would do here

Run several workers in one repository without them collidingGive each worker a declared scope, and find out immediately when two of them claim the same paths.described start · check · finish
Hand unfinished work to the next sessionStop mid-task and leave the next worker something to act on that is not a transcript.described checkpoint · handover · context · check
Serve the repository's AI layer to every AI client through one shared serverOpen the repository in any client the tool declares a provider for (docs/generated/providers.md) and have each of them read the same rules, prompts and knowledge over MCP from one process, seeing each other.described init · doctor
Record a decision so the next worker can find itWrite down what was decided and why as state, then find it again without reading a conversation.described decision · search · history
Record what one worker did in one sittingOpen a session, do the work under whatever tasks it touches, and close it into an envelope that references what it produced and copies nothing.described session · history · knowledge
Start a session from a rendered framing, not a pasted transcriptList the prompt assets the repository ships, render one against the durable state, and read the context it embeds.described prompt · context
Deliver issues in waves the graph computes, and take the next oneValidate the plan, read the execution waves the dependency graph yields, see which issues are ready and which are blocked on what, and take the one issue a worker should do now.described plan · start
Read back what happened, and keep the ledger within its capRead the append-only ledger as operational history, filtered by task and event, validate every line, and rotate the oldest lines into an archive rather than deleting them.described history · search · watch
Resume in the right worktree, never against somebody else’s taskFind the handover that belongs to this worktree and branch, and see a task record from another checkout reported as foreign rather than enforced here.described handover · check · context
Hand work over with a question still open, and keep it blockingClose a task into a handover while a question is unresolved, start the follow-up task, and see the same question still refuse acceptance there.described handover · start · check · question · finish
Have the session opened and closed without anybody remembering toWire the provider''s own session events, and the episode opens when the sitting begins, hands the worker what the last one left, records what a compaction is about to discard, and closes with a continuation record beside its envelope.described capture · session · doctor · start · checkpoint · handover

The rules that matter here

blocking Scope integrity
blocking State consistency
blocking Handover integrity