All posts
Product6 min read

Company as code, in practice

An org chart nobody reads is dead weight. Version it like software and agents can read it, diff it and follow it.

Nimind Team

Product

Every company runs on documents: the onboarding guide, the pricing policy, the list of things a new hire should not do without asking. They live in a drive, they age badly, and nobody can say which version is current. Then an agent is asked to act on them and the problem becomes expensive.

Put the company in a repo

A Nimind project repo holds the parts of a company a new hire needs on day one: who owns what, how the brand sounds, which decisions need a signature. Markdown and YAML, in git, one branch per change.

The agents read from the same repo. When the refund policy changes, the reviewer agent does not need a new prompt; it needs the next commit. That is the whole trick.

  • `company/org.yaml` — roles, owners and escalation paths.
  • `policies/refunds.md` — what an agent may promise and what it must escalate.
  • `skills/` — the procedures that repeat every week.
  • `agents/` — who is allowed to run which of them.

Diffs are the audit trail

When the company lives in files, approval becomes a pull request. You can see who changed the policy, what else moved with it, and who signed off. The question stops being “who told the agent it could do this” and becomes “who approved this commit”.

It also makes rollback boring, which is the highest compliment a rollback can get. Revert the commit; the agents follow the previous version on their next run.

Start smaller than you think

You do not need to document a whole company before you start. Write the three policies that already caused a bad outcome, the one procedure you have explained more than twice, and the org file. That is enough for the first agent to be useful and for the second one to be safe.

Published October 15, 2026 · Nimind Team

Back to all posts