ownership-partitioning

You can prevent file overwrites by enforcing hard write partitioning across parallel agents. This requires reading workspace/ownership.lock.json to validate assigned file globs and blocking any writes to shared_read_only or forbidden paths.

Forbidden paths in workspace governance are file globs, such as plugin directories, that agents are blocked from touching. This safety validation prevents destabilizing generated or third-party content during parallel pipeline phases.

You validate file ownership by running orchestrate.py ownership-check with the agent name and target files. This deterministic runtime verification checks planned edits against assigned globs and fails fast with a non-zero exit on violations.

You cannot write to shared_read_only paths during a parallel agent session. While agents can read these paths to access critical configuration, writing them is strictly forbidden to protect essential files from conflicting edits.

You need file partitioning when pipeline.parallel_allowed is true and writer agents run in phases that modify repository content. It enforces hard write boundaries to avoid conflicting edits and silent rule violations between parallel workers.

If an agent violates file write partitioning rules, the orchestrate.py ownership-check command exits with a non-zero code. This deterministic runtime verification fails fast, preventing the pipeline from moving to the next phase.