# Execution Gate Matrix v0.1

Use this matrix to map `destination + reliance level` to minimum release controls.

## Field definitions

- `destination`: where output is going next
- `reliance level`: how strongly downstream users may treat output as authoritative
- `review requirement`: human review needed before release
- `approval requirement`: named approver requirement before release
- `evidence requirement`: artefacts required to justify release
- `audit fields`: fields to write to the audit event
- `blocked states`: conditions that force hold/block/escalation

## Matrix

| Destination | Reliance level | Review requirement | Approval requirement | Evidence requirement | Audit fields | Blocked states |
|---|---|---|---|---|---|---|
| Internal workspace notes | Assistive | Optional peer spot check | None | Prompt summary + source list (if used) | Task id, run id, model id, policy version, reviewer `null` | Missing matter id, missing policy version |
| Matter team working channel | Reviewed | Assigned matter reviewer | Matter lead for novel legal position | Prompt summary, cited sources, reviewer notes | Matter id, task id, destination, reliance, reviewer id, gate outcome, timestamp | Reviewer conflict, uncited legal conclusion, privileged data in non-approved environment |
| Client-facing communication | Authoritative | Supervising lawyer review | Named responsible partner (or delegate per mandate) | Draft-to-final diff, cited authorities, client-term checks | Client id, matter id, gate id, approver id, evidence hash, policy version, timestamp | No approver, unresolved red flags, policy mismatch with client terms |
| External filing / regulator / tribunal | Authoritative-plus | Dual review (matter + filing specialist) | Filing authority owner | Citation packet, procedural checklist, submission controls evidence | Filing id, jurisdiction, gate chain, reviewer ids, approver id, evidence bundle id, immutable timestamp | Jurisdiction block flag, incomplete checklist, unverified source, missing filing authority |

## Minimum audit schema

- `gate_id`
- `gate_outcome` (`pass` / `fail` / `escalate` / `block`)
- `policy_version`
- `destination`
- `reliance_level`
- `matter_id`
- `task_id`
- `reviewer_ids`
- `approver_id`
- `evidence_refs`
- `blocked_reason` (nullable)
- `created_at`

## Escalation and blocked-state rules

- Escalate when confidence signals or retrieval coverage are below policy threshold.
- Block when destination/reliance pair requires approval and no valid approver is present.
- Block when evidence package does not match destination controls (for example client-facing output with no authority support).
- Escalate when client terms, jurisdiction, or mandate flags conflict with current route.

## Notes

- Tune this matrix per practice area and jurisdiction.
- Keep matrix versions in source control and log version id in every gate event.