MetadataOps
The discipline of running your metadata estate as an operated system, and the role that owns it.
Twenty-two pages, four free tools, no vendor named until the last layer. Read it in order or start where you are.
Start with the introduction if you want the practice explained before the contents.
Somebody has to own it
In most organizations the work is split across four teams and held by none of them. This layer covers the role, how it relates to context engineering, where it sits, how to hire for it, and how to run it.
Run it as an operated system
Five stages with a dependency chain between them, five dimensions that make the state measurable, and a maturity ladder that turns a score into a roadmap.
And a platform built for it
Everything above this line is free, unbranded, and works on any stack. This is the one layer where MetaKarta answers for itself, against the same ten questions the operating model puts to everyone.