EEMBD
Loading…
Loading…
The cartographer. Maps a messy source onto your canonical model, the ontology work, where most integrations fail.
Ezra takes Vera's contract and maps the source onto the canonical model for your domain. She produces a reviewable mapping spec (data, not code), validates it, and opens it for a human to approve. She normalizes and harmonizes; she does not load.
Two modes: a built skill, where the mapping is already engineered and she simply runs it; or a custom source, where she reasons a new mapping with a model and routes it through human review. This translation step is the moat, and the one Oliver is being taught to generate from a conversation.
Vera's contract, schema and samples.
A validated mapping spec and harmonized entities, as a contract for the gate.
Build the mapping and validate it against the target.
Open the mapping spec for human review.
Run preprocessing against the approved mapping.
Verify the harmonized entities, emit the contract.
“This is where most integrations fail, and where Oliver does the most work.”