Which record fields should an escalation listing expose to buyers?

A listing is easier to trust when it names the structure. For this workflow, a release can expose four linked tables.

- **applications:** `case_id`, `product_code`, `requested_amount`, `submitted_at`, `status` - **reviewers:** `reviewer_id`, `role`, `tier`, `team` - **authority_limits:** `role`, `product_code`, `max_amount`, `exception_allowed`, `effective_from`, `effective_to` - **escalations:** `escalation_id`, `case_id`, `from_reviewer_id`, `to_role`, `reason_code`, `rationale_text`, `status_from`, `status_to`, `decided_at`, `outcome`, `conditions`

The key links are `escalations.case_id` to `applications.case_id`, and `authority_limits` joined on role and product at the decision date. Because limits carry effective dates, a buyer can check whether the correct version applied.

A release can ship these as JSONL for event-style records and Parquet for wide tables, with a schema file describing types and keys. Your catalogue entry can mirror the table list, key relationships and schema version so buyers can map it to their own pipelines.

For onward licensing, record the schema version in each listing. If a later release changes a field, buyers can see which version they hold. The identifiers are generated, so they do not point at real people or accounts.