A company’s units and teams, the jobs its people are employed in and the two lines that run through them, written as pages a check holds.
Robert Blust · Software Engineer & Architect
The pack writes the units, jobs and reporting lines of organization design down as pages.
A unit, or a team drawn from units. Its kind tells the two apart and says whether it stands in the disciplinary line.
A job is what a person is employed as. A seat is a responsibility in a process. Our team also names an agent and our talks' voices, which hold seats and no job.
It runs through the people a unit names and up through part-of. Each answers to the unit's Lead, and no person carries a field naming their superior.
A group's guides names the jobs whose discipline it sets, wherever the people who do them sit.
A team draws its people from units, and they keep their units. A temporary group has a start and an end, not a status.
A staff unit stands in the line beside the head it serves; the flag is on its kind. A rank orders a group among all the company's groups, not among one parent's children.
A position a group is looking to fill is a row of Openings while it is open, not an object that outlives its holders.
Every human in a group directs every agent in it. Where a company grants direction per agent, the group’s Direction says which human directs which, and an agent named there takes direction from no one else.
Where the pack does not do what its sources do, its README says so, and why.
reportsTotwo lines, as SAP, HR-XML and German practice keep them apartgroup, because a team drawn across units is a group and not a unitWhat the pack does not have yet is named in its README, not hidden.
No one drew these by hand. The MCP server’s own code draws them from the example company’s pages, at the commit the site pins, and an agent can ask it for the same.
The chart you draw and the one people work in, both written as pages a check holds. Where the pack departs from its sources, its README says why.