← Back to catalogue
Published

Decision / Approval Record

vr.wm-rec-010 · wm-rec-010-decision-approval-record

Provide the format-neutral context an agent needs to identify, create, interpret, validate and operate an authoritative record of a decision or approval: what was decided, on what question, by whom under what authority, on what reasons and evidence, with what conditions, from when until when it is valid, and how it is superseded, challenged, disclosed and retained.

World Models Information and virtual systems INF.REC.DEC

Bundle → Layer → Finding → Questions Filled

7 bundles · 13 layers · 32 findings · 137 questions

Identity and classification How a decision or approval record is uniquely designated, versioned as expressions and manifestations, typed, and bounded in subject matter and applicability.

Identity and designation

Identifier assignment for the decision act and its record, and the versioned expression structure that keeps corrections and translations distinct from the abstract decision.

Decision and record identifier assignment

The identifier that designates the decision, the authority that mints it, and the separation between the identifier of the decision act, the identifier of the record and any governed global identifier such as an ECLI.

  1. Which identifier scheme designates this decision, and which body governs and issues values in that scheme? identity
  2. Does the identifier designate the decision act, the record documenting it, or both, and how is the other one identified? identity
  3. When an authoritative master-system number, a governed global identifier and a locally minted UUID/ULID all exist, which is canonical for citation and which are aliases? identity
  4. How is an identifier minted for a decision taken without a meeting, a case number or a hearing — for example a delegated sign-off or unanimous written consent? identity
  5. Are any date-bearing tokens inside the identifier being relied on as the decision date, and if so how is that dependency removed? constraint

Version, expression and manifestation identity

How successive language versions, corrected texts, consolidated texts and published formats of the same decision are distinguished without fragmenting its identity.

  1. At which identity level does each stored item sit — abstract decision (work), a specific version or language (expression), a format (manifestation), or a single file (item)? composition
  2. Which expression is the authentic or authoritative text, and what governs divergence between language versions? authority
  3. When a text is corrected, is a new expression created or is the existing one edited, and how is the superseded expression preserved? lifecycle
  4. Does an anonymised or redacted published expression exist alongside a full internal expression, and are they explicitly linked? privacy

Title, language and alternative names

A short noun-phrase title representing the problem and chosen solution, plus language and any alternative citations. DCMI title and alternative apply; Nygard and MADR require a short representative heading.

  1. What short title names this decision in terms of the problem solved and the outcome chosen? definition
  2. In which language or languages is the authoritative text of the decision expressed? classification
  3. What alternative names, docket numbers or popular citations should retrieve the same record without becoming identifiers? identity

Classification and subject matter

The type of decision or approval, its binding character, and the subject matter, jurisdiction and population to which it applies.

Decision type and binding character

Classification of the record along the axes that change how it must be handled: decision family, binding versus advisory, interim versus final, and positive versus negative outcome.

  1. Which decision family does this record belong to — administrative decision, judicial judgment, corporate resolution, delegated approval, gate or change approval, or retained machine authorization decision? classification
  2. Is the instrument binding, or is it an opinion, recommendation or advice that does not itself dispose of the matter? classification
  3. Is this an interim, partial, recommended or final decision, and if not final what does it leave undecided? state
  4. Where an external decision vocabulary is used, is it the canonical classification or an alignment, and what does not map? interoperability

Subject matter and scope of application

What the decision is about and how far its effect reaches — addressees only or a general class, which territory or jurisdiction, and which organisational or asset scope.

  1. What subject matter does the decision concern, and against which classification scheme is that subject expressed? classification
  2. Does the decision bind only named addressees, or does it apply generally to a class of persons, cases or objects? constraint
  3. Which jurisdiction, territory or organisational unit does the decision operate in, and is its effect limited to that boundary? spatial
  4. Is the decision intended to have precedential or policy effect beyond the instant matter, and who may rely on it? authority
Substance and reasoning The decided question, the outcome and any attached conditions or obligations, together with the reasons, alternatives considered and evidence that support the outcome.

Decision substance

The question put, the disposition reached, and the conditions, obligations and implementation duties attached to it.

Question put for decision

The precise question, proposal, motion or request the decision resolves, including how it was framed and by whom it was brought.

  1. What exact question, motion or proposal was put, and in what wording was it put to the deciding body? definition
  2. What triggered the decision — an application, a referral, a statutory duty, a scheduled review or an own-initiative act — and who initiated it? process
  3. Which stakeholder concerns, requirements or criteria was the decision required to address? requirement
  4. Was the question amended, split or reframed before decision, and is the final wording distinguishable from the original? lifecycle

Outcome and disposition

The operative determination: the outcome value, the order or relief granted or refused, and any non-outcome such as deferral, withdrawal or inability to decide.

  1. What is the operative outcome value, and from which controlled vocabulary is it drawn? decision
  2. How are non-dispositive results represented — deferral, adjournment, withdrawal, no quorum, tie, not applicable or unable to determine? exception
  3. Which part of the record is the operative determination, and which parts are reasoning that does not bind? composition
  4. Where the decision grants in part and refuses in part, how is each element of relief and refusal separately expressed? composition
  5. If an external four-valued authorization vocabulary is used, which administrative outcomes have no equivalent and how is that recorded? interoperability

Conditions, obligations, advice and implementation duties

What must happen for the decision to take or keep effect, what the decision obliges parties to do, what is merely advisory, and which implementation and enforcement duties follow.

  1. Which conditions must be satisfied before the decision takes effect, and which conditions if breached end its effect? constraint
  2. Which attached requirements are binding obligations that must be discharged and which are advice that may be disregarded without invalidating the outcome? requirement
  3. Who is responsible for implementing and enforcing the decision, and what happens if it is not implemented? process
  4. Is effectiveness deliberately deferred to a later date or a future event, and is there a maximum permitted deferral? temporal

