Skip to content

Error reference

Every library crate in this workspace (mif-schema, mif-ontology, mif-frontmatter, mif-embed, mif-store) and both binaries (mif-cli, mif-mcp) map their errors to an RFC 9457 application/problem+json envelope via the shared mif_problem crate. Each problem type gets a stable, versioned type URI of the form:

https://modeled-information-format.github.io/mif-rs/references/errors/{slug}/{version}

That URI is dereferenceable: it resolves to the reference page documenting that exact problem type, one page per {slug}/{version} pair below.

invalid-json, document-not-found, and io are each problem types unique to mif-cli/mif-mcp, and each is defined per binary with its own mif-cli-*/mif-mcp-* prefixed slug — mif-cli and mif-mcp never share a slug with each other or with mif-ontology (which defines its own separate mif-ontology-io problem type for the identical conceptual failure; see mif-ontology-io/v1 above). Every other failure they report delegates verbatim to the wrapped library crate’s own problem type.

mif-rh is the compiled research-harness ontology engine — deterministic resolve()/review(), the hypothesis layer (suggest_type(), the FindingIndex, the suggestion queue), and confidence calibration. Three of its MifRhError variants (Ontology, Frontmatter, Embed) wrap and delegate verbatim to mif-ontology/mif-frontmatter/mif-embed’s own problem types rather than defining their own — those wrapped variants are not listed again below.