Skip to main content

​
Get bounded ontology-binding context

Use ontology_binding__get_context to give an agent the relevant logical definitions and governed physical mappings from one exact binding release.
  • Required inputs: binding_id, release_id, and query.
  • Optional inputs: ontology_release_id, max_resources, max_depth, max_tokens, diagnostics, session_id, and Gateway’s rationale.
  • Limits: max_resources is 1–50, max_depth is 0–3, and max_tokens is 128–32,000.
  • Effect: read only.
Use the stable ontology_binding_... artifact ID with an exact Core Registry rel_... release ID. The result keeps the binding’s original ontology release pin visible for audit and includes physical source, relation, field, transformation, and governed-join declarations relevant to the query. You may pass a newer ontology_release_id for the same ontology. Reuse succeeds only when every logical resource referenced by the binding has the same exact version and content hash. An incompatible release returns a diagnostic instead of silently reusing stale mappings. Physical identities are declarations. The tool does not connect to a source, verify that a table or column exists, read business data, generate SQL, or run a query.