Glossary
Conformance
Passing a published test suite before making a claim: K1–K7 for Run components, C1–C14 for third-party agents.
Read the termGlossary · Term 07 of 39
Contract
A contract in elan1 Run is one of ten versioned fusion.*/v1 capability contracts that define how applications call a part of the open-source AI stack. Each has two licence-clean implementations, so applications are written against the contract, not the component, and a component can be replaced through governed substitution.
In one sentence: One of ten versioned fusion.*/v1 capability contracts in elan1 Run, each with two licence-clean implementations.
01In more detail
What it means in practice
The ten contracts are chat, gateway, inference, retrieval, vectors, trace, tools, run, memory and guard. A call names its contract in the X-Fusion-Contract header.
Because every contract has two licence-clean implementations, a component can be replaced without rebuilding the integration. Run never depends on Govern: infrastructure gets swapped, but the write path must not.
02Where this shows up in elan1
elan1 Run, beneath the fusion.*/v1 seam — one of the only two crossings between layers.
Defined in the elan1 glossary · Last reviewed 10 Oct 2026. Definitions change only with a dated note.
// SEE IT
See the term in a governed action.
The walkthrough follows one write from intent to proof record, using the words in this glossary.