Reasoning and evidence

The stated reasons, the alternatives weighed and rejected, and the evidence and findings of fact on which the outcome rests.

Statement of reasons

The reasoning that justifies the outcome, whether giving reasons is legally required for this decision, and whether the reasons form part of the operative instrument or a separate document.

  1. Is there a legal or policy duty to give reasons for this decision, and what instrument imposes it? requirement
  2. Do the reasons address all material issues of fact, law and discretion presented, and how is that completeness checked? validation
  3. Are the reasons part of the operative instrument, an annexed statement, or a separately requestable document? composition
  4. Where reasons are abbreviated, standardised or omitted, what justifies that and is a fuller statement available on request? exception

Options considered and rejected

The alternatives evaluated, the criteria and weights applied, and the recorded justification for rejecting each alternative not chosen.

  1. Which alternatives were formally considered, and is the list complete relative to what the deciding body was given? evidence
  2. Against which criteria and weights were the alternatives assessed, and were those criteria fixed before assessment? measurement
  3. For each rejected alternative, what is the recorded reason for rejection? decision
  4. Was the status quo or 'take no action' option explicitly assessed, and on what basis was it set aside? decision

Evidence relied upon and findings of fact

The inputs the decision-maker used, the facts found from them, submissions received, and any communications that a rule requires to be placed on the record.

  1. Which specific inputs did the decision-maker use, and are they retained and resolvable at the version actually relied upon? provenance
  2. What facts were found, and which input supports each finding? evidence
  3. Was the affected party heard before an adverse measure, and what submissions were received and considered? process
  4. Were any prohibited or off-record communications received, and were they placed on the record as required? exception
  5. For machine-evaluated inputs, which attribute sources supplied values and were any required attributes missing? provenance

Completeness of rulings and confirmation of implementation

APA requires the record to show the ruling on each finding, conclusion or exception. MADR confirmation describes how implementation or compliance will be checked. Completeness is a quality property of the decision record; implementation evidence may live in sibling operational models.

  1. Does the record contain a ruling on every material issue and every exception presented, and which items are missing? quality
  2. How will compliance with the decision be confirmed, and by whom? validation
  3. Has implementation been confirmed, with what result and evidence? evidence
Authority, approval and attestation The competence under which the decision was taken, delegation and limits on it, the participation and voting that produced it, declared conflicts, and the evidence that fixes and attributes the record.

Mandate and competence

The source of power to decide, and the delegation instruments and thresholds that bound it.

Decision authority and legal basis

Which body or role held competence to take this decision, the instrument conferring that competence, and the rules of composition it had to satisfy.

  1. Which body, office or role took the decision, as distinct from anyone who prepared, recommended or merely signed it? authority
  2. Which instrument and provision confer competence to take this decision, and was it in force at the decision time? authority
  3. What composition, quorum or qualification rules applied to the deciding body, and what is their source? constraint
  4. How is it verified that the decision falls within the conferred competence, and what happens if it does not? validation

Delegation, sub-delegation and approval limits

Where the decision was taken under delegated power, the delegation chain, its thresholds and exclusions, and its validity at the decision time.

  1. Who delegated the power, to whom, and is there a sub-delegation chain back to the original holder of competence? authority
  2. What monetary, categorical or risk thresholds bound the delegated power, and does this decision fall inside them? constraint
  3. Which matters are expressly excluded from delegation and reserved to the delegating body? constraint
  4. Was the delegation in force at the decision time, and had it been revoked, suspended or lapsed? temporal

Approval acts, participation and objections

The individual acts of approval, participation, voting, dissent and recusal that constitute or evidence the decision.

Participation, quorum and vote result

Who took part and how, whether quorum was met, how votes or consents were counted, and how decisions taken without a meeting are represented.

  1. Was quorum required and met, counted against which denominator, and who determined that? validation
  2. How were votes cast and counted — in favour, against, abstaining, absent — and what majority did the outcome require? measurement
  3. If the decision was taken without a meeting, how was consent collected, when did it become effective, and where is it filed? process
  4. Did any participant attend by remote communication, and does the governing rule count that as presence? constraint
  5. Where approval is multi-step, were the steps sequential or parallel, and was any step skipped, escalated or auto-approved on timeout? process

Dissent, recusal and conflicts of interest

Recorded disagreement with the outcome, withdrawals from participation on interest grounds, and declared conflicts affecting the decision's soundness.

  1. Did any participant dissent or issue a separate opinion, and is that text part of the published record? evidence
  2. Did any eligible participant recuse themselves, on what stated ground, and at what point in the process? process
  3. What conflicts of interest were declared, by whom, and how were they managed? quality
  4. What control detects an undeclared conflict after the decision, and what remedy applies if one is found? exception

Attestation and record integrity

The evidence that fixes the record's content and attributes it to its signatories, and the point at which it becomes unalterable.

Signature, seal, time-stamp and integrity evidence

How the record is signed or sealed, how its content is fixed by digest and third-party time attestation, and how a later verifier can re-establish that it has not changed.

  1. Who signed or sealed the record, in what capacity, and with what kind of signature or seal? provenance
  2. Is there a third-party attested time of existence for the record content, and how does it differ from the asserted signing time? evidence
  3. Which content was hashed, with which algorithm, and does the digest cover the reasons and annexes as well as the operative part? validation
  4. When was verification last performed, by whom, with what verdict, and what is the re-verification interval? validation
  5. At which lifecycle point does the record become unalterable, and what mechanism enforces that? lifecycle
Time, validity and lifecycle The distinct times attaching to a decision, the period during which it is valid, its status transitions and finality, and the ways it is superseded, revoked, challenged or annulled.

