# Reference Input Payloads

This page provides ready-to-use test payloads for simulating different compliance submission scenarios inside the **Global Control Copilot – Cross-Jurisdiction Policy Interpreter** template.

Each example includes expected logic routing, escalation behavior, and guidance for Save Point logging and observability.

Use these inputs with the **Parameter Extractor block**, preloaded memory, or API-driven sessions during testing and demo workflows.

***

### 🧾 Example A — MiCA Disclosure (EU, Finance)

```yaml
user_region: EU  
submission_type: Disclosure  
user_role: Finance Manager

risk_exposure: 920000  
checklist_status: Complete  
submission_date: 2025-05-22  
policy_reference: MiCA
```

#### 🔁 Expected Routing:

* Loads MiCA thresholds via `Knowledge Retrieval`
* Passes policy checks: exposure < €1M and checklist = Complete
* Flows through `LLM → HTTP Request → Save Point`

#### 🚨 Escalation Conditions (if triggered):

* `checklist_status != "Complete"`
* `risk_exposure > 1000000`

***

### 🧾 Example B — SOX Attestation (US, Legal Counsel)

```yaml
user_region: US  
submission_type: Attestation  
user_role: Legal Counsel

cfo_attestation: true  
audit_trail_present: true  
submission_date: 2025-04-15  
policy_reference: SOX
```

#### 🔁 Expected Routing:

* Loads SOX policy from memory or retrieval
* Validates `cfo_attestation` and `audit_trail_present`
* If both pass → generate approval summary
* `Save Point` logs legal context, signoff metadata

#### 🚨 Escalation Conditions:

* `cfo_attestation == false`
* `audit_trail_present == false`
* Submission date older than 45 days from quarter-end

***

### 🧾 Example C — Exception Report (APAC, Product Ops)

```yaml
user_region: APAC  
submission_type: Exception Report  
user_role: Product Ops

override_reason: "Smart contract error auto-mitigated under protocol X"  
policy_reference: APAC_Fallback_Policy  
checklist_status: Missing
```

#### 🔁 Expected Routing:

* Loads fallback policy (e.g., internal controls)
* Skips checklist validation
* Checks for presence of `override_reason`
* Generates justification summary

#### 🚨 Escalation Conditions:

* `override_reason == null`

***

### 🧾 Example D — Incident Report (Global, External Submitter)

```yaml
user_region: Global  
submission_type: Incident  
user_role: External Submitter

incident_timestamp: 2025-05-20T14:30:00Z  
audit_log_attached: true  
dpo_approval: true  
policy_reference: Internal_Control_Policy
```

#### 🔁 Expected Routing:

* Uses fallback internal compliance logic
* Requires 72h window + complete metadata
* Flags submission source as external in summary
* Logs all evidence fields in `Save Point`

#### 🚨 Escalation Conditions:

* Missing `incident_timestamp`
* `audit_log_attached == false`
* `dpo_approval == false`

***

### 🧠 Save Point Logging Tips

To maximize traceability and make audits reviewable:

* ✅ Include all key input variables in the Save Point output:

  ```json
  {
    "user_region": "US",
    "submission_type": "Attestation",
    "user_role": "Legal Counsel",
    "policy_reference": "SOX",
    "escalation_triggered": false,
    "reasoning_path": "Auto-approved under SOX thresholds"
  }
  ```
* ✅ Set a `session_label` or `test_case_id` for QA:

  ```yaml
  session_label: "Demo – SOX Legal Signoff"
  ```
* ✅ Log `escalation_reason` or `policy_matched` fields to track execution
* ✅ Export to JSON for diff-based comparisons across test cases


---

# 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/reference-input-payloads.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.