> For the complete documentation index, see [llms.txt](https://docs.glik.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glik.ai/templates/compliance-advisors/global-control-copilot-cross-jurisdiction-policy-interpreter.md).

# Global Control Copilot – Cross-Jurisdiction Policy Interpreter

<figure><img src="https://3916444914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDBilw3zq3DIWtwBIyxN9%2Fuploads%2FEHGWWTAvs1Ch5ejy0nbU%2Fimage.png?alt=media&amp;token=62b2e1c6-a96c-436a-983a-c99c774a7b82" alt=""><figcaption><p>This block sequence handles the post-decision logic for the Global Control Copilot. If the submission is compliant, the LLM generates an approval summary with policy references, followed by a structured API submission with retry logic. If not, the flow escalates to a human analyst and provides the user with real-time guidance on why the submission failed. Both paths conclude with a Save Point block that logs the session's decision logic and outcome for auditability.</p></figcaption></figure>

{% hint style="info" %}
[Download Practice Files](https://drive.google.com/drive/u/4/folders/1RlcikzgdwXiKdNpuErhc2GqwjhanIW8x)
{% endhint %}

### 🔹 Phase 1: Context Initialization

| Step | Block Type            | Custom Block Name              | Description                                                                                                                                                                |
| ---- | --------------------- | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1    | `Parameter Extractor` | **Extract Request Context**    | Parses user-provided data and environmental metadata (e.g., `user_region`, `user_role`, `submission_type`). Establishes contextual variables for downstream logic.         |
| 2    | `Knowledge Retrieval` | **Load Applicable Policy Set** | Pulls the relevant policy corpus (e.g., MiCA, GDPR, SOX) based on the user’s region, department, and role. This is the source of truth for threshold checks and reasoning. |
| 3    | `Variable Assigner`   | **Assign Policy Thresholds**   | Converts raw policy values (e.g., `max_disclosure_days`, `reporting_limit`) into variables for downstream evaluation. Enables precise compliance enforcement logic.        |

### 🔹 Phase 2: Submission Intake & Preprocessing

| Step | Block Type        | Custom Block Name                  | Description                                                                                                                              |
| ---- | ----------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| 4    | `Doc Extractor`   | **Extract User Submission Fields** | Parses uploaded or pasted documents to extract relevant fields for analysis (e.g., `submitted_on`, `disclosure_category`, `risk_flags`). |
| 5    | `Data Enrichment` | **Normalize User + Context Data**  | Normalizes units (e.g., dates, monetary values), maps job roles and region codes, and prepares a clean dataset for analysis.             |

### 🔹 Phase 3: Compliance Reasoning

| Step | Block Type | Custom Block Name                | Description                                                                                                                                                         |
| ---- | ---------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 6    | `LLM`      | **Interpret Policy Constraints** | Uses a large language model to interpret extracted fields in light of the policy document. Detects vague, contradictory, or missing input that could violate rules. |
| 7    | `IF/ELSE`  | **Is Submission Compliant?**     | Branches logic based on LLM output and structured thresholds. If the submission passes all policy rules, proceeds to approval. Otherwise triggers escalation.       |

### 🔹 Phase 4A: Approval Track (IF Branch)

| Step | Block Type     | Custom Block Name                    | Description                                                                                                                                     |
| ---- | -------------- | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| 8    | `LLM`          | **Generate Approval Summary**        | Writes a natural language summary confirming that the submission meets compliance standards — with references to policy sections or thresholds. |
| 9    | `HTTP Request` | **Submit to Compliance Tracker API** | Sends structured output to an API endpoint or audit tool (e.g., Google Sheet, RegTech portal). Configured to retry on failure for reliability.  |

### 🔹 Phase 4B: Escalation Track (ELSE Branch)

| Step | Block Type | Custom Block Name                             | Description                                                                                                                                  |
| ---- | ---------- | --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| 8    | `Agent`    | **Escalate to Compliance Analyst**            | Routes non-compliant or ambiguous cases to a human analyst with full context for review. May include notification, form handoff, or tagging. |
| 9    | `LLM`      | **Generate User Guidance & Exception Reason** | Provides the user with clear feedback on why the submission failed, referencing the violated policy and suggesting next actions.             |

### 🔹 Phase 5: Session Closure & Audit

| Step | Block Type   | Custom Block Name                       | Description                                                                                                                                                      |
| ---- | ------------ | --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 10   | `Save Point` | **Generate Compliance Session Summary** | Generates a markdown or JSON summary of the session, including extracted data, evaluation results, reasoning chain, and outcome. Ideal for logging or exporting. |
| 11   | `End`        | **End Session**                         | Concludes the workflow session and hands off the result to the UI or storage system.                                                                             |