Temporal frame

The set of separately recorded times around a decision, and the validity period distinct from any of them.

Decision event timeline

The distinct, separately recorded moments in a decision's life — taken, consented, signed, issued, served, published, in force — plus the observation time at which each was recorded.

  1. Which distinct times exist for this decision, and which one is the authoritative 'decision time' for citation and for computing deadlines? temporal
  2. Are the time the event occurred and the time it was recorded or ingested stored separately, and how far apart are they? provenance
  3. Does every stored time carry an explicit UTC offset or Z, and how is an unknown local offset represented? constraint
  4. For action taken by consent rather than at a sitting, what rule fixes the moment the decision was taken? temporal
  5. When was the decision served on or notified to each addressee, and does that start a challenge period? temporal

Validity window, retroactivity and expiry

The period during which the decision is valid, whether effect reaches backwards in time, and how expiry, renewal and suspension of validity are represented.

  1. From when until when is the decision valid, and is the end open, fixed, conditional or event-driven? temporal
  2. Does the decision take effect from a date earlier than it was taken, and what authorises that retroactivity? temporal
  3. Can validity be suspended without being ended, and what events suspend and restore it? state
  4. Is the decision renewable or subject to periodic review, and does renewal create a new decision or extend this one? lifecycle
  5. How does a consumer ask whether the decision was valid at a specific past instant, and what does the answer depend on? validation

Lifecycle, change and challenge

Status transitions and the point of finality, the mechanisms by which a decision is amended, replaced or undone, and the routes by which it can be challenged.

Status model and finality

The permitted states of a decision record, the transitions between them, and the point at which the decision becomes final and the record unalterable.

  1. What is the complete set of permitted states, and which are terminal? state
  2. Which transitions are permitted, who may trigger each, and what preconditions guard them? lifecycle
  3. When does the decision become final in the substantive sense — no longer open to ordinary challenge — and is that different from the record becoming unalterable? lifecycle
  4. At what point does a draft or proposed decision become a record subject to management, and how are pre-record drafts handled? lifecycle
  5. Which operations remain permitted after finality, and how is each recorded without altering the fixed content? constraint

Supersession, amendment, corrigendum and revocation

How a later act changes or displaces this decision, distinguishing correction of the text from amendment of the substance and from withdrawal of the decision itself.

  1. Which change type applies — corrigendum to the text, amendment to the substance, replacement by a new decision, or revocation without replacement? lifecycle
  2. Which decision replaces this one and which does this one replace, expressed as explicit bidirectional links? relationship
  3. Does the change affect the whole decision or only identified parts, and does the remainder stay in force? composition
  4. Who is competent to revoke or amend this decision, and must it be the same or a higher authority? authority
  5. From when does the change take effect, and does it disturb acts already taken in reliance on the original? temporal

Challenge, appeal, review and annulment

The routes by which the decision can be contested, the time limits and suspensive effects that apply, and how the outcome of a challenge is recorded against the original.

  1. What challenge routes exist — internal review, administrative appeal, judicial review, ombudsman — and which apply to this decision? process
  2. What is the time limit for challenge, from which event does it run, and can it be extended? temporal
  3. Does lodging a challenge suspend the decision's effect, and if not can suspension be requested separately? state
  4. How is the outcome of a challenge recorded — upheld, varied, quashed, remitted — and does it alter, replace or annul the original? lifecycle
  5. Where a decision is annulled, does the annulment operate from the original date or only from the annulment, and what happens to acts done meanwhile? temporal

Adjudicative grade and conclusiveness

In hearings under APA § 557, a presiding employee may issue an initial decision that becomes the agency decision unless appealed or reviewed; otherwise a recommended or tentative decision may be required, except where the agency finds on the record that due and timely execution of its functions imperatively and unavoidably requires omission.

  1. Is this an initial, recommended, tentative or final agency decision, or does that grading not apply? classification
  2. Did the deciding body preside at the reception of the evidence, and if not, who is the presiding or recommending employee? process
  3. Was the recommended or tentative decision omitted because the agency found on the record that due and timely execution of its functions imperatively and unavoidably required it? exception
Relational context The links that place a decision in its wider setting — the matter, occasion and prior decisions that produced it, and the parties and objects it acts upon.

Contextual linkage

Typed relationships from the decision to its procedural context, related decisions, addressees and subject objects.

Relationships to matter, occasion and other decisions

Typed links to the case or matter, the meeting or consent process that produced the decision, and prior, related, implementing and cited decisions.

  1. Which case, matter, project or programme contains this decision, and is containment exclusive? relationship
  2. Was the decision produced at a meeting or by a consent process, and which agenda item or consent round does it correspond to? relationship
  3. Which other decisions does this one implement, rely on, cite, contradict or depend on for its validity? relationship
  4. What happens when a linked decision is revoked, annulled or destroyed under a retention rule — is this decision's validity affected? exception

Addressees, affected parties and subject objects

Who the decision is addressed to, who else it affects, and which concrete objects — assets, applications, permits, budgets, systems — it operates on.

  1. Who are the formal addressees of the decision, and how are they identified authoritatively rather than by name alone? identity
  2. Which parties are affected without being addressees, and do they acquire procedural rights such as being heard or challenging? relationship
  3. Which objects does the decision operate on, and are they identified at a specific version or state? relationship
  4. Does the decision produce legal or similarly significant effects on a natural person, and does that trigger additional safeguards? privacy

Generating activity, used entities and derivation

