How It Works

Import. Map. Govern. Every step on the ledger.

Three steps from raw schema to a ULID‑keyed, SHA‑256 hash‑chained record an auditor can verify — with role‑separated approval at every transition.

Import

Upload Avro, XML Schema, JSON Schema, Excel, Erwin XML, or connect via JDBC. Each ingest writes a SchemaIngested entry to the ledger — ULID‑keyed, hash‑chained, and stamped with the source fingerprint — so nothing reaches the MetaModel without a signed provenance row.

Map

Domain experts draft source‑to‑target mappings with Semantic Match suggestions. Every draft, edit, reviewer comment, and field‑level change appends MappingDrafted, MappingRevised, or ReviewerCommented entries to the chain — full provenance, no silent overwrites.

Govern

Approvers sign releases under role‑at‑time‑of‑action RBAC. ApproverReleaseSigned closes the chain for that version, ReleasePromoted records each environment promotion, and CI/CD pulls the signed spec — no untracked path to production.