Metadata is the whole game. Everything the approach depends on — the model, the mappings, the rules, the time policies, the lineage, the meaning — is metadata: structure and logic captured as data rather than buried in code or slides. Get the metadata right and the platform can be generated from it, the AI can read it, and the auditor can query it. Get it wrong or leave it implicit, and you are back to archaeology. The shift is to stop treating metadata as documentation about the system and start treating it as the substance of the system. Descriptive metadata drifts because nothing breaks when it is wrong; the metadata that matters here is the kind that runs the platform, so it cannot lie. Structured, versioned and open — markdown, YAML, rules in git — it becomes the single source that SQL, tests, docs and answers are all generated from. Metadata is the noun the whole family of concepts hangs off: executable metadata is the property that makes it run, the metadata star is the image of everything orbiting it, and metadata-as-code gives it an engineering lifecycle. Model it well and the leverage follows; ignore it and there is nothing for the tools to stand on. This is where all of it comes together. A great deal has to be modeled — structure, transformations, contracts, deliveries, calendars, incidents, the process, the change over time — and these models keep changing. The result of all that modeling effort is stored as metadata, accessible to the systems, to the AI, and to the MCP servers — and through those MCP servers, to other systems and to stakeholders who can simply ask their questions and get grounded answers. And it is all versioned over time: in git, and as versioned metadata, so you can see not just what the system is now, but how it got there. One evolving, queryable source, open to everyone and everything that needs it.
← All concepts & vocabulary