A decision record is a PROV entity generated by a deciding activity that used submissions, evidence, prior decisions, models or meeting records. Derivation and revision relate a later record to an earlier one without implying that usage alone is sufficient. Bundles support provenance of provenance.

  1. Which activity generated this decision record, and over what interval did that activity run? provenance
  2. Which evidence, submissions, prior decisions, models or other entities were used in making the decision? provenance
  3. From which prior records or drafts is this record derived or revised, and is a PROV bundle available for those assertions? provenance
Automated and assisted decisioning How much of the decision was made by a machine, which system and configuration produced it, and what human oversight, explanation and contestability attach as a result.

Automation, oversight and explanation

Decision mode and system attribution, and the oversight, explanation and contest mechanisms triggered by automation.

Decision mode and system attribution

Whether the decision was human, system-assisted or solely automated, and which system, model, policy version and inputs produced or shaped the result.

  1. Was the decision human-made, system-assisted or based solely on automated processing, and who assessed that classification? classification
  2. Which system, model or rule engine produced or recommended the result, at which version and configuration? provenance
  3. Which policy, rule set or decision logic was applied, and is that exact version retained and retrievable? provenance
  4. What execution logs were generated, what do they contain, and for how long are they kept? evidence
  5. Where a human signed off a system-generated result, was that review substantive enough to displace 'solely automated' status? validation

Human oversight, explanation and contestability

The oversight measures applied to an automated or assisted decision, the explanation owed to the affected person, and the mechanisms for intervention and contest.

  1. What human oversight measures applied, who exercised them, and did the overseer have authority and competence to change the outcome? authority
  2. What explanation of the logic and of the significance and consequences is owed and provided to the affected person? requirement
  3. How can the affected person obtain human intervention, express a point of view and contest the decision, and what are the time limits? process
  4. Were any overrides of the system result recorded, by whom and on what stated ground? event
Disclosure, retention and interoperability How the decision is published or served, who may access which parts under what redactions, how long it is kept and how it is disposed of, and how it is expressed for exchange with external systems.

Disclosure, notification and access

Proactive publication and individual service, access classification, redaction and anonymisation.

Publication, notification and service

How the decision is made known — published to a register or the public, and served on or notified to addressees — and the proof that communication occurred.

  1. Is there a duty to publish, a duty to notify addressees individually, or both, and what instrument imposes each? requirement
  2. Through which channel and register was the decision published or served, and in which language versions? process
  3. What proof exists that each addressee received the decision, and what is the deemed-service rule where receipt is unproven? evidence
  4. What happens if publication or notification fails or is late — does the decision still take effect, and does the challenge clock still run? exception

Access classification, confidentiality and redaction

Who may see which parts of the record, what must be withheld or anonymised, and how a party's right to access their own file is reconciled with confidentiality.

  1. What access classification applies to the record as a whole, and do any parts carry a stricter classification? access
  2. How does an affected party exercise the right to access their own file, and what may legitimately be withheld from them? access
  3. Which content must be redacted or anonymised before disclosure, on what basis, and who performs and approves the redaction? privacy
  4. Are deliberative materials — draft reasoning, internal advice, vote-level detail — withheld while the operative decision is disclosed, and under what rule? exception

Retention, disposition and external alignment

How long the decision record is kept and how it is disposed of or transferred, and how it is projected into external identifier schemes and vocabularies.

Retention trigger, disposition and disposal hold

The event that starts the retention clock for a decision, the authorised disposition outcome, and the holds that suspend disposal.

  1. Which event starts the retention period — creation, issuance, expiry of validity, exhaustion of challenge routes or closure of the containing case? retention
  2. Which disposition authority or schedule governs this record, and what disposition outcome does it prescribe? authority
  3. Is any disposal hold in force, who applied it, on what basis, and when is it reviewed? exception
  4. When disposal or transfer is executed, what evidence of it is retained after the record itself is gone? evidence
  5. Does the decision have enduring evidential, precedential or historical value that requires permanent retention or archival transfer? quality

External alignment, identifiers and exchange projection

How the decision record maps to external identifier schemes and vocabularies for exchange, and which mappings are lossy, conflicting or unsupported.

  1. Which external identifier schemes apply to this decision, and is each one authoritative, an alias or merely advisory? interoperability
  2. Which external vocabularies is the record projected into for exchange, and which internal elements have no target? interoperability
  3. Which mappings are lossy or semantically inexact, and how is that recorded so a consumer is not misled? quality
  4. Is conformance to any external standard claimed, and what evidence supports the claim? validation
  5. Can an exported projection be re-imported without loss of identity, versioning or attestation, and what is lost if not? interoperability

Classifiers Filled

Family
World Models
Category
Information and virtual systems
Entry kind
entity
Navigation path
NAV.INF.REC.DEC
Domain
INF.REC.DEC
Industry
Cross-industry
Tags
decisionapprovalrecordinf.rec.dec

What it is Filled

The model covers the record that constitutes or evidences a discrete decision or approval act and the act's decision-relevant attributes. It treats the decision act and the record of it as distinct but co-modelled: the act supplies authority, outcome, reasons and timing; the record supplies identity, versioned expression, integrity evidence, disclosure and disposition. It spans administrative decisions, judicial judgments, corporate and board resolutions, delegated sign-offs, gate/change approvals and retained machine authorization decisions. It excludes the deliberative occasion, the containing case or procedure, the norms applied, party master data and generic record custody mechanics, which belong to sibling or parent models.

