Decision / Approval Activity
Provide the context an agent needs to understand, create, inspect and operate a single decision or approval activity occurrence: the authority under which it was taken, the inputs and criteria actually used, the choice among admissible options, and the outcome with its conditions, validity window and contestation path.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 25 findings · 100 questions
Decision framing and identity What this decision occurrence is, what question it answers, what it concerns and what kind of decision it is.
Identity and subject
Identification of the occurrence and the question and subject matter it addresses.
Decision occurrence identity
How one decision or approval occurrence is identified and kept distinct from its subject, its notice and the rule set applied.
- Which system of record issues the authoritative identifier for this decision occurrence, and what is that identifier? identity
- If no master-system reference exists, which governed IRI or Dimension-minted UUID/ULID identifies it, and who mints it? identity
- How is this identifier kept distinct from the identifiers of the subject, the decision notice and the applied rule set? relationship
- Under which later events (correction, re-vote, appeal outcome) does the identifier stay stable rather than being reissued? constraint
Question, subject and granularity
The exact question decided, the subject matter it reaches, the admissible answers and what counts as one occurrence rather than a chain.
- What exact question does this decision answer, and whose formulation of it is authoritative? definition
- Which subject entities, requests or assets does the decision reach, and by which references? relationship
- Which answers were admissible before the choice was made? constraint
- Is one occurrence a single approval step, a whole approval chain, or one item within a multi-item session? composition
Typing and modality
Classification of the decision and whether it was reached by human, automated or hybrid means.
Decision type, modality and materiality
The governed decision-type code, whether the outcome was produced solely by automated processing, and the materiality and reversibility of the decision.
- Which decision-type code, from which governed code list and version, classifies this occurrence? classification
- Was the outcome produced solely by automated processing, by a human, or by a human acting on an automated recommendation? decision
- Which materiality or impact tier applies, and which scale sets that tier? measurement
- Is the decision reversible in practice, and what makes it irreversible once acted upon? quality
Authority, mandate and participation The power under which the decision was taken, its limits and delegation, and who took part with what independence.
Authority basis and limits
The instrument conferring the power to decide, its delegation chain and its competence limits.
Authority basis, mandate and delegation
The instrument that confers the power to take this decision, the position that holds it, and any delegation or substitution under which someone acted on behalf of the holder.
- Which instrument confers the power to take this decision, and what is its citation, version and effective date? authority
- Which position or role, rather than which individual, holds the decision right under that instrument? ownership
- Which agent acted on behalf of which responsible agent, under what delegation instrument and validity period? provenance
- Which act is reserved to the holder and cannot be delegated to a designated representative? constraint
Competence limits and escalation
The quantitative and categorical bounds on the authority applied, the escalation path when they are exceeded, and any emergency authority.
- Which value, risk-class, subject-matter or jurisdictional limits bound the authority applied? constraint
- What is the escalation path when a request exceeds the holder's limit? process
- Under what emergency conditions may a limit be exceeded, and what after-the-fact ratification is required? exception
- How is the limit check evidenced at decision time rather than asserted afterwards? evidence
Participation and decision integrity
Who took part in which role, and the independence and multi-party conditions that make the decision validly constituted.
Participant roles and responsibility
The agents who took part, the role each held with respect to the activity, and who remains accountable for the outcome.
- Which agents participated, in which roles, and with what share of responsibility for the outcome? relationship
- How is the design-time decision owner or decision maker in the rule model distinguished from the agent who actually decided this occurrence? classification
- Who is accountable for the decision after it is taken, if that differs from who signed it? ownership
- Which participants' acts were required for completion and which were advisory only? requirement
Separation of duties and conflict control
The incompatibility rules, dual-authorization requirements and recusal or conflict declarations that protect the integrity of the decision.
- Which separation-of-duties rule applies, and which role pairs are incompatible for this decision type? constraint
- Is dual authorization or two-person control required, and on which criterion is that requirement triggered? requirement
- How are declared conflicts of interest, recusals and abstentions recorded, and what effect do they have on validity? exception
- How is a self-approval or maker-equals-checker violation detected and recorded? validation
Collective decision rules (declared evidence gap)
Quorum, voting method, thresholds and treatment of abstentions and proxies for decisions taken by a body rather than an individual; no consulted primary standard defines these normatively, so this finding is marked as a gap and must not be treated as canonical.
- What quorum and majority threshold made this decision validly constituted? requirement
- Which voting method was used, and how were abstentions, proxies and absentees counted? process
- What were the counted results for, against and abstaining? measurement
- How were decisions taken by written procedure or by chair's action subsequently ratified? exception
Inputs, criteria and reasoning What the decision used, which criteria applied, which options existed and why the chosen one was chosen.
Inputs and applied criteria
The fixed evidence set actually used and the pinned criteria or rule set applied to it.
Input and evidence set
The inputs actually used, fixed by version, digest or as-of time, together with what was missing or uncertain.
- Which inputs, documents and datasets were actually used, at which version or as-of time? evidence
- Where did each input come from and who attested to its accuracy? provenance
- What was missing, stale or uncertain at decision time, and how was that gap treated? quality
- How is the package fixed so that later changes at the source do not silently alter what was decided upon? validation
Applied criteria and rule-set reference
Which rule set, policy or decision model was applied at which pinned version, and any recorded departure from it.
- Which rule set, policy or decision model was applied, at which pinned version? interoperability
- Who owns that rule set, and is this decision permitted to depart from it? authority
- If the decision departed from the criteria, what deviation reason and additional approval were recorded? exception
- Where more than one rule matched, which resolution or hit policy determined the result? constraint
Options, rationale and deliberation
The admissible option space, the reasons connecting inputs to the chosen option, and the record of deliberation and dissent.
Option set and rejected alternatives
The options on the table at the moment of choice, which was taken and why the others were not.
- Which options were on the table when the choice was made? composition
- Which option was chosen and what stated reason rejected each of the others? decision
- Was the null option of deferring or taking no action admissible, and was it considered? constraint
- How is an option added late in the process distinguished from one available from the outset? temporal
Rationale and owed explanation
The reasoning connecting inputs and criteria to the chosen option, and the explanation owed to affected parties where the decision significantly affects them.
- What reasoning connects the inputs and applied criteria to the chosen option? evidence
- Which explanation is owed to the affected party, in what form and within what period? privacy
- How complete must the rationale be for the decision to be effectively contestable? quality
- Where automated components contributed, what is recorded about their role, logic and limits? interoperability
Deliberation events and dissent
The sessions in which the matter was considered, attendance, and any recorded dissenting or minority position.
- Which deliberation events took place, when, and who attended each? event
- Which dissenting or minority positions were recorded, and by whom? state
- Which parts of the deliberation are confidential and which are disclosable? access
- Who certified the minutes and when were they approved? provenance
Outcome, conditions and hand-over The choice made, the terms attached to it, its validity window, and how it is communicated and handed to whatever executes it.
Outcome and attached terms
The outcome value from a governed vocabulary and the conditions, obligations and validity attached to it.
Outcome value and disposition
The recorded outcome from a governed vocabulary, its mapping to external decision values, and the instants at which it was decided and recorded.
- What is the outcome value, from which governed outcome vocabulary and version? decision
- How does the outcome map to the referenced authorization model's decision values, and where does that mapping lose meaning? interoperability
- How are 'no applicable authority' and 'could not decide' distinguished from an explicit refusal? classification
- At what instant did the decision take effect, and how does that differ from when it was recorded? temporal
Conditions, obligations and validity window
Binding terms and limitations attached to the outcome, obligations placed on the recipient, and the period and triggers governing validity.
- Which conditions, limitations and restrictions attach to the outcome, and which of them are binding rather than advisory? constraint
- Which obligations must the recipient discharge, by when, and what follows if they are not discharged? requirement
- From when until when is the decision valid, and is validity time-driven, event-driven or open-ended? temporal
- Which events trigger mandatory review or automatic lapse of the decision? event
Communication and execution hand-over
How the outcome reaches its addressees and how it is handed to whatever must act on it, without this model taking on execution.
Notification, acknowledgement and execution hand-over
Communication of the outcome to addressees with evidence of acknowledgement, and the hand-over of the decision to the systems that act on it while enforcement stays outside this model.
- To whom must the outcome be communicated, in what form, and within what period? process
- How are receipt of the notice and acceptance of its terms evidenced, and what happens if acknowledgement fails? evidence
- Which downstream system consumes this decision, and what exactly is in the hand-over payload? interoperability
- Which model owns enforcement of the outcome, and how is drift between the decided outcome and the enforced state detected? authority
Lifecycle, oversight and contestation How the decision changes state over time, how automated decisions are overseen, and how the decision can be challenged, overridden or undone.
Decision state and change
Permitted states of a decision occurrence and the ways it is superseded, revoked, suspended or renewed.
Decision status lifecycle
The permitted states of the decision occurrence, the legal transitions between them and who may cause each.
- What are the permitted states of the decision occurrence and which transitions between them are legal? lifecycle
- Which state means decided but not yet effective, and which means effective but suspended? state
- Who may cause each transition, and may that differ from who took the original decision? authority
- How is each transition timestamped, and by whose clock and offset? temporal
Supersession, revocation and reauthorization
How a decision is replaced, revoked or suspended, what becomes of the rights and obligations it created, and what forces a fresh decision instead of an amendment.
- Which decision supersedes or revokes which, and from what effective instant? lifecycle
- What happens to obligations and rights created by the superseded or revoked decision? relationship
- Which elapsed periods or events force reauthorization rather than amendment? event
- Is retroactive revocation permitted here, and what evidence must support it? exception
Oversight and contestation
Human oversight of automated decisions and the paths by which a decision is challenged, reviewed or overridden.
Human oversight of automated decisions
Assignment and exercise of oversight where the outcome is produced or materially shaped by automation, including disregard, override and reversal.
- Who is assigned oversight of this automated or assisted decision, and with what competence and means to intervene? authority
- Was the automated output disregarded, overridden or reversed, and on what basis? exception
- On what legal or policy basis is a solely automated decision permitted for this decision type? requirement
- What evidence shows the human intervention was substantive rather than a formality? evidence
Contestation, appeal and ratification
Who may challenge the decision, how the review is conducted and how emergency overrides or after-the-fact ratifications are recorded.
- Who may contest this decision, on what grounds, and within what period? access
- How does the review outcome relate to the original decision: confirm, amend, replace or remit? lifecycle
- Which body reviews the decision, and must it be independent of the original decider? ownership
- How are emergency overrides and after-the-fact ratifications of this decision recorded? exception
Attribution, record and interoperability How the decision is attributed and attested, how its record is kept and disclosed, and how it maps to external vocabularies.
Attribution and attestation
Who is recorded as responsible, under what plan, and how the decision is signed.
Attribution, plan and activity timing
The qualified association between the decision activity and its responsible agents, the procedure followed, and the separation of activity time from recording time.
- Which agent was associated with the decision activity, in which role, and following which plan or procedure version? provenance
- What are the start and end times of the decision activity, and how are they distinguished from recording or ingestion time? temporal
- Which prior activities informed this decision and which entities did it generate? relationship
- How is a provenance assertion made by the deciding system distinguished from one asserted by a third party? quality
Signature and its declared meaning
Signatures applied to the decision, the meaning each carries, and their inseparable binding to the signed record; verification itself is external.
- What meaning is attached to each signature: review, approval, responsibility or authorship? evidence
- Which signer identity is bound to the signature, and how was that identity authenticated? identity
- How is the signature bound to the record so it cannot be excised, copied or transferred to another record? security
- Which model verifies the signature, and where is the verification result referenced from here? validation
Record, access and alignment
The durable record and its disposition boundary, who may see what, and how the context maps to external standards.
Decision record and disposition boundary
The durable record produced by the decision, the retention class asserted for it, and the explicit statement that disposition is executed elsewhere.
- Which retention class and schedule apply to the decision record and, separately, to its deliberation content? retention
- Which model or policy executes disposition, and what does this model keep as a tombstone afterwards? authority
- What blocks destruction while the decision still confers rights or imposes obligations? constraint
- How are erasure requests for personal data reconciled with the obligation to keep the decision record? privacy
Access, confidentiality and mandatory disclosure
Who may read the outcome, the rationale and the deliberation, what personal data are involved, and which disclosures override the default restriction.
- Which parties may read the outcome, the rationale and the deliberation, and on what basis each? access
- Which personal data appear in the decision context, and under what lawful basis are they held? privacy
- What confidentiality marking applies to each part, and who may downgrade it? security
- Which mandatory disclosures to a data subject, auditor, supervisory authority or court override the default restriction? exception
External alignment and crosswalk
Mappings from this decision context to external decision, provenance, authorization, policy and archival vocabularies, with recorded conflicts and no conformance claim.
- Which external vocabularies is this decision context mapped to, and at which versions? interoperability
- Where does the mapping to authorization decision values lose or distort meaning? classification
- What evidence would be required before claiming conformance to any of these standards? validation
- Who maintains each mapping and when was it last checked against the source version? provenance
Classifiers Filled
- Family
- World Models
- Category
- Activities and processes
- Entry kind
- event
- Navigation path
- NAV.ACT.DEC
- Domain
- ACT.DEC
- Industry
- Cross-industry
- Tags
- decisionapprovalactivityact.dec
What it is Filled
Scope is one bounded decision or approval occurrence, in the PROV sense of an activity that occurred over a period and bears assigned responsibility. The model records that a decision was taken, by whom, on what authority, from what inputs, with what result and under what conditions. It does not evaluate policy, enforce outcomes, author rule logic, keep audit trails or execute disposition; those remain with referenced models. Storage and interface (JSON, YAML, Markdown, Git, MCP, MongoDB) are projections of this semantics, not part of it.
In scope
- Identification of a single decision or approval occurrence and the question it answers
- Authority basis, mandate, delegation chain and competence limits under which the decision was taken
- Participants and their roles, independence requirements and multi-party approval facts
- The input and evidence set actually used, fixed by version, digest or as-of time
- The admissible option set, the chosen option and the rejected alternatives with reasons
- Rationale, dissent and the explanation owed to affected parties
- Outcome value, attached conditions and obligations, effective instant and validity window
- Decision status lifecycle, supersession, revocation, suspension and reauthorization triggers
- Human oversight of automated or assisted decisions, contestation, appeal and override records
- Reference bindings and crosswalks to external decision, provenance and authorization vocabularies
Out of scope
- Runtime policy evaluation, rule combining algorithms, obligation discharge and access enforcement
- Audit-trail record structure, storage, immutability guarantees and log retention execution
- Authoring, versioning and testing of decision logic, rule sets, decision tables and hit policies
- The subject entity's own attributes and lifecycle (application, change, budget, dossier, system)
- Workflow orchestration, routing, queueing and task assignment engines
- Party and agent master data, organisational structure and position registries
- Retention schedule definition and disposition or destruction execution
- Cryptographic signature creation, certificate handling and signature validation
- Risk assessment methodology, scoring scales and control assessment procedures
- Notification transport, messaging infrastructure and publication channels
- Constitutive organisational rules (board composition, standing orders) as normative content
Why it exists Filled
Provide the context an agent needs to understand, create, inspect and operate a single decision or approval activity occurrence: the authority under which it was taken, the inputs and criteria actually used, the choice among admissible options, and the outcome with its conditions, validity window and contestation path.
Distinguishing features Filled
- Records who decided what, on which inputs, under which authority, and when; the decision logic itself lives in a rule model such as DMN.
- It differs from automated authorization evaluation, which answers access questions at runtime.
- It captures what actually happened, including recusals, dissent and emergency exceptions, not what the procedure prescribed.
- A decision that significantly affects a person is incomplete until a rationale and a route to contest it are recorded.
What robots and AI may and may not do Filled
Must not
- Record a decision as made by a human when an agent made it.
- Bypass separation of duties or dual authorization.
- Make a decision with significant effect on a person without human review where law or policy requires it.
- Close a decision without the rationale needed for contestation.
- Edit a recorded outcome instead of recording a superseding decision.
Only with a human decision
- Making or approving a decision with significant effect on people.
- Overriding, suspending or revoking a decision.
- Approving an emergency exception to normal procedure.
May
- Assemble and check the input package for a decision.
- Record deliberation, votes and the declared outcome as observed.
- Issue decision notices and record acknowledgements.
- Check that authority, participants and rationale are complete before closing.
Moral aspects Filled
- People affected by decisions have a right to know the reasons and to contest them.
- Automated or agent-assisted decisions can embed bias; their part in the decision must be visible.
- Unclear authority lets responsibility be shifted onto no one.
Who is affected
- Subjects of the decision
- Decision makers and approvers
- Auditors, reviewers and courts
Owners Filled
Steward
The adopting Dimension must designate an accountable owner for the decision-context package who is organisationally distinct from the approvers whose decisions the package records.
Roles
- Decision-context owner
- Maintain the model package, its code lists, vocabularies and referenced-model bindings; Approve breaking changes and publish migration notes; Ensure organisational separation from the approvers whose decisions are recorded
- Deciding authority
- Take the decision within the bounds of the conferring instrument and its limits; Accept the risk and attach terms, conditions and validity to the outcome; Trigger reauthorization, revocation or suspension when conditions change
- Decision recorder or secretariat
- Capture sessions, attendance, tallies, dissent and declarations at the time of the act; Issue serial-numbered notices and minutes and maintain the register sequence; Fix the input package and record its digest and as-of times
- Assurance and review role
- Run completeness validation against the bound profile and report gaps; Check separation-of-duties, dual-authorization and recusal facts; Verify that alignment mappings were checked against current target versions
- Records and privacy liaison
- Assert retention classes and holds and coordinate disposition with the records model; Handle erasure and access requests and record the redaction applied; Coordinate mandatory disclosures to data subjects, auditors and supervisory authorities
Links to other meta-models Filled
child
- WM-ACT-002 (parent activity model) - Inherit generic activity identity, temporal bounds, participation and status machinery; this model adds only the decision-specific authority, option set, choice and outcome surface and does not restate the generic activity attributes.
references
- Party / agent model of the adopting Dimension (person, organisation, position, software agent) - Resolve every participant, authority holder, signer and recipient by reference; party master data, organisational structure and position registries stay in the target model.
- Authorization policy evaluation model (XACML-style PDP and PEP) - Carry the decision-request and response reference plus the subject-specific binding parameters; policy evaluation, combining algorithms, obligation discharge and enforcement remain owned by the target.
- Rule / decision-logic model (DMN decision requirement graph and decision tables) - Pin the applied rule-set version and record deviations from it; authoring, versioning, testing and execution of decision logic remain owned by the target.
- Records management, retention and disposition model - Bind the decision record reference and asserted retention class; appraisal, schedule definition and destruction execution are owned by the target.
- Audit trail / immutable event log model - Name the events this model requires to be logged and where the log lives; audit-record structure, immutability, storage and log retention are owned by the target and are never asserted here.
- Electronic signature and seal model - Reference signature objects and their verification results while keeping the declared meaning-of-signature binding local; cryptography, credentials and validation are owned by the target.
- Process and case model (BPMN process, task and case routing) - Reference the containing process, task or case instance; orchestration, routing, queueing and assignment are owned by the target.
- Risk assessment and determination model - Reference the risk determination that fed the decision; assessment methodology, scoring and control assessment are owned by the target.
composes
- Vote / ballot record model - Compose per-ballot records into a collective decision occurrence where a body decides; ballot mechanics, secrecy and counting procedures belong to the composed model.
aligned
- OMG Decision Model and Notation 1.5 - Crosswalk the question, admissible answers, input data, authority requirement and decision-owner concepts; alignment only, with no conformance claim and no import of DMN execution semantics.
- W3C PROV-O (Activity, Association, Delegation, Plan) - Crosswalk attribution, roles, plans, delegation and activity timing to PROV terms for provenance interchange.
- OASIS XACML 3.0 decision values, obligations and advice - Crosswalk outcome values and the binding versus advisory distinction, with explicit recording of cases that do not map, such as conditional approval and deferral.
- W3C ODRL Information Model 2.2 - Crosswalk the conditions, duties and constraints attached to an approval outcome to ODRL rule structures without importing policy evaluation.
- ICA Records in Contexts Ontology 1.1 (Mandate, AuthorityRelation, Activity) - Crosswalk the authority basis, mandate and record context to archival description terms for long-term interpretability.
neighbor
- WM-ACT-002 Activity (registry parent) - Generic activity identity, temporal bounds, participation and status machinery are defined once in the parent; this model adds only decision-specific authority, option set, choice and outcome and must not restate the generic activity surface.
- Authorization policy evaluation service (XACML PDP/PEP) - A reference to an evaluator never grants ownership of evaluation. This model records that a decision exists and by what authority; policy evaluation, combining algorithms, obligation discharge and enforcement stay with the PDP and PEP.
- Audit trail / event log model - This model states which decision events must be logged and where the log reference lives; audit-record structure, tamper evidence, immutability and log retention are owned by the audit model.
- Records management and disposition model - Retention class and legal-hold status are asserted here as attributes of the decision record; appraisal, schedule definition and destruction execution belong to the records model or the adopting Dimension's retention policy.
- Decision logic / rule model (DMN decision requirement graph) - Design-time decisions, business knowledge models, decision tables and hit policies are authored and versioned there; this model pins the applied version and records deviations from it.
- Subject of the decision - The thing decided about keeps its own model and lifecycle; the decision carries a reference plus decision-specific parameters and must not mirror the subject's attributes.
- Electronic signature and seal model - Signature creation and cryptographic validation are external; what is local is the binding of a signature to this decision and the declared meaning of that signature.
parent
- WM-ACT-002
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, such as the resolution, case, authorization or approval reference held by the deciding body's register.
- Governed global identifier or IRI from a recognised registry or namespace where no master-system reference exists.
- UUID or ULID minted by the adopting Dimension, recorded together with the minting authority and the reason no higher-priority identifier was available.
- A decision date, meeting date, agenda position or sequence position is never an identifier, and no identifier may embed a date as its distinguishing part.
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, participants, inputs, options, an outcome, a rationale and a date.
- Confused with a recommendation, a rule definition, a workflow step and the archived record of the decision.
Capabilities and actions required Filled
- Open decision activity: Register a new decision or approval occurrence with its question, subject and proposed type.
- Bind authority and participants: Record the authority instrument, the holding position, any delegation and the participating agents with their roles.
- Assemble input package: Fix the evidence set used by the decision with versions, as-of times and a content digest.
- Record deliberation and votes: Capture sessions, attendance, tallies, abstentions and dissent leading up to the decision.
- Record decision outcome: Record the chosen option, outcome value, attached conditions and obligations, validity window and deciding agent.
- Issue and acknowledge decision notice: Produce the decision notice, transmit it to addressees and capture acknowledgement of its terms.
- Supersede, revoke or suspend decision: Change the standing of an existing decision and link the change to the acting authority and reason.
- Register contestation or override: Record a challenge, human intervention or emergency override against a decision and the determination that follows.
- Validate decision context completeness: Check a decision occurrence against a bound validation profile and report gaps.
- Project decision context for exchange: Emit a storage-neutral projection of the decision context mapped to a target external vocabulary.
Hazards and failure modes required Filled
- Decisions taken by people without authority.
- Missing evidence that blocks review or appeal.
- Hidden bias in automated contributions.
Standards and interfaces required Filled
- OMG Decision Model and Notation (DMN).
- OASIS XACML 3.0.
- ICA Records in Contexts ontology (RiC-O).
- EU GDPR Article 22 on automated individual decision-making.
Context of use required Filled
- GDPR and the AI Act are EU instruments used here as structural evidence for contestation, explanation and oversight; other jurisdictions impose different or sectoral duties and the corresponding elements may be optional there.
- 21 CFR Part 11 applies to FDA-regulated activity in the United States; its signature-meaning requirement is adopted here as good general practice, not as a universal legal requirement.
- NIST SP 800-37 and SP 800-53 describe US federal practice and are used as a worked normative pattern for formal approval and multi-party control, not as globally binding requirements.
- Quorum, board composition and written-procedure ratification follow local company, association or public law and are left entirely to the adopting Dimension.
- Local offsets are preserved because deadlines, validity windows and contest periods are frequently defined in local civil time rather than UTC.
Sources Filled
- Decision Model and Notation (DMN) - Object Management Group
- DMN 1.5 XML Schema (DMN15.xsd) - Object Management Group
- PROV-O: The PROV Ontology - World Wide Web Consortium
- eXtensible Access Control Markup Language (XACML) Version 3.0 - OASIS
- NIST SP 800-37 Rev. 2, Risk Management Framework for Information Systems and Organizations - National Institute of Standards and Technology
- 21 CFR Part 11 — Electronic Records; Electronic Signatures - U.S. Food and Drug Administration (via GPO govinfo)
- Regulation (EU) 2016/679 (General Data Protection Regulation) - European Union (EUR-Lex)
- Regulation (EU) 2024/1689 (Artificial Intelligence Act) - European Union (EUR-Lex)
- ODRL Information Model 2.2 - World Wide Web Consortium
- RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force
- Records in Contexts Ontology (RiC-O) - International Council on Archives
- NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations - National Institute of Standards and Technology
- Business Process Model and Notation (BPMN) Version 2.0.2 - Object Management Group
- NIST SP 800-37 Rev. 2 Appendix F — Authorization Decisions and Authorization Decision Information (verbatim rendering) - bsafes (independent mirror of the NIST publication text)
Open questions
- Verify against WM-ACT-002's actual finding and question set that the generic activity surface (identity, temporal bounds, participation, status machinery) is genuinely not restated here; the 0.06 overlap factor and the parent boundary note are asserted, not demonstrated, and the parent record is not in this pack.
- Populate the relationship contract with model IDs and link types for the seven prose-named neighbours — audit trail / event log, records management and disposition, decision logic / DMN decision requirement graph, the subject of the decision, party and agent master data, the authorization PDP/PEP, and the electronic signature and seal model — and set relations_ref on the registry record.
- Close the function gaps identified in this audit: recording the applied rule-set version pin and any deviation, recording recusals, conflict declarations and separation-of-duties observations, applying a signature with its declared meaning, and setting the retention class, legal hold and access markings.
- Resolve the default granularity rule for one occurrence (single approval act by one authority instance versus a whole approval chain versus one item within a multi-item session) and specify how chains and multi-item sessions are represented as linked occurrences.
- Determine whether the RFC 3339 pin needs supplementing by a later IETF timestamp specification, and whether preserving local offsets requires an explicit rule for offset changes (daylight-saving or legal time changes) that fall inside a validity window or a contestation period.
- Consult at least one archival, records-management or administrative-decision standard from outside the EU and US to test the declared regional assumptions, which currently rest entirely on GDPR, the AI Act, 21 CFR Part 11, NIST SP 800-37/800-53 and RiC-O.
- Dissenting-opinion structure and minority-report handling are modelled from records practice; no consulted primary source defines them normatively.
- Jurisdiction and venue of the deciding authority are captured only as a limit class, not as a full spatial or legal-geography model.
- Cost, effort and decision-latency measures are not modelled; they belong to a process performance model.
- Group decision techniques (weighted scoring, multi-criteria analysis, consensus protocols) are referenced only as criteria, with no internal structure.
- Negotiated and conditional multi-party agreements where approval is mutual rather than unilateral are only partially served by the assigner-style role model.
- Machine-to-machine decision batches at high volume are addressable but no sampling or aggregation semantics are provided.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-act-024-decision-approval-activity/spec.yaml, ver-cy/world-models/card-supplements/wm-act-024-decision-approval-activity.json