Standard operating procedures
When the answer is a rule,
not a screen.
Procedure the Project Management Office writes and owns. Each one states what it covers, why it exists, and what it stops going wrong quietly.
Adding or changing a tool
Every card on this page is generated from the TOOLS array at the bottom
of this file. Add an entry, and the card, its node on the culm, its fade-in delay and
the count above all follow. Nothing else needs editing. The grove runs two abreast; an
odd tool out closes it across the full width.
Written procedure comes from the SOPS array below it. Those are documents,
not applications, so they read as ruled entries rather than cards — a node band, no culm
through it. An SOP with no href shows a link-needed flag unless its status
is planned, which is how a document that exists but nobody can open stays
visible as a problem.
Keep why about what changes for the business. A feature list tells nobody
whether the tool is worth opening.
Leave note off unless it stays true indefinitely. Version numbers and
build dates go stale here without anyone noticing, and a stamp nobody trusts is worse
than no stamp — each tool shows its own version when you open it.