In scope

  • Decision identity, versioned expression identity and classification of decision or approval type
  • Decided question, outcome/disposition, attached conditions, obligations and advice
  • Statement of reasons, alternatives considered and rejected, evidence and findings of fact relied on
  • Decision authority, legal or constitutional basis, delegation, approval limits, quorum and voting
  • Approval participation acts, dissent, abstention, recusal and conflict-of-interest declarations
  • Attestation evidence: signature, seal, trusted time-stamp token, hash and finality of the record
  • Distinct decision-relevant times: taken, consented, issued, served, published, in force, recorded
  • Validity window, retroactivity, conditions of validity, expiry and renewal
  • Status model, finality, supersession, amendment, corrigendum, revocation and annulment
  • Challenge, appeal, review outcome and suspensive effect
  • Automated, assisted and solely automated decision modes with human oversight and contestability
  • Publication, individual notification/service, access classification, redaction and anonymisation
  • Decision-specific retention triggers, disposition and disposal/legal hold
  • Alignment to external decision identifiers and vocabularies (ECLI, Akoma Ntoso, PROV, DCMI, XACML)

Out of scope

  • The deliberative occasion itself — agenda, attendance, minutes as a whole (WM-ACT-025 Meeting)
  • The containing administrative case, application or procedure lifecycle (WM-POL-017)
  • Generic record custody, storage media, format migration and preservation mechanics (parent WM-REC-001)
  • The normative content of the policy, statute, rule or standard being applied (policy/rule sibling model)
  • Master data for persons, organisational units and positions holding decision roles (party/agent sibling model)
  • Authoring and administration of machine access-control policies; only a retained decision result is in scope
  • Contract or agreement terms that a decision may authorise (agreement sibling model)
  • Workflow engine internals, task queues and routing logic that carry an approval request
  • Downstream financial posting, permit issuance or benefit payment produced by a decision

Why it exists Filled

Provide the format-neutral context an agent needs to identify, create, interpret, validate and operate an authoritative record of a decision or approval: what was decided, on what question, by whom under what authority, on what reasons and evidence, with what conditions, from when until when it is valid, and how it is superseded, challenged, disclosed and retained.

Distinguishing features Filled

  • Models the decision act and the record that evidences it together: authority, outcome and reasons beside identity and integrity.
  • Differs from a runtime authorization decision, which is a transient machine result, not an accountable act.
  • Differs from a meeting record, which may contain many decisions, and from case law, which has its own identifiers.
  • Tracks validity over time through supersession, amendment, challenge and disposal holds.

What robots and AI may and may not do Filled

Must not

  • Make, approve or sign a decision on behalf of a person or body.
  • Alter a fixed decision record instead of recording a correction or supersession.
  • Present a draft or proposal as an adopted decision.
  • Omit the reasons or appeal information that the record must carry.
  • Dispose of a record under a hold or open challenge.

Only with a human decision

  • Adopting, signing or sealing a decision.
  • Recording the outcome of an appeal or challenge.
  • Approving disposal of a decision series.

May

  • Register a decision record with authority, outcome, reasons and effective date.
  • Check quorum, majority and delegation limits against recorded rules and report the result.
  • Verify integrity and attestation of an existing record.
  • Produce a redacted disclosable expression for an authorized requester.

Moral aspects Filled

  • People affected by a decision have a right to know its reasons and how to challenge it.
  • Automated or agent-assisted decisions need a clear record of human accountability.
  • Records must not be rewritten to hide who decided and on what basis.

Who is affected

  • People and organizations bound by the decision
  • Decision makers and approvers
  • Auditors, courts and the public

Owners Filled

Steward

The adopting Dimension must name a single accountable record owner for each decision series and a records-management authority empowered to approve disposition; ownership of a decision record must not default to the system that stores it.

Roles

Record owner
Accountable for the completeness, accuracy and timely capture of decision records in an assigned series; Nominates the authoritative identifier and confirms the authority basis version relied upon; Approves creation and pre-fixity updates; Refers competence failures for ratification or escalation
Decision authority / approver
Takes the decision or casts an approval, consent, dissent or abstention within their competence; Declares conflicts of interest and recuses where required; Signs or seals the record in a stated capacity; Confirms that the reasons address the material issues before issuance
Records-management authority
Maintains the disposition authority and approves retention triggers and outcomes for each decision family; Applies, reviews and releases disposal holds; Authorises executed disposal and archival transfer and retains the resulting certificates; Investigates records-integrity exceptions
Access and privacy officer
Sets and reviews access classification at record and part level; Approves redaction and anonymisation and records the ground for each withholding; Handles party access requests and refusals, including refusals of erasure; Oversees explanation and contest obligations for automated decisions
Interoperability steward
Maintains mappings to external identifier schemes and vocabularies with versions and lossiness notes; Records conflicts between external standards rather than resolving them silently; Governs export profiles and blocks conformance claims that lack assessment evidence; Verifies round-trip fidelity of projections
System custodian
Operates the storage and interface projections without acquiring ownership of the records; Preserves the append-only event history and prevents in-place modification after fixity; Retains execution logs for machine-rendered decisions for the declared period; Reproduces the canonical form on demand for verification

Links to other meta-models Filled

extends

  • WM-REC-001 - WM-REC-010 is a specialisation of the generic record. The parent owns record characteristics, custody, format, preservation and baseline metadata; this model adds only decision-specific authority, outcome, reasons, validity and supersession semantics and must not restate parent mechanics.

references

  • WM-ACT-025 - A meeting may produce decision records. The link is optional in both directions because Delaware §141(f) unanimous written consent and delegated sign-offs produce decisions with no meeting at all. Attendance, agenda and full minutes stay in the meeting model; only the occasion reference, agenda item and quorum/vote result attach here.
  • Party / agent master-data model (sibling candidate, model ID not yet registered) - Deciders, approvers, dissenters, addressees and affected parties must resolve to governed party identifiers rather than being named inline, so that authority, delegation and conflicts can be verified against master data.
  • Policy, rule and mandate model (sibling candidate, model ID not yet registered) - The authority basis, the rules applied and the machine policy sets evaluated are cited at a specific in-force version. Their normative content belongs to the policy model; this model records only which version was relied upon and to what effect.
  • Retention schedule and disposition authority model (sibling candidate, model ID not yet registered) - Retention periods, disposition outcomes and appraisal criteria are jurisdiction-specific and change independently of decisions. This model references a schedule item and records the resolved trigger, never embedding a period.

composes

  • WM-POL-017 - An administrative case ends or changes state through decisions. The case model owns the procedure and its state; this model owns each decision within it. One case may compose many decisions of different procedural stages, and one decision may close or alter several cases.
  • Electronic signature, seal and time-stamp evidence model (sibling candidate, model ID not yet registered) - Attestation evidence is mixed in rather than owned: this model holds references, coverage statements and verification verdicts, while the cryptographic object model, trust anchors and long-term validation material live in the evidence model.

aligned

  • W3C PROV-O (http://www.w3.org/ns/prov#) - Alignment only. The decision act maps to prov:Activity, deciders and systems to prov:Agent, the record to prov:Entity, roles to a qualified prov:Association with prov:hadRole, delegation to prov:actedOnBehalfOf, supersession to prov:wasDerivedFrom and cessation of effect to prov:wasInvalidatedBy. PROV has no native concept of competence, quorum or validity window, so the alignment is partial.
  • OASIS XACML 3.0 Result vocabulary - Alignment only, for retained machine authorization decisions: Decision, Status, Obligations, AssociatedAdvice and PolicyIdentifierList map onto outcome, status detail, obligations, advisory items and applied policy identifiers. Permit/Deny must not be equated with a reasoned grant or refusal, and NotApplicable has no administrative equivalent.
  • ECLI (European Case Law Identifier) and OASIS Akoma Ntoso v1.0 - Alignment for judicial and legislative decisions: ECLI supplies a governed global identifier for the decision as a work; Akoma Ntoso supplies the Work/Expression/Manifestation/Item identity levels and the judgment structure. Neither is imposed on administrative or corporate decisions.
  • DCMI Metadata Terms (http://purl.org/dc/terms/) - Alignment for the temporal and supersession vocabulary: valid, issued, created, modified, dateAccepted, replaces, isReplacedBy, provenance, accessRights and conformsTo. Adopted because these terms keep validity, issuance and modification separate, which a single decision date collapses.
  • ISO/IEC/IEEE 42010:2022 architecture decision and rationale - Alignment for design-governance decisions, where a decision pertains to concerns, affects description elements and carries rationale covering alternatives not chosen. Used to justify the options-considered and reasons findings as a general pattern, not to import architecture description structure.

neighbor

  • WM-ACT-025 Meeting - A meeting is an occasion; a decision record is an outcome assertion. The relationship is optional in both directions: Delaware General Corporation Law §141(f) permits board action without any meeting by unanimous written or electronic consent, and delegated single-signature approvals never involve a meeting. Meeting attendance and agenda stay in the meeting model; only the linkage, the agenda item decided and the quorum/vote result attach to the decision record.
  • WM-POL-017 Administrative case - A case is the procedural container and may hold many decisions — procedural, interim, partial and final. Case state transitions are driven by decisions but are not decisions. Ex parte communications belong to the case record and are referenced by the decision record only where a rule requires them to be placed on the record of decision.
  • WM-REC-001 Record (parent) - The parent supplies generic record properties: authenticity, reliability, integrity and usability as record characteristics, custody, format and preservation. WM-REC-010 adds only what is decision-specific — authority, outcome, reasons, validity and supersession — and must not restate parent mechanics.
  • Runtime authorization decision (XACML PDP result) - A PDP result has the same logical shape (decision value, status, obligations, advice, applicable policy identifiers) but is normally ephemeral and produced at log scale. The boundary is retention as a record: a PDP result becomes an instance of this model only when it is captured and managed as a record. XACML decision values are an alignment vocabulary, not the canonical outcome set.
  • Judicial judgment / case law item - A judgment is a specialised decision record with a governed global identifier (ECLI) and a document structure of introduction, background, motivation and decision. That structure is judicial and must not be imposed on administrative or corporate decisions; court organisation, procedure and case-law citation networks are out of scope.
  • Electronic signature, seal and time-stamp evidence - Attestation evidence is referenced, not owned. The decision record holds pointers to signature/seal objects and time-stamp tokens plus a verification verdict and verification time; the cryptographic object model, trust lists and long-term validation data belong to a signature-evidence sibling model.
  • Approval as an independent object - Boundary under review. In this model an approval is either an outcome value of a decision or a participation act within one, because the cited sources give approvals no independent identity. Standing authorisations such as licences and permits do have independent validity and holders, and may justify a separate sibling model; flagged rather than assumed.
  • Architecture decision record (ADR) practice - ISO/IEC/IEEE 42010:2022 treats an architecture decision as pertaining to concerns and affecting architecture description elements, with rationale covering alternatives not chosen. That is a design-governance specialisation of the same shape; the architecture description, viewpoints and models it affects are out of scope here.

parent

  • WM-REC-001

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Authoritative master-system identifier issued by the system of record for the decision series, such as a case-management decision number or a resolution number from the governing body's own register.
  • Governed global identifier or IRI issued under an external scheme the Dimension participates in, such as an ECLI for a judicial decision or a work-level IRI under a legal-document naming convention.
  • UUID or ULID minted by the adopting Dimension, used only where neither of the above exists, and recorded together with the reason the higher-priority options were unavailable.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A decision record names an authority, an act, an outcome, reasons, a date and an integrity seal or signature.
  • Often confused with minutes, a policy-engine permit result and an architecture decision record.

Capabilities and actions required Filled

  • Register decision record: Create a decision record and bind it to a canonical identifier following the identity priority, capturing both the event time and the ingestion time.
  • Record approval or consent act: Attach an individual approval, consent, vote, abstention or recusal to a decision record, preserving actor, capacity and time.
  • Evaluate quorum and required majority: Determine whether the applicable quorum was satisfied and whether the recorded acts meet the required majority, including the no-meeting consent path.
  • Verify competence and delegation limits: Check that the decider held competence at the decision time and that the decision falls within any delegated thresholds and outside reserved matters.
  • Attest, seal and fix the record: Apply signature or seal, compute a content digest over a declared canonical form, obtain a third-party attested time and mark the record unalterable.
  • Verify integrity and attestation: Recompute the digest over the declared canonical form and validate signature, seal and time-stamp evidence, returning a dated verdict.
  • Issue, publish and serve: Formally issue the decision, publish it where a duty exists and serve it on addressees, capturing proof of service and starting any challenge period.
  • Evaluate validity at an instant: Answer whether the decision was valid, suspended, expired, revoked or annulled at a specified instant, returning the evidence used.
  • Supersede, amend or correct: Link a later act to this decision as a corrigendum, amendment, replacement or revocation and create the resulting expression without altering fixed content.
  • Record challenge outcome: Register a lodged challenge and its disposal against the original decision, applying the outcome's effect on validity and finality.
  • Produce disclosable expression: Generate a redacted or anonymised expression of the decision for publication or third-party access, recording the basis for every withholding.
  • Apply disposition or disposal hold: Resolve the retention trigger, compute the earliest disposal date, apply or release holds, and execute the authorised disposition outcome.
  • Export exchange projection: Serialise the decision record into a named external vocabulary at a stated version, declaring unmapped elements and lossy mappings.
  • Classify decision mode and oversight adequacy: Determine whether a decision was human, assisted or solely automated, and whether recorded human review was substantive enough to change that classification.
  • Stay or invalidate effect: Stay, vacate or invalidate the effect of a decision without treating that act as deletion of the evidence record.

Hazards and failure modes required Filled

  • Acting on a superseded or challenged decision.
  • Decisions taken beyond delegated authority being treated as valid.
  • Disclosure of personal data contained in reasons.

Standards and interfaces required Filled

  • ISO 15489-1 records management.
  • W3C PROV-O.
  • RFC 3339 timestamps.
  • Regulation (EU) No 910/2014 (eIDAS) for electronic signatures and seals.
  • Akoma Ntoso (OASIS LegalDocML) for legal and parliamentary documents.

Context of use required Filled

  • ECLI applies to participating European jurisdictions and does not exist elsewhere; the identity priority degrades to master-system identifier then Dimension-minted identifier outside its scope.
  • Charter of Fundamental Rights Article 41 binds Union institutions, bodies, offices and agencies. Member State authorities' duty to give reasons arises from national law and general principles, not directly from Article 41, so the duty must be cited per jurisdiction.
  • 5 U.S.C. §557 governs formal adjudication by United States federal agencies only. Its findings-and-reasons requirement is not a general rule of administrative law and is not assumed elsewhere.
  • Delaware General Corporation Law §141 is the law of one United States state. Quorum floors, committee limits, remote-presence rules and the sixty-day consent window vary by jurisdiction and by corporate form and are cited as a verified counterexample source rather than as a default.
  • NARA's Universal ERM Requirements apply to United States federal agencies. They are used as a lifecycle requirement pattern, not as a retention schedule for any other jurisdiction.
  • MoReq2010 originates in a European context and its development was discontinued after 2018; it is treated as a stable reference rather than a current obligation.
  • Qualified electronic signature and seal frameworks are assumed to be jurisdiction-specific. Because the eIDAS text was not retrievable, the model deliberately asserts no assurance-tier vocabulary and relies on RFC 3161 for the time-attestation semantics only.
  • Non-Western and customary decision-making traditions, and consensus-based or non-adversarial procedures, were not researched; the model's quorum-and-majority orientation may be a poor fit for them.
  • Adjudicative grades, ex parte docketing and emergency omission of recommended decisions are taken from US APA § 557 and do not automatically apply outside US formal adjudication.
  • Public-records disclosure overlays (FOIA and analogues) are jurisdiction-specific; DCMI accessRights is the generic hook.
  • ADR/MADR status vocabularies originate in software-engineering practice and are not legal status codes.
  • ISO 15489/23081 are international but implementation instruments (retention schedules, classification schemes) are always local.
  • Retroactive (nunc pro tunc) effect is treated as an exception requiring local authority, not as a default.

Sources Filled

  1. PROV-O: The PROV Ontology - World Wide Web Consortium (W3C)
  2. ISO 15489-1:2016 Information and documentation — Records management — Part 1: Concepts and principles - International Organization for Standardization (ISO)
  3. eXtensible Access Control Markup Language (XACML) Version 3.0 - OASIS
  4. 5 U.S.C. § 557 — Initial decisions; conclusiveness; review by agency; submissions by parties; contents of decisions; record - United States Government Publishing Office (govinfo)
  5. RFC 3339 — Date and Time on the Internet: Timestamps - Internet Engineering Task Force (IETF)
  6. European Case Law Identifier (ECLI) - European Union — European e-Justice Portal
  7. Article 41 — Right to good administration, Charter of Fundamental Rights of the European Union - European Union Agency for Fundamental Rights (FRA)
  8. DCMI Metadata Terms - Dublin Core Metadata Initiative (DCMI)
  9. Akoma Ntoso Version 1.0. Part 1: XML Vocabulary - OASIS
  10. Delaware General Corporation Law, Title 8, Chapter 1, Subchapter IV — Directors and Officers (§ 141) - State of Delaware
  11. Universal Electronic Records Management (ERM) Requirements - U.S. National Archives and Records Administration (NARA)
  12. RFC 3161 — Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) - Internet Engineering Task Force (IETF)
  13. AI Act — Regulatory framework for artificial intelligence - European Commission (Directorate-General for Communications Networks, Content and Technology)
  14. Guidelines on Automated individual decision-making and Profiling for the purposes of Regulation 2016/679 (wp251rev.01) - Article 29 Data Protection Working Party (endorsed by the European Data Protection Board)
  15. Art. 22 GDPR — Automated individual decision-making, including profiling - gdpr-info.eu (unofficial consolidated reproduction of Regulation (EU) 2016/679)
  16. ISO/IEC/IEEE 42010:2022 Software, systems and enterprise — Architecture description - ISO / IEC / IEEE
  17. MoReq2010: Modular Requirements for Records Systems — Volume 1: Core Services & Plug-in Modules - DLM Forum Foundation
  18. ISO 23081 Metadata for records (ISO 23081-1:2017 principles; ISO 23081-2:2021 conceptual and implementation issues) - ISO/TC 46/SC 11 Archives/records management
  19. PROV-DM: The PROV Data Model - World Wide Web Consortium
  20. Decision Model and Notation (DMN) Specification Version 1.5 - Object Management Group
  21. 5 U.S.C. § 557 Initial decisions; conclusiveness; review by agency; submissions by parties; contents of decisions; record - U.S. National Archives and Records Administration (Office of the Federal Register)
  22. Markdown Architectural Decision Records (MADR) - MADR project (adr.github.io)
  23. Documenting Architecture Decisions - Cognitect (Michael Nygard)
  24. ISO 15489 (DCC Standards Watch briefing) - Digital Curation Centre

Open questions

  • Standing authorisations (licences, permits, accreditations) with independent holders, renewal cycles and their own validity: determine whether these require a sibling model or can remain outcome values of this one. This is the base's own flagged open boundary and the single largest structural risk in the model.
  • Voting and consent mechanics beyond quorum-and-simple-majority: weighted voting, qualified majority with population thresholds, consensus and objection-based procedures, ranked and multi-round ballots, and proxy or alternate voting are representable but not individually modelled by either provider.
  • Security dimension: key management, trust-anchor governance, cryptographic agility, long-term validation material for archival attestation, and access-event auditing (reads, exports, failed attempts). The base marks security as a gap and Grok's single access-audit question has no primary requirement source.
  • Multilingual authentic-text divergence: no rule exists in either pack for resolving substantive conflict between equally authentic language versions; expression identity alone does not settle which text governs.
  • Non-Western, customary and consensus-based decision traditions, and non-adversarial procedures, were researched by neither provider. The model's quorum-and-majority orientation may be a poor fit and should be tested before the coverage claim is widened.
  • Question-level enrichment carried forward from rejected Grok nodes: the §557(d) designation of when ex parte prohibitions begin (under f10 or f14), and the oral-then-memorialised capture-completeness exception (under f18 q18-draft-boundary).
  • The full normative texts of ISO 15489-1:2016, ISO/IEC/IEEE 42010:2022 and the ISO 23081 metadata series were not inspected; iso.org returned HTTP 403 to automated retrieval. Claims attributed to them are at catalogue, abstract and secondary-summary level and should be re-verified against purchased copies before any conformance statement.
  • EUR-Lex could not be retrieved during this research. The eIDAS Regulation (EU) No 910/2014 was therefore not consulted at all, and the GDPR and the AI Act were consulted through an unofficial reproduction and an official Commission overview page rather than the Official Journal text. No electronic-signature assurance tier, seal semantics or article-level AI Act obligation is asserted on that basis.
  • Sector-specific approval regimes — medicines and device authorisation, building and environmental permits, credit and underwriting decisions, research-ethics approvals, export licensing, clinical treatment decisions — are covered only by the generic structure. Each is likely to add mandatory elements this model does not name.
  • Voting mechanics are modelled generically. Weighted voting, qualified majority with population thresholds, consensus and objection-based procedures, ranked and multi-round ballots, and proxy or alternate voting are not individually represented.
  • Multilingual authentic-text divergence is handled only through expression identity; no rule is given for resolving substantive conflict between equally authentic language versions.
  • Long-term preservation of validation data for attestation evidence — archival time-stamps, revocation information, cryptographic agility over decades — is referenced but not modelled.
  • Group, class-action and collective decisions with many co-equal deciders across organisations are representable but were not stress-tested against a real instrument.
  • No retention period, challenge deadline or quorum threshold is asserted as a value anywhere in the model; all are referenced to instruments that the adopting Dimension must supply.
  • eIDAS/ETSI qualified electronic signatures and trust-service evidence profiles were not fetched and are not specified.
  • GDPR Article 22 and other automated individual-decision rights regimes were not fetched; software-agent deciders are modelled only via PROV Agent.
  • Corporate board-resolution statutes, company-law filing numbers and notarisation practices are not in the source set.
  • Maker-checker or SOX/COSO dual-control is asked as a local policy question, not as a normative requirement.
  • Akoma Ntoso, LegalDocML and judicial-opinion structure are excluded; court orders may still instantiate this record.
  • ISO 9001 documented-information controls and ISO 30300 vocabulary were not fetched as primary texts.
  • ISO 15489-1:2016 full clause text is paywalled; characteristics are taken from ISO 23081 TC46/SC11 and the official 2016 abstract, with DCC 2007 as secondary and version-lagged.
  • Clinical, safety-case and financial-trade approval specialisations are not modelled.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-rec-010-decision-approval-record/spec.yaml, ver-cy/world-models/card-supplements/wm-rec-010-decision-approval-record.json