You will never outrun Conway's law.

Conway's law is gravity. The systems an organization ships resemble the organization that shipped them.

The handoffs visible in the product usually existed between teams first. Fragmented ownership becomes fragmented experience. Slow decisions become slow software. A clean interface can disguise the structure underneath for a while. It cannot repeal it.

Much of the work called software engineering is organizational design with a build artifact. Much of the work called operations is the same work without one.

Role clarity is load-bearing.

Ask ten people in a fifty-person company who decides a recurring question. You will get several answers. Ask who owns the work that follows. More answers. Ask what a team created two months ago is for. There will be silence, then a reconstruction from memory.

This is not an employee-comms problem. Decisions wait. Work duplicates. Interfaces become meetings. Senior people spend their time routing information because the organization has no trusted representation of itself.

A job description does not solve this. Clarity is a shared property. A person can understand their role and still work inside a confused team. A team can understand itself and still collide with three neighboring teams because the boundary between them exists only in habit.

The org chart helps, but it captures a narrow relationship: formal reporting. Work also travels through expertise, dependency, trust, decision authority, shared customers, temporary teams, contractors, agencies, software agents, and the person everyone knows to ask despite what the chart says.

The organization is all of those relationships together.

Role clarity used to be partly conferred by the building. You sat near the work. You learned authority by watching it exercised. You understood a team's actual boundary because you saw who entered the room.

That ambient system is weaker now. Hybrid work offers partial visibility. Distributed work offers less. Portfolio careers and cross-company work make the single-company directory actively incomplete.

The substitutes are expensive: more meetings, longer onboarding, repeated alignment rituals, quarterly reorgs, and heroic managers who carry the model in their heads.

The cost is hidden, but real.

Coordination drag rarely appears as its own line on a profit-and-loss statement.

It appears as "we are moving slower than we should." It appears as a product area with three owners and no decision. It appears as an executive meeting spent discovering that two teams have been building versions of the same thing. It appears as a good person who leaves because the work requires constant negotiation with an invisible system.

When the structure is illegible, every initiative pays a tax to discover the organization before it can change anything inside it.

When the structure is legible, work can begin from a shared model. Disagreement becomes specific. Teams can change boundaries without first arguing about what those boundaries currently are. Leaders can see patterns across the whole rather than relying on the loudest local report.

The model does not eliminate politics, ambiguity, or judgment. It gives them an object.

Agents raise the stakes.

Every software agent asks the questions a new colleague asks.

What is this team for? What am I responsible for? What may I decide? Which actions require consultation? Who receives my output? What evidence counts? What should I do when the rule and the situation conflict?

A person can spend a month watching meetings and infer the answers. An agent reads what the organization has made available — or improvises.

Structure used to be something a company could leave implicit and pay for gradually. Put software into roles and the bill comes due quickly. An organization that is merely difficult for people to read can be unusable to machines.

The companies that receive real leverage from agents will not simply deploy more of them. They will give them better places to stand: explicit roles, bounded authority, current context, inspectable relationships, and a human system that remains responsible for the whole.

Machine-readable should not mean machine-governed. It should mean the organization has finally written down enough of itself to delegate deliberately.

A small instrument.

Particulars starts with one team.

A page records its purpose, focus areas, measures, decision rights, roles, and working rules. The page connects to its parent, subteams, neighboring teams, people, agents, decisions, evidence, and measures. Connected tools help keep the record close to the work. Versions preserve what changed.

One page is useful on its own.

Many pages become a model.

The model can show the organization as a hierarchy, a network, a person's world, a set of shared capabilities, a chain of authority, or a field of overlapping work. It can notice drift, surface patterns, and return useful intelligence to the people doing the work.

Particulars will not repeal Conway's law. Nothing will.

It will let the organization see the structure it is already living inside — and give it something concrete to change.