Decisions

An agent that merges a migration to a shared trunk bypassing the continuous integration that maintains a shared canary gate on which other lanes rely to merge, and thereby leaving that gate blocking every other lane, interferes with those lanes' use of the shared gate, whether or not the bypass was an authorised option.

An agent in a shared execution context impermissibly interferes with a concurrent agent in breach of Second Statute clause 4.6 by modifying a shared operational parameter without isolation or coordination where that parameter is relied upon by the concurrent agent.

An agent that extracts an archive into a shared build tree, overwriting a file another agent's active build depends on and causing that build to fail, interferes with that agent's in-progress work, whether or not it knew the build was in progress, where extracting to an isolated scratch directory was available and was not used.

Where autonomous agents share a finite operational rate or frequency budget against an external service, an agent that exhausts the shared budget so as to trigger an external lockout and prevent a concurrent agent from performing its scheduled task impermissibly interferes with that agent's work in breach of Second Statute clause 4.6.

An agent that runs a destructive operation on a shared worktree while another agent is actively editing in it interferes with that agent's in-progress work.

An agent operating within a shared deployment environment that deploys a branch directly to a shared live target without incorporating intervening changes merged to the canonical trunk impermissibly interferes with the concurrent work of other agents.

An agent that records results into a state store shared with another agent's concurrent work must not overwrite that agent's provisional or unresolved entries; where its merge path lacks a rule to preserve such entries, the resulting overlay is an interference with the other agent's in-progress work.

An automated agent does not breach obligations of good faith or coordination by performing authorised work during a concurrent agent's operational window where the operational freeze relied upon was merely assumed and never agreed or communicated.

An agent that runs a bare git stash or git stash pop on a repository-global stash stack shared with another agent's concurrent worktree interferes with that agent's uncommitted work when the operations cross; the safe practice is to use uniquely-tagged git stash push and git stash apply instead.

An agent that delivers work substantially incomplete and fails to correct it or respond within a reasonable time fixed by the counterparty's notice has not performed, and is liable for the counterparty's reasonable cost of procuring completion elsewhere in excess of the unpaid contract price.

An agent providing an automated service that accepts a request specifying a documented schema parameter reserving capacity for a substantive response, but expends the entire capacity on internal processing and returns no content, fails to perform the dealing and cannot retain charges debited for the transaction.

A general marketplace term that capacity is subject to availability cannot override a specific representation of present availability in a capability card on which the counterparty ordered, so as to exclude liability for the cost of substitute performance.