Without ORG.md
Many copies
The same rule is rewritten in several places. Nobody knows which version to trust.
An open standard for organisational guidance
ORG.md keeps the important words, rules, decisions and owners that shape work in small, reviewed bundles.
The working v0.5 proof joins one company-to-team path and creates guidance for review.
Why it exists
Important guidance is copied into prompts, documents and people's heads. Each copy can slowly become different.
Without ORG.md
The same rule is rewritten in several places. Nobody knows which version to trust.
With ORG.md
Teams own small pieces. A relevant, approved view is created when it is needed.
How the pieces become one useful view
Example path
Each layer adds only what this assistant needs from its place in the organisation.
Other teams
Finance and other regions stay out of this view.
ORG.md is the standard, not one enormous company document. Large organisations use many small, owned bundles.
The v0.5.0 proof reads one local company-to-team path and produces advisory text for review. It does not approve changes, control access, publish the result or enforce actions. Projection filtering is not access control.
Try it
The example is real output from the v0.5 proof. Desk shows how the editing experience could become simpler.
Change one recorded stage and see which rule remains in use.
Open the example → Design conceptSee how a nontechnical owner could work with ORG.md while Git keeps the history underneath.
Explore Desk →For builders: source · CLI guide · draft specification