A living model of the organization.

Give every agent a place, a mandate, and limits.

An agent can fill a role like any other contributor, but it should never arrive without organizational context. Particulars gives it the team’s purpose, its own focus, the authority it may exercise, the decisions that require consultation, its human and software collaborators, and the guidelines it must follow. Context stays current because it comes from the model. Access is read-only, revocable, and scoped to one team.

The model begins where the work already happens.

Particulars reads connected work systems to draft a starting model, cite the evidence behind its observations, and notice when the page and the work diverge. Editors decide what becomes part of the record. Slack is live. Documents and project systems come next.

Connect once at the organization level. Each team chooses the channels that contain useful evidence about its work.

Keep the model close to the work.

Work moves first. Documentation notices later. On a regular cadence, Particulars compares a team’s model with evidence from its connected sources. It flags specific drift, shows what produced the observation, and proposes a small repair. A person confirms every change — the model becomes more truthful without becoming autonomous.

Turn authority into a record.

Decision rights describe how authority should work. The decision record shows how it actually works. Raise an issue, connect it to the authority that governs it, record the decision, and preserve who was consulted. Over time, Particulars can show latency, throughput, repeated escalation, and the places where the organization routinely waits for someone it did not need.

The org chart shows reporting. The network shows work.

Because teams share one shape and relationships become real edges, Particulars can render the organization from many useful points of view. See the whole company. Find every team touching a capability. Zoom to one team’s neighborhood — what it depends on, what depends on it, and where the work crosses a boundary the hierarchy cannot express. The org chart is still there. It is simply no longer mistaken for the whole organization.

A serious model should still feel like a document.

Inline editing. Keyboard-first movement. Plain language before configuration. Share a team publicly or keep it scoped to the organization. Subscribe to change. The structure exists to make the work clearer — the interface should get out of the way.

The organization changes. Keep the history.

Every save becomes a version with a named author and a readable diff. See how a team’s purpose, focus, authority, roles, and measures evolved. Restore an earlier version. Learn which changes lasted and which ones quietly reversed. The model is current without becoming amnesiac.