The operating manual for metadata
Every other part of your stack picked up an owner and an ops process over the last 15 years. Metadata mostly lived in a wiki, which is why an agent can sound more certain than your estate can back up.
This is where the practice gets written down, from the first hire to the first audit. Read it in order or pick your role below and start with the problem already in your queue.
Somebody has to own it
In most organizations the work is split across multiple 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.