← Back to catalogue
Published

Legal case and dispute

EM-LEG-05 · em-leg-05

Maintain a traceable dispute history so responsible counsel can assess claims, manage procedural obligations and follow outcomes.

Enterprise profiles Enterprise subject EnterpriseLEG

Bundle → Layer → Finding → Questions Filled

3 bundles · 4 layers · 6 findings · 11 questions

Case and parties This bundle identifies the dispute, its participants and related proceedings.

Case structure

This layer identifies disputes independently of whether proceedings exist.

Legal case

This finding records dispute identity, proceeding status and party participation.

  1. What stable internal identifier identifies this dispute?
  2. What is this dispute's proceeding status, including its forum and case number if proceedings have been instituted?
  3. Which party and procedural role does this participation record identify?

Related proceedings

This finding records connections between proceedings without implying a new decision.

  1. Which proceedings does this relationship record connect, and is the relationship a counterclaim, appeal or another connection?
Claims and events This bundle records asserted claims, procedural events and deadlines.

Claim records

This layer separates asserted claims from established outcomes.

Claim record

This finding identifies a claim, its requested remedy and its supported status.

  1. Who asserts this claim, and what amount or remedy is requested?
  2. What status is recorded for this claim, and which source supports that status?

Proceeding events

This layer records procedural actions and obligations separately from decisions.

Procedural event

This finding records dated procedural events, including the filing of an appeal.

  1. What occurred in this procedural event, and when did it occur?

Procedural deadline

This finding records the basis, responsibility and status of a procedural deadline.

  1. Which trigger and governing rule or order establish this deadline and its due date, time and time zone?
  2. Which responsible role and completion or extension status are recorded for this deadline?
Case outcome This bundle records adjudicated and non-adjudicated dispute outcomes.

Outcome records

This layer records decisions, settlements, withdrawals and other outcomes with their supporting evidence.

Case outcome

This finding records an outcome's type, authority, scope and subsequent status.

  1. What outcome type, result, affected claims, effective date, deciding body or responsible parties, and supporting decision, agreement or other evidence are recorded for this outcome?
  2. What finality, review or fulfillment status is recorded for this outcome, and which later event or record supports any change?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseLEG
Industry
Cross-industry
Tags
EM-LEG-05W3subjectLegalCaseClaimProceedingEventCaseOutcome

What it is Filled

A record of a dispute, including disputes without instituted proceedings, with parties, claims, procedural deadlines, events and decisions, while contracts, evidence and financial reserves remain references.

Why it exists Filled

Maintain a traceable dispute history so responsible counsel can assess claims, manage procedural obligations and follow outcomes.

Distinguishing features Filled

  • A party's assertion is recorded with its proof status and is not an established fact.
  • Every decision is tied to a deciding body and a date.
  • Filing an appeal is a procedural event, while any subsequent appellate decision is recorded separately and preserves earlier decisions.
  • Settlements, withdrawals and other non-adjudicated outcomes are recorded with their supporting authority and evidence.
  • The case references contracts, evidence and financial reserves without owning those records.

What robots and AI may and may not do Filled

Must not

  • Record a claimed amount as a confirmed debt.
  • Erase or overwrite an earlier decision when it is appealed.
  • Disclose case material to people outside the restricted access group.
  • File documents or take a procedural step on its own initiative.

Only with a human decision

  • Any filing, settlement or procedural step.
  • Setting or releasing a financial reserve for the case.

May

  • Build a timeline of proceedings, events and decisions.
  • Track procedural deadlines and report them to the responsible lawyer.
  • Summarise claims and their proof status.

Moral aspects Filled

  • Case files contain sensitive personal data and privileged communications.
  • Mistaking claims for facts can damage a party's reputation and finances.
  • Access must respect legal privilege and confidentiality orders.

Who is affected

  • Parties to the dispute
  • Witnesses and other named persons
  • Legal counsel

Owners Filled

Steward

The responsible legal matter owner is accountable for the dispute record and its legal interpretation.

Master systems

  • A matter management system maintains the dispute record.
  • A document management system retains supporting legal documents.
  • A court filing portal provides authoritative filing records for proceedings within its scope.

Links to other meta-models Filled

references

  • WM-POL-009 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A stable internal dispute identifier identifies the record whether or not proceedings have been instituted.
  • Proceedings additionally reference their forum and assigned case number when available.
  • Court decisions may reference the European Case Law Identifier established through the Council of the European Union where the jurisdiction uses it.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition required Filled

  • A dispute record identifies parties, contested claims and its proceeding status.
  • A forum, case number and dated procedural events identify instituted proceedings when available.
  • The dispute record is distinct from an underlying contract or an internal complaint record, although either may be referenced.

Capabilities and actions required Filled

  • The sequence of facts and decisions can be reconstructed as of any date.
  • Several proceedings of one dispute can be viewed together.

Hazards and failure modes required Filled

  • Procedural deadlines may be missed.
  • Privileged material may be disclosed without authority.
  • Overturned decisions may be treated as final.

Standards and interfaces optional Filled

  • The European Case Law Identifier established through the Council of the European Union identifies court decisions in participating jurisdictions.
  • LegalDocML from OASIS supports representation of judgments and legal documents.
  • ISO 8601 from the International Organization for Standardization supports representation of procedural event dates.

Context of use required Filled

  • The record supports disputes before proceedings and disputes in litigation, arbitration or regulatory proceedings.
  • Procedure and deadlines depend on the forum and must be checked against its rules.

Sources Filled

  1. OASIS UBL: business documents for agreements and orders
  2. FIBO (EDM Council, OMG): financial agreements, parties and obligations
  3. ODRL: permission, prohibition, duty and constraint
  4. Primary legal sources of selected jurisdictions; subject-matter verification of applicability is mandatory
  5. OASIS Universal Business Language (UBL) 2.3 - Checked live (HTTP 200) on 2026-10-07.
  6. W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • How to separate a party's assertion from an established fact?
  • How to link several proceedings of one dispute?
  • How to model an appeal?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-leg-05/brief.json, ver-cy/world-models/card-supplements/em-leg-05.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.