Requested relief can be represented as source, scope, class, and review status records. Honesty note: simplified remedies and relief model; jurisdictions and rule sets vary; the pinned first step states the as-of date; not legal advice.
highlighted = computed this step
Remedies model honesty note
Honesty note: simplified remedies and relief model; jurisdictions and rule sets vary; as of June 24, 2026; not legal advice; code encodes a stated structural model, not the law itself.
remedies model as of June24,2026
Start with the request record
The stated process models requested relief as source, scope, remedy-class label, and review-status fields. A request record is not a remedy decision.
request record before review
Example request packet
The toy pleading file has monetary-label, order-label, and declaration-label rows for review.
money label plus order label plus declaration label
The table recomputes support
The retrieval table recomputes 3 request records and 3 token-supported rows from the authored source fields.
records=3,support=3
Diagram note
The diagram is a request-record table. It shows review coordinates, not a decision about relief.
record table only
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated structural model, not the law itself.
Summary
Remedy modeling should expose the requested relief fields before proof, calculation, or equitable review.