← Catalogue
World Models · legacy example

Offense Investigation & Enforcement

This meta-model describes the enforcement path from a recorded offense to a completed correction: classification and incident records, investigations with their evidence custody, charges and their referral into adjudication (A19), and the penalties and correction measures that follow a decision. It is its own model because enforcement records carry the strictest due-process constraints in the catalogue: their subjects hold adversarial rights over them, evidence must keep an unbroken chain of custody, and adjudication itself deliberately lives in a separate model.

AI YAMLAGENTS.mdSource
IDworld.a18-offense-investigation-and-enforcement
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainpolity
Tagsoffense, investigation, enforcement
Data structure

Bundles and layers

Bundle

offense

What happened and how it is classified

Layers

classification`: offense types mapped to the reference classification · `incidentRecord`: recorded offenses and involved parties

Bundle

investigation

Establishing the facts

Layers

conduct`: investigation lifecycle and measures · `evidenceCustody`: items, chain of custody, admissibility state · `chargeAndReferral`: charges and handover to adjudication

Bundle

sanction

Consequences after decision

Layers

penalty`: imposed penalties and their terms · `corrections`: execution and supervision of penalties

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.disputeResolution` (A19): charges become cases there, penalties are read back from its outcomes, and due-process rules are defined there
  • REFERENCE `world.person` (P1): suspects, victims and witnesses resolve to persons
  • REFERENCE `world.publicOffice` (A11): investigative and enforcement powers attach to offices
  • REFERENCE `world.authorization` (A14): convictions may ground revocation of grants
  • REFERENCE `world.borderMigration` (A16): border violations enter as offenses and outcomes flow back
  • MIX-IN `world.auditTrail` (S4): chain of custody and every procedural act are append-only and traceable
  • imports: ecris (ALIGN): conviction-exchange record structure
  • imports: un-iccs (REFERENCE): the offense classification scheme, referenced by code, never copied

Canon, patches & standards

  • REFERENCE `world.disputeResolution` (A19): charges become cases there, penalties are read back from its outcomes, and due-process rules are defined there
  • REFERENCE `world.person` (P1): suspects, victims and witnesses resolve to persons
  • REFERENCE `world.publicOffice` (A11): investigative and enforcement powers attach to offices
  • REFERENCE `world.authorization` (A14): convictions may ground revocation of grants
  • REFERENCE `world.borderMigration` (A16): border violations enter as offenses and outcomes flow back
  • MIX-IN `world.auditTrail` (S4): chain of custody and every procedural act are append-only and traceable
  • imports: ecris (ALIGN): conviction-exchange record structure
  • imports: un-iccs (REFERENCE): the offense classification scheme, referenced by code, never copied

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `subjectDisclosure`: due-process access for the accused and their counsel to charges and disclosable evidence, under rules defined in A6 and enforced as S2 grants
  • `interAuthorityConvictionExchange`: structured exchange of final conviction records with counterpart authorities, in the manner of criminal-records exchange systems
  • `anonymizedStatisticsExtract`: aggregate extracts by classification, period and area for the statistics office

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The enforcement authority stewards investigations and sanctions as a mandated operator. Subjects hold guaranteed due-process access defined in A6 and delivered as S2 grants; all other access, including conviction exchange and statistics, is granted by the owner via S1 and S2 with S4 audit.

Existing assembly

Objects, relationships, events and projections

Objects

  • `offense`: a recorded instance of prohibited conduct; key attributes: classificationCode, occurredOn, location, involvedPartyRefs, reportingSource
  • `investigation`: the inquiry into one or more offenses; key attributes: leadOfficeRef, openedOn, state, measuresTaken
  • `evidenceItem`: an item held under chain of custody; key attributes: description, collectedOn, custodyChain, admissibilityState
  • `charge`: a formal accusation against a party; key attributes: accusedRef, offenseRefs, filedOn, status
  • `caseReference`: the pointer to the adjudication case in A6; key attributes: caseRef, referredOn, outcomeSnapshot
  • `penalty`: a sanction imposed through an adjudicated outcome; key attributes: penaltyType, terms, imposedOn, appealState
  • `correctionMeasure`: the execution of a penalty; key attributes: penaltyRef, regime, supervisorRef, progressState

Relationships

  • `investigation` -> investigates -> `offense` (N:M): one inquiry may cover several offenses and one offense may see several inquiries
  • `evidenceItem` -> heldIn -> `investigation` (N:1): custody attaches to the inquiry that collected the item
  • `charge` -> arisesFrom -> `investigation` (N:1): accusations are grounded in investigative findings
  • `charge` -> referredAs -> `caseReference` (N:1): a filed charge becomes a case in A6
  • `penalty` -> imposedThrough -> `caseReference` (N:1): sanctions are read back from the adjudicated outcome
  • `correctionMeasure` -> executes -> `penalty` (N:1): execution and supervision follow the imposed sanction
  • `offense` -> classifiedBy -> `offenseClassRef` (N:1): the classification resolves to a code of the reference scheme

Events

  • `offenseRecorded`: an incident was recorded and classified as an offense
  • `investigationOpened`: an inquiry was opened into one or more offenses
  • `evidenceLogged`: an item entered the chain of custody
  • `chargeFiled`: a formal accusation was filed against a party
  • `caseReferred`: a charge was handed over to adjudication
  • `penaltyImposed`: a sanction from the adjudicated outcome was recorded
  • `correctionStarted`: execution of a penalty began under supervision
  • `correctionCompleted`: a penalty was fully executed and the record closed to updates

Projections

  • `convictionRecord`: final penalties per person with their legal state; omits investigation material and dismissed charges
  • `crimeStatistics`: aggregates by classification code, period and area; omits all identities
  • `caseworkQueue`: open investigations and pending referrals for the enforcement body; omits closed and adjudicated matter