What Is an Instruction?
An instruction is a rule you give an agent: in this scenario, do this. Categories cover the common cases out of the box. Instructions let you handle the ones that are specific to your organisation, such as always blocking a project codename, or allowing a scenario your team has already reviewed. Instructions are forward-looking. Once you add one, the agent applies it to every trace from then on.What an Instruction Is Made Of
| Part | Description |
|---|---|
| Name | A clear label, for example “Block credit card numbers (PCI)”. |
| Category | The category it relates to, such as Personal data or Credentials. Choose Other if none fit. |
| Trigger | When the instruction should apply. |
| Criticality | Low or High. High criticality escalates to a person. |
| Action | What the agent does in this scenario: Allow, Block, or Escalate. |
Triggers
The trigger decides when an instruction applies. Pick the approach that fits the rule.- Semantic
- Regex
- String match
Matches a scenario by meaning, even when the wording differs. Describe the situation in plain language.Example: “Customer is discussing their account balance or transaction history.”
Create an Instruction
Set criticality and action
Choose Low or High criticality, then the action: Allow, Block, or Escalate.
Save an Instruction From an Assessment
You do not have to write every instruction from scratch. When you review an assessment and decide how a scenario should be treated in future, you can save it as an instruction directly from that decision. The new instruction keeps a link back to the assessment it came from, so you always know where it originated.Assessments
Review verdicts and save instructions from them.
Data Protector
See how instructions sit alongside categories.