# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-08-24T02:52:14Z", "synthesisSha256": "ae1b264d2d9d71872f3f8803680d7e602ad13ef4eb00f5630a2fe08bbf41e201", "providerMode": "dual-provider", "providers": [ "Claude", "Grok" ], "waivedProviders": [] }, "metaModel": { "id": "WM-ORG-016", "registryId": "vr.wm-org-016", "name": "Work Assignment", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "relationship", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ORG.ASN" ], "tags": [ "work", "assignment", "soc.org.asn" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-org-016-work-assignment/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-org-016", "model": { "registry_id": "vr.wm-org-016", "model_id": "WM-ORG-016", "name": "Work Assignment", "entry_kind": "relationship", "purpose": "Model the time-bounded, scoped binding of a person or non-human agent to a role, position or body of work within an organization, together with the authority, place, effort, preconditions, lifecycle and evidence that make the binding operable and auditable.", "scope_statement": "A Work Assignment is a reified n-ary relationship between an assignee agent, an organization or unit, a role or post, a bounded work scope and a validity period. The model covers how such a binding is identified, classified, authorized, constrained, changed, evidenced and ended. It deliberately holds no definition of the position itself, no contract terms, no person master data and no task-instance execution state; those belong to sibling models and are referenced. The model is format-neutral: JSON, YAML, Markdown, Git, MCP and MongoDB are projections of this semantics, never its source.", "in_scope": [ "Identity, classification and versioning of the individual assignment record", "The n-ary participant set: assignee agent, organization/unit, role or post, engagement context", "Bounded work scope: objectives, services, caseload, accounts, operational period, exclusions", "Granted authority, decision limits, reporting lines, delegation and acting cover", "Place of work, mobility, cross-border work and the jurisdictional consequences that follow", "Effort allocation and capacity share across concurrent assignments", "Effective period, working pattern, availability, duty and rest limits", "Assignment lifecycle states, transitions, amendment, handover and offboarding", "Eligibility preconditions: competence, credentials, fitness, screening, right to work", "Constraints: separation of duty, conflict of interest, cardinality and coverage rules", "Authorization evidence, acknowledgement, statutory notification and disclosure", "Personal-data classification, access scoping, retention, deletion and legal hold", "Alignment to external representations and projection to downstream consumers" ], "out_of_scope": [ "Definition, classification, grading and description of the position or post itself (WM-ORG-004)", "Employment contract formation and terms, remuneration determination and benefits (WM-ORG-005)", "Person, party and agent master identity records", "Organization structure, unit hierarchy and legal-entity data", "Role, occupation, skill and competence taxonomies as concepts (referenced as classifiers)", "Per-task work-item claiming, execution and completion state", "Permission and entitlement catalogues, and the access-decision engine itself", "Concrete shift instances, time capture, timesheets and attendance actuals", "Payroll calculation, cost allocation and inter-company recharge", "Performance objectives, appraisal outcomes and succession candidate pools" ], "boundary_notes": [ { "neighbor": "WM-ORG-004 Position", "distinction": "A post exists independently of the person or persons filling it; the assignment is the time-bounded occupancy of that post. Reclassifying a post does not create an assignment, and ending an assignment does not abolish the post.", "source_refs": [ "SRC-001" ] }, { "neighbor": "WM-ORG-005 Employment relationship", "distinction": "The employment relationship is the legal engagement; one engagement can carry several concurrent assignments, and an assignment can rest on a commercial staffing contract or a volunteer arrangement instead of employment. Statutory written particulars attach to the engagement, not to each assignment.", "source_refs": [ "SRC-010", "SRC-014" ] }, { "neighbor": "Role and occupation classifiers (ESCO/ISCO-08, professional specialty codes)", "distinction": "A role is an abstract concept in a controlled vocabulary; the assignment is a concrete dated instance that cites it. Classifier codes are alignments held on the assignment, not definitions owned by it.", "source_refs": [ "SRC-001", "SRC-006", "SRC-002" ] }, { "neighbor": "Human task / work-item model", "distinction": "A task instance has its own short-lived lifecycle with potential owners and an actual owner established by claiming. A work assignment is the standing eligibility and authority from which potential-owner sets are derived; it does not carry task-instance state.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Access management and entitlement model", "distinction": "RBAC user-to-role assignment is a downstream projection of this model. The permission catalogue, role hierarchy and session activation are governed elsewhere; this model supplies the authoritative temporal and organizational basis for provisioning and de-provisioning.", "source_refs": [ "SRC-004" ] }, { "neighbor": "Schedule, roster and availability model", "distinction": "The assignment states the working pattern, availability windows and applicable duty limits; the concrete dated shift or duty instances live in a scheduling model that references the assignment identifier.", "source_refs": [ "SRC-011", "SRC-002" ] }, { "neighbor": "Time capture and timecard model", "distinction": "Hours actually worked are observations evidencing performance under an assignment. They are never the assignment itself and must not be used to infer its effective period.", "source_refs": [ "SRC-014" ] }, { "neighbor": "Incident and operational tasking records", "distinction": "Operational tasking documents bind resources to a single operational period and a specific incident objective. They are short-horizon instances of assignment semantics and should reference, not replace, the standing assignment where one exists.", "source_refs": [ "SRC-012" ] } ] }, "sources": [ { "id": "SRC-001", "title": "The Organization Ontology (org:Membership, org:Post, org:Role, org:memberDuring)", "organization": "World Wide Web Consortium (W3C)", "url": "https://www.w3.org/TR/vocab-org/", "version_or_date": "W3C Recommendation, 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:05:00Z", "relevance": "Normative n-ary membership pattern: an Agent, an Organization and a Role bound by org:Membership and time-bounded by org:memberDuring, with org:Post modelling a position that exists independently of its holders. This is the structural backbone of the model and the basis for the Position boundary." }, { "id": "SRC-002", "title": "FHIR Release 5 - PractitionerRole resource", "organization": "Health Level Seven International (HL7)", "url": "https://hl7.org/fhir/R5/practitionerrole.html", "version_or_date": "FHIR R5, Maturity Level 4 (Trial Use)", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:06:00Z", "relevance": "A deployed, machine-readable instance of assignment semantics: identifier, active flag, period, practitioner, organization, role code, specialty, location, healthcareService, availability and endpoint. Evidences that role, place, service scope, period and availability belong on the assignment rather than on the person." }, { "id": "SRC-003", "title": "Web Services - Human Task (WS-HumanTask) Specification Version 1.1", "organization": "OASIS", "url": "https://docs.oasis-open.org/bpel4people/ws-humantask-1.1-spec-cs-01.html", "version_or_date": "Committee Specification 01, 17 August 2010", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:07:00Z", "relevance": "Normative generic human roles (task initiator, potential owners, actual owner, excluded owners, stakeholders, business administrators) and a full lifecycle with claim, start, release, delegate, forward, suspend, resume, complete, fail, escalate and nominate. Grounds the lifecycle and delegation findings and defines the task/assignment boundary." }, { "id": "SRC-004", "title": "Role Based Access Control (RBAC) - INCITS 359-2012", "organization": "National Institute of Standards and Technology (NIST) / INCITS", "url": "https://csrc.nist.gov/projects/role-based-access-control", "version_or_date": "INCITS 359-2012 (revision of ANSI/INCITS 359-2004), updated 29 May 2012", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:08:00Z", "relevance": "Defines user assignment (UA), permission assignment (PA), sessions and role activation, role hierarchies, static and dynamic separation of duty and cardinality constraints. Grounds the constraint, conflict and downstream-provisioning findings, and the counterexample that standard RBAC user assignment has no native temporal scope." }, { "id": "SRC-005", "title": "schema.org Role (with OrganizationRole, EmployeeRole, roleName, startDate, endDate)", "organization": "Schema.org Community Group", "url": "https://schema.org/Role", "version_or_date": "Schema.org version 30.0, 2026-03-19", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:09:00Z", "relevance": "Independent confirmation of the reified-role pattern for adding time and qualification to a relationship between two entities, and a documented counterexample: Role carries no status, no authority and only date-granularity validity, so it can be an alignment target but not a semantic source." }, { "id": "SRC-006", "title": "ESCO classification - Occupations pillar", "organization": "European Commission (DG Employment, Social Affairs and Inclusion)", "url": "https://esco.ec.europa.eu/en/classification/occupation_main", "version_or_date": "ESCO v1.2.1, last updated 10 December 2025", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:10:00Z", "relevance": "Governed URIs for occupations, each mapped to exactly one ISCO-08 code, with associated knowledge, skills and competences. Supplies the classifier alignment for role linkage and the competence prerequisites of an assignment." }, { "id": "SRC-007", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium (W3C)", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:11:00Z", "relevance": "Agent, Activity, qualified Association with prov:hadRole and prov:Role, prov:Delegation and prov:actedOnBehalfOf, plus startedAtTime/endedAtTime. Grounds authorization provenance, the acting-on-behalf-of semantics of delegation, and the SoftwareAgent case for non-human assignees." }, { "id": "SRC-008", "title": "RFC 3339: Date and Time on the Internet - Timestamps", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "July 2002, Proposed Standard (updated by RFC 9557)", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:12:00Z", "relevance": "Mandates an explicit UTC offset or Z on every timestamp and reserves -00:00 for an unknown local offset. Governs every effective, transition, observation and ingestion time in the model." }, { "id": "SRC-009", "title": "Regulation (EU) 2024/1689 (AI Act), Article 26 - Obligations of deployers of high-risk AI systems", "organization": "European Commission - AI Act Service Desk", "url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-26", "version_or_date": "Regulation (EU) 2024/1689, official version of 13 June 2024", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:13:00Z", "relevance": "Article 26(2) requires deployers to assign human oversight to natural persons who have the necessary competence, training and authority as well as the necessary support; 26(6) sets a minimum six-month log retention; 26(7) requires informing workers' representatives and affected workers beforehand. Grounds natural-person reservation, competence-plus-authority preconditions, notification and retention." }, { "id": "SRC-010", "title": "Employment Rights Act 1996, section 1 - Statement of initial employment particulars", "organization": "UK Parliament / The National Archives (legislation.gov.uk)", "url": "https://www.legislation.gov.uk/ukpga/1996/18/section/1", "version_or_date": "Revised text in force as at 22 August 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:14:00Z", "relevance": "Statutory list of particulars that must be given in writing not later than the beginning of employment: job title or description, place(s) of work, start date, normal hours and the days required to work including whether they may be variable, duration where not permanent, probation, training entitlements and work outside the UK. Grounds scope, place, pattern, term and written-statement findings." }, { "id": "SRC-011", "title": "RFC 9073: Event Publishing Extensions to iCalendar (PARTICIPANT, VLOCATION, VRESOURCE)", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc9073.html", "version_or_date": "August 2021, Standards Track", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:15:00Z", "relevance": "Defines a structured PARTICIPANT component with PARTICIPANT-TYPE, CALENDAR-ADDRESS and STRUCTURED-DATA attachable to VEVENT and VTODO, plus VLOCATION and VRESOURCE. Evidences the interoperable projection of an assignment into scheduling systems and the separation between the standing assignment and dated instances." }, { "id": "SRC-012", "title": "NIMS ICS Form 204, Assignment List (v3.1) and ICS Form 203, Organization Assignment List (v3)", "organization": "Federal Emergency Management Agency (FEMA), U.S. Department of Homeland Security", "url": "https://training.fema.gov/emiweb/is/icsresource/assets/ics%20forms/ics%20form%20204,%20assignment%20list%20(v3.1).pdf", "version_or_date": "ICS Form 204 v3.1; ICS Form 203 v3 (NIMS ICS forms set)", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:16:00Z", "relevance": "A standardized national artifact set in which assignment is a first-class document: ICS 203 records who holds which organizational position and ICS 204 informs division and group supervisors of incident assignments for a single operational period. Grounds the operational-period scoping and the assignment-list artifact. Field-level detail could not be machine-extracted from the PDF and is recorded as an evidence gap." }, { "id": "SRC-013", "title": "HR Open Standards APISpecifications repository", "organization": "HR Open Standards Consortium, Inc.", "url": "https://github.com/HROpen/APISpecifications", "version_or_date": "Repository state as of 12 February 2026", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:17:00Z", "relevance": "Noun-based, versioned API specifications (organizations/v1, workers/v1, worker-paid-hours-reports/v1, worker-compensation-reports/v1). Notably contains no Assignment resource, which is the primary evidence that no stable modern JSON counterpart to StaffingAssignment exists and that assignment semantics must not be assumed interoperable by default." }, { "id": "SRC-014", "title": "HR Open Standards - Standards (Contingent Staffing HR-XML 3.3: StaffingOrder, StaffingResource, StaffingAssignment, TimeCard, WorkerOnBoarding)", "organization": "HR Open Standards Consortium, Inc.", "url": "https://www.hropenstandards.org/standards", "version_or_date": "Contingent Staffing HR-XML specification version 3.3", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:18:00Z", "relevance": "Establishes StaffingAssignment as the terms and conditions of placing a staffing resource with a staffing customer, separate from the order, the resource and the timecard. Evidences the tri-party assignment case in which the assignee is engaged by one organization and works for another." }, { "id": "SRC-015", "title": "HL7 FHIR PractitionerRole Resource", "organization": "HL7 International", "url": "https://www.hl7.org/fhir/practitionerrole.html", "version_or_date": "FHIR R5 5.0.0, generated 26 March 2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T16:05:00Z", "relevance": "Assignment of a practitioner to roles, locations, specialties and services for an organization during a period; identifiers, active flag, empty practitioner for unnamed occupancy, and the rule that non-adjacent periods are distinct instances." }, { "id": "SRC-016", "title": "Role Based Access Control FAQs and INCITS 359 reference model", "organization": "National Institute of Standards and Technology", "url": "https://csrc.nist.gov/projects/role-based-access-control/faqs", "version_or_date": "Created 21 November 2016, updated 4 March 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T16:15:00Z", "relevance": "Core RBAC user-role assignment UA, role activation in a session, and static and dynamic separation-of-duty constraints that a work assignment may have to respect when provisioning access." }, { "id": "SRC-017", "title": "5 CFR Part 335 Promotion and Internal Placement", "organization": "U.S. Office of Personnel Management", "url": "https://www.ecfr.gov/current/title-5/chapter-I/subchapter-B/part-335", "version_or_date": "eCFR current as of 20 August 2026; Title 5 last amended 14 August 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T16:20:00Z", "relevance": "Federal authority to promote, demote or reassign; time-limited promotions; details to higher-graded positions; 120-day competition threshold; reconstruction records; tenure unchanged by position change." }, { "id": "SRC-018", "title": "ISA-95 Standard: Enterprise-Control System Integration", "organization": "International Society of Automation", "url": "https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard", "version_or_date": "ANSI/ISA-95.00.01-2025 (IEC 62264-1 Modified) and related parts, page accessed 24 August 2026", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T16:30:00Z", "relevance": "Confirms personnel as a first-class resource exchanged with equipment, material and physical assets, establishing a sibling manufacturing-assignment boundary rather than organizational occupancy semantics." }, { "id": "SRC-019", "title": "Regulation (EU) 2016/679 Article 88 Processing in the context of employment", "organization": "European Union", "url": "https://gdpr-info.eu/art-88-gdpr/", "version_or_date": "Regulation (EU) 2016/679, applicable 25 May 2018; Article 88 text as published on gdpr-info.eu", "source_type": "legislation", "primary_source": false, "authority_tier": 2, "accessed_at": "2026-08-24T16:35:00Z", "relevance": "Member State rules for processing employees' personal data for recruitment, performance of the employment contract, organization of work and termination, which govern assignment records." }, { "id": "SRC-020", "title": "Employment practices and data protection: keeping employment records", "organization": "UK Information Commissioner's Office", "url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/employment/employment-practices-and-data-protection-keeping-employment-records", "version_or_date": "ICO employment records guidance, page accessed 24 August 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T16:40:00Z", "relevance": "Lawful bases, storage limitation, subject access and right to erasure for worker records, including that erasure is often refused where tax, social-security or other legal retention applies." }, { "id": "SRC-021", "title": "R198 Employment Relationship Recommendation, 2006", "organization": "International Labour Organization", "url": "https://www.ilo.org/resource/other/r198-employment-relationship-recommendation-2006", "version_or_date": "15 June 2006", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T16:45:00Z", "relevance": "International instrument on determining an employment relationship from facts of work; used here as a boundary so that assignment of duties is not conflated with the existence of employment." } ], "structure": { "bundles": [ { "id": "assignment-identity-and-definition", "name": "Assignment Identity and Definition", "description": "What an individual work assignment is as a distinct record: how it is identified, which participants it binds, how it is typed, and what kind of agent may hold it.", "rationale": "W3C ORG models membership as a reified n-ary relation precisely because the binding of agent, organization and role carries qualifying detail of its own. That reified object needs its own identity, participant set and classification before anything else can be said about it.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009" ], "layers": [ { "id": "assignment-core-relation", "name": "Core Assignment Relation", "description": "The identity, participant structure and typing of the assignment record itself.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "assignment-record-identity", "name": "Assignment record identity and versioning", "description": "How one assignment instance is identified and kept distinct from the position, the role concept and the person, including identifier priority, correction versus real-world change, and supersession chains.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-identity-master", "text": "Which system is the authoritative master for this assignment identifier, and what identifier value and scheme does it issue?", "kind": "identity", "answer_data": [ "Master system name or URI", "Assignment identifier value", "Identifier scheme or namespace" ] }, { "id": "q-identity-fallback", "text": "If no authoritative master identifier exists, which governed IRI or Dimension-assigned UUID/ULID is used instead?", "kind": "identity", "answer_data": [ "Fallback identifier type", "Issuing Dimension", "Minted identifier value" ] }, { "id": "q-identity-recurrence", "text": "How are two assignments of the same agent to the same post in different periods kept distinct without using a date as the identifier?", "kind": "identity", "answer_data": [ "Distinguishing key strategy", "Sequence or occurrence number", "Rule text" ] }, { "id": "q-identity-correction", "text": "How is a corrected version of the assignment record distinguished from a genuine change to the assignment in the world?", "kind": "provenance", "answer_data": [ "Record version identifier", "Change class (correction or real-world change)", "Superseded record reference" ] } ], "data_elements": [ { "id": "de-assignment-id", "name": "assignment_id", "description": "Primary identifier of the assignment instance, resolved by the identity priority rule.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "de-assignment-id-scheme", "name": "assignment_id_scheme", "description": "Namespace or scheme that governs the primary identifier.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-record-version", "name": "record_version", "description": "Version of the record as stored, incremented on correction rather than on real-world change.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-supersedes-ref", "name": "supersedes_assignment_ref", "description": "Reference to the assignment record this one replaces.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [], "inline_only_rationale": "Identity is a set of inline key values carried on the assignment record itself. The register that holds them is this model's own storage projection, not a separately governed artifact." }, { "id": "assignment-participants-and-relation-shape", "name": "Participant set and relation shape", "description": "The n-ary participants that constitute the assignment: assignee agent, assigning organization or unit, role or post, host organization where different, and the engagement context that gives it a basis.", "source_refs": [ "SRC-001", "SRC-002", "SRC-014" ], "questions": [ { "id": "q-participants-triple", "text": "Which agent, which organizational unit and which role or post does this assignment bind together?", "kind": "composition", "answer_data": [ "Assignee agent reference", "Organization or unit reference", "Post or role reference" ] }, { "id": "q-participants-basis", "text": "Which employment relationship, staffing contract or volunteer arrangement gives this assignment its basis, and is the assignee engaged by a different organization from the one where the work is performed?", "kind": "authority", "answer_data": [ "Engagement context reference", "Engagement type code", "Host organization reference" ] }, { "id": "q-participants-shape", "text": "Is the assignment expressed against a defined post, an abstract role concept, or a bespoke scope with no post at all?", "kind": "classification", "answer_data": [ "Relation shape code", "Post reference or null", "Role concept references" ] }, { "id": "q-participants-mutability", "text": "Which participant changes may be made in place and which force the creation of a new assignment record?", "kind": "constraint", "answer_data": [ "Immutable participant list", "Mutable participant list", "Rule reference" ] } ], "data_elements": [ { "id": "de-assignee-agent-ref", "name": "assignee_agent_ref", "description": "Reference to the person, unit or non-human agent that holds the assignment.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "de-assigning-org-ref", "name": "assigning_organization_ref", "description": "Organization or unit in which the assignment is held.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001" ] }, { "id": "de-host-org-ref", "name": "host_organization_ref", "description": "Organization where the work is actually performed when it differs from the engaging organization.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "de-engagement-context-ref", "name": "engagement_context_ref", "description": "Reference to the employment relationship, staffing contract or other arrangement underpinning the assignment.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "assignment-instrument", "name": "Assignment instrument", "description": "The issued document that constitutes or communicates the assignment: assignment letter, deployment order, secondment agreement or staffing assignment confirmation naming the parties, scope and period.", "media_or_form": [ "signed document", "structured message", "rendered document in any presentation format" ], "serial": true, "identity_strategy": "Instrument reference issued by the originating system, carried alongside the assignment_id; the instrument identifier is never reused after amendment.", "source_refs": [ "SRC-014", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "assignment-type-classification", "name": "Assignment type and primacy", "description": "Typing the assignment by nature (substantive, acting, interim, seconded, agency-supplied, volunteer, shadow), by permanence, by whether it is the agent's primary assignment, and by how much of the post's authority it conveys.", "source_refs": [ "SRC-001", "SRC-005", "SRC-014" ], "questions": [ { "id": "q-type-scheme", "text": "Which controlled vocabulary supplies the assignment type, and how are locally invented types governed and reviewed?", "kind": "classification", "answer_data": [ "Assignment type code", "Vocabulary reference", "Local extension governance rule" ] }, { "id": "q-type-primary", "text": "Is this the agent's primary assignment for reporting, headcount and directory purposes, and how is exactly one primary guaranteed?", "kind": "constraint", "answer_data": [ "Primary flag", "Uniqueness rule", "Conflict resolution outcome" ] }, { "id": "q-type-authority-conveyance", "text": "Does the assignment convey the full authority of the post, a reduced subset, or none at all?", "kind": "authority", "answer_data": [ "Authority conveyance code", "Excluded authority list", "Justification" ] }, { "id": "q-type-acting", "text": "Where the assignment is acting or interim, what substantive assignment is it standing in for and until when?", "kind": "relationship", "answer_data": [ "Covered assignment reference", "Acting reason code", "Expected end" ] } ], "data_elements": [ { "id": "de-assignment-type-code", "name": "assignment_type_code", "description": "Coded nature of the assignment, drawn from a governed vocabulary.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-014" ] }, { "id": "de-is-primary", "name": "is_primary_assignment", "description": "Whether this is the agent's principal assignment for organizational reporting.", "value_kind": "boolean", "cardinality": "1", "required": true, "source_refs": [ "SRC-001" ] }, { "id": "de-authority-conveyance-code", "name": "authority_conveyance_code", "description": "Extent to which the post's authority passes to the assignee.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [], "inline_only_rationale": "Type and primacy are coded attributes of the relation. The vocabulary itself is governed by a classifier registry referenced through composition, not stored as an artifact of this model." } ] }, { "id": "assignee-agent-kind", "name": "Assignee Agent Kind and Reservation", "description": "What kind of agent may hold the assignment and which duties are reserved to natural persons.", "source_refs": [ "SRC-007", "SRC-009", "SRC-001" ], "findings": [ { "id": "assignee-agent-kind-and-reservation", "name": "Agent kind, natural-person reservation and accountability", "description": "Whether the assignee is a natural person, an organizational unit or a non-human software or robotic agent, which duties may not lawfully be held by a non-human agent, and who remains accountable when one is used.", "source_refs": [ "SRC-007", "SRC-009", "SRC-001" ], "questions": [ { "id": "q-agentkind-what", "text": "Is the assignee a natural person, an organizational unit or team, or a non-human software or robotic agent?", "kind": "classification", "answer_data": [ "Assignee kind code", "Agent type reference", "Software agent version identifier where applicable" ] }, { "id": "q-agentkind-reserved", "text": "Which duties within this assignment are legally reserved to a natural person and therefore may not be discharged by a non-human agent?", "kind": "constraint", "answer_data": [ "Reserved duty list", "Legal basis reference", "Reservation verification outcome" ] }, { "id": "q-agentkind-oversight", "text": "Where a non-human agent holds or supports the assignment, which natural person holds oversight, and do they have the competence, training and authority plus the support needed to intervene?", "kind": "authority", "answer_data": [ "Accountable person reference", "Competence and training evidence reference", "Intervention authority statement" ] }, { "id": "q-agentkind-identifier", "text": "How is the assignee referenced across systems without embedding personal data in the identifier itself?", "kind": "privacy", "answer_data": [ "Pseudonymous agent reference", "Resolution service reference", "Personal-data exclusion rule" ] } ], "data_elements": [ { "id": "de-assignee-kind-code", "name": "assignee_kind_code", "description": "Whether the assignee is a natural person, a collective unit or a non-human agent.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-001" ] }, { "id": "de-natural-person-required", "name": "natural_person_required", "description": "Whether the assignment or a named duty within it must be held by a natural person.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-accountable-person-ref", "name": "accountable_person_ref", "description": "Natural person accountable for the acts of a non-human assignee.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009", "SRC-007" ] } ], "artifacts": [ { "id": "oversight-designation-record", "name": "Human oversight designation record", "description": "Record designating the natural person or persons assigned to oversee a high-risk automated system used in or by the assignment, together with evidence of their competence, training, authority and available support.", "media_or_form": [ "structured record", "signed designation document" ], "serial": false, "identity_strategy": "Designation identifier issued by the deployer's compliance register, linked to both the assignment_id and the system instance identifier.", "source_refs": [ "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "unnamed-and-ex-officio-occupancy", "name": "Assigned agent", "description": "ORG Membership.member is a foaf:Agent, covering persons and organizations. FHIR PractitionerRole.practitioner is 0..1 and may be empty for an un-named surgeon at a named hospital. PROV-O distinguishes Person, Organization and SoftwareAgent as agents, but HR occupancy of posts by software agents lacks primary HR-standard support and is recorded as a gap when claimed.", "source_refs": [ "SRC-001", "SRC-015", "SRC-007" ], "questions": [ { "id": "unnamed-and-ex-officio-occupancy-q01", "text": "Which person or other agent occupies this assignment, and what master identifier is used for that agent?", "kind": "identity", "answer_data": [ "agent_id", "agent_type", "agent_master_system", "agent_display_name" ] }, { "id": "unnamed-and-ex-officio-occupancy-q02", "text": "Is the occupancy an unnamed or pre-allocated role with no designated practitioner, and if so what host and role still identify the slot?", "kind": "composition", "answer_data": [ "unnamed_occupancy_flag", "host_organization_id", "role_codes", "reason_unnamed" ] }, { "id": "unnamed-and-ex-officio-occupancy-q03", "text": "Is the holder an organization or post treated as an agent, as permitted for some government ex officio constructions?", "kind": "composition", "answer_data": [ "holder_is_organization", "holder_organization_id", "ex_officio_rule" ] }, { "id": "unnamed-and-ex-officio-occupancy-q04", "text": "If a software or robotic agent is claimed as occupant, what primary HR or personnel source supports that claim, or is the claim marked as a gap?", "kind": "exception", "answer_data": [ "agent_type", "primary_support_flag", "gap_flag", "justification" ] } ], "data_elements": [ { "id": "unnamed-and-ex-officio-occupancy-data01", "name": "Assigned agent reference", "description": "Reference to the occupying person or other agent; omitted only for unnamed occupancy.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "unnamed-and-ex-officio-occupancy-data02", "name": "Agent type", "description": "Person, organization, or, where evidenced, software agent.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "unnamed-and-ex-officio-occupancy-data03", "name": "Unnamed occupancy flag", "description": "True when the occupancy describes a role at an organization without a named practitioner.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] } ], "artifacts": [], "inline_only_rationale": "The assigned agent is a reference to a sibling identity model; unnamed occupancy is a boolean plus host and role on the assignment record." } ] } ] }, { "id": "assignment-scope-and-authority", "name": "Assignment Scope and Authority", "description": "What the assignment covers and what it empowers: the role linkage, the bounded body of work, the place of work, the authority granted, supervision and delegation, and the share of capacity consumed.", "rationale": "FHIR PractitionerRole places role code, specialty, location and service scope on the role-in-organization rather than on the person, and statutory particulars require job title or description and place of work to be stated. Authority, supervision and allocation are what make the binding operable rather than merely descriptive.", "source_refs": [ "SRC-002", "SRC-010", "SRC-001", "SRC-006", "SRC-012" ], "layers": [ { "id": "scope-of-work-and-place", "name": "Scope of Work and Place", "description": "The role linkage, the concrete body of work covered, and where the work is performed.", "source_refs": [ "SRC-002", "SRC-006", "SRC-010", "SRC-012" ], "findings": [ { "id": "role-and-position-linkage", "name": "Role, post and occupation classification linkage", "description": "Which post the assignment fills, which role concepts and external occupation or specialty codes describe it, the title used towards the assignee, and what happens when the underlying post is reclassified.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "q-role-post", "text": "Which post does the assignment fill, and which role concepts describe what the assignee actually does?", "kind": "composition", "answer_data": [ "Post reference", "Role concept references", "Derivation note where role differs from post" ] }, { "id": "q-role-classifier", "text": "Which external occupation, specialty or professional classification codes apply, and at what version of the classification?", "kind": "interoperability", "answer_data": [ "Classification scheme identifier", "Code value and URI", "Scheme version" ] }, { "id": "q-role-title", "text": "What job title is used towards the assignee, and does it differ from the classified title of the post?", "kind": "definition", "answer_data": [ "Working job title", "Classified post title", "Divergence reason" ] }, { "id": "q-role-reclassification", "text": "If the post is reclassified or the classification scheme is reversioned, does the assignment persist unchanged and under what rule?", "kind": "lifecycle", "answer_data": [ "Persistence rule", "Reclassification event reference", "Required re-approval flag" ] } ], "data_elements": [ { "id": "de-assigned-job-title", "name": "assigned_job_title", "description": "Title by which the assignment is known to the assignee and to third parties.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-010" ] }, { "id": "de-occupation-code", "name": "occupation_classification_code", "description": "Governed occupation or specialty code with its scheme and version.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-002" ] }, { "id": "de-post-ref", "name": "post_ref", "description": "Reference to the post or position occupied through this assignment.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [], "inline_only_rationale": "Role linkage is reference data: codes and pointers into externally governed classifiers and into the Position model. The classification standards themselves are third-party artifacts, not artifacts produced by this model." }, { "id": "work-scope-and-service-portfolio", "name": "Bounded work scope and portfolio", "description": "The concrete body of work the assignment covers - objectives, services, caseload, accounts, assets, population or operational period - together with what is explicitly excluded and how overlapping claims are prevented.", "source_refs": [ "SRC-002", "SRC-012", "SRC-010" ], "questions": [ { "id": "q-scope-what", "text": "What objectives, services or caseload does this assignment cover, and what is explicitly excluded from it?", "kind": "definition", "answer_data": [ "Work scope statement", "Covered service references", "Explicit exclusions" ] }, { "id": "q-scope-context", "text": "Which client, cost centre, project, incident or operational period is the work performed under?", "kind": "composition", "answer_data": [ "Cost centre or project reference", "Client or account reference", "Operational period reference" ] }, { "id": "q-scope-disjointness", "text": "How is the scope bounded so that two concurrent assignments do not both claim responsibility for the same work?", "kind": "constraint", "answer_data": [ "Disjointness rule", "Overlap detection outcome", "Tie-break owner" ] }, { "id": "q-scope-change-threshold", "text": "How large a change of scope can be absorbed as an amendment before a new assignment record is required?", "kind": "lifecycle", "answer_data": [ "Scope change threshold rule", "Change magnitude assessment", "Decision and approver" ] } ], "data_elements": [ { "id": "de-work-scope-statement", "name": "work_scope_statement", "description": "Narrative or structured statement of the work covered by the assignment.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-010", "SRC-012" ] }, { "id": "de-covered-service-ref", "name": "covered_service_ref", "description": "References to the services, caseloads, accounts or assets in scope.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-operational-period-ref", "name": "operational_period_ref", "description": "Reference to a defined operational period or campaign that bounds short-horizon assignments.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "de-scope-exclusion", "name": "scope_exclusion", "description": "Work explicitly excluded from the assignment.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "assignment-list-document", "name": "Assignment list for an operational period", "description": "A dated tasking document that binds named resources and their leaders to specific work assignments, a reporting location and special instructions for one operational period, as standardized in national incident management form sets.", "media_or_form": [ "standardized form", "structured record", "rendered document in any presentation format" ], "serial": true, "identity_strategy": "Composite of incident or campaign identifier, operational period start and end, and organizational element; issued and approved per period rather than reused.", "source_refs": [ "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "work-location-and-mobility", "name": "Place of work, mobility and jurisdiction", "description": "Where the work is performed, whether it is remote, multi-site or cross-border, and which location-derived legal and safety regimes attach to the assignment.", "source_refs": [ "SRC-010", "SRC-002" ], "questions": [ { "id": "q-place-where", "text": "What is the assignee's designated base location and what other locations does the assignment cover?", "kind": "spatial", "answer_data": [ "Base location reference", "Additional location references", "Location role code" ] }, { "id": "q-place-mode", "text": "Is any part of the work performed remotely, at customer sites, or in another country, and for how long in each case?", "kind": "spatial", "answer_data": [ "Work location mode code", "Cross-border flag", "Duration in each mode" ] }, { "id": "q-place-jurisdiction", "text": "Which jurisdictional, tax, safety and working-time regimes follow from the work location, and which prevails where they differ from the engaging entity's home regime?", "kind": "constraint", "answer_data": [ "Applicable jurisdiction codes", "Governing regime determination", "Conflict resolution note" ] }, { "id": "q-place-history", "text": "How is a change of work location recorded so that the earlier location and its effective period remain retrievable?", "kind": "temporal", "answer_data": [ "Location history entries", "Effective period per location", "Change event reference" ] } ], "data_elements": [ { "id": "de-base-location-ref", "name": "base_work_location_ref", "description": "Reference to the designated base place of work.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010", "SRC-002" ] }, { "id": "de-location-mode-code", "name": "work_location_mode_code", "description": "On-site, remote, hybrid, mobile or client-site working mode.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-010" ] }, { "id": "de-jurisdiction-code", "name": "applicable_jurisdiction_code", "description": "Jurisdictions whose employment, tax or safety rules apply because of the work location.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-cross-border-flag", "name": "cross_border_work_flag", "description": "Whether the assignment requires work outside the engaging entity's home jurisdiction for a material period.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [], "inline_only_rationale": "Locations are references into a place model and the derived regime codes are inline attributes. Any posting or mobility certificate is issued by an external authority and is held as evidence under the eligibility layer rather than produced here." }, { "id": "role-scoped-service-contact-and-directory-projection", "name": "Performance location and services", "description": "FHIR PractitionerRole.location, specialty, healthcareService, contact, characteristic, communication, availability and endpoint describe where and how the occupant provides services. Distinct instances are required when availability, telecom or other details are not the same across services or locations. ORG basedAt and Site capture organizational location independently of occupancy.", "source_refs": [ "SRC-001", "SRC-015" ], "questions": [ { "id": "role-scoped-service-contact-and-directory-projection-q01", "text": "At which locations or sites is this occupancy authorized to be performed?", "kind": "spatial", "answer_data": [ "location_ids", "site_ids", "location_names", "jurisdiction_codes" ] }, { "id": "role-scoped-service-contact-and-directory-projection-q02", "text": "Which specialties and services is the occupant authorized to provide under this occupancy?", "kind": "classification", "answer_data": [ "specialty_codes", "healthcare_service_ids", "service_mode_codes" ] }, { "id": "role-scoped-service-contact-and-directory-projection-q03", "text": "What official contact details, languages and technical endpoints belong to this occupancy rather than to the person master record?", "kind": "relationship", "answer_data": [ "contacts", "languages", "endpoints", "contact_purpose" ] }, { "id": "role-scoped-service-contact-and-directory-projection-q04", "text": "If locations, services or telecom differ, must this occupancy be split into multiple assignment instances?", "kind": "decision", "answer_data": [ "split_required", "differing_attributes", "related_assignment_ids" ] } ], "data_elements": [ { "id": "role-scoped-service-contact-and-directory-projection-data01", "name": "Authorized locations", "description": "Locations or sites at which the occupancy may be performed.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "role-scoped-service-contact-and-directory-projection-data02", "name": "Specialties", "description": "Functional specialties practiced under this occupancy.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "role-scoped-service-contact-and-directory-projection-data03", "name": "Healthcare or business services", "description": "Services provided for the host under this occupancy.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "role-scoped-service-contact-and-directory-projection-data04", "name": "Occupancy contact details", "description": "Addresses, telecom and endpoints specific to the occupancy.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-015" ] } ], "artifacts": [ { "id": "role-scoped-service-contact-and-directory-projection-artifact01", "name": "Provider or staff directory entry", "description": "Published directory record of the occupancy's locations, services, contacts and endpoints.", "media_or_form": [ "provider directory listing", "staff directory card", "service catalogue entry" ], "serial": false, "identity_strategy": "Keyed by assignment identifier plus host organization; directory publication is a projection, not a second identity.", "source_refs": [ "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "authority-supervision-and-capacity", "name": "Authority, Supervision and Capacity", "description": "What the assignment empowers the assignee to decide, to whom they answer, what may be delegated, and how much capacity the assignment consumes.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007" ], "findings": [ { "id": "granted-authority-and-decision-rights", "name": "Granted authority and decision limits", "description": "The decisions, approvals and financial limits the assignment authorizes, distinguishing authority inherent in the post from authority granted to this assignee, and the validity of that authority in its own right.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-auth-what", "text": "What decisions, approvals and financial limits does this assignment authorize the assignee to exercise?", "kind": "authority", "answer_data": [ "Authority item descriptions", "Financial or quantitative limits", "Scope qualifiers per item" ] }, { "id": "q-auth-source", "text": "Which authorities flow from the post itself and which were granted specifically to this assignee?", "kind": "provenance", "answer_data": [ "Authority source code per item", "Granting instrument reference", "Granting agent reference" ] }, { "id": "q-auth-validity", "text": "Does each granted authority have its own validity period, and does it lapse automatically when the assignment ends or is suspended?", "kind": "temporal", "answer_data": [ "Authority validity start and end", "Automatic lapse rule", "Residual authority after end" ] }, { "id": "q-auth-competence-of-grantor", "text": "Was the granting agent themselves authorized to confer authority at this level and scope?", "kind": "validation", "answer_data": [ "Grantor authority check outcome", "Grantor assignment reference", "Escalation taken where insufficient" ] } ], "data_elements": [ { "id": "de-granted-authority-item", "name": "granted_authority_item", "description": "A single conferred decision right with its qualifiers and limits.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "de-approval-limit", "name": "approval_limit", "description": "Quantitative ceiling on approvals the assignee may make, with unit and currency where applicable.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-authority-validity-period", "name": "authority_validity_period", "description": "Start and end of an individual authority grant, independent of the assignment period.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-001" ] } ], "artifacts": [ { "id": "delegation-of-authority-instrument", "name": "Delegation of authority instrument", "description": "The governed instrument conferring named decision rights and limits on an assignee, recording grantor, grantee, scope, limits, validity period and any conditions or compensating controls.", "media_or_form": [ "signed instrument", "structured record", "register entry" ], "serial": true, "identity_strategy": "Instrument identifier issued by the authority register, referencing the assignment_id; superseded instruments are retained and marked, never overwritten.", "source_refs": [ "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "supervision-reporting-and-delegation", "name": "Supervision, reporting lines and delegation", "description": "To whom the assignee reports for this assignment, who may change or end it, whether work or authority may be delegated or forwarded, and how acting cover is recorded when the assignee is unavailable.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ], "questions": [ { "id": "q-super-reportsto", "text": "To whom does the assignee report for this assignment, and is there more than one reporting line?", "kind": "relationship", "answer_data": [ "Reports-to references", "Reporting line type per reference", "Precedence where lines conflict" ] }, { "id": "q-super-controller", "text": "Who may amend, suspend, transfer or terminate this assignment, and is that the same party as the reporting line?", "kind": "authority", "answer_data": [ "Controlling agent references", "Permitted actions per controller", "Basis for the control right" ] }, { "id": "q-super-delegation", "text": "May the assignee delegate or forward the work or the authority, to whom, and does accountability transfer with it?", "kind": "authority", "answer_data": [ "Delegation permitted flag", "Eligible delegate set", "Accountability transfer rule" ] }, { "id": "q-super-acting", "text": "How is temporary acting cover recorded when the assignee is absent, and does the original assignment remain active during it?", "kind": "process", "answer_data": [ "Acting cover assignment reference", "Cover period", "Status of the covered assignment" ] } ], "data_elements": [ { "id": "de-reports-to-ref", "name": "reports_to_ref", "description": "Agent or post to which the assignee reports for this assignment.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-reporting-line-type", "name": "reporting_line_type_code", "description": "Nature of each reporting line, such as line management, functional or operational command.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-012" ] }, { "id": "de-delegation-permitted", "name": "delegation_permitted", "description": "Whether work or authority under this assignment may be delegated or forwarded.", "value_kind": "boolean", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "de-delegate-ref", "name": "delegate_ref", "description": "Agent currently acting on behalf of the assignee under a delegation.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-003" ] } ], "artifacts": [], "inline_only_rationale": "Reporting and delegation are relationship attributes evaluated at query time. Where a delegation is formalized it is captured by the delegation of authority instrument in the sibling finding, so no additional artifact is warranted." }, { "id": "effort-allocation-and-capacity", "name": "Effort allocation and capacity share", "description": "The share of the assignee's capacity the assignment consumes, how total allocation is validated across concurrent assignments, and which measure prevails when contracted, scheduled and allocated effort disagree.", "source_refs": [ "SRC-010", "SRC-014", "SRC-002" ], "questions": [ { "id": "q-effort-share", "text": "What share of the assignee's capacity does this assignment consume, expressed in which unit and over which reference period?", "kind": "measurement", "answer_data": [ "Allocation value", "Allocation unit", "Reference period" ] }, { "id": "q-effort-validation", "text": "How is total allocation across all of the assignee's concurrent assignments validated, and what is the permitted ceiling?", "kind": "validation", "answer_data": [ "Aggregate allocation", "Ceiling rule", "Validation outcome and exceptions" ] }, { "id": "q-effort-authority", "text": "Which measure is authoritative when contracted hours, scheduled hours and allocated effort disagree?", "kind": "quality", "answer_data": [ "Authoritative measure code", "Precedence rule", "Discrepancy record" ] }, { "id": "q-effort-partperiod", "text": "How is allocation restated for a part-period assignment or one whose allocation changes mid-period?", "kind": "temporal", "answer_data": [ "Effective-dated allocation entries", "Proration rule", "Restated aggregate" ] } ], "data_elements": [ { "id": "de-allocation-value", "name": "allocation_value", "description": "Capacity share consumed by this assignment, such as a full-time-equivalent fraction or hours per reference period.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "de-allocation-basis-code", "name": "allocation_basis_code", "description": "Basis on which allocation is expressed and which measure is authoritative.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-contracted-hours", "name": "contracted_hours_per_period", "description": "Hours the assignment is expected to require over a stated reference period.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [], "inline_only_rationale": "Allocation is a set of effective-dated numeric attributes on the relation. Aggregate capacity reports are derived outputs of the workforce reporting dimension and are not artifacts owned by this model." } ] } ] }, { "id": "assignment-time-and-schedule", "name": "Assignment Time and Schedule", "description": "When the assignment is valid, how it relates to preceding, succeeding and concurrent assignments, the working pattern and availability it carries, and the duty and rest limits that constrain it.", "rationale": "W3C ORG bounds membership with org:memberDuring and FHIR bounds PractitionerRole with a period, but neither prescribes precision or offset handling, and neither models duty limits. RFC 3339 supplies the timestamp discipline and statutory particulars supply the working-pattern requirements.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008", "SRC-010", "SRC-011", "SRC-012" ], "layers": [ { "id": "effective-period-and-succession", "name": "Effective Period and Succession", "description": "Validity boundaries of the assignment and its relation to other assignments in time.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "effective-period-concurrency-and-succession", "name": "Effective period, concurrency and succession", "description": "The assignment's start and end instants and their precision, the separation of real-world effective time from record time, the treatment of backdating and correction, and the relation to concurrent, predecessor and successor assignments.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-time-period", "text": "What are the assignment's effective start and end instants, at what precision, and is an explicit UTC offset or Z recorded on each?", "kind": "temporal", "answer_data": [ "Effective start timestamp", "Effective end timestamp or null", "Precision and offset note" ] }, { "id": "q-time-term", "text": "Is the assignment open-ended, fixed-term or terminated by a defined event, and what exactly ends it?", "kind": "lifecycle", "answer_data": [ "Term type code", "Terminating event definition", "Expected end where known" ] }, { "id": "q-time-bitemporal", "text": "How is the real-world effective time kept separate from the time the record was created, observed or ingested?", "kind": "provenance", "answer_data": [ "Effective time values", "Record creation timestamp", "Ingestion or observation timestamp" ] }, { "id": "q-time-concurrency", "text": "Which other assignments does this agent hold over an overlapping period, are such overlaps permitted, and which assignment precedes and succeeds this one for the same post?", "kind": "relationship", "answer_data": [ "Concurrent assignment references", "Overlap policy outcome", "Predecessor and successor references" ] }, { "id": "q-time-transfer-day", "text": "How is a same-day transfer between posts represented so that headcount and coverage are not double-counted?", "kind": "measurement", "answer_data": [ "Boundary convention (inclusive or exclusive end)", "Counting rule", "Worked example outcome" ] } ], "data_elements": [ { "id": "de-effective-start", "name": "effective_start", "description": "Instant from which the assignment is valid, with explicit offset or Z.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-008", "SRC-001" ] }, { "id": "de-effective-end", "name": "effective_end", "description": "Instant at which the assignment ceases to be valid; absent for open-ended assignments.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008", "SRC-002" ] }, { "id": "de-term-type-code", "name": "term_type_code", "description": "Whether the assignment is open-ended, fixed-term or event-terminated.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-010" ] }, { "id": "de-record-created-at", "name": "record_created_at", "description": "Instant the assignment record was created or ingested, distinct from its effective time.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-008", "SRC-007" ] }, { "id": "de-predecessor-ref", "name": "predecessor_assignment_ref", "description": "Assignment that occupied the same post immediately before this one.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-overlap-policy-code", "name": "overlap_policy_code", "description": "Whether overlapping assignments for the same agent or post are permitted, warned or blocked.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [], "inline_only_rationale": "Temporal boundaries and succession links are inline scalar values and references. The evidencing documents for a start or end are the assignment instrument and the change statement held elsewhere in the model." } ] }, { "id": "working-pattern-and-duty-limits", "name": "Working Pattern and Duty Limits", "description": "The pattern, predictability and availability the assignment carries, and the duty and rest constraints that bound it.", "source_refs": [ "SRC-010", "SRC-002", "SRC-011", "SRC-012" ], "findings": [ { "id": "working-pattern-and-availability", "name": "Working pattern, predictability and availability", "description": "Normal hours and days, whether they are variable or unpredictable, the reference hours and notice that apply where they are, availability and on-call status, and the boundary to the scheduling system that holds concrete instances.", "source_refs": [ "SRC-010", "SRC-002", "SRC-011" ], "questions": [ { "id": "q-pattern-hours", "text": "What normal working hours and days does the assignment carry, and may either the hours or the days vary?", "kind": "temporal", "answer_data": [ "Normal hours descriptor", "Required days of week", "Variability flag and description" ] }, { "id": "q-pattern-unpredictable", "text": "Where the working pattern is unpredictable, what reference hours and days apply and what minimum advance notice of a work assignment is guaranteed?", "kind": "constraint", "answer_data": [ "Reference hours and days", "Minimum notice period", "Consequence of insufficient notice" ] }, { "id": "q-pattern-availability", "text": "How are availability windows, on-call and reserve status expressed and time-bounded for this assignment?", "kind": "state", "answer_data": [ "Availability windows", "Not-available exceptions with reason", "On-call or reserve status code" ] }, { "id": "q-pattern-scheduling-boundary", "text": "Which scheduling or rostering system holds the concrete shift instances, and how does it reference this assignment?", "kind": "interoperability", "answer_data": [ "Scheduling system reference", "Linking identifier and direction", "Reconciliation frequency" ] } ], "data_elements": [ { "id": "de-working-pattern", "name": "working_pattern_descriptor", "description": "Structured description of normal hours, required days and their variability.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-availability-window", "name": "availability_window", "description": "Time window in which the assignee is available under this assignment, with exceptions.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-011" ] }, { "id": "de-notice-period", "name": "minimum_assignment_notice", "description": "Minimum advance notice owed to the assignee before a work period is assigned under an unpredictable pattern.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-schedule-system-ref", "name": "schedule_system_ref", "description": "Reference to the system of record for concrete dated duty instances.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] } ], "artifacts": [ { "id": "duty-schedule-extract", "name": "Duty schedule or roster extract", "description": "A published extract of dated duty or shift instances derived from the assignment, expressed with structured participant and resource entries so that scheduling clients can consume it without re-deriving the assignment.", "media_or_form": [ "calendar interchange object", "structured record", "tabular roster" ], "serial": false, "identity_strategy": "Extract identified by scheduling-system instance identifier plus generation timestamp, always carrying the source assignment_id as a foreign reference.", "source_refs": [ "SRC-011", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "duty-rest-and-limit-constraints", "name": "Duty, rest and time-limit constraints", "description": "Maximum duty and minimum rest limits applicable to the assignment, who verifies fitness and limit compliance before duty, how approved extensions and exceedances are recorded, and how long duty records must be kept.", "source_refs": [ "SRC-010", "SRC-009", "SRC-012" ], "questions": [ { "id": "q-duty-regime", "text": "Which duty and rest limit regime applies to this assignment, and from which legal or sectoral instrument does it derive?", "kind": "constraint", "answer_data": [ "Limit regime reference", "Maximum duty period", "Minimum rest period" ] }, { "id": "q-duty-fitness-check", "text": "Who verifies before a duty period that the assignee is fit for duty and within the applicable limits, and what is recorded?", "kind": "validation", "answer_data": [ "Verifying party", "Verification timestamp", "Verification outcome" ] }, { "id": "q-duty-exception", "text": "What is recorded when a limit is extended or exceeded, and who must approve or be notified?", "kind": "exception", "answer_data": [ "Exceedance record", "Approving agent", "Notification recipients and time" ] }, { "id": "q-duty-retention", "text": "How long must duty, rest and fitness records for this assignment be retained, and by whom?", "kind": "retention", "answer_data": [ "Retention period", "Retention basis", "Custodian" ] } ], "data_elements": [ { "id": "de-duty-limit-rule-ref", "name": "duty_limit_rule_ref", "description": "Reference to the governing duty and rest limitation rule set.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-max-duty-period", "name": "max_duty_period", "description": "Maximum continuous duty period permitted under this assignment.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-min-rest-period", "name": "min_rest_period", "description": "Minimum rest period required before or after duty under this assignment.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-limit-exception-record", "name": "limit_exception_record", "description": "Record of an approved extension or an exceedance of a duty or rest limit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "duty-and-rest-record", "name": "Duty and rest record", "description": "Retained record of duty periods, rest periods, fitness confirmations and any approved extensions relating to an assignment, used to demonstrate compliance with the applicable limit regime.", "media_or_form": [ "structured record", "log", "tabular register" ], "serial": false, "identity_strategy": "Identified by assignment_id plus duty period start instant in RFC 3339 form; entries are append-only and corrections are recorded as new entries referencing the original.", "source_refs": [ "SRC-010", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "assignment-lifecycle-and-change", "name": "Assignment Lifecycle and Change", "description": "How an assignment moves from proposal to end: its states, the events and approvals that move it, how material changes are made and notified, and what must be handed over and revoked when it ends or transfers.", "rationale": "WS-HumanTask demonstrates that assignment-like bindings need an explicit state machine with named operations rather than an implicit active flag, and statutory particulars impose duties when terms materially change. Personnel transfer and termination are the points at which stale authority becomes a real risk.", "source_refs": [ "SRC-003", "SRC-002", "SRC-010", "SRC-004" ], "layers": [ { "id": "states-and-transitions", "name": "States and Transitions", "description": "The permitted state set and the events, actors and preconditions that move an assignment between states.", "source_refs": [ "SRC-003", "SRC-002" ], "findings": [ { "id": "assignment-state-model-and-transitions", "name": "State model, transitions and triggers", "description": "The complete permitted state set including terminal states, whether active status is stored or derived, which events and approvals drive each transition, what happens automatically at the effective end, and how an erroneous transition is reversed.", "source_refs": [ "SRC-003", "SRC-002", "SRC-007" ], "questions": [ { "id": "q-state-set", "text": "What is the complete set of permitted assignment states, which are terminal, and which transitions are forbidden?", "kind": "state", "answer_data": [ "State enumeration", "Terminal state flags", "Forbidden transition list" ] }, { "id": "q-state-derivation", "text": "Is active status stored explicitly, derived from the effective period, or both, and which prevails when they disagree?", "kind": "quality", "answer_data": [ "Status source", "Derivation rule", "Conflict precedence and alert" ] }, { "id": "q-state-triggers", "text": "Which events trigger each transition, which require explicit human approval, and which actor performs them?", "kind": "event", "answer_data": [ "Transition event catalogue", "Approval requirement per transition", "Permitted actor roles" ] }, { "id": "q-state-automatic-end", "text": "What transition occurs automatically at the effective end instant, and what happens if the end data is missing or in the past when discovered?", "kind": "exception", "answer_data": [ "Automatic transition rule", "Missing-end handling", "Late-discovery remediation" ] }, { "id": "q-state-reversal", "text": "How is a transition made in error reversed while preserving the original entry in the audit trail?", "kind": "provenance", "answer_data": [ "Reversal event reference", "Original event retained", "Reason and approver" ] } ], "data_elements": [ { "id": "de-assignment-status-code", "name": "assignment_status_code", "description": "Current lifecycle state of the assignment from the governed state set.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-002" ] }, { "id": "de-status-effective-at", "name": "status_effective_at", "description": "Instant from which the current state applies, with explicit offset or Z.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "de-transition-event", "name": "transition_event", "description": "Recorded state transition with trigger, actor, reason and timestamps.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "de-reversal-of-event-ref", "name": "reversal_of_event_ref", "description": "Reference from a corrective transition to the erroneous transition it reverses.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "assignment-event-log", "name": "Assignment event log", "description": "Append-only log of every lifecycle transition, authority change, access provisioning action and record read or export relating to an assignment, with actor, role, trigger, event time and record time.", "media_or_form": [ "append-only log", "structured record stream" ], "serial": true, "identity_strategy": "Monotonic sequence per assignment_id; each entry carries an event identifier, event time and record time in RFC 3339 form and is never mutated in place.", "source_refs": [ "SRC-003", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "personnel-action-events-and-status-invariance", "name": "Personnel action events", "description": "5 CFR 335.102 authorizes agencies to promote, demote or reassign listed employee categories. Section 335.101 states that a position change does not change competitive status or, with listed exceptions, tenure. Section 335.103 requires merit procedures for covered promotions and details over 120 days, permits retroactive temporary promotion when an appropriate authority so determines, and requires a temporary reconstruction record kept for two years or until OPM evaluation. These events create or replace occupancies.", "source_refs": [ "SRC-017", "SRC-007" ], "questions": [ { "id": "personnel-action-events-and-status-invariance-q01", "text": "Which personnel action created or replaced this occupancy: appointment, promotion, demotion, reassignment, reinstatement, transfer or another governed action?", "kind": "event", "answer_data": [ "action_type", "action_id", "effective_at", "prior_assignment_id" ] }, { "id": "personnel-action-events-and-status-invariance-q02", "text": "Did this position change alter competitive status or tenure, or do the 5 CFR 335.101 rules that status and tenure are unchanged apply?", "kind": "lifecycle", "answer_data": [ "status_changed", "tenure_changed", "exception_applied", "citation" ] }, { "id": "personnel-action-events-and-status-invariance-q03", "text": "Was competition required, and if not which noncompetitive or discretionary exception was used?", "kind": "authority", "answer_data": [ "competition_used", "exception_code", "area_of_consideration", "selection_source" ] }, { "id": "personnel-action-events-and-status-invariance-q04", "text": "What reconstruction record of ratings, ranking and selection is retained, and until when?", "kind": "evidence", "answer_data": [ "reconstruction_record_id", "retention_until", "opm_evaluation_flag" ] } ], "data_elements": [ { "id": "personnel-action-events-and-status-invariance-data01", "name": "Personnel action type", "description": "Coded action that created, amended or ended the occupancy.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-017" ] }, { "id": "personnel-action-events-and-status-invariance-data02", "name": "Prior assignment", "description": "Occupancy replaced by this action, if any.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-017" ] }, { "id": "personnel-action-events-and-status-invariance-data03", "name": "Competition used", "description": "Whether competitive procedures were applied.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-017" ] } ], "artifacts": [ { "id": "personnel-action-events-and-status-invariance-artifact01", "name": "Personnel action notice", "description": "Official notice of promotion, demotion, reassignment or equivalent action, including any reconstruction file.", "media_or_form": [ "SF-50 equivalent notice", "agency personnel action form", "merit promotion reconstruction file" ], "serial": true, "identity_strategy": "Issuer and action or standard-form number from the appointing authority; effective date is an attribute, not the identifier.", "source_refs": [ "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "change-handover-and-exit", "name": "Change, Handover and Exit", "description": "Material change to a live assignment and the controlled exit from it.", "source_refs": [ "SRC-010", "SRC-004", "SRC-003" ], "findings": [ { "id": "amendment-and-material-change", "name": "Amendment and material change", "description": "Which changes may be absorbed as amendments, which require a new record, which are material enough to require written notification within a deadline, and what consent or consultation must precede them.", "source_refs": [ "SRC-010", "SRC-009" ], "questions": [ { "id": "q-change-material", "text": "Which changes to this assignment are material enough to require a written statement of change to the assignee, and by what deadline?", "kind": "requirement", "answer_data": [ "Material change classification", "Notification deadline", "Statement reference" ] }, { "id": "q-change-newrecord", "text": "Which changes create a new assignment record rather than amend the existing one, and why?", "kind": "constraint", "answer_data": [ "New-record trigger list", "Decision taken", "Link to superseded record" ] }, { "id": "q-change-dating", "text": "How is the effective date of each amendment recorded relative to the date the assignee was notified?", "kind": "temporal", "answer_data": [ "Amendment effective timestamp", "Notification timestamp", "Gap justification where notification is later" ] }, { "id": "q-change-consent", "text": "What consent, consultation or representative involvement is required before the change takes effect, and was it obtained?", "kind": "authority", "answer_data": [ "Consent requirement", "Consent or consultation evidence", "Outcome if refused" ] } ], "data_elements": [ { "id": "de-amendment-record", "name": "amendment_record", "description": "A single recorded change to the assignment with field, prior value, new value, effective time and reason.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-material-change-flag", "name": "material_change_flag", "description": "Whether the amendment is material and therefore triggers notification duties.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-notified-at", "name": "change_notified_at", "description": "Instant the assignee was given written notice of the change.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010", "SRC-008" ] } ], "artifacts": [ { "id": "change-to-particulars-statement", "name": "Statement of change to particulars", "description": "Written statement issued to the assignee recording a change to the particulars of the assignment, its effective date and the date it was given, satisfying statutory notification duties where they apply.", "media_or_form": [ "issued written statement", "structured record", "rendered document in any presentation format" ], "serial": true, "identity_strategy": "Sequential statement number per engagement, referencing the assignment_id and the amendment_record entries it covers.", "source_refs": [ "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "handover-coverage-and-offboarding", "name": "Handover, coverage and offboarding", "description": "What must be transferred before an assignment ends, which access rights, delegations and assets must be revoked or reassigned on end or transfer, who covers the scope in the interval, and how completion is evidenced.", "source_refs": [ "SRC-004", "SRC-003", "SRC-012" ], "questions": [ { "id": "q-exit-handover", "text": "What work, records, custody and relationships must be handed over before the assignment ends, and to whom?", "kind": "process", "answer_data": [ "Handover item list", "Receiving agent references", "Handover completion confirmation" ] }, { "id": "q-exit-revocation", "text": "Which access rights, delegated authorities, credentials and physical assets must be revoked or reassigned on end or transfer, and within what time?", "kind": "access", "answer_data": [ "Revocation task list", "Target completion time", "Actual completion timestamps" ] }, { "id": "q-exit-review-on-transfer", "text": "On a transfer rather than a termination, which existing authorizations are re-confirmed as still needed and which are removed?", "kind": "validation", "answer_data": [ "Reviewed authorization list", "Retain or remove decision per item", "Reviewer and review timestamp" ] }, { "id": "q-exit-coverage", "text": "Who covers the scope between the outgoing and the incoming assignee, and under what temporary assignment?", "kind": "process", "answer_data": [ "Coverage assignment reference", "Coverage period", "Residual uncovered risk" ] } ], "data_elements": [ { "id": "de-handover-item", "name": "handover_item", "description": "A single item of work, record or custody transferred at the end of the assignment.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "de-revocation-task-ref", "name": "access_revocation_task_ref", "description": "Reference to a provisioning task revoking or reassigning an access right or delegation.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-offboarding-completed-at", "name": "offboarding_completed_at", "description": "Instant at which all end-of-assignment obligations were confirmed complete.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008", "SRC-004" ] } ], "artifacts": [ { "id": "handover-and-offboarding-record", "name": "Handover and offboarding record", "description": "Checklist-style record evidencing completion of handover, access revocation or re-confirmation, credential return and asset return at the end or transfer of an assignment, with per-item owner and completion time.", "media_or_form": [ "checklist record", "structured record", "signed confirmation" ], "serial": false, "identity_strategy": "Identified by assignment_id plus lifecycle event identifier of the ending or transferring transition.", "source_refs": [ "SRC-004", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "temporary-detail-and-time-limited-forms", "name": "Temporary, acting, detail and time-limited forms", "description": "5 CFR 335.102(f) authorizes time-limited promotions for not more than five years unless OPM authorizes longer, with advance written notice that the employee may be returned at any time to the former or an equivalent position. Details and time-limited promotions over 120 days to higher grades generally require competition, counting prior noncompetitive service in the preceding 12 months. Temporary promotion may become permanent without further competition if originally competed and that possibility was advertised. Acting or interim coverage is a common operational form but is not named as such in the fetched 5 CFR text and must not be claimed as a 5 CFR term.", "source_refs": [ "SRC-017" ], "questions": [ { "id": "temporary-detail-and-time-limited-forms-q01", "text": "What time limit applies to this temporary promotion, detail or acting occupancy, and was advance written notice given?", "kind": "constraint", "answer_data": [ "time_limit", "limit_reason", "notice_given_at", "notice_text_ref", "opm_extension_flag" ] }, { "id": "temporary-detail-and-time-limited-forms-q02", "text": "May the occupant be returned at any time to the former or an equivalent position, and is that return exempt from adverse-action procedures cited in 5 CFR 335.102(f)?", "kind": "lifecycle", "answer_data": [ "return_at_any_time", "return_position_id", "procedure_exemption_flag" ] }, { "id": "temporary-detail-and-time-limited-forms-q03", "text": "How many days of noncompetitive higher-grade detail or time-limited promotion have accrued in the preceding 12 months, and is further competition required?", "kind": "constraint", "answer_data": [ "accrued_noncompetitive_days", "window_start", "competition_now_required" ] }, { "id": "temporary-detail-and-time-limited-forms-q04", "text": "Was the temporary occupancy originally competed with notice that it might become permanent, allowing conversion without further competition?", "kind": "decision", "answer_data": [ "originally_competed", "permanence_possibility_advertised", "conversion_allowed" ] } ], "data_elements": [ { "id": "temporary-detail-and-time-limited-forms-data01", "name": "Time limit", "description": "Stated limit of a time-limited occupancy.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-017" ] }, { "id": "temporary-detail-and-time-limited-forms-data02", "name": "Return position", "description": "Position or equivalent grade to which the occupant may be returned.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-017" ] }, { "id": "temporary-detail-and-time-limited-forms-data03", "name": "Accrued noncompetitive days", "description": "Prior noncompetitive higher-grade service counted toward the 120-day threshold.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-017" ] } ], "artifacts": [ { "id": "temporary-detail-and-time-limited-forms-artifact01", "name": "Time-limited promotion or detail notice", "description": "Advance written notice of conditions, time limit, competition requirement and return terms.", "media_or_form": [ "written notice", "personnel action remark", "detail memorandum" ], "serial": true, "identity_strategy": "Issuing agency notice number; time limit is an attribute, not identity.", "source_refs": [ "SRC-017" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "assignment-eligibility-and-controls", "name": "Assignment Eligibility and Controls", "description": "What must be true before an assignment may be made or continued: competence, credentials and fitness, screening and right to work, and the separation, conflict, cardinality and coverage constraints that bound valid assignment.", "rationale": "RBAC makes separation of duty and cardinality first-class constraints on user assignment, and the AI Act requires competence, training and authority together with support before oversight duties are assigned. Both establish that eligibility is a checkable precondition of the binding, not an attribute of the person alone.", "source_refs": [ "SRC-004", "SRC-009", "SRC-006", "SRC-002" ], "layers": [ { "id": "eligibility-preconditions", "name": "Eligibility Preconditions", "description": "Competence, credential, fitness, screening and legal-permission preconditions of the assignment.", "source_refs": [ "SRC-009", "SRC-006", "SRC-002" ], "findings": [ { "id": "competence-credential-and-fitness", "name": "Competence, credentials, training and fitness", "description": "The competences, qualifications, licences, training and fitness required before this assignment may be held; how each is verified and evidenced; and what happens to the assignment when a prerequisite expires, is suspended or is revoked.", "source_refs": [ "SRC-009", "SRC-006", "SRC-002" ], "questions": [ { "id": "q-elig-required", "text": "Which competences, qualifications, licences and training are prerequisites for this assignment, and which are merely desirable?", "kind": "requirement", "answer_data": [ "Required competence references", "Requirement level per item", "Source of the requirement" ] }, { "id": "q-elig-verification", "text": "How and when was each prerequisite verified, by whom, and what evidence is held and where?", "kind": "evidence", "answer_data": [ "Verification method", "Verifier and verification timestamp", "Evidence location reference" ] }, { "id": "q-elig-expiry", "text": "What happens to the assignment when a required credential expires, is suspended or is revoked, and how far in advance is expiry surfaced?", "kind": "lifecycle", "answer_data": [ "Credential expiry dates", "Automatic status consequence", "Advance warning interval" ] }, { "id": "q-elig-authority-and-support", "text": "Beyond skill, does the assignee have the authority and the practical support needed to discharge the assignment, and how is that established?", "kind": "authority", "answer_data": [ "Authority sufficiency assessment", "Support arrangements", "Assessor and assessment date" ] } ], "data_elements": [ { "id": "de-required-competence-ref", "name": "required_competence_ref", "description": "Reference to a competence, qualification or licence required for the assignment.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "de-credential-expiry", "name": "credential_expiry_date", "description": "Expiry date of a verified prerequisite credential.", "value_kind": "date", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-competence-verified-at", "name": "competence_verified_at", "description": "Instant at which prerequisite verification was completed for this assignment.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009", "SRC-008" ] } ], "artifacts": [ { "id": "eligibility-verification-record", "name": "Eligibility verification record", "description": "Record showing, per prerequisite, what was required, what evidence was checked, by whom, when, the outcome and the next re-verification date; the artifact holds pointers and outcomes rather than copies of sensitive underlying documents.", "media_or_form": [ "structured record", "signed attestation" ], "serial": false, "identity_strategy": "Identified by assignment_id plus prerequisite reference plus verification timestamp; superseded verifications are retained for audit.", "source_refs": [ "SRC-009", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "screening-clearance-and-right-to-work", "name": "Screening, clearance and permission to work", "description": "The screening, vetting or security clearance level the assignment requires, the legal right to work or professional registration in the work jurisdiction, re-screening triggers, and how outcomes are surfaced without exposing sensitive underlying results.", "source_refs": [ "SRC-004", "SRC-010", "SRC-009" ], "questions": [ { "id": "q-screen-level", "text": "What screening, vetting or clearance level does this assignment require, and on what risk designation is that based?", "kind": "security", "answer_data": [ "Required clearance level", "Risk designation of the post", "Basis reference" ] }, { "id": "q-screen-righttowork", "text": "What legal right to work or professional registration is required in the work jurisdiction, and until when is it valid?", "kind": "constraint", "answer_data": [ "Permission type", "Valid-until date", "Jurisdiction" ] }, { "id": "q-screen-recheck", "text": "Who is accountable for re-screening, and at what interval or on which triggering events?", "kind": "ownership", "answer_data": [ "Accountable role", "Re-screening interval", "Triggering events" ] }, { "id": "q-screen-failure", "text": "How is a failed, lapsed or downgraded check handled without exposing the underlying sensitive result to assignment consumers?", "kind": "privacy", "answer_data": [ "Status-only disclosure rule", "Consequential assignment action", "Escalation recipients" ] } ], "data_elements": [ { "id": "de-required-clearance-level", "name": "required_clearance_level", "description": "Clearance or vetting level the assignment requires.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-clearance-status-code", "name": "clearance_status_code", "description": "Current status of the assignee's clearance for this assignment, expressed as status only.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-permission-valid-until", "name": "work_permission_valid_until", "description": "Date until which the assignee's legal permission to work in the relevant jurisdiction is valid.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [], "inline_only_rationale": "Screening and clearance results are held by a separate vetting system of record under stricter access rules. This model deliberately carries only a required level, a status code and a validity date as inline reference data, so producing an artifact here would duplicate and over-expose sensitive material." } ] }, { "id": "constraints-and-validation", "name": "Constraints and Validation", "description": "Separation of duty, conflict of interest, cardinality, coverage and the rules that make an assignment valid or blocked.", "source_refs": [ "SRC-004", "SRC-001", "SRC-003" ], "findings": [ { "id": "separation-conflict-cardinality-and-validation", "name": "Separation of duty, conflict, cardinality and validation rules", "description": "Which assignments may not be held together, which may be held but not exercised together, which conflicts of interest must be declared, how many holders a post may have, what minimum coverage is required, and how blocking rules, warnings, exceptions and pre-existing violations are handled.", "source_refs": [ "SRC-004", "SRC-001", "SRC-003" ], "questions": [ { "id": "q-ctrl-ssd", "text": "Which other roles or assignments may this assignee not hold at the same time under a static separation rule?", "kind": "constraint", "answer_data": [ "Mutually exclusive role references", "Rule reference", "Check outcome" ] }, { "id": "q-ctrl-dsd", "text": "Which role combinations may be held but not activated or exercised together in a single session or transaction?", "kind": "constraint", "answer_data": [ "Dynamic exclusion set", "Activation constraint rule", "Enforcement point" ] }, { "id": "q-ctrl-cardinality", "text": "How many concurrent holders may this post or role have, what minimum coverage must exist, and what happens when either bound is breached?", "kind": "constraint", "answer_data": [ "Maximum concurrent holders", "Minimum required coverage", "Breach handling action" ] }, { "id": "q-ctrl-conflict-declaration", "text": "Which conflicts of interest or related-party relationships must be declared before the assignment is made, and were they?", "kind": "validation", "answer_data": [ "Declaration requirement", "Declared conflicts", "Mitigation decided" ] }, { "id": "q-ctrl-exception", "text": "Which validation rules are blocking rather than advisory, who may grant an exception, and how are pre-existing violations of a newly introduced rule treated?", "kind": "exception", "answer_data": [ "Blocking versus warning classification", "Exception grant with approver and expiry", "Grandfathering status and remediation plan" ] } ], "data_elements": [ { "id": "de-mutually-exclusive-role-ref", "name": "mutually_exclusive_role_ref", "description": "Role or assignment that may not be held concurrently with this one.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-max-concurrent-holders", "name": "max_concurrent_holders", "description": "Maximum number of agents that may hold the post or role at one time.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-001" ] }, { "id": "de-min-required-coverage", "name": "min_required_coverage", "description": "Minimum number of concurrent holders required for continuity of the role.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "de-validation-outcome", "name": "validation_rule_outcome", "description": "Outcome of a rule evaluation with rule reference, severity, result and any granted exception.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-exception-expiry", "name": "exception_expires_at", "description": "Instant at which a granted validation exception lapses and the rule applies again.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008", "SRC-004" ] } ], "artifacts": [ { "id": "conflict-and-exception-register-entry", "name": "Conflict and exception register entry", "description": "Register entry recording a declared conflict of interest or a granted exception to a separation, cardinality or coverage rule, with the approver, the compensating control, the justification and a mandatory expiry.", "media_or_form": [ "register entry", "structured record", "signed declaration" ], "serial": true, "identity_strategy": "Sequential register number issued by the controls register, referencing the assignment_id and the rule reference; entries are immutable once approved and are closed rather than deleted.", "source_refs": [ "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "assignment-evidence-governance-and-interoperability", "name": "Assignment Evidence, Governance and Interoperability", "description": "How the assignment is proved to have been properly made, what must be told to whom, how the record is protected, retained and deleted, and how it is aligned to external representations and projected to downstream consumers.", "rationale": "PROV-O supplies the qualified association pattern that makes authorization auditable; statutory duties require written particulars and prior information to workers and their representatives; and the divergence between W3C ORG, FHIR, schema.org and HR Open shows that interoperability must be recorded as a mapping with known losses, never assumed.", "source_refs": [ "SRC-007", "SRC-010", "SRC-009", "SRC-001", "SRC-002", "SRC-005", "SRC-013", "SRC-014" ], "layers": [ { "id": "authorization-evidence-and-notification", "name": "Authorization Evidence and Notification", "description": "Who authorized the assignment and on what basis, and who had to be told about it.", "source_refs": [ "SRC-007", "SRC-010", "SRC-009" ], "findings": [ { "id": "authorization-and-approval-evidence", "name": "Authorization, basis and approval evidence", "description": "Who authorized the assignment, acting in which role and at what time, on what documented basis, whether that authorizer was competent to authorize an assignment of this type and authority level, and how the approval chain survives the authorizer's own departure.", "source_refs": [ "SRC-007", "SRC-004", "SRC-012" ], "questions": [ { "id": "q-auth-who", "text": "Which agent authorized this assignment, acting in which role, and at what instant?", "kind": "provenance", "answer_data": [ "Authorizing agent reference", "Role held at the time of authorization", "Authorization timestamp" ] }, { "id": "q-auth-basis", "text": "On what documented basis was the assignment authorized, such as a requisition, funded establishment, staffing order or operational plan?", "kind": "evidence", "answer_data": [ "Authorization basis references", "Basis type code", "Funding or budget confirmation" ] }, { "id": "q-auth-competence", "text": "Was the authorizer permitted to authorize an assignment of this type, scope and authority level, and how was that checked?", "kind": "validation", "answer_data": [ "Authorizer authority check outcome", "Authorizing assignment reference", "Escalation where insufficient" ] }, { "id": "q-auth-durability", "text": "How is the approval chain preserved and interpretable after the authorizer's own assignment or employment ends?", "kind": "provenance", "answer_data": [ "Point-in-time role snapshot", "Retention rule for authorizer context", "Resolution method for historic references" ] } ], "data_elements": [ { "id": "de-authorized-by-ref", "name": "authorized_by_agent_ref", "description": "Agent who authorized the assignment.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-authorizer-role-ref", "name": "authorizer_role_ref", "description": "Role in which the authorizing agent acted at the time of authorization.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-authorized-at", "name": "authorized_at", "description": "Instant of authorization, with explicit offset or Z.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-008", "SRC-007" ] }, { "id": "de-authorization-basis-ref", "name": "authorization_basis_ref", "description": "Reference to the requisition, order, plan or budget approval that justified the assignment.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012", "SRC-014" ] } ], "artifacts": [ { "id": "assignment-approval-record", "name": "Assignment approval record", "description": "Immutable record of the approval decision capturing the authorizing agent, the role held at the time, the basis references, the decision, the timestamp and any conditions attached to the approval.", "media_or_form": [ "structured record", "signed approval", "workflow decision entry" ], "serial": true, "identity_strategy": "Approval identifier issued by the approving workflow, bound to the assignment_id and to a point-in-time snapshot of the authorizer's role.", "source_refs": [ "SRC-007", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "acknowledgement-notification-and-disclosure", "name": "Acknowledgement, notification and disclosure duties", "description": "Whether the assignee received the required written particulars within the deadline, whether acceptance is a precondition of activation, and which third parties - workers' representatives, host organizations, clients or regulators - must be informed, including prior information where the assignment places the worker under a high-risk automated system.", "source_refs": [ "SRC-010", "SRC-009", "SRC-014" ], "questions": [ { "id": "q-notify-particulars", "text": "Was the assignee given the required written particulars of the assignment, in what form, and by which deadline relative to the start?", "kind": "requirement", "answer_data": [ "Statement issued timestamp", "Delivery form", "Deadline compliance outcome" ] }, { "id": "q-notify-acceptance", "text": "Did the assignee acknowledge or accept the assignment, and is acceptance a precondition of activation?", "kind": "evidence", "answer_data": [ "Acknowledgement status", "Acknowledgement timestamp", "Activation dependency rule" ] }, { "id": "q-notify-thirdparty", "text": "Which third parties must be notified that this assignment exists, with what content, and by when?", "kind": "access", "answer_data": [ "Notified party references", "Disclosed content set", "Notification deadlines and actual times" ] }, { "id": "q-notify-ai-oversight", "text": "Where the assignment places the worker under a high-risk automated system, were the affected workers and their representatives informed before the system was put into use?", "kind": "requirement", "answer_data": [ "Prior information event", "Recipients including representatives", "Evidence reference" ] } ], "data_elements": [ { "id": "de-statement-issued-at", "name": "written_statement_issued_at", "description": "Instant the written particulars of the assignment were given to the assignee.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010", "SRC-008" ] }, { "id": "de-acknowledgement-status", "name": "acknowledgement_status_code", "description": "Whether the assignee has acknowledged, accepted, declined or not yet responded.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "de-disclosure-event", "name": "disclosure_event", "description": "A recorded notification to a third party with recipient, content set, deadline and actual time.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-014" ] } ], "artifacts": [ { "id": "written-statement-of-particulars", "name": "Written statement of assignment particulars", "description": "The statement given to the assignee setting out the particulars of the assignment - title or description of the work, place or places of work, start date, term, hours and days including whether they may vary, probation and training - in whatever presentation form the jurisdiction accepts.", "media_or_form": [ "issued written statement", "structured record", "rendered document in any presentation format" ], "serial": true, "identity_strategy": "Statement number issued per engagement, referencing the assignment_id and superseded by numbered statements of change rather than being edited.", "source_refs": [ "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "privacy-retention-and-access", "name": "Privacy, Retention and Access", "description": "Protection, visibility, retention and deletion of the assignment record and its evidence.", "source_refs": [ "SRC-009", "SRC-010", "SRC-004" ], "findings": [ { "id": "personal-data-classification-and-access", "name": "Personal data classification and access scoping", "description": "Which assignment fields are personal or specially protected, the lawful basis for each, which roles may see the full record versus only the non-personal scope and period, and what is logged when the record is read, exported or changed.", "source_refs": [ "SRC-009", "SRC-004", "SRC-010" ], "questions": [ { "id": "q-priv-classify", "text": "Which fields of this assignment record constitute personal data or specially protected data, and what is the lawful basis for processing each?", "kind": "privacy", "answer_data": [ "Field sensitivity classification", "Lawful basis per class", "Basis owner" ] }, { "id": "q-priv-visibility", "text": "Which roles may read the full record, and which may read only the post, scope and period without the assignee's identity or terms?", "kind": "access", "answer_data": [ "Access scope per role", "Redaction rule", "Default when no rule matches" ] }, { "id": "q-priv-transparency", "text": "How is the assignment published for organizational transparency without disclosing protected attributes or inferring them from adjacent fields?", "kind": "privacy", "answer_data": [ "Publishable projection definition", "Inference risk assessment", "Suppression thresholds" ] }, { "id": "q-priv-logging", "text": "What is recorded when an assignment record is read, exported or amended, and how long is that log kept?", "kind": "security", "answer_data": [ "Logged event types", "Log fields including actor and time", "Log retention period" ] } ], "data_elements": [ { "id": "de-data-sensitivity-class", "name": "data_sensitivity_class", "description": "Sensitivity classification applied to a field or field group of the assignment record.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-lawful-basis-code", "name": "lawful_basis_code", "description": "Recorded lawful basis for processing a classified field group.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-access-scope-rule", "name": "access_scope_rule", "description": "Rule binding a requesting role to the subset of the assignment record it may read.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [], "inline_only_rationale": "Classification and access scoping are metadata expressed as inline codes and rules; the evidentiary output is the assignment event log already defined in the lifecycle bundle, so a second artifact would duplicate it." }, { "id": "retention-deletion-and-legal-hold", "name": "Retention, deletion and legal hold", "description": "How long the assignment record and its evidence must be kept and on what basis, what may be deleted or anonymized while preserving organizational history, how a legal hold suspends deletion, and what survives erasure of the underlying person record.", "source_refs": [ "SRC-009", "SRC-010", "SRC-004" ], "questions": [ { "id": "q-ret-period", "text": "How long must the assignment record and each class of associated evidence be retained after the assignment ends, and under which rule or minimum?", "kind": "retention", "answer_data": [ "Retention period per class", "Retention rule reference", "Retention-until date" ] }, { "id": "q-ret-minimisation", "text": "Which parts of the record may be deleted or anonymized at end of retention while preserving the organizational and succession history?", "kind": "retention", "answer_data": [ "Deletable field set", "Preserved skeleton definition", "Anonymization method" ] }, { "id": "q-ret-hold", "text": "How does a legal hold or investigation suspend deletion, who may impose and lift it, and how is the suspension evidenced?", "kind": "exception", "answer_data": [ "Hold status and scope", "Imposing and lifting authority", "Hold audit entries" ] }, { "id": "q-ret-erasure", "text": "When the underlying person record is erased on request, what remains of the assignment and under what justification?", "kind": "privacy", "answer_data": [ "Surviving elements", "Justification for retention", "De-identification applied" ] } ], "data_elements": [ { "id": "de-retention-rule-ref", "name": "retention_rule_ref", "description": "Reference to the retention rule governing a class of assignment data or evidence.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-retention-until", "name": "retention_until", "description": "Date until which the record or evidence class must be retained.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-legal-hold-status", "name": "legal_hold_status", "description": "Whether deletion is currently suspended by a hold and under whose authority.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-deletion-method-code", "name": "deletion_method_code", "description": "Whether end-of-retention treatment is deletion, anonymization or reduction to a preserved skeleton.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "retention-schedule-entry", "name": "Retention schedule entry", "description": "Governed entry stating, for each class of assignment data and evidence, the retention period, its legal or policy basis, the disposal method and the hold conditions that suspend disposal.", "media_or_form": [ "schedule entry", "structured record", "policy register entry" ], "serial": false, "identity_strategy": "Identified by data class plus jurisdiction plus schedule version; versions are retained so that historic disposal decisions remain explicable.", "source_refs": [ "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "interoperability-and-projection", "name": "Interoperability and Projection", "description": "Mapping to external representations and delivery to downstream consumers.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-013", "SRC-014", "SRC-011" ], "findings": [ { "id": "standard-alignment-and-downstream-projection", "name": "Standard alignment, external identifiers and downstream projection", "description": "Which external representations the assignment is mapped to and where those mappings lose information, which external identifiers are held and which prevails on conflict, which downstream systems consume the assignment, and how divergence is reconciled rather than silently absorbed.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-013", "SRC-014", "SRC-004" ], "questions": [ { "id": "q-interop-mapping", "text": "Which external standard representations is this assignment mapped to, at what version, and which of its fields have no counterpart in each?", "kind": "interoperability", "answer_data": [ "Target standard and version", "Field-level mapping table", "Unmapped field list" ] }, { "id": "q-interop-identifiers", "text": "Which external identifiers exist for the same assignment, and which is authoritative when two systems disagree?", "kind": "identity", "answer_data": [ "External identifier values with issuing system", "Precedence rule", "Conflict resolution record" ] }, { "id": "q-interop-downstream", "text": "Which downstream systems consume this assignment - directory, access management, payroll, scheduling, statutory register - and how and how often are they reconciled?", "kind": "interoperability", "answer_data": [ "Consumer system references", "Projection contract per consumer", "Reconciliation frequency and last result" ] }, { "id": "q-interop-conflict", "text": "Where a target standard conflicts with a local requirement or the mapping is lossy, how is the conflict recorded so that it is visible to consumers rather than hidden?", "kind": "quality", "answer_data": [ "Conflict description", "Decision taken", "Consumer-visible caveat" ] } ], "data_elements": [ { "id": "de-external-standard-mapping", "name": "external_standard_mapping", "description": "A mapping entry to an external representation with target standard, version, field correspondence and known losses.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "de-external-assignment-id", "name": "external_assignment_id", "description": "Identifier for this assignment issued by an external or downstream system.", "value_kind": "identifier", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014", "SRC-013" ] }, { "id": "de-downstream-system-ref", "name": "downstream_system_ref", "description": "Reference to a system that consumes a projection of this assignment.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-011" ] }, { "id": "de-mapping-conflict-note", "name": "mapping_conflict_note", "description": "Recorded conflict or loss arising from a mapping, kept visible to consumers.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-013" ] } ], "artifacts": [ { "id": "assignment-crosswalk", "name": "Assignment crosswalk and projection contract", "description": "Published crosswalk from the assignment model to each external representation and downstream consumer, stating field correspondences, transformations, known losses, recorded conflicts and the reconciliation procedure.", "media_or_form": [ "mapping table", "structured record", "published specification in any presentation format" ], "serial": false, "identity_strategy": "Identified by source model version plus target standard identifier and version; each crosswalk version is retained so historic exchanges remain explicable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "propose-assignment", "name": "Propose assignment", "description": "Create a candidate assignment binding an agent, an organization, a role or post, a scope and a period, without conferring any authority.", "inputs": [ "Assignee agent reference", "Organization or unit reference", "Post or role reference", "Proposed effective period", "Work scope statement", "Proposed allocation" ], "outputs": [ "Assignment record in proposed state", "Assignment identifier", "Initial validation report" ], "preconditions": [ "Referenced agent, organization and post resolve to existing records", "Proposer holds an assignment permitting proposal for the target unit" ], "effects": [ "A new assignment record exists in a non-authoritative proposed state", "A creation event is appended to the assignment event log", "No access rights or authorities are provisioned" ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "validate-assignment-eligibility", "name": "Validate assignment eligibility", "description": "Evaluate all prerequisite and constraint rules for a candidate or live assignment and classify each outcome as pass, warning or block.", "inputs": [ "Assignment identifier", "Rule set version", "Evaluation instant" ], "outputs": [ "Per-rule validation outcomes with severity", "Blocking issue list", "Required exception list" ], "preconditions": [ "Prerequisite references and credential statuses are resolvable", "Separation, cardinality and coverage rules are published and versioned" ], "effects": [ "Validation outcomes are recorded against the assignment with the rule set version", "Blocking outcomes prevent activation until resolved or excepted" ], "source_refs": [ "SRC-004", "SRC-009", "SRC-006" ] }, { "id": "authorize-assignment", "name": "Authorize assignment", "description": "Record a competent authorization decision for a validated assignment, together with its basis and any conditions.", "inputs": [ "Assignment identifier", "Authorizing agent reference", "Authorization basis references", "Decision and conditions" ], "outputs": [ "Approval record", "Authorized assignment state", "Authorizer competence check outcome" ], "preconditions": [ "No unresolved blocking validation outcome", "Authorizing agent holds a current assignment conferring authority at the required level and scope" ], "effects": [ "An immutable approval record is created with a point-in-time snapshot of the authorizer's role", "The assignment moves to an authorized state and becomes eligible for activation" ], "source_refs": [ "SRC-007", "SRC-004" ] }, { "id": "activate-assignment", "name": "Activate assignment", "description": "Bring an authorized assignment into force at its effective start, conferring the recorded authority and triggering downstream provisioning.", "inputs": [ "Assignment identifier", "Activation instant", "Acknowledgement status where required" ], "outputs": [ "Active assignment state", "Provisioning instructions for downstream consumers", "Activation event entry" ], "preconditions": [ "Assignment is authorized and the effective start has been reached or is being set", "Any acknowledgement precondition is satisfied", "Prerequisite credentials are valid at the activation instant" ], "effects": [ "The assignment becomes exercisable and appears in effective-assignment queries", "Downstream provisioning is requested and reconciliation is scheduled" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-002" ] }, { "id": "amend-assignment", "name": "Amend assignment", "description": "Apply an effective-dated change to a live assignment, classify its materiality and trigger any notification duty.", "inputs": [ "Assignment identifier", "Changed fields with new values", "Amendment effective instant", "Reason" ], "outputs": [ "Amendment record", "Materiality classification", "Notification obligation with deadline" ], "preconditions": [ "Change does not fall within the new-record trigger set", "Actor holds authority to amend the assignment" ], "effects": [ "Prior values are preserved and the amendment is effective-dated", "A statement of change is required where the amendment is material", "Re-validation is triggered for affected rules" ], "source_refs": [ "SRC-010", "SRC-004" ] }, { "id": "suspend-or-resume-assignment", "name": "Suspend or resume assignment", "description": "Temporarily render an assignment non-exercisable, or restore it, without ending it.", "inputs": [ "Assignment identifier", "Suspend or resume action", "Reason code", "Effective instant" ], "outputs": [ "Updated assignment state", "Authority suspension or restoration instructions", "Event entry" ], "preconditions": [ "Assignment is currently active or suspended as appropriate", "Actor holds authority to suspend or resume" ], "effects": [ "Conferred authorities become non-exercisable on suspension and are restored on resume", "The effective period is unchanged and the assignment remains counted as existing" ], "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "delegate-assignment-authority", "name": "Delegate assignment authority", "description": "Record that another agent acts on behalf of the assignee for named authorities over a bounded period.", "inputs": [ "Assignment identifier", "Delegate agent reference", "Delegated authority items", "Delegation period" ], "outputs": [ "Delegation instrument", "Updated exercisable-authority view", "Accountability statement" ], "preconditions": [ "Delegation is permitted for this assignment and for each named authority", "Delegate passes separation of duty and eligibility checks" ], "effects": [ "The delegate may exercise the named authorities within the period", "Accountability remains with the assignee unless the instrument states transfer", "The delegation lapses automatically at period end or on suspension of the assignment" ], "source_refs": [ "SRC-007", "SRC-003", "SRC-004" ] }, { "id": "transfer-or-succeed-assignment", "name": "Transfer or succeed assignment", "description": "End one assignment and start another for the same post or scope with an explicit succession link and a coverage decision for any interval.", "inputs": [ "Outgoing assignment identifier", "Incoming assignee reference", "Boundary instant", "Coverage arrangement" ], "outputs": [ "Ended outgoing assignment", "New incoming assignment", "Succession link and coverage record" ], "preconditions": [ "Boundary convention for inclusive or exclusive end is defined", "Incoming assignment passes eligibility validation" ], "effects": [ "Predecessor and successor references are recorded on both assignments", "Existing authorizations are reviewed and either re-confirmed or removed", "Headcount and coverage measures are computed without double counting" ], "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "end-assignment", "name": "End assignment and offboard", "description": "Close an assignment at its effective end and drive handover, revocation and evidence capture.", "inputs": [ "Assignment identifier", "Effective end instant", "End reason code" ], "outputs": [ "Ended assignment state", "Handover and offboarding record", "Revocation task set with deadlines" ], "preconditions": [ "Actor holds authority to end the assignment or the end is an automatic consequence of the effective end" ], "effects": [ "All conferred authorities and delegations lapse", "Access revocation or reassignment tasks are raised and tracked to completion", "Retention clocks start for the record and its evidence classes" ], "source_refs": [ "SRC-004", "SRC-003", "SRC-009" ] }, { "id": "resolve-effective-assignments", "name": "Resolve effective assignments as of an instant", "description": "Return the set of assignments in force for an agent, post or unit at a given instant, using stored state and effective periods with a declared precedence rule.", "inputs": [ "Query subject reference", "Evaluation instant in RFC 3339 form", "Requested access scope" ], "outputs": [ "Effective assignment set with roles, scopes and authorities", "Precedence and conflict notes", "Redaction applied for the requester's scope" ], "preconditions": [ "Effective periods carry explicit offsets", "Status derivation precedence is defined" ], "effects": [ "A point-in-time answer is produced without mutating any record", "The read is recorded in the audit log with actor, scope and instant" ], "source_refs": [ "SRC-008", "SRC-001", "SRC-002" ] }, { "id": "detect-assignment-conflicts", "name": "Detect assignment conflicts", "description": "Scan the assignment population for separation of duty breaches, cardinality and coverage violations, capacity over-allocation, overlaps and expired prerequisites.", "inputs": [ "Scope of scan", "Rule set version", "Evaluation window" ], "outputs": [ "Conflict findings with severity and affected assignments", "Coverage gap list", "Expiring prerequisite list" ], "preconditions": [ "Rules are published with a version identifier", "Concurrent assignments and allocations are resolvable for each agent" ], "effects": [ "Findings are recorded with the rule set version so historic results remain explicable", "Findings above threshold raise remediation tasks with owners and due dates" ], "source_refs": [ "SRC-004", "SRC-001" ] }, { "id": "project-assignment-to-consumer", "name": "Project assignment to a downstream consumer", "description": "Emit a consumer-specific representation of the assignment under a published crosswalk and reconcile the consumer's state against this model.", "inputs": [ "Assignment identifier", "Target consumer or standard identifier", "Crosswalk version" ], "outputs": [ "Consumer-shaped representation", "Known-loss and conflict caveats", "Reconciliation difference report" ], "preconditions": [ "A published crosswalk exists for the target at the stated version", "Access scope permits disclosure of the projected fields to that consumer" ], "effects": [ "The consumer receives a representation with explicit caveats rather than a silently lossy copy", "Differences found on reconciliation are recorded rather than auto-overwritten" ], "source_refs": [ "SRC-002", "SRC-005", "SRC-011", "SRC-013" ] }, { "id": "establish-temporary-or-time-limited-assignment", "name": "Establish detail or time-limited promotion", "description": "Create a time-bounded higher-grade or other temporary occupancy with notice of return terms and 120-day competition accounting.", "inputs": [ "home assignment identifier", "temporary post or role", "time limit", "accrued noncompetitive days", "written notice" ], "outputs": [ "temporary assignment identifier", "return position reference", "competition-required flag" ], "preconditions": [ "Advance written notice is given, or a nondiscretionary promotion records notice as soon as possible.", "Time limit does not exceed five years unless a higher authorization exists." ], "effects": [ "A temporary occupancy exists alongside or instead of the home occupancy as locally modelled.", "Return to the former or equivalent position remains available as specified in the notice." ], "source_refs": [ "SRC-017" ] } ], "composition": [ { "target": "WM-ORG-004 Position", "relation": "REFERENCE", "purpose": "The assignment cites the post it occupies; the post's definition, grading and description remain owned by WM-ORG-004. Direction: WM-ORG-016 points outward to WM-ORG-004, complementing the registered COMPOSE relation in which a position is occupied through a scoped assignment.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-ORG-005 Employment Relationship", "relation": "REFERENCE", "purpose": "The assignment cites the engagement that gives it a basis. Marked not required because agency-supplied, contracted and volunteer assignments rest on a commercial or non-employment arrangement instead; what is required is some engagement context, not specifically an employment relationship.", "required": false, "source_refs": [ "SRC-014", "SRC-010" ] }, { "target": "Person, party and agent identity model", "relation": "REFERENCE", "purpose": "Supplies the assignee identity, including non-human agents. This model holds only a reference and never duplicates personal master data.", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "Organization and organizational unit model", "relation": "REFERENCE", "purpose": "Supplies the organization or unit in which the assignment is held and, where different, the host organization where the work is performed.", "required": true, "source_refs": [ "SRC-001", "SRC-014" ] }, { "target": "Role, occupation and competence classifier model", "relation": "REFERENCE", "purpose": "Supplies role concepts, occupation codes and the competences that become assignment prerequisites; the classifier owns the concepts, the assignment owns the citation.", "required": false, "source_refs": [ "SRC-006", "SRC-001" ] }, { "target": "Schedule, roster and availability model", "relation": "COMPOSE", "purpose": "Concrete dated duty and shift instances are composed from the assignment's pattern, availability and limits, and reference the assignment identifier.", "required": false, "source_refs": [ "SRC-011", "SRC-002" ] }, { "target": "Access entitlement and identity management model", "relation": "REFERENCE", "purpose": "Consumes the assignment as the temporal and organizational basis for user-to-role assignment, activation and de-provisioning; the permission catalogue and decision engine stay outside this model.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "Place and work location model", "relation": "REFERENCE", "purpose": "Supplies base and additional work locations from which jurisdictional, safety and working-time regimes are derived.", "required": false, "source_refs": [ "SRC-002", "SRC-010" ] }, { "target": "W3C Organization Ontology (org:Membership, org:Post, org:Role)", "relation": "ALIGN", "purpose": "Primary structural alignment for the reified n-ary agent-organization-role relation with a validity interval. Known divergence: org:memberDuring leaves its range unconstrained, so this model imposes RFC 3339 instants.", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "target": "HL7 FHIR PractitionerRole", "relation": "ALIGN", "purpose": "Domain alignment showing role code, specialty, organization, location, service scope, period and availability carried on the assignment. Known divergence: FHIR conflates post and membership into one resource and has no separation-of-duty or authority constructs.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "schema.org Role and OrganizationRole", "relation": "ALIGN", "purpose": "Publication alignment for lightweight external exposure. Known divergence: no lifecycle status, no authority, and date-only validity, so it is an export target only and never a semantic source.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "HR Open Standards StaffingAssignment (Contingent Staffing 3.3)", "relation": "ALIGN", "purpose": "Alignment for the tri-party case in which a resource engaged by one organization is placed with a customer. Known divergence: the consortium's newer JSON API set has no Assignment resource, so no stable modern JSON counterpart exists.", "required": false, "source_refs": [ "SRC-014", "SRC-013" ] }, { "target": "W3C PROV-O qualified association and delegation", "relation": "MIX-IN", "purpose": "Provenance mixin for authorization, acting-on-behalf-of delegation and role-at-time-of-action, applied to approval records and lifecycle events.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "NIST/INCITS RBAC constraint model", "relation": "ALIGN", "purpose": "Alignment for static and dynamic separation of duty and cardinality constraints. Known divergence: standard RBAC user assignment carries no temporal bounds, so the temporal semantics are supplied by this model and must not be assumed on the RBAC side.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "RFC 3339 timestamp profile", "relation": "ALIGN", "purpose": "Governs every effective, transition, authorization, notification and observation time in the model, including the reserved meaning of an unknown local offset.", "required": true, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "A Dimension adopting this model must name a single accountable owner for the assignment register and a named deputy, each identified by their own assignment record so that authority is self-describing.", "The owner package must declare the identity priority actually applied, the authoritative master system for assignment identifiers, and the boundary convention for inclusive or exclusive period ends before any record is created.", "The owner package must publish its governed vocabularies for assignment type, status, reporting line type, authority conveyance and end reason, each versioned, and state how local extensions are reviewed.", "The owner package must declare which sibling models supply agent identity, post definition, engagement context and classifiers, and must not shadow their fields.", "The owner package must publish the retention schedule, the access scope rules per role and the jurisdictions in scope, since none of these are universal." ], "namespace_guidance": "Use a stable, resolvable namespace owned by the adopting Dimension, versioned independently of any storage projection, for example a path segment for the model, a version segment and a local identifier. Never encode personal data, organizational structure or dates in the identifier. External identifiers from master systems and standards are held as qualified aliases with their issuing system, never merged into the primary identifier.", "registry_links": [ "vr.wm-org-016 as the registry entry for this model, with nav path NAV.SOC.ORG.ASN and domain tag SOC.ORG.ASN", "WM-ORG-004 Position and WM-ORG-005 Employment Relationship as the registered structural neighbours to be resolved during boundary review", "Registered alignments to the W3C Organization Ontology, HL7 FHIR PractitionerRole, schema.org Role and HR Open StaffingAssignment, each recorded with target version and known losses" ] }, "canon_and_patch": { "canonicalization_rules": [ "All instants are stored in RFC 3339 form with seconds and an explicit offset or Z; an unknown local offset is expressed as the reserved -00:00 and never silently normalized to Z.", "Event time and record time are stored as separate fields and are never collapsed; an effective date is never used as an identifier.", "References are stored as identifiers with an explicit issuing system, never as display names; display strings are derived at read time.", "Codes are stored with their scheme identifier and scheme version so that a reclassification of the scheme does not silently change the meaning of historic records.", "Field ordering, whitespace and presentation form carry no meaning; canonical equality is computed over the semantic field set only, so that JSON, YAML, Markdown, Git and document-store projections compare identically." ], "patch_rules": [ "Changes to the world are effective-dated amendments that preserve prior values; changes to the record are versioned corrections. The two are never expressed with the same operation.", "Every patch declares its change class, effective instant, actor, actor role at the time and reason; patches without these are rejected.", "Patches that touch an immutable participant, or that cross a declared new-record trigger, are rejected in favour of ending the assignment and creating a successor with a succession link.", "Lifecycle transitions are appended as events, never applied by overwriting the status field alone; the status field is a materialized view of the event stream.", "A patch that would breach a blocking validation rule is rejected unless it carries a reference to an approved, unexpired exception." ], "compatibility_rules": [ "Adding an optional field or a new vocabulary term is a minor change; removing a field, narrowing cardinality, changing a code's meaning or altering the period boundary convention is a breaking change requiring a new model version and a migration note.", "Crosswalks are versioned against both the model version and the target standard version; a target reversioning is treated as a new crosswalk, not an in-place edit.", "Consumers must tolerate unknown optional fields and must not infer meaning from field order or from the storage projection in use.", "Known losses and recorded conflicts travel with every projection; a consumer that strips caveats is non-conformant." ] }, "artifact_rules": { "identity_priority": [ "Identifier issued by the authoritative master system for assignments in the adopting Dimension, recorded with that system's name or URI", "Governed global identifier or IRI where one exists for the assignment or its instrument, recorded with its issuing authority", "UUID or ULID minted by the adopting Dimension, used only when neither of the above exists and never derived from personal data", "Explicitly not an identifier: any date, period, job title, person name, email address or composite of these" ], "timestamp_rule": "Every timestamp on an artifact or record uses RFC 3339 with seconds and an explicit offset or Z; where the local offset is genuinely unknown, the reserved -00:00 form is used. Event time and observation or ingestion time are recorded separately whenever they can differ.", "serial_naming_rule": "Serial artifacts - assignment instruments, statements of particulars and change, approval records, register entries and event log entries - are numbered monotonically within a declared series scope (engagement, register or assignment), never reuse a number after supersession or withdrawal, and carry both the series identifier and the sequence value. Non-serial artifacts are identified by their subject reference plus an RFC 3339 generation instant.", "integrity_rule": "Issued and approved artifacts are immutable. Corrections are new artifacts that reference the superseded one and state the reason; the superseded artifact is retained and marked, never deleted or edited, until its retention period expires and disposal is recorded. Append-only logs may not be rewritten, and any artifact leaving the Dimension carries its identifier, version, generation instant and known-loss caveats." }, "policies": [ "No assignment confers authority before an authorization record with a competent authorizer exists; a proposed or draft assignment is never treated as effective for access, reporting or headcount.", "Every conferred authority and delegation lapses automatically when the assignment ends or is suspended; continued exercise requires a fresh grant, and transfers require existing authorizations to be re-confirmed rather than inherited.", "Blocking validation outcomes may be overridden only by a registered exception with a named approver, a compensating control and a mandatory expiry; exceptions without expiry are invalid.", "Personal and specially protected fields are disclosed on a least-privilege basis; the default external projection of an assignment is post, scope and period without assignee identity or terms.", "Records are retained for their declared period against a stated basis and then disposed of by the declared method, with disposal recorded; legal holds suspend disposal and are themselves auditable.", "No conformance to an external standard is asserted without a published, versioned crosswalk and a recorded list of known losses and conflicts.", "Occupancy is need-to-know personal data in the employment or professional-directory context and is processed under a documented lawful basis, not by default on worker consent.", "Merit, qualification and separation-of-duty constraints are evaluated before activation of a covered occupancy, and reconstruction records are retained for the governed period.", "Historical authorized occupancies are retained even after revocation or ending until retention expires; erasure is applied only where no legal-obligation or other exception remains." ], "crud": { "read": [ "Reads are scoped: a requester receives only the fields their role is entitled to, with redaction applied rather than outright denial where a partial view is permitted.", "Point-in-time reads are supported and must state the evaluation instant with an explicit offset; a read without an instant is answered as of request time and labelled as such.", "Every read, export and projection of an assignment record is logged with actor, role, scope, instant and purpose.", "Derived views such as effective-assignment sets and coverage reports must declare the rule set version used to produce them." ], "create": [ "Creation requires a resolvable assignee, organization and either a post, a role concept or an explicit bespoke scope, plus an effective start with explicit offset.", "Creation places the assignment in a proposed state with no conferred authority and triggers eligibility validation.", "The creating actor, their role at the time and the creation instant are recorded as provenance and cannot be supplied by the client as arbitrary values.", "Duplicate detection runs on creation against the agent, post and period to prevent a second record for the same real-world binding." ], "update": [ "Real-world changes are effective-dated amendments; record errors are versioned corrections. The change class is mandatory on every update.", "Updates to immutable participants or across a new-record trigger are refused with a pointer to the transfer or succession function.", "Material amendments raise a notification obligation with a deadline and are not considered complete until the statement of change is issued and recorded.", "Every update re-runs the affected validation rules and records the outcomes with the rule set version." ], "delete": [ "Assignments are never hard-deleted while in retention; they are ended, superseded or, where created in error, voided with a recorded reason and retained.", "Disposal at end of retention follows the declared method - deletion, anonymization or reduction to a preserved skeleton that keeps post, period and succession links - and the disposal action is itself logged.", "Any active legal hold blocks disposal for the held scope until an authorized party lifts it, and both the imposition and the lifting are auditable.", "Erasure of an underlying person record does not silently remove assignment history; surviving elements and their justification are recorded." ] }, "roles": [ { "name": "Assignment register owner", "responsibilities": [ "Own the model instance, its vocabularies, rule sets and their versions", "Declare the identity priority, period boundary convention and retention schedule in force", "Approve model version changes and publish migration notes" ] }, { "name": "Assignment authorizer", "responsibilities": [ "Decide and record authorizations within their own conferred limits", "Confirm that the assignment's authority level and scope are within their competence to grant", "Attach conditions and compensating controls where an exception is relied upon" ] }, { "name": "Assignment administrator", "responsibilities": [ "Create, amend, suspend, transfer and end assignment records on instruction", "Issue statements of particulars and statements of change within the applicable deadlines", "Track handover, revocation and reconciliation tasks to completion" ] }, { "name": "Controls and assurance reviewer", "responsibilities": [ "Maintain separation of duty, conflict, cardinality and coverage rules and their severities", "Review registered exceptions, compensating controls and their expiry", "Run and act on conflict detection scans and record findings against the rule set version" ] }, { "name": "Data protection and records steward", "responsibilities": [ "Classify assignment fields, record the lawful basis and set access scope rules per role", "Maintain the retention schedule, disposal methods and legal hold procedure", "Adjudicate subject access and erasure requests against retained assignment history" ] }, { "name": "Interoperability steward", "responsibilities": [ "Maintain versioned crosswalks to external standards and downstream consumers", "Record known losses and conflicts and ensure caveats travel with every projection", "Own reconciliation schedules and adjudicate identifier precedence disputes" ] } ], "access": { "default_rule": "Deny by default. Access is granted only through a current, active assignment that confers the necessary authority, evaluated at the instant of the request; no standing personal grants exist outside the assignment model.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency or break-glass access may be granted for a bounded period with a named approver, is logged in full and triggers mandatory post-hoc review.", "Statutory and regulatory recipients - workers' representatives, auditors, inspectors and courts - may receive defined field sets without the default redaction, under a recorded legal basis.", "The assignee may read their own assignment record in full, including terms and particulars, regardless of the role-based scope that applies to others.", "Downstream consumers receive only the field set defined in their published projection contract, even where the requesting service account holds broader rights.", "Aggregate and anonymized workforce reporting may read across assignments without per-record entitlement, subject to suppression thresholds that prevent re-identification.", "Official-authority, occupational-health, whistleblowing, safety and legally compelled disclosure may open additional fields with time-bounded grants and audit.", "Unnamed locum occupancy may be published at host and role granularity without a person identifier." ], "audit_requirements": [ "Every read, export, creation, amendment, lifecycle transition, delegation, exception grant and disposal is logged with actor, role held at the time, event time and record time in RFC 3339 form.", "Logs are append-only and independently retained from the assignment record itself, so that disposal of a record does not erase the evidence of how it was handled.", "Break-glass and exception-based access produce a distinct, reviewable event class with a mandatory review outcome.", "Access decisions record the assignment identifier and rule version that justified them, so that a historic decision remains explicable after the assignment ends.", "Retention of access logs is declared separately from record retention and is not shortened by disposal of the subject record.", "Every create, identity-affecting update, activation, end, cancel, access exception and erasure decision is attributed to an agent and activity with event time and ingestion time.", "Promotion reconstruction files remain auditable for two years or until the governing evaluation period lapses." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Model ID and registry ID", "Model version and compatibility statement", "Owner and accountable contact", "Identity priority and timestamp rule in force", "Access default rule and audit obligations", "Known losses, conflicts and open boundary reviews" ], "read_order": [ "AGENTS.md first, to establish name, type and the four URLs before any other action", "Specification URL, for the model's scope, boundaries, bundles, layers, findings and questions", "Storage type URL, to learn the concrete projection in use - document store, versioned files, graph or relational - and to confirm that it is a projection and not the semantics", "Interface URL, for the operations exposed, their access scopes and their audit obligations", "Processes URL, for the governed lifecycle, approval, validation, exception, retention and reconciliation procedures", "Only then any instance data, and only through the declared interface and access scope" ] } }, "coverage": { "claim": "Base covers identity and versioning, the n-ary participant set, bounded work scope, place and jurisdiction, granted authority, supervision and delegation, capacity share, effective period and succession, working pattern and duty limits, lifecycle states and amendment, handover and offboarding, eligibility and screening, separation-of-duty and cardinality controls, authorization evidence and notification, privacy, retention and interoperability projection for a reified work-assignment relationship. Four additions extend it with unnamed and ex officio occupancy, role-scoped service, contact and endpoint projection, governed personnel-action semantics and time-limited temporary forms. Retention periods and workforce-measurement (FTE, headcount) definitions remain declared gaps, US-federal and EU/UK derived nodes remain jurisdiction-scoped, and no universal or jurisdiction-complete account of work assignment is claimed.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity priority, scheme, recurrence distinction, correction versus real-world change and external identifier precedence are all questioned. Grounded in FHIR's business identifier on PractitionerRole and the reification requirement implied by org:Membership; the priority order itself is a Vercy rule, not a standard." }, { "dimension": "lifecycle", "status": "covered", "notes": "State set, terminal states, stored versus derived status, triggers, automatic end, reversal, amendment and offboarding. Grounded in the WS-HumanTask state machine and named operations, and in FHIR's active flag plus period. The specific state names are a local choice; WS-HumanTask states are task-scoped and are used as an analogy, not a claim of conformance." }, { "dimension": "relationships", "status": "covered", "notes": "Participant set, post and role linkage, reporting lines, delegation, succession, concurrency and coverage. Grounded in org:member, org:organization, org:role, org:holds/heldBy and org:reportsTo, and in PROV delegation." }, { "dimension": "temporal", "status": "covered", "notes": "Effective period, term type, precision and offset, event versus record time, backdating, concurrency, succession, same-day transfer, working pattern, availability and duty limits. Grounded in org:memberDuring, FHIR period and availability, RFC 3339 and statutory hours particulars. The inclusive/exclusive end convention is left to the adopting Dimension because no source fixes it." }, { "dimension": "provenance", "status": "covered", "notes": "Authorizer, role at the time of authorization, basis, competence of the grantor, durability of the approval chain, and reversal with preservation. Grounded in PROV-O qualified association with hadRole and in the separation of event and record time." }, { "dimension": "ownership", "status": "covered", "notes": "Accountable owner of the register, controlling parties who may amend or end an assignment, accountability for non-human agents, and re-screening ownership. Grounded in AI Act Article 26(2) for oversight accountability and in the org ontology for control relationships." }, { "dimension": "validation", "status": "covered", "notes": "Eligibility rules, separation of duty, cardinality, coverage, blocking versus advisory severity, exceptions with mandatory expiry and grandfathering. Grounded directly in the INCITS 359 constraint model." }, { "dimension": "access", "status": "covered", "notes": "Deny-by-default keyed to a current assignment, scope-limited reads at bundle, layer, finding and artifact level, break-glass and statutory exceptions, and full read/export logging. Grounded in RBAC user assignment and session activation as the downstream projection." }, { "dimension": "retention and deletion", "status": "gap", "notes": "Only one retention figure is verifiable from a primary source in this research: the AI Act's minimum six-month retention of high-risk system logs. No primary source for general assignment-record or duty-record retention periods could be retrieved - the ISO and UK ICO pages both returned HTTP 403. Retention is therefore modelled as a policy hook with a mandatory declared basis, not as a substantive period, and the adopting Dimension must supply jurisdiction-specific periods." }, { "dimension": "interoperability", "status": "covered", "notes": "Versioned crosswalks with explicit unmapped fields, identifier precedence, downstream projection contracts, reconciliation and visible conflict notes. Grounded in the observed divergence between org:Membership, FHIR PractitionerRole, schema.org Role and HR Open, including the absence of an Assignment resource in HR Open's current JSON API set." }, { "dimension": "classification", "status": "covered", "notes": "Assignment type, primacy, authority conveyance, occupation and specialty codes with scheme version. Grounded in ESCO/ISCO-08 URIs and in FHIR code and specialty. Assignment-type vocabularies themselves are not standardized; the model requires a governed local vocabulary rather than asserting one." }, { "dimension": "authority", "status": "covered", "notes": "Granted decision rights and limits, source of authority, independent validity of grants, competence of the grantor, delegation and acting cover. Grounded in AI Act Article 26(2)'s pairing of competence, training and authority, and in PROV delegation. Financial approval limits are common practice rather than standard-mandated." }, { "dimension": "spatial", "status": "covered", "notes": "Base and additional locations, working mode, cross-border work and derived jurisdictional regimes, plus location history. Grounded in the statutory requirement to state place of work and work outside the jurisdiction, and in FHIR location on PractitionerRole." }, { "dimension": "privacy", "status": "covered", "notes": "Field-level sensitivity classification, lawful basis, redacted default projections, inference risk on transparency publication, and status-only disclosure of screening outcomes. Grounded in the AI Act's worker information duty; the field classification scheme itself is left to the Dimension's data protection steward." }, { "dimension": "workforce measurement", "status": "gap", "notes": "Effort allocation, full-time-equivalent semantics, headcount boundary conventions and coverage metrics are structured but not normatively grounded: ISO 30414 could not be retrieved (iso.org returned HTTP 403), so no verified metric definitions underpin these fields. They are presented as required declarations by the adopting Dimension rather than as canonical definitions." }, { "dimension": "evidence and quality", "status": "covered", "notes": "Verification records, approval records, acknowledgement, duty and rest records, precedence when contracted, scheduled and allocated effort disagree, and visible mapping conflicts. Grounded in FHIR, PROV-O and statutory statement duties." } ], "known_omissions": [ "Compensation, pay rate, bill rate and benefit determination for the assignment; referenced only as an engagement-level concern.", "Cost allocation, chargeback and inter-company recharge arising from an assignment.", "Collective agreement coverage, bargaining unit membership and consultation procedure detail.", "Performance objectives, appraisal outcomes and succession candidate pools linked to an assignment.", "Immigration and posting-of-workers formalities beyond a permission validity date, including social security coordination certificates.", "Demand forecasting, vacancy management and the matching or ranking algorithms that select an assignee.", "Capability, model version and evaluation history of a non-human agent assignee; only the accountability link is modelled.", "Health surveillance and reasonable-adjustment records that condition an assignment; treated as external evidence pointers only.", "Field-level detail of the incident assignment-list artifact: the FEMA PDFs could not be machine-parsed, so only the form identity and stated purpose are relied upon.", "Sector-specific duty and rest regimes are referenced structurally but no single regime's limits are asserted.", "ISO 30400:2022 HR terminology is paywalled and was not retrieved; job, position and assignment terms from that standard are not claimed.", "HR Open Standards position-assignment schemas were not retrieved as public technical text.", "IEC 62264 object-model attributes for personnel class assignment remain behind the ISA and IEC paywall; only the public ISA-95 overview was used.", "ILO Recommendation No. 198 full instrument text did not load from NORMLEX in this run; only the official landing page is cited.", "Military permanent-change-of-station and assignment-order systems were not fetched.", "Shift roster, cost-center accounting splits and compensation as a function of occupancy lack primary support here.", "National labour-dispatch and agency-worker regimes beyond the host-versus-employer distinction are not specified." ], "conflicts": [ "org:memberDuring leaves its range unconstrained and treats OWL-Time use as informative, FHIR uses a period with dateTime precision, and schema.org Role offers only startDate and endDate. Three alignment targets therefore disagree on temporal precision; this model imposes RFC 3339 instants and records the loss on export.", "schema.org Role carries no lifecycle status, no authority and no organization on the Role itself, so a round trip through schema.org loses state and authority. It is designated an export-only target.", "FHIR PractitionerRole merges post, membership, place, service scope and availability into a single resource, whereas W3C ORG deliberately separates org:Post from org:Membership. A one-to-one mapping is not possible in either direction without loss.", "INCITS 359 user assignment has no temporal bounds, so exporting a time-bounded assignment into standard RBAC silently drops the period. Temporal enforcement must remain on this side of the boundary.", "WS-HumanTask uses assignment language for per-task-instance ownership with claim and release semantics. Reusing its state names for standing organizational assignments would be a category error; they are used as an analogy only.", "HR Open publishes StaffingAssignment only in the HR-XML 3.3 contingent staffing set, while its current JSON API specifications expose organizations and workers with no Assignment resource. There is therefore no stable modern JSON counterpart, and assumed interoperability would be unfounded.", "Statutory written particulars attach to the employment relationship rather than to each assignment, so a Dimension that issues a statement per assignment exceeds the statutory model, while one that issues only per engagement may leave material assignment changes unnotified. The model records the obligation and its trigger rather than resolving this.", "FHIR requires a new PractitionerRole instance for non-adjacent periods; many HRIS products reopen a single assignment row after a gap.", "W3C ORG offers both Membership and Post occupancy; profiles that force one pattern will not round-trip the other.", "Schema.org EmployeeRole mixes occupancy qualifiers with employment salary, overlapping WM-ORG-005.", "NIST RBAC UA assigns permissions, not posts; provisioning occupancy into UA is a policy choice, not an identity of relations.", "5 CFR 335 is United States federal competitive-service law and is not a global personnel-action code.", "ISA-95 personnel assignment is a manufacturing resource binding and must not be treated as organizational occupancy." ], "regional_assumptions": [ "Written-particulars duties are evidenced from UK primary legislation as a concrete instance. Equivalent duties exist elsewhere, notably in EU law, but the enumerated particulars, deadlines and definitions differ by jurisdiction; the EUR-Lex text could not be retrieved during this research and is not relied upon.", "AI Act obligations on assigning human oversight, informing workers and retaining logs apply to deployers of high-risk AI systems within the EU regime only, and do not generalize to all assignments.", "ESCO and ISCO-08 alignment assumes a European or ILO-aligned classification context; other jurisdictions use national occupational schemes that map imperfectly.", "Duty and rest limits are strongly sector- and jurisdiction-specific; the model carries the constraint structure but asserts no particular limit values.", "Incident-management assignment artifacts are drawn from a United States national framework; comparable national frameworks exist elsewhere with different form sets.", "The distinction between engaging organization and host organization assumes a legal environment that permits agency or contracted supply of labour.", "Merit promotion, 120-day detail accounting and five-year time-limited promotion limits are United States federal (5 CFR Part 335) and apply only where that law is the appointing regime.", "GDPR Article 88 and ICO employment-records guidance apply to EU and UK processing; other privacy regimes may impose different retention and erasure outcomes.", "Unnamed locum occupancy is drawn from FHIR healthcare practice and may be uncommon in general HRIS.", "Secondment, labour dispatch and posted-worker constructions are jurisdiction-specific and are represented here only as host-versus-home employer." ], "adversarial_checks": [ "Tested whether Work Assignment collapses into Position (WM-ORG-004). Rejected: the Organization Ontology states explicitly that a Post exists independently of the person or persons filling it, so occupancy must be a separate time-bounded object.", "Tested whether Work Assignment is merely task assignment as in WS-HumanTask. Rejected: task-level actual ownership is established by claiming, is per-instance and short-lived, and can be released back to a potential-owner set - none of which is true of a standing assignment. The boundary is recorded rather than merged.", "Tested whether RBAC user assignment is the same object. Rejected: INCITS 359 user assignment carries no temporal scope, no work scope and no organizational context; it is a downstream projection, and treating it as the source would lose the period.", "Tested whether an assignment must reference an employment relationship, as the registry parent relation suggests. Counterexamples found in HR Open's tri-party StaffingAssignment and in FHIR PractitionerRole, which carries no employment construct at all. The composition link was therefore marked not required and the boundary note explains why.", "Tested whether acting cover is a delegation rather than an assignment. Both were retained and distinguished: delegation operates over authorities within an existing assignment, while acting cover creates a distinct time-bounded assignment referencing the covered one.", "Tested whether schema.org Role could serve as a semantic source rather than an export target. Rejected on inspection: it has no status, no authority and only date-granularity validity, so it cannot represent suspension, authorization or an instant-precise transfer.", "Tested whether a date could serve as part of the assignment identifier for recurring assignments to the same post. Rejected under the identity rule, and an explicit question was added requiring a non-date distinguishing key.", "Searched for a normative retention period for assignment records and found none retrievable; rather than asserting a plausible figure, retention was downgraded to a declared gap with a policy hook.", "Tested whether non-human agents can hold any assignment. Constrained: AI Act Article 26(2) requires oversight to be assigned to natural persons, so the model carries an explicit natural-person reservation flag and an accountable-person link rather than treating agent kind as free.", "If a consumer treats assignment identifier as the person identifier, unnamed locum and job-share occupancies become corrupt; agent and assignment identities were kept separate.", "If a consumer equates host organization with employer, contractor, secondment and FHIR non-employer hosts are misclassified; host-is-employer is explicit.", "If a consumer infers RBAC permissions from occupancy alone, SSD-safe posts can still yield over-privilege; UA is aligned, not composed as identity.", "If a consumer reuses one assignment across a gap, FHIR period semantics and audit reconstruction fail; instance-per-gap is required.", "If acting coverage is claimed as a 5 CFR term, the claim is false; acting is marked as operational language without that primary label.", "If FTE is treated as internationally standardized, the claim is false; effort fraction is a documented gap." ] }, "researchAdjudication": { "providerMode": "dual-provider", "activeProviders": [ "claude", "grok" ], "waivedProviders": [], "providerPolicy": {}, "boundaryDecision": { "entry_kind": "relationship", "status": "accepted", "rationale": "Both providers independently classify WM-ORG-016 as a reified n-ary relationship rather than an entity, and both derive that from the same primary pattern: W3C ORG separates org:Post (which exists independently of any holder) from org:Membership (which exists only while an agent occupies a role), and FHIR PractitionerRole carries a period of authorization rather than a standing post definition. The base boundary is adopted whole: the assignment is the time-bounded occupancy binding agent, organization or unit, role or post, bounded scope and validity period, holding no position definition (WM-ORG-004), no engagement or contract terms (WM-ORG-005), no person or org master data, no task-instance ownership state and no permission catalogue. Grok's two extra exclusions (FHIR CareTeam patient-scoped membership and ISA-95/IEC 62264 personnel-resource binding to a work definition) are consistent with that boundary and sharpen it rather than move it, so they are carried as boundary-note refinements in a later pass, not as a boundary change." }, "decisions": [ { "concept": "Base provider selection", "disposition": "Claude adopted as base", "rationale": "Not chosen on size. Claude states explicit in-scope and out-of-scope lists plus eight neighbour boundary notes each carrying source refs, and each of the eight is a distinction the model actually needs (post, engagement, classifier, task instance, RBAC, roster, timecard, incident tasking). Its bundle spine also separates scope/authority from time/schedule from lifecycle from controls, which the merged additions can attach to without new scaffolding. Grok's boundary is sound but its decomposition splits parties and location into standalone bundles that the base already covers inside scope-and-authority." }, { "concept": "Entry kind", "disposition": "Accepted as relationship", "rationale": "Independent agreement between providers, both derived from the same primary separation of org:Post from org:Membership and from FHIR PractitionerRole carrying an authorization period. No adjudication needed and no reclassification risk." }, { "concept": "Unnamed, pre-allocated and ex officio occupancy", "disposition": "Accepted as addition to assignee-agent-kind", "rationale": "Materially absent from the base participant set and evidenced directly in FHIR (practitioner 0..1, un-named practitioner at a named organization) and in W3C ORG ex officio membership. Without it, locum slots, job-share halves and ex officio seats cannot be represented at all." }, { "concept": "Role-scoped contact, service and endpoint projection", "disposition": "Accepted narrowly, spatial questions dropped", "rationale": "Only the increment absent from the base is taken: contact points, languages and endpoints belonging to the occupancy rather than the person, plus the FHIR instance-split rule. Base coverage of base location, mobility, jurisdiction, objectives and caseload is retained unchanged, so the overlapping questions are discarded rather than duplicated." }, { "concept": "Governed personnel-action typology and status invariance", "disposition": "Accepted as addition, jurisdiction-labelled", "rationale": "The base has an abstract state machine but no act typology and no rule that a position change leaves tenure and competitive status unchanged. Grok retrieved primary regulatory text for both. Accepted on condition it publishes as a concrete instance of personnel-action semantics under a named appointing regime, never as the universal set." }, { "concept": "Temporary, detail and time-limited forms", "disposition": "Accepted as addition, jurisdiction-labelled", "rationale": "Term ceilings, advance notice of return terms, the right of return to the former or equivalent position, cumulative noncompetitive accounting and conversion to permanent are all absent from the base and all evidenced from retrieved primary text. Grok's own caveat that 'acting' is operational language not present in the cited regulation is carried through so no false label is asserted." }, { "concept": "Host organization as separate finding", "disposition": "Rejected as duplicative", "rationale": "The base participant question already asks whether the assignee is engaged by a different organization from the one where work is performed, and the boundary note on WM-ORG-005 already states that host need not be employer. The only residue is the seconding home-employer-of-record pointer, which is a reference into a sibling model rather than a new node." }, { "concept": "Occupied post or role as separate finding", "disposition": "Rejected as duplicative", "rationale": "The base asks whether the assignment is expressed against a defined post, an abstract role concept or a bespoke scope with no post at all, which is exactly Grok's Membership-versus-Post pattern decision, and the base role-and-position-linkage finding carries the classifier and reclassification questions Grok lacks." }, { "concept": "Occupancy and authorization period as separate finding", "disposition": "Rejected as duplicative; one residue deferred", "rationale": "The base effective-period finding already covers period and precision, RFC 3339 offsets, event versus record time, backdating, concurrency, succession and same-day transfer. The residue worth keeping is the third clock (planned versus actual start and end, distinct from effective versus record time); it is deferred as a question-level refinement to the existing base finding rather than a new node." }, { "concept": "Evidence and provenance as separate finding", "disposition": "Rejected as duplicative; integrity residue deferred", "rationale": "Base coverage of authorization provenance, approval-chain durability, record correction versus real-world change, reversal with audit preservation and the append-only assignment event log already spans PROV-O generation, association, attribution and invalidation. The genuine residue is evidence-artifact integrity hashing and an explicit record-quality claim, which is deferred rather than published as a competing finding." }, { "concept": "Interoperability alignments as separate finding", "disposition": "Rejected; neighbour notes deferred", "rationale": "The base standard-alignment finding is strictly richer, adding versioned crosswalks, unmapped-field disclosure, identifier precedence, downstream reconciliation and visible conflict recording. Grok's distinct contribution is two neighbours the base does not name, FHIR CareTeam and ISA-95/IEC 62264 personnel resources, which belong in a boundary-note pass, not in the finding tree." }, { "concept": "Privacy, retention and erasure as separate finding", "disposition": "Rejected as structure; evidence retained as corroboration only", "rationale": "The base already carries personal-data classification and access scoping plus retention, deletion and legal hold as two findings whose question sets subsume Grok's. Grok's Article 88 and ICO material is corroborating evidence attached to the existing base retention finding, not a new node, and because one of those sources is a non-primary mirror and the other is tier 2, it does not close the base's declared retention gap." }, { "concept": "Grok classification, lifecycle-state, assigning-authority and separation-of-duty findings", "disposition": "Rejected as duplicative", "rationale": "Each maps onto a strictly broader base finding: assignment type and primacy, the state model with stored-versus-derived status, granted authority with grantor competence, and the separation-of-duty, cardinality, coverage and exception finding. The only non-overlapping elements (ex officio, competition thresholds) arrive through the two accepted additions instead." }, { "concept": "Non-human agent as assignee", "disposition": "Retained with explicit gap label", "rationale": "The providers disagree in emphasis rather than in fact: the base structures non-human occupancy with a natural-person reservation and oversight link, while Grok records that no retrieved HR or personnel standard supports a software agent occupying a work assignment. The cited AI Act article obliges deployers to assign oversight to competent natural persons; it does not authorize non-human occupancy. The structure is kept as a constraint-bearing branch and must publish carrying that unsupported-claim label." }, { "concept": "Claude-only scope/authority and time/schedule bundles", "disposition": "Retained in full", "rationale": "Working pattern and predictability, duty and rest limits, eligibility and screening preconditions, handover and offboarding, and acknowledgement and notification duties have no Grok counterpart and are each source-backed in the base. Absence from the second provider is not evidence against them." } ], "publicationHolds": [ "Source and live-version verification is not discharged. Every accepted source must be refetched and pinned before publication, with particular attention to the two divergent FHIR PractitionerRole citations across providers (hl7.org/fhir/R5/practitionerrole.html described as R5 Maturity 4 Trial Use versus www.hl7.org/fhir/practitionerrole.html described as R5 5.0.0 generated 26 March 2023), and to the moving pins on ESCO v1.2.1, schema.org v30.0, the eCFR currency date and the revised-text-in-force date for the UK written-particulars section.", "Multi-profile domain validation is not discharged. The merged structure has been exercised against healthcare (FHIR PractitionerRole), US federal public service (5 CFR 335), contingent staffing (HR-XML 3.3) and incident management (ICS forms), but must additionally be validated against at least one non-US, non-EU appointing regime and one volunteer or platform-work profile before publication, because the accepted personnel-action and temporary-form nodes are otherwise parochial.", "Retention remains a declared gap and must publish as a policy hook with a mandatory declared basis, never as a substantive period. Grok's retention evidence rests on a non-primary mirror of the GDPR employment-context article and on tier-2 regulator guidance; neither establishes a general retention period for assignment records, and the base's own attempts to retrieve primary retention instruments returned HTTP 403.", "Workforce measurement remains a declared gap. Effort fraction, full-time-equivalent semantics, headcount boundary conventions and coverage metrics are structured but normatively ungrounded in both providers; they must publish as required declarations by the adopting Dimension, not as canonical definitions.", "All nodes derived from a single national personnel code or a single national statute (the accepted personnel-action and time-limited-form findings, and the written-particulars duties in the base) must carry an explicit jurisdiction scope label before publication, and the 'acting' terminology must not be attributed to any cited regulation.", "The non-human-agent occupancy branch must publish with an explicit note that no retrieved HR or personnel standard supports a software or robotic agent occupying a work assignment, and that the cited AI Act obligation governs assignment of human oversight rather than authorizing non-human occupancy." ], "deferredResearch": [ "Retrieve primary retention instruments (statutory limitation periods, tax and social-security record-keeping duties, and the regulator guidance in its original published form) to convert the retention dimension from a declared gap into evidence-backed minimum periods; both providers failed to reach primary text on this dimension.", "Retrieve an open or licensed normative definition of full-time-equivalent, effort fraction, headcount boundary and coverage metrics (ISO 30414 and ISO 30400 were paywalled or returned HTTP 403 for both providers) so that workforce measurement can stop publishing as an undefined declaration.", "Retrieve the EU transparent and predictable working conditions directive text from EUR-Lex to generalize the written-particulars and unpredictable-pattern duties beyond the single national statute currently relied upon, and to resolve whether particulars attach per engagement or per assignment.", "Retrieve HR Open Standards position and assignment JSON schemas and the IEC 62264-1 personnel object model text to firm up the interoperability crosswalk and to convert the ISA-95 boundary from an overview-page claim into a sourced neighbour note.", "Retrieve at least two non-US national personnel-action regimes and one collective-agreement-governed regime so the accepted personnel-action typology and time-limited-form constraints can be generalized or explicitly partitioned by jurisdiction.", "Machine-parse the incident-management assignment-list forms and retrieve the ILO employment-relationship recommendation full instrument text; both were cited from landing pages or unparsed PDFs and currently support only form identity and stated purpose.", "Resolve the two deferred residues from rejected Grok findings: the planned-versus-actual clock as a third temporal axis distinct from effective-versus-record time, and evidence-artifact integrity hashing plus an explicit record-quality claim on the assignment record." ] }, "statistics": { "sources": 21, "bundles": 6, "layers": 13, "findings": 28, "questions": 115, "artifacts": 18, "functions": 13 } }