Charters and controls

A Charter is your organization’s versioned configuration for controls, monitoring and recording. A control evaluates a supported input or output and produces a result. Its configured action determines how that result affects the operation.

Choose controls for a purpose

Supported controls address concerns such as sensitive information, instruction-like content, required terms or structured output. Available choices and actions depend on the deployment and its installed capabilities. Use the Charter in your portal for the current options.

For example, you might flag a detected term for investigation while blocking another category of content. A flag can still allow content through; it is not evidence that a person approved the operation.

Some controls use deterministic rules and others use models. Both have limits. Evaluate the configuration against representative examples from your own workload before relying on its results.

Change the Charter

A saved draft is different from the active configuration. Review and activate a change through the available approval flow, then check the deployment’s acknowledgement. An earlier receipt remains evidence of the revision recorded for that operation.

An enabled switch alone does not prove a control executed. Inspect the reported state and the relevant receipt. An unavailable evaluation must not be read as a passing check.

Controls can be turned off without creating a separate deployment mode. Covered requests still receive signed receipts, and recording settings still apply. Calls rejected before evaluation or sent outside the Proxy may have no receipt.

See receipts and trust for what those records establish, and Drift monitoring for changes across observations.