2.0Mandates & Charter

Outcome-based rules, compiled for you.

Declare a plain-English outcome, and Xybern compiles it into the mix of enforcement primitives needed to hold it. The signed collection of your mandates is your Charter, the single source of truth for what your agents may do.

Outcomes, not syntax

2.1

You state an outcome such as no personal data may leave the organisation. Xybern compiles it into a combination of deterministic, semantic, verdict and sequence rules, so you author intent and the engine handles the mechanics.

  • Plain-English outcomes compiled to enforcement primitives
  • One mandate can span several rule types
  • No rule syntax to hand-write
Outcomes, not syntax

Backtest before you sign

2.2

Every mandate can be backtested against real traffic before it goes live, so you can see what it would have caught and what it would have allowed. Signing it adds it to your Charter.

  • Backtest against historical actions
  • See catches and allows before enforcing
  • Sign into the Charter when you are ready
Backtest before you sign

The Charter as source of truth

2.3

The Charter is the audit view of every rule actually in force, from your mandates to agent boundaries. It is what the engine evaluates on each action.

The Charter as source of truth

More in Authorisation & Charter.

Related capabilities on the same authorisation layer. Every one is enforced before an action runs and sealed to the Provenance Vault.

1.0Intent Contracts

Approve the plan once, enforce every step.

Learn more
2.0Risk Verdict

A signed verdict, not a mystery score.

Learn more
3.0Rules

The audit view of what is in force.

Learn more
4.0Shadow Mode

See what a rule would do before it does it.

Learn more

See Mandates & Charter in your workflow.

Put one workflow behind Xybern and watch every agent action authorised, and sealed to the vault.