> ## Documentation Index
> Fetch the complete documentation index at: https://docs.esheria.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Filing, Evidence, And Penalties

> Use first-class filing rules, evidence requirements, penalty facts, and review audit metadata.

The current Regulatory Pack API separates source material from tenant-owned
work. Filing rules, evidence requirements, and penalties are canonical
source-traced facts. They help downstream products decide what to do, what to
prove, and how to triage consequences, but they are not customer task records by
themselves.

## Filing Rules

```bash curl theme={null}
curl --compressed -sS \
  "$ESHERIA_API_BASE_URL/api/v1/domain-packs/UK-DATA-PROTECTION-PRIVACY/filing-calendar?limit=25" \
  -H "x-api-key: $ESHERIA_API_KEY" | jq
```

The response prefers first-class `filing_rule` facts when available and falls
back to legacy obligation deadline fields for older packs. Filing rule rows can
include:

* `filing_rule_id`
* `filing_name`
* `trigger`
* `deadline_rule`
* `recurrence`
* `regulator`
* `duty_holders`
* `submission_channel`
* `evidence_or_proof_expected`
* `linked_obligation_ids`
* `forms`
* `citation_ids`

Use `version=<domain_pack_version>` to read historical canonical filing rules
when that version is loaded.

## Evidence Requirements

```bash curl theme={null}
curl --compressed -sS \
  "$ESHERIA_API_BASE_URL/api/v1/domain-packs/UK-DATA-PROTECTION-PRIVACY/evidence-register" \
  -H "x-api-key: $ESHERIA_API_KEY" | jq
```

The response prefers first-class `evidence_requirement` facts when available.
Evidence rows can include:

* `evidence_requirement_id`
* `evidence_type`
* `description`
* `requirement_level`
* `required`
* `retention_period`
* `linked_obligation_ids`
* `linked_filing_rule_ids`
* `forms`
* `citation_ids`
* `verification_metadata`

This is the legal basis for evidence. Uploaded files, attestations, approvals,
and evidence review status belong in the downstream operating workbench.

## Penalty Facts

```bash curl theme={null}
curl --compressed -sS \
  "$ESHERIA_API_BASE_URL/api/v1/domain-packs/UK-DATA-PROTECTION-PRIVACY/penalty-facts?limit=25" \
  -H "x-api-key: $ESHERIA_API_KEY" | jq
```

Penalty rows are source-backed consequence facts, not customer risk scores. They
can include:

* `penalty_fact_id`
* `trigger_or_violation`
* `consequence_type`
* `amount_or_range`
* `regulator_or_enforcer`
* `linked_obligation_ids`
* `linked_provision_ids`
* `citation_ids`
* `materiality`
* `confidence`

Supported filters include `version`, `regulator_or_enforcer`,
`consequence_type`, `linked_obligation_id`, `linked_provision_id`, `q`, `limit`,
and `offset`.

## Legal Review Audit

```bash curl theme={null}
curl --compressed -sS \
  "$ESHERIA_API_BASE_URL/api/v1/domain-packs/UK-DATA-PROTECTION-PRIVACY/legal-review-audit?limit=25" \
  -H "x-api-key: $ESHERIA_API_KEY" | jq
```

Legal review audit rows explain canonical classification and publication
decisions. They can include:

* `fact_class`
* `duty_holder_type`
* `audience_type`
* `operability_class`
* `customer_actionability`
* `legal_effect`
* `recommended_use`
* `promotion_state`
* `promotion_tier`
* `review.review_decision`
* blocking reasons
* primitive summary
* citations and quote spans

<Warning>
  This endpoint is an audit surface for canonical legal intelligence. It does
  not expose tenant owners, operating statuses, uploaded evidence, comments, or
  remediation records.
</Warning>