# Predefined Policy Thresholds

This page documents sample policy rule sets and threshold values used by the **Global Control Copilot – Cross-Jurisdiction Policy Interpreter** template.

These rules are dynamically selected at runtime based on the values of `user_region` and `submission_type`. They are then injected into the workflow using a `Variable Assigner` or `Knowledge Retrieval` block and can be used to determine auto-approval, escalation, or user guidance behavior.

***

### 🔍 How Policies Are Used in GLIK

Policy definitions can be used to:

* Populate compliance thresholds (e.g., exposure caps, deadline limits)
* Control which sections are required for a submission to pass
* Inform `LLM` reasoning blocks about regulatory expectations
* Enable auto-approval or trigger escalation pathways
* Support jurisdiction-specific logic, without rewriting the workflow

They can be injected in three main ways:

1. **Variable Assigner** block (static config or memory preload)
2. **Knowledge Retrieval** block (dynamic policy fetch)
3. **Preloaded session memory** (for SDK and automation use)

***

### 🌐 Example Policy Rule Sets

***

#### 🧾 MiCA (Markets in Crypto-Assets)

```yaml
policy_reference: MiCA
risk_exposure_limit_eur: 1000000
reporting_deadline_days: 5
checklist_required: true
attestation_required: true
liquidity_disclosure_required: true
```

***

#### 🧾 SOX (Sarbanes-Oxley Act)

```yaml
policy_reference: SOX
quarterly_disclosure_deadline_days: 45
cfo_attestation_required: true
audit_trail_required: true
sec_submission_flag: true
```

***

#### 🧾 GDPR (General Data Protection Regulation)

```yaml
policy_reference: GDPR
incident_disclosure_window_hours: 72
data_classification_required: true
dpo_approval_required: true
audit_log_required: true
```

***

### 🔁 Dynamic Policy Loading

These rules can be fetched dynamically using a `Knowledge Retrieval` block, where `user_region` or `submission_type` is passed in as a query variable. This allows the template to stay modular and respond to jurisdiction-specific needs in real time.

Example:

```yaml
retriever_query:
  policy_name: {{user_region}}_compliance_policy
```

***

### 🧰 Fallback Behavior (Missing or Null Policy Values)

If any required threshold (e.g., `risk_exposure_limit_eur`) is missing or malformed:

* The workflow should default to **safe mode** — typically triggering escalation
* You can add an `IF/ELSE` guard:

  ```yaml
  if risk_exposure_limit_eur == null:
    escalate = true
  ```
* `LLM` blocks can also be configured to explain "policy unknown" conditions gracefully to the end user

***

### ⚙️ Overriding Policies Mid-Session

GLIK workflows can support dynamic override logic — for example, if `submission_type == Exception Report` and the user provides a valid `override_reason`, policy rules can be conditionally relaxed.

Use an `IF/ELSE` block:

```yaml
if submission_type == "Exception Report" and override_reason != null:
  apply_exception_handling = true
```

***

### 📦 Storing Policies in GLIK Knowledge

Instead of using YAML only, policy definitions can also be stored in **GLIK Knowledge** as structured chunks or JSON nodes. This is ideal for organizations managing multiple policies or updates over time.

Use `Knowledge Retrieval` to query:

* MiCA policies by country
* GDPR enforcement by sector
* Internal control matrices

***

### 📌 Best Practices

* Keep policy keys consistent across all regions for easier variable mapping
* Use `user_region` and `submission_type` together to disambiguate edge cases
* Always log which policy was used via `Save Point` or memory trace

***

### 📄 Related Pages

* [Input Logic & Routing Behavior](/templates/compliance-advisors/global-control-copilot-cross-jurisdiction-policy-interpreter/input-logic-and-routing-behavior.md)
* [Compliance Copilot – MiCA Reporting](/templates/compliance-and-audit-automation/compliance-copilot-mica-reporting.md)
* [Blocks & Nodes Overview](/system-architecture/blocks-and-nodes.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glik.ai/templates/compliance-advisors/global-control-copilot-cross-jurisdiction-policy-interpreter/predefined-policy-thresholds.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.