5. Ownership and coordination

Contributions rather than staffing positions

Chirality names several contributions: continuity with the person, conception and design, implementation and integration, and bounded execution. Roles make these contributions available for discussion. They need not require a different agent for each kind of thinking.

One person-facing agent can investigate, propose, implement and examine one coherent undertaking. Another owner becomes useful when a contribution benefits from sustained separate attention or independent preparation. Model capability is a further question. A difficult bounded review can need more reasoning than routine coordination. For a deterministic operation, a tool can be the better choice.

Contribution ownership means responsibility for carrying assigned work through examination, repair and transfer. Integration ownership concerns how contributions become a usable result. Neither one transfers the person's accountability for reliance. This distinction helps participants delegate work while keeping responsibility for integration explicit.

Capability, authority and enforcement

A capable agent can perform an operation that it is not authorized to perform in the present undertaking. A host can permit a write that the project's instructions prohibit. And an authorized operation can remain technically unavailable. Capability, authority and host permission concern different relationships. Treating one as evidence of the others can cause practical errors.

Written instructions can set a procedural boundary without enforcing it. In the Root custody case in chapter 9, a separate process could still write to the held material. The useful finding was the actual limit of the arrangement. Coordination identified who should act, but it did not exclude other writers at the filesystem. A description of that arrangement as an enforced lock would have encouraged reliance on a protection that did not exist.

The distinction also affects how records represent action. A role name or a permission field cannot establish what an operation actually did. These distinctions let people examine a claim about control, and they do not require every practical safeguard to take the same technical form.

Continuity through repair

An owner who knows the input basis, the attempted approaches and the governing conditions can often repair a finding better than a newly introduced agent. A separate reviewer can challenge assumptions while the implementation owner keeps continuity. If each small correction goes to a new agent, the result can be many completed tasks but little completed work.

The boundary of the assignment matters. A contributor that was asked only for a first fragment can reasonably stop there, even when the intended result needs connected repair and reconciliation. A broader boundary can remove interruptions without a reduction in scrutiny. Chapter 9 examines such a change in Root's practice.

Independence remains necessary where the claim needs it. A review adds little when another agent only confirms the author's summary. Its value depends on access to the actual candidate and the relevant sources. It also depends on the possibility of finding a premise that the author did not test.

Concurrent work and shared conditions

Separate source files do not ensure independence. Contributors can share a model state, a fixture, a numerical convention, a machine budget or limited review capacity. More simultaneous production can increase unfinished work if integration becomes the bottleneck.

A common premise can make concurrent work possible, and it can also multiply a defect. A small connecting exercise can expose a mistaken interface before many components depend on it. After the relevant premise is established, its evidence can support further work. That evidence need not be repeated simply because another agent now carries the work.

A temporary resource limit belongs to its setting. If someone treats it as a permanent staffing doctrine, they confuse a condition of one undertaking with the general method. In the same way, the absence of a declared dependency cannot prove that two actions are independent.

A return that reaches its recipient

Coordination depends on actual communication mechanisms. A prepared prompt, a dispatched task, a completed operation and a received result are different events. A contributor can finish in a separate session while the coordinator receives only silence. A summary of expected behavior can hide the fact that nothing ran.

These distinctions have a practical consequence. When a return is uncertain, examining the actual operation and available result helps the coordinator distinguish missing work from missing communication. A repeated request for status does not fix an assignment that was never dispatched or a broken return route. The necessary mechanism belongs in the host and project instructions that use it. The general lesson is that the relationship must actually exist.

Useful coordination includes the cost of preparation, waiting, review and repair. Neither the number of workers nor the frequency of messages measures progress toward a result that someone can use. Ownership earns its value through that result and through the continuity that makes it possible.