#context-contract

Agent Context Contract is a ai interface contract that defines what context may be passed into a model call for tool-using assistant workflows. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Alignment Context Contract is a ai interface contract that defines what context may be passed into a model call for model behavior shaping and policy fit. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Context Context Contract is a ai interface contract that defines what context may be passed into a model call for runtime memory and retrieved information. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Evaluation Context Contract is a ai interface contract that defines what context may be passed into a model call for AI quality and safety testing. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Guardrail Context Contract is a ai interface contract that defines what context may be passed into a model call for policy controls around model input and output. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Inference Context Contract is a ai interface contract that defines what context may be passed into a model call for model execution for user or system requests. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Memory Context Contract is a ai interface contract that defines what context may be passed into a model call for persistent or session-level AI state. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Model Context Contract is a ai interface contract that defines what context may be passed into a model call for foundation model behavior and serving. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Prompt Context Contract is a ai interface contract that defines what context may be passed into a model call for instructions and context passed to a model. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

RAG Context Contract is a ai interface contract that defines what context may be passed into a model call for retrieval-augmented generation pipelines. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Routing Context Contract is a ai interface contract that defines what context may be passed into a model call for selection among models, tools, and workflows. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.

Tool Call Context Contract is a ai interface contract that defines what context may be passed into a model call for model-triggered calls into software systems. It uses schemas, redaction rules, source labels, and token budgets so teams can keep model inputs relevant and safe while keeping evidence, reliability, and public-safe operational boundaries clear.