# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T07:54:53Z", "synthesisSha256": "c3ba73aa14bba850ddbe38f1fa713756cc525da3c923d1ff7725e642198d5dc1", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-040", "registryId": "vr.wm-act-040", "name": "Onboarding / Offboarding", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.HR" ], "tags": [ "onboarding", "offboarding", "act.hr" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-040-onboarding-offboarding/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-040", "model": { "registry_id": "vr.wm-act-040", "model_id": "WM-ACT-040", "name": "Onboarding / Offboarding", "entry_kind": "aggregate", "purpose": "Represent one governed worker transition case for joining, moving, leaving or rejoining, coordinating desired changes and independently verified execution across employment, access, asset, knowledge and support systems.", "scope_statement": "Owns case identity and lineage, mandatory transition profile, trigger and authority, exact employment and role bindings, plan releases, tasks, dependencies, notices, desired account and access changes, asset and workspace coordination, data and knowledge handover, induction and training coordination, execution evidence, verification, exceptions, closure, quality, interoperability, privacy and retention. Person, Employment, Role, Organization, Account, Credential, Access Grant, Device, Asset, Licence, Workspace, Training, Competency, Agreement, Benefit, Dataset, Record, Communication and Audit masters remain external.", "in_scope": [ "Case identity, join/move/leave/rejoin profile, trigger, authority, employment and role bindings, plans, tasks and obligations", "Identity, accounts, access, credentials, workspaces, facilities, assets, licences, data custody, handover, induction, training, administration and support coordination", "Execution and verification evidence, revocation, returns, exit, closure, lifecycle, metrics, exceptions, interoperability, privacy, retention and safe agents" ], "out_of_scope": [ "Independent person, employment, role, account, access, asset, training, agreement, benefit, data, communication or audit master lifecycles", "Inferring employment, authority, access, task completion, revocation, return or deletion from a request, checklist or adjacent state", "Implementing an HR system, identity provider, device manager, payroll, benefits, learning system, records repository or universal labour regime" ], "boundary_notes": [ { "neighbor": "Person, Employment and Role Assignment", "distinction": "The case binds exact external relationships and desired changes but does not create or terminate those masters.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010" ] }, { "neighbor": "Account, Credential, Group and Access Grant", "distinction": "The case requests and verifies changes; authoritative identity and access systems own effective state and authorization semantics.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007" ] }, { "neighbor": "Device, Asset, Licence, Workspace and Facility", "distinction": "The case coordinates issue, transfer or return while inventory and custody masters retain identity and lifecycle.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "neighbor": "Training, Competency, Agreement and Benefit", "distinction": "The case binds requirements and completion evidence but does not own the underlying definitions, awards, agreements or benefits.", "source_refs": [ "SRC-001", "SRC-005", "SRC-008", "SRC-010" ] }, { "neighbor": "Dataset, Record, Communication and Audit", "distinction": "Handover and access evidence are referenced; content, retention, disclosure and audit masters remain separately governed.", "source_refs": [ "SRC-009", "SRC-010", "SRC-012", "SRC-013" ] } ] }, "sources": [ { "id": "SRC-001", "title": "SP 800-53 Rev. 5 Security and Privacy Controls", "organization": "National Institute of Standards and Technology", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final", "version_or_date": "Rev. 5 with Release 5.2.0 notice, 27 August 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Controls for account management, training, physical access, personnel termination and transfer, agreements, audit, privacy and system protection." }, { "id": "SRC-002", "title": "CIS Critical Security Controls Navigator v8", "organization": "Center for Internet Security", "url": "https://www.cisecurity.org/controls/cis-controls-navigator/v8", "version_or_date": "CIS Controls v8 current navigator", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Account inventory and access granting and revoking safeguards, including immediate disabling upon termination or role change." }, { "id": "SRC-003", "title": "SCIM Core Schema", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/info/rfc7643/", "version_or_date": "RFC 7643, September 2015", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Platform-neutral User, Group, active status, enterprise extension and membership exchange semantics." }, { "id": "SRC-004", "title": "SCIM Protocol", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/info/rfc7644/", "version_or_date": "RFC 7644, September 2015", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "HTTP protocol for creating, retrieving, replacing, patching, deleting and bulk-managing identity resources." }, { "id": "SRC-005", "title": "Getting On Board: A Model for Integrating and Engaging New Employees", "organization": "U.S. Office of Personnel Management", "url": "https://www.opm.gov/policy-data-oversight/training-and-development/reference-materials/online-courses/maximizing-employee-engagement/content/common/cw/data/Getting_Onboard_a_Model_for_Integrating_and_Engaging_New_Employees.pdf", "version_or_date": "Official OPM guide accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Onboarding preparation, orientation, workspace, equipment, accounts, role clarity, sponsor, training, follow-up and feedback." }, { "id": "SRC-006", "title": "Managing Risk of Adverse or Involuntary Employee Separations", "organization": "Cybersecurity and Infrastructure Security Agency", "url": "https://www.cisa.gov/sites/default/files/2024-08/ISC-Managing-Risk-of-Adverse-Involuntary-Employee-Separations_508__2024-05-30.pdf", "version_or_date": "Interagency Security Committee guide, May 2024", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Separation planning, notification, exit interview, continuing obligations, access revocation, property return and heightened-risk controls." }, { "id": "SRC-007", "title": "Identity and access management", "organization": "UK National Cyber Security Centre", "url": "https://www.ncsc.gov.uk/collection/10-steps/identity-and-access-management", "version_or_date": "10 Steps guidance accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Joiners, movers and leavers policy, organizational identities, third-party access and prompt revocation or role adjustment." }, { "id": "SRC-008", "title": "ISO 30414:2025 Human capital reporting and disclosure", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/30414", "version_or_date": "ISO 30414:2025 edition 2; public abstract only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Human-capital reporting areas include workforce composition, compliance, mobility, turnover, skills and development; full text was unavailable." }, { "id": "SRC-009", "title": "General Data Protection Regulation", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=celex%3A32016R0679", "version_or_date": "Regulation (EU) 2016/679 official text", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Purpose limitation, minimization, accuracy, transparency, security, rights and storage limitation for worker data." }, { "id": "SRC-010", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "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-09-06T07:42:00Z", "relevance": "Attributable plans, activities, agents, usage, generation, derivation, revision and invalidation." }, { "id": "SRC-011", "title": "Web Content Accessibility Guidelines 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/WCAG22/", "version_or_date": "W3C Recommendation, 12 December 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Accessible digital induction, training, task, communication and exit interfaces." }, { "id": "SRC-012", "title": "NIST Privacy Framework", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/privacy-framework", "version_or_date": "Privacy Framework 1.0 with evolution materials", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Risk-based privacy governance across collection, use, sharing and retention." }, { "id": "SRC-013", "title": "Disposing of records", "organization": "The National Archives, United Kingdom", "url": "https://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/disposal/", "version_or_date": "Official guidance accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Policy-based appraisal, retention and disposition with legal, business and accountability needs." }, { "id": "SRC-014", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:42:00Z", "relevance": "Timestamps with seconds and explicit offset." } ], "structure": { "bundles": [ { "id": "case-identity-trigger-and-authority", "name": "Case identity, trigger and authority", "description": "Groups governed context for case identity, trigger and authority.", "rationale": "One case coordinates one governed worker transition without becoming the employment or person master.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ], "layers": [ { "id": "transition-profile-identity-and-lineage", "name": "Transition profile, identity and lineage", "description": "Groups transition evidence for transition profile, identity and lineage.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010", "SRC-014" ], "findings": [ { "id": "join-move-leave-rejoin-profile-and-neighbor-boundary", "name": "Join, move, leave, rejoin profile and neighbor boundary", "description": "Records join, move, leave, rejoin profile and neighbor boundary as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010", "SRC-014" ], "questions": [ { "id": "join-move-leave-rejoin-profile-and-neighbor-boundary-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish join, move, leave, rejoin profile and neighbor boundary?", "kind": "classification", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "join-move-leave-rejoin-profile-and-neighbor-boundary-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support join, move, leave, rejoin profile and neighbor boundary?", "kind": "state", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "join-move-leave-rejoin-profile-and-neighbor-boundary-q03", "text": "How may join, move, leave, rejoin profile and neighbor boundary be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "process", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "join-move-leave-rejoin-profile-and-neighbor-boundary-data", "name": "Join, move, leave, rejoin profile and neighbor boundary data", "description": "Structured data for join, move, leave, rejoin profile and neighbor boundary with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "join-move-leave-rejoin-profile-and-neighbor-boundary-record", "name": "Join, move, leave, rejoin profile and neighbor boundary record", "description": "Versioned evidence-bearing transition record for join, move, leave, rejoin profile and neighbor boundary.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus join-move-leave-rejoin-profile-and-neighbor-boundary assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "case-identifier-source-version-predecessor-successor-and-lineage", "name": "Case identifier, source, version, predecessor, successor and lineage", "description": "Records case identifier, source, version, predecessor, successor and lineage as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010", "SRC-014" ], "questions": [ { "id": "case-identifier-source-version-predecessor-successor-and-lineage-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish case identifier, source, version, predecessor, successor and lineage?", "kind": "identity", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "case-identifier-source-version-predecessor-successor-and-lineage-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support case identifier, source, version, predecessor, successor and lineage?", "kind": "ownership", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "case-identifier-source-version-predecessor-successor-and-lineage-q03", "text": "How may case identifier, source, version, predecessor, successor and lineage be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "interoperability", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "case-identifier-source-version-predecessor-successor-and-lineage-data", "name": "Case identifier, source, version, predecessor, successor and lineage data", "description": "Structured data for case identifier, source, version, predecessor, successor and lineage with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "case-identifier-source-version-predecessor-successor-and-lineage-record", "name": "Case identifier, source, version, predecessor, successor and lineage record", "description": "Versioned evidence-bearing transition record for case identifier, source, version, predecessor, successor and lineage.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus case-identifier-source-version-predecessor-successor-and-lineage assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "trigger-employment-role-and-authority", "name": "Trigger, employment, role and authority", "description": "Groups transition evidence for trigger, employment, role and authority.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ], "findings": [ { "id": "employment-role-organization-manager-location-and-effective-change-binding", "name": "Employment, role, organization, manager, location and effective-change binding", "description": "Records employment, role, organization, manager, location and effective-change binding as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ], "questions": [ { "id": "employment-role-organization-manager-location-and-effective-change-binding-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish employment, role, organization, manager, location and effective-change binding?", "kind": "relationship", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "employment-role-organization-manager-location-and-effective-change-binding-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support employment, role, organization, manager, location and effective-change binding?", "kind": "event", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "employment-role-organization-manager-location-and-effective-change-binding-q03", "text": "How may employment, role, organization, manager, location and effective-change binding be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "provenance", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "employment-role-organization-manager-location-and-effective-change-binding-data", "name": "Employment, role, organization, manager, location and effective-change binding data", "description": "Structured data for employment, role, organization, manager, location and effective-change binding with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "employment-role-organization-manager-location-and-effective-change-binding-record", "name": "Employment, role, organization, manager, location and effective-change binding record", "description": "Versioned evidence-bearing transition record for employment, role, organization, manager, location and effective-change binding.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus employment-role-organization-manager-location-and-effective-change-binding assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "trigger-reason-request-authority-risk-urgency-and-confidentiality", "name": "Trigger, reason, request, authority, risk, urgency and confidentiality", "description": "Records trigger, reason, request, authority, risk, urgency and confidentiality as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ], "questions": [ { "id": "trigger-reason-request-authority-risk-urgency-and-confidentiality-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish trigger, reason, request, authority, risk, urgency and confidentiality?", "kind": "authority", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "trigger-reason-request-authority-risk-urgency-and-confidentiality-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support trigger, reason, request, authority, risk, urgency and confidentiality?", "kind": "security", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "trigger-reason-request-authority-risk-urgency-and-confidentiality-q03", "text": "How may trigger, reason, request, authority, risk, urgency and confidentiality be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "privacy", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "trigger-reason-request-authority-risk-urgency-and-confidentiality-data", "name": "Trigger, reason, request, authority, risk, urgency and confidentiality data", "description": "Structured data for trigger, reason, request, authority, risk, urgency and confidentiality with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "trigger-reason-request-authority-risk-urgency-and-confidentiality-record", "name": "Trigger, reason, request, authority, risk, urgency and confidentiality record", "description": "Versioned evidence-bearing transition record for trigger, reason, request, authority, risk, urgency and confidentiality.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus trigger-reason-request-authority-risk-urgency-and-confidentiality assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "planning-governance-and-obligations", "name": "Planning, governance and obligations", "description": "Groups governed context for planning, governance and obligations.", "rationale": "A versioned plan coordinates accountable work, dependencies, notices and obligations.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ], "layers": [ { "id": "transition-plan-tasks-roles-and-dependencies", "name": "Transition plan, tasks, roles and dependencies", "description": "Groups transition evidence for transition plan, tasks, roles and dependencies.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ], "findings": [ { "id": "plan-template-profile-milestone-window-readiness-and-success-criteria", "name": "Plan template, profile, milestone, window, readiness and success criteria", "description": "Records plan template, profile, milestone, window, readiness and success criteria as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ], "questions": [ { "id": "plan-template-profile-milestone-window-readiness-and-success-criteria-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish plan template, profile, milestone, window, readiness and success criteria?", "kind": "requirement", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "plan-template-profile-milestone-window-readiness-and-success-criteria-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support plan template, profile, milestone, window, readiness and success criteria?", "kind": "interoperability", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "plan-template-profile-milestone-window-readiness-and-success-criteria-q03", "text": "How may plan template, profile, milestone, window, readiness and success criteria be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "relationship", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "plan-template-profile-milestone-window-readiness-and-success-criteria-data", "name": "Plan template, profile, milestone, window, readiness and success criteria data", "description": "Structured data for plan template, profile, milestone, window, readiness and success criteria with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "plan-template-profile-milestone-window-readiness-and-success-criteria-record", "name": "Plan template, profile, milestone, window, readiness and success criteria record", "description": "Versioned evidence-bearing transition record for plan template, profile, milestone, window, readiness and success criteria.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus plan-template-profile-milestone-window-readiness-and-success-criteria assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "task-owner-dependency-deadline-state-evidence-exception-and-escalation", "name": "Task, owner, dependency, deadline, state, evidence, exception and escalation", "description": "Records task, owner, dependency, deadline, state, evidence, exception and escalation as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ], "questions": [ { "id": "task-owner-dependency-deadline-state-evidence-exception-and-escalation-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish task, owner, dependency, deadline, state, evidence, exception and escalation?", "kind": "process", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "task-owner-dependency-deadline-state-evidence-exception-and-escalation-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support task, owner, dependency, deadline, state, evidence, exception and escalation?", "kind": "composition", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "task-owner-dependency-deadline-state-evidence-exception-and-escalation-q03", "text": "How may task, owner, dependency, deadline, state, evidence, exception and escalation be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "event", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "task-owner-dependency-deadline-state-evidence-exception-and-escalation-data", "name": "Task, owner, dependency, deadline, state, evidence, exception and escalation data", "description": "Structured data for task, owner, dependency, deadline, state, evidence, exception and escalation with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "task-owner-dependency-deadline-state-evidence-exception-and-escalation-record", "name": "Task, owner, dependency, deadline, state, evidence, exception and escalation record", "description": "Versioned evidence-bearing transition record for task, owner, dependency, deadline, state, evidence, exception and escalation.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus task-owner-dependency-deadline-state-evidence-exception-and-escalation assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "policy-notice-agreements-and-continuing-duties", "name": "Policy, notice, agreements and continuing duties", "description": "Groups transition evidence for policy, notice, agreements and continuing duties.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ], "findings": [ { "id": "policy-jurisdiction-notice-privacy-purpose-consent-rights-and-accessibility", "name": "Policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility", "description": "Records policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ], "questions": [ { "id": "policy-jurisdiction-notice-privacy-purpose-consent-rights-and-accessibility-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility?", "kind": "privacy", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "policy-jurisdiction-notice-privacy-purpose-consent-rights-and-accessibility-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility?", "kind": "spatial", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "policy-jurisdiction-notice-privacy-purpose-consent-rights-and-accessibility-q03", "text": "How may policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "decision", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "policy-jurisdiction-notice-privacy-purpose-consent-rights-and-accessibility-data", "name": "Policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility data", "description": "Structured data for policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "policy-jurisdiction-notice-privacy-purpose-consent-rights-and-accessibility-record", "name": "Policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility record", "description": "Versioned evidence-bearing transition record for policy, jurisdiction, notice, privacy purpose, consent, rights and accessibility.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus policy-jurisdiction-notice-privacy-purpose-consent-rights-and-accessibility assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "employment-security-confidentiality-ip-conduct-access-and-post-exit-obligations", "name": "Employment, security, confidentiality, IP, conduct, access and post-exit obligations", "description": "Records employment, security, confidentiality, ip, conduct, access and post-exit obligations as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ], "questions": [ { "id": "employment-security-confidentiality-ip-conduct-access-and-post-exit-obligations-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish employment, security, confidentiality, ip, conduct, access and post-exit obligations?", "kind": "constraint", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "employment-security-confidentiality-ip-conduct-access-and-post-exit-obligations-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support employment, security, confidentiality, ip, conduct, access and post-exit obligations?", "kind": "process", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "employment-security-confidentiality-ip-conduct-access-and-post-exit-obligations-q03", "text": "How may employment, security, confidentiality, ip, conduct, access and post-exit obligations be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "ownership", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "employment-security-confidentiality-ip-conduct-access-and-post-exit-obligations-data", "name": "Employment, security, confidentiality, IP, conduct, access and post-exit obligations data", "description": "Structured data for employment, security, confidentiality, ip, conduct, access and post-exit obligations with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "employment-security-confidentiality-ip-conduct-access-and-post-exit-obligations-record", "name": "Employment, security, confidentiality, IP, conduct, access and post-exit obligations record", "description": "Versioned evidence-bearing transition record for employment, security, confidentiality, ip, conduct, access and post-exit obligations.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus employment-security-confidentiality-ip-conduct-access-and-post-exit-obligations assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "identity-access-workplace-and-facilities", "name": "Identity, access, workplace and facilities", "description": "Groups governed context for identity, access, workplace and facilities.", "rationale": "Desired access must be separately requested, executed and verified in authoritative systems.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011" ], "layers": [ { "id": "identity-accounts-credentials-and-access", "name": "Identity, accounts, credentials and access", "description": "Groups transition evidence for identity, accounts, credentials and access.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010" ], "findings": [ { "id": "person-identity-proofing-worker-id-directory-account-and-alias-binding", "name": "Person identity proofing, worker ID, directory account and alias binding", "description": "Records person identity proofing, worker id, directory account and alias binding as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010" ], "questions": [ { "id": "person-identity-proofing-worker-id-directory-account-and-alias-binding-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish person identity proofing, worker id, directory account and alias binding?", "kind": "identity", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "person-identity-proofing-worker-id-directory-account-and-alias-binding-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support person identity proofing, worker id, directory account and alias binding?", "kind": "quality", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "person-identity-proofing-worker-id-directory-account-and-alias-binding-q03", "text": "How may person identity proofing, worker id, directory account and alias binding be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "privacy", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "person-identity-proofing-worker-id-directory-account-and-alias-binding-data", "name": "Person identity proofing, worker ID, directory account and alias binding data", "description": "Structured data for person identity proofing, worker id, directory account and alias binding with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "person-identity-proofing-worker-id-directory-account-and-alias-binding-record", "name": "Person identity proofing, worker ID, directory account and alias binding record", "description": "Versioned evidence-bearing transition record for person identity proofing, worker id, directory account and alias binding.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus person-identity-proofing-worker-id-directory-account-and-alias-binding assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "access-grant-role-group-entitlement-credential-mfa-privilege-and-separation", "name": "Access grant, role, group, entitlement, credential, MFA, privilege and separation", "description": "Records access grant, role, group, entitlement, credential, mfa, privilege and separation as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010" ], "questions": [ { "id": "access-grant-role-group-entitlement-credential-mfa-privilege-and-separation-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish access grant, role, group, entitlement, credential, mfa, privilege and separation?", "kind": "access", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "access-grant-role-group-entitlement-credential-mfa-privilege-and-separation-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support access grant, role, group, entitlement, credential, mfa, privilege and separation?", "kind": "exception", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "access-grant-role-group-entitlement-credential-mfa-privilege-and-separation-q03", "text": "How may access grant, role, group, entitlement, credential, mfa, privilege and separation be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "state", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "access-grant-role-group-entitlement-credential-mfa-privilege-and-separation-data", "name": "Access grant, role, group, entitlement, credential, MFA, privilege and separation data", "description": "Structured data for access grant, role, group, entitlement, credential, mfa, privilege and separation with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "access-grant-role-group-entitlement-credential-mfa-privilege-and-separation-record", "name": "Access grant, role, group, entitlement, credential, MFA, privilege and separation record", "description": "Versioned evidence-bearing transition record for access grant, role, group, entitlement, credential, mfa, privilege and separation.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus access-grant-role-group-entitlement-credential-mfa-privilege-and-separation assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "applications-workspaces-facilities-and-safety", "name": "Applications, workspaces, facilities and safety", "description": "Groups transition evidence for applications, workspaces, facilities and safety.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011" ], "findings": [ { "id": "application-service-account-owner-start-stop-provisioning-and-verification", "name": "Application, service, account, owner, start, stop, provisioning and verification", "description": "Records application, service, account, owner, start, stop, provisioning and verification as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011" ], "questions": [ { "id": "application-service-account-owner-start-stop-provisioning-and-verification-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish application, service, account, owner, start, stop, provisioning and verification?", "kind": "validation", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "application-service-account-owner-start-stop-provisioning-and-verification-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support application, service, account, owner, start, stop, provisioning and verification?", "kind": "identity", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "application-service-account-owner-start-stop-provisioning-and-verification-q03", "text": "How may application, service, account, owner, start, stop, provisioning and verification be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "measurement", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "application-service-account-owner-start-stop-provisioning-and-verification-data", "name": "Application, service, account, owner, start, stop, provisioning and verification data", "description": "Structured data for application, service, account, owner, start, stop, provisioning and verification with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011" ] } ], "artifacts": [ { "id": "application-service-account-owner-start-stop-provisioning-and-verification-record", "name": "Application, service, account, owner, start, stop, provisioning and verification record", "description": "Versioned evidence-bearing transition record for application, service, account, owner, start, stop, provisioning and verification.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus application-service-account-owner-start-stop-provisioning-and-verification assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "workspace-location-badge-key-physical-access-safety-emergency-and-return", "name": "Workspace, location, badge, key, physical access, safety, emergency and return", "description": "Records workspace, location, badge, key, physical access, safety, emergency and return as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011" ], "questions": [ { "id": "workspace-location-badge-key-physical-access-safety-emergency-and-return-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish workspace, location, badge, key, physical access, safety, emergency and return?", "kind": "spatial", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "workspace-location-badge-key-physical-access-safety-emergency-and-return-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support workspace, location, badge, key, physical access, safety, emergency and return?", "kind": "lifecycle", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "workspace-location-badge-key-physical-access-safety-emergency-and-return-q03", "text": "How may workspace, location, badge, key, physical access, safety, emergency and return be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "definition", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "workspace-location-badge-key-physical-access-safety-emergency-and-return-data", "name": "Workspace, location, badge, key, physical access, safety, emergency and return data", "description": "Structured data for workspace, location, badge, key, physical access, safety, emergency and return with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011" ] } ], "artifacts": [ { "id": "workspace-location-badge-key-physical-access-safety-emergency-and-return-record", "name": "Workspace, location, badge, key, physical access, safety, emergency and return record", "description": "Versioned evidence-bearing transition record for workspace, location, badge, key, physical access, safety, emergency and return.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus workspace-location-badge-key-physical-access-safety-emergency-and-return assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "assets-data-knowledge-and-readiness", "name": "Assets, data, knowledge and readiness", "description": "Groups governed context for assets, data, knowledge and readiness.", "rationale": "Assets, information custody, knowledge and competence remain explicit and reconciled.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "layers": [ { "id": "equipment-assets-licences-and-custody", "name": "Equipment, assets, licences and custody", "description": "Groups transition evidence for equipment, assets, licences and custody.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ], "findings": [ { "id": "device-equipment-card-key-token-software-licence-and-inventory-reference", "name": "Device, equipment, card, key, token, software licence and inventory reference", "description": "Records device, equipment, card, key, token, software licence and inventory reference as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ], "questions": [ { "id": "device-equipment-card-key-token-software-licence-and-inventory-reference-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish device, equipment, card, key, token, software licence and inventory reference?", "kind": "composition", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "device-equipment-card-key-token-software-licence-and-inventory-reference-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support device, equipment, card, key, token, software licence and inventory reference?", "kind": "authority", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "device-equipment-card-key-token-software-licence-and-inventory-reference-q03", "text": "How may device, equipment, card, key, token, software licence and inventory reference be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "requirement", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "device-equipment-card-key-token-software-licence-and-inventory-reference-data", "name": "Device, equipment, card, key, token, software licence and inventory reference data", "description": "Structured data for device, equipment, card, key, token, software licence and inventory reference with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "device-equipment-card-key-token-software-licence-and-inventory-reference-record", "name": "Device, equipment, card, key, token, software licence and inventory reference record", "description": "Versioned evidence-bearing transition record for device, equipment, card, key, token, software licence and inventory reference.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus device-equipment-card-key-token-software-licence-and-inventory-reference assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "issue-custody-condition-transfer-return-loss-damage-wipe-and-disposal-evidence", "name": "Issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence", "description": "Records issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ], "questions": [ { "id": "issue-custody-condition-transfer-return-loss-damage-wipe-and-disposal-evidence-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence?", "kind": "evidence", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "issue-custody-condition-transfer-return-loss-damage-wipe-and-disposal-evidence-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence?", "kind": "measurement", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "issue-custody-condition-transfer-return-loss-damage-wipe-and-disposal-evidence-q03", "text": "How may issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "retention", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "issue-custody-condition-transfer-return-loss-damage-wipe-and-disposal-evidence-data", "name": "Issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence data", "description": "Structured data for issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "issue-custody-condition-transfer-return-loss-damage-wipe-and-disposal-evidence-record", "name": "Issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence record", "description": "Versioned evidence-bearing transition record for issue, custody, condition, transfer, return, loss, damage, wipe and disposal evidence.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus issue-custody-condition-transfer-return-loss-damage-wipe-and-disposal-evidence assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "data-knowledge-training-and-support", "name": "Data, knowledge, training and support", "description": "Groups transition evidence for data, knowledge, training and support.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "findings": [ { "id": "data-owner-record-custody-file-mailbox-repository-transfer-retention-and-hold", "name": "Data owner, record custody, file, mailbox, repository, transfer, retention and hold", "description": "Records data owner, record custody, file, mailbox, repository, transfer, retention and hold as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "data-owner-record-custody-file-mailbox-repository-transfer-retention-and-hold-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish data owner, record custody, file, mailbox, repository, transfer, retention and hold?", "kind": "ownership", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "data-owner-record-custody-file-mailbox-repository-transfer-retention-and-hold-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support data owner, record custody, file, mailbox, repository, transfer, retention and hold?", "kind": "privacy", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "data-owner-record-custody-file-mailbox-repository-transfer-retention-and-hold-q03", "text": "How may data owner, record custody, file, mailbox, repository, transfer, retention and hold be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "lifecycle", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "data-owner-record-custody-file-mailbox-repository-transfer-retention-and-hold-data", "name": "Data owner, record custody, file, mailbox, repository, transfer, retention and hold data", "description": "Structured data for data owner, record custody, file, mailbox, repository, transfer, retention and hold with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "data-owner-record-custody-file-mailbox-repository-transfer-retention-and-hold-record", "name": "Data owner, record custody, file, mailbox, repository, transfer, retention and hold record", "description": "Versioned evidence-bearing transition record for data owner, record custody, file, mailbox, repository, transfer, retention and hold.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus data-owner-record-custody-file-mailbox-repository-transfer-retention-and-hold assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "induction-training-policy-acknowledgement-competency-mentor-handover-and-readiness", "name": "Induction, training, policy acknowledgement, competency, mentor, handover and readiness", "description": "Records induction, training, policy acknowledgement, competency, mentor, handover and readiness as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ], "questions": [ { "id": "induction-training-policy-acknowledgement-competency-mentor-handover-and-readiness-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish induction, training, policy acknowledgement, competency, mentor, handover and readiness?", "kind": "quality", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "induction-training-policy-acknowledgement-competency-mentor-handover-and-readiness-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support induction, training, policy acknowledgement, competency, mentor, handover and readiness?", "kind": "decision", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "induction-training-policy-acknowledgement-competency-mentor-handover-and-readiness-q03", "text": "How may induction, training, policy acknowledgement, competency, mentor, handover and readiness be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "evidence", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "induction-training-policy-acknowledgement-competency-mentor-handover-and-readiness-data", "name": "Induction, training, policy acknowledgement, competency, mentor, handover and readiness data", "description": "Structured data for induction, training, policy acknowledgement, competency, mentor, handover and readiness with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "artifacts": [ { "id": "induction-training-policy-acknowledgement-competency-mentor-handover-and-readiness-record", "name": "Induction, training, policy acknowledgement, competency, mentor, handover and readiness record", "description": "Versioned evidence-bearing transition record for induction, training, policy acknowledgement, competency, mentor, handover and readiness.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus induction-training-policy-acknowledgement-competency-mentor-handover-and-readiness assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "execution-verification-handover-and-outcome", "name": "Execution, verification, handover and outcome", "description": "Groups governed context for execution, verification, handover and outcome.", "rationale": "Completion is evidence-bearing and distinct from request, checklist state and downstream master state.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ], "layers": [ { "id": "communications-administration-benefits-and-support", "name": "Communications, administration, benefits and support", "description": "Groups transition evidence for communications, administration, benefits and support.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014" ], "findings": [ { "id": "welcome-exit-notice-audience-channel-template-language-acknowledgement-and-feedback", "name": "Welcome or exit notice, audience, channel, template, language, acknowledgement and feedback", "description": "Records welcome or exit notice, audience, channel, template, language, acknowledgement and feedback as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014" ], "questions": [ { "id": "welcome-exit-notice-audience-channel-template-language-acknowledgement-and-feedback-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish welcome or exit notice, audience, channel, template, language, acknowledgement and feedback?", "kind": "event", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "welcome-exit-notice-audience-channel-template-language-acknowledgement-and-feedback-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support welcome or exit notice, audience, channel, template, language, acknowledgement and feedback?", "kind": "relationship", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "welcome-exit-notice-audience-channel-template-language-acknowledgement-and-feedback-q03", "text": "How may welcome or exit notice, audience, channel, template, language, acknowledgement and feedback be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "identity", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "welcome-exit-notice-audience-channel-template-language-acknowledgement-and-feedback-data", "name": "Welcome or exit notice, audience, channel, template, language, acknowledgement and feedback data", "description": "Structured data for welcome or exit notice, audience, channel, template, language, acknowledgement and feedback with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014" ] } ], "artifacts": [ { "id": "welcome-exit-notice-audience-channel-template-language-acknowledgement-and-feedback-record", "name": "Welcome or exit notice, audience, channel, template, language, acknowledgement and feedback record", "description": "Versioned evidence-bearing transition record for welcome or exit notice, audience, channel, template, language, acknowledgement and feedback.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus welcome-exit-notice-audience-channel-template-language-acknowledgement-and-feedback assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "payroll-benefit-tax-legal-form-contact-support-and-downstream-handoff", "name": "Payroll, benefit, tax, legal form, contact, support and downstream handoff", "description": "Records payroll, benefit, tax, legal form, contact, support and downstream handoff as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014" ], "questions": [ { "id": "payroll-benefit-tax-legal-form-contact-support-and-downstream-handoff-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish payroll, benefit, tax, legal form, contact, support and downstream handoff?", "kind": "relationship", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "payroll-benefit-tax-legal-form-contact-support-and-downstream-handoff-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support payroll, benefit, tax, legal form, contact, support and downstream handoff?", "kind": "provenance", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "payroll-benefit-tax-legal-form-contact-support-and-downstream-handoff-q03", "text": "How may payroll, benefit, tax, legal form, contact, support and downstream handoff be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "requirement", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "payroll-benefit-tax-legal-form-contact-support-and-downstream-handoff-data", "name": "Payroll, benefit, tax, legal form, contact, support and downstream handoff data", "description": "Structured data for payroll, benefit, tax, legal form, contact, support and downstream handoff with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014" ] } ], "artifacts": [ { "id": "payroll-benefit-tax-legal-form-contact-support-and-downstream-handoff-record", "name": "Payroll, benefit, tax, legal form, contact, support and downstream handoff record", "description": "Versioned evidence-bearing transition record for payroll, benefit, tax, legal form, contact, support and downstream handoff.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus payroll-benefit-tax-legal-form-contact-support-and-downstream-handoff assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "revocation-return-exit-and-certification", "name": "Revocation, return, exit and certification", "description": "Groups transition evidence for revocation, return, exit and certification.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-014" ], "findings": [ { "id": "disable-revoke-terminate-session-rotate-secret-remove-group-and-verify-access-loss", "name": "Disable, revoke, terminate session, rotate secret, remove group and verify access loss", "description": "Records disable, revoke, terminate session, rotate secret, remove group and verify access loss as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-014" ], "questions": [ { "id": "disable-revoke-terminate-session-rotate-secret-remove-group-and-verify-access-loss-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish disable, revoke, terminate session, rotate secret, remove group and verify access loss?", "kind": "security", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "disable-revoke-terminate-session-rotate-secret-remove-group-and-verify-access-loss-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support disable, revoke, terminate session, rotate secret, remove group and verify access loss?", "kind": "process", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "disable-revoke-terminate-session-rotate-secret-remove-group-and-verify-access-loss-q03", "text": "How may disable, revoke, terminate session, rotate secret, remove group and verify access loss be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "access", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "disable-revoke-terminate-session-rotate-secret-remove-group-and-verify-access-loss-data", "name": "Disable, revoke, terminate session, rotate secret, remove group and verify access loss data", "description": "Structured data for disable, revoke, terminate session, rotate secret, remove group and verify access loss with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "disable-revoke-terminate-session-rotate-secret-remove-group-and-verify-access-loss-record", "name": "Disable, revoke, terminate session, rotate secret, remove group and verify access loss record", "description": "Versioned evidence-bearing transition record for disable, revoke, terminate session, rotate secret, remove group and verify access loss.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus disable-revoke-terminate-session-rotate-secret-remove-group-and-verify-access-loss assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "exit-interview-return-reconciliation-knowledge-transfer-continuing-duty-and-closure-certificate", "name": "Exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate", "description": "Records exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-014" ], "questions": [ { "id": "exit-interview-return-reconciliation-knowledge-transfer-continuing-duty-and-closure-certificate-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate?", "kind": "validation", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "exit-interview-return-reconciliation-knowledge-transfer-continuing-duty-and-closure-certificate-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate?", "kind": "security", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "exit-interview-return-reconciliation-knowledge-transfer-continuing-duty-and-closure-certificate-q03", "text": "How may exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "temporal", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "exit-interview-return-reconciliation-knowledge-transfer-continuing-duty-and-closure-certificate-data", "name": "Exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate data", "description": "Structured data for exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "exit-interview-return-reconciliation-knowledge-transfer-continuing-duty-and-closure-certificate-record", "name": "Exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate record", "description": "Versioned evidence-bearing transition record for exit interview, return reconciliation, knowledge transfer, continuing duty and closure certificate.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus exit-interview-return-reconciliation-knowledge-transfer-continuing-duty-and-closure-certificate assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-quality-interoperability-and-agents", "name": "Lifecycle, quality, interoperability and agents", "description": "Groups governed context for lifecycle, quality, interoperability and agents.", "rationale": "History, exceptions, projections and automation remain attributable and loss-aware.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ], "layers": [ { "id": "lifecycle-exceptions-quality-and-improvement", "name": "Lifecycle, exceptions, quality and improvement", "description": "Groups transition evidence for lifecycle, exceptions, quality and improvement.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-014" ], "findings": [ { "id": "planned-authorized-scheduled-active-blocked-completed-cancelled-corrected-and-archived-event", "name": "Planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event", "description": "Records planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-014" ], "questions": [ { "id": "planned-authorized-scheduled-active-blocked-completed-cancelled-corrected-and-archived-event-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event?", "kind": "lifecycle", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "planned-authorized-scheduled-active-blocked-completed-cancelled-corrected-and-archived-event-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event?", "kind": "exception", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "planned-authorized-scheduled-active-blocked-completed-cancelled-corrected-and-archived-event-q03", "text": "How may planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "quality", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "planned-authorized-scheduled-active-blocked-completed-cancelled-corrected-and-archived-event-data", "name": "Planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event data", "description": "Structured data for planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "planned-authorized-scheduled-active-blocked-completed-cancelled-corrected-and-archived-event-record", "name": "Planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event record", "description": "Versioned evidence-bearing transition record for planned, authorized, scheduled, active, blocked, completed, cancelled, corrected and archived event.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus planned-authorized-scheduled-active-blocked-completed-cancelled-corrected-and-archived-event assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "timeliness-completeness-access-drift-asset-gap-exception-incident-feedback-and-improvement", "name": "Timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement", "description": "Records timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-014" ], "questions": [ { "id": "timeliness-completeness-access-drift-asset-gap-exception-incident-feedback-and-improvement-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement?", "kind": "measurement", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "timeliness-completeness-access-drift-asset-gap-exception-incident-feedback-and-improvement-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement?", "kind": "classification", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "timeliness-completeness-access-drift-asset-gap-exception-incident-feedback-and-improvement-q03", "text": "How may timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "composition", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "timeliness-completeness-access-drift-asset-gap-exception-incident-feedback-and-improvement-data", "name": "Timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement data", "description": "Structured data for timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-014" ] } ], "artifacts": [ { "id": "timeliness-completeness-access-drift-asset-gap-exception-incident-feedback-and-improvement-record", "name": "Timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement record", "description": "Versioned evidence-bearing transition record for timeliness, completeness, access drift, asset gap, exception, incident, feedback and improvement.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus timeliness-completeness-access-drift-asset-gap-exception-incident-feedback-and-improvement assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "provenance-interoperability-retention-and-safe-automation", "name": "Provenance, interoperability, retention and safe automation", "description": "Groups transition evidence for provenance, interoperability, retention and safe automation.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ], "findings": [ { "id": "scim-security-control-hr-system-task-and-provenance-crosswalk", "name": "SCIM, security-control, HR-system, task and provenance crosswalk", "description": "Records scim, security-control, hr-system, task and provenance crosswalk as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ], "questions": [ { "id": "scim-security-control-hr-system-task-and-provenance-crosswalk-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish scim, security-control, hr-system, task and provenance crosswalk?", "kind": "interoperability", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "scim-security-control-hr-system-task-and-provenance-crosswalk-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support scim, security-control, hr-system, task and provenance crosswalk?", "kind": "temporal", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "scim-security-control-hr-system-task-and-provenance-crosswalk-q03", "text": "How may scim, security-control, hr-system, task and provenance crosswalk be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "constraint", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "scim-security-control-hr-system-task-and-provenance-crosswalk-data", "name": "SCIM, security-control, HR-system, task and provenance crosswalk data", "description": "Structured data for scim, security-control, hr-system, task and provenance crosswalk with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "scim-security-control-hr-system-task-and-provenance-crosswalk-record", "name": "SCIM, security-control, HR-system, task and provenance crosswalk record", "description": "Versioned evidence-bearing transition record for scim, security-control, hr-system, task and provenance crosswalk.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus scim-security-control-hr-system-task-and-provenance-crosswalk assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "purpose-redaction-retention-hold-agent-authority-idempotency-dry-run-and-postcheck", "name": "Purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check", "description": "Records purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check as source-qualified desired, requested, executed or verified transition context without absorbing external master records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ], "questions": [ { "id": "purpose-redaction-retention-hold-agent-authority-idempotency-dry-run-and-postcheck-q01", "text": "What transition-scoped identities, classes, roles, versions, values and explicit unknowns establish purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check?", "kind": "access", "answer_data": [ "identities and classifications", "roles, versions and values", "explicit unknowns" ] }, { "id": "purpose-redaction-retention-hold-agent-authority-idempotency-dry-run-and-postcheck-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limits support purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check?", "kind": "requirement", "answer_data": [ "authority and source", "method and evidence", "times, confidence and limits" ] }, { "id": "purpose-redaction-retention-hold-agent-authority-idempotency-dry-run-and-postcheck-q03", "text": "How may purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check be validated, executed, challenged, corrected, related, retained or disposed without losing history?", "kind": "exception", "answer_data": [ "validation and execution", "challenge and correction", "relations, retention and disposition" ] } ], "data_elements": [ { "id": "purpose-redaction-retention-hold-agent-authority-idempotency-dry-run-and-postcheck-data", "name": "Purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check data", "description": "Structured data for purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check with authority, time, state, evidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "purpose-redaction-retention-hold-agent-authority-idempotency-dry-run-and-postcheck-record", "name": "Purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check record", "description": "Versioned evidence-bearing transition record for purpose, redaction, retention, hold, agent authority, idempotency, dry run and post-check.", "media_or_form": [ "logical transition assertion", "task, reference, event, evidence or outcome record" ], "serial": true, "identity_strategy": "Transition case ID plus purpose-redaction-retention-hold-agent-authority-idempotency-dry-run-and-postcheck assertion or event ID; person name, date, timestamp and digest never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-transition-case", "name": "Register transition case", "description": "Governed operation to register transition case with attributable evidence and no hidden master-system mutation.", "inputs": [ "trigger", "employment and role refs", "profile" ], "outputs": [ "case root" ], "preconditions": [ "identity and authority pass" ], "effects": [ "bounded case exists" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010" ] }, { "id": "plan-and-authorize-transition", "name": "Plan and authorize transition", "description": "Governed operation to plan and authorize transition with attributable evidence and no hidden master-system mutation.", "inputs": [ "case", "policy", "tasks", "roles" ], "outputs": [ "authorized plan" ], "preconditions": [ "scope, dependency and timing pass" ], "effects": [ "accountable work is released" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "provision-identity-access-and-workplace", "name": "Provision identity, access and workplace", "description": "Governed operation to provision identity, access and workplace with attributable evidence and no hidden master-system mutation.", "inputs": [ "plan", "identity refs", "access requests" ], "outputs": [ "execution evidence" ], "preconditions": [ "need, approval and least privilege pass" ], "effects": [ "authorized resources become usable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "issue-and-reconcile-assets", "name": "Issue and reconcile assets", "description": "Governed operation to issue and reconcile assets with attributable evidence and no hidden master-system mutation.", "inputs": [ "plan", "asset refs", "custody events" ], "outputs": [ "custody evidence" ], "preconditions": [ "inventory and responsibility pass" ], "effects": [ "assets remain traceable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "transfer-data-and-knowledge", "name": "Transfer data and knowledge", "description": "Governed operation to transfer data and knowledge with attributable evidence and no hidden master-system mutation.", "inputs": [ "records", "repositories", "handover plan" ], "outputs": [ "custody and handover evidence" ], "preconditions": [ "owner, access, retention and privacy pass" ], "effects": [ "continuity is preserved without ownership collapse" ], "source_refs": [ "SRC-006", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ] }, { "id": "deliver-induction-training-and-support", "name": "Deliver induction, training and support", "description": "Governed operation to deliver induction, training and support with attributable evidence and no hidden master-system mutation.", "inputs": [ "role needs", "training refs", "mentor" ], "outputs": [ "readiness evidence" ], "preconditions": [ "accessibility, competence and acknowledgement pass" ], "effects": [ "worker receives governed preparation" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-011" ] }, { "id": "revoke-access-and-recover-assets", "name": "Revoke access and recover assets", "description": "Governed operation to revoke access and recover assets with attributable evidence and no hidden master-system mutation.", "inputs": [ "leave or move authority", "inventories" ], "outputs": [ "revocation and return evidence" ], "preconditions": [ "timing, scope, exceptions and verification pass" ], "effects": [ "unneeded access ends and custody is reconciled" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "close-and-certify-transition", "name": "Close and certify transition", "description": "Governed operation to close and certify transition with attributable evidence and no hidden master-system mutation.", "inputs": [ "task evidence", "exceptions", "handoffs" ], "outputs": [ "closure certificate" ], "preconditions": [ "required evidence and residual risk pass" ], "effects": [ "case closes without asserting downstream states falsely" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-010", "SRC-014" ] }, { "id": "measure-quality-and-correct-drift", "name": "Measure quality and correct drift", "description": "Governed operation to measure quality and correct drift with attributable evidence and no hidden master-system mutation.", "inputs": [ "case events", "service targets", "inventory checks" ], "outputs": [ "quality report and corrections" ], "preconditions": [ "denominator, source and privacy pass" ], "effects": [ "late, missing or stale changes are visible" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-012" ] }, { "id": "project-retain-and-audit", "name": "Project, retain and audit", "description": "Governed operation to project, retain and audit with attributable evidence and no hidden master-system mutation.", "inputs": [ "case revision", "target profile", "purpose", "policy" ], "outputs": [ "projection or disposition event" ], "preconditions": [ "mapping loss, hold, idempotency and post-check pass" ], "effects": [ "context remains interoperable and accountable" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ] } ], "composition": [ { "target": "Person, Employment, Role Assignment, Organization and Unit models", "relation": "REFERENCE", "purpose": "Bind subject and transition authority without absorbing workforce masters.", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-010" ] }, { "target": "Account, Credential, Group, Access Grant and Facility Access models", "relation": "COMPOSE", "purpose": "Coordinate desired and verified access changes while masters retain effective state.", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007" ] }, { "target": "Device, Asset, Licence, Workspace and Facility models", "relation": "REFERENCE", "purpose": "Coordinate custody and readiness through authoritative inventory references.", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] }, { "target": "Training, Competency, Agreement, Benefit, Dataset, Record, Communication and Audit models", "relation": "REFERENCE", "purpose": "Link obligations, readiness, handover and evidence without lifecycle cascade.", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ] }, { "target": "NIST SP 800-53, CIS Controls v8, SCIM RFC 7643 and RFC 7644", "relation": "ALIGN", "purpose": "Project security-control and identity-provisioning views with pinned versions and declared loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension owner and worker-transition authority", "Employment, role, access, asset, training, record and policy registries", "Master mappings for people, employment, roles, accounts, grants, assets, training, agreements, data and audit", "Joiner, mover, leaver, rejoin, emergency exit, privacy, retention and agent policies" ], "namespace_guidance": "Mint case, plan-release, task, event, verification and closure IDs; preserve external person, employment, account, grant, asset and record identities.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by source, case ID, mandatory profile and lineage head, never person name or date.", "Keep desired, requested, executed, verified and effective states distinct." ], "patch_rules": [ "Extensions declare profile, authority, lifecycle, privacy, security and interoperability effects.", "Released plans, tasks and evidence are immutable; corrections create successors.", "Never silently change role, access, asset, evidence, outcome or time." ], "compatibility_rules": [ "Ignore additive fields only when identity, profile, authority, tasks, evidence, lifecycle and provenance survive.", "SCIM and control mappings pin versions and declare loss." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system transition-case identifier qualified by source and profile.", "Governed global case IRI.", "Dimension UUID." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; separate planned, requested, executed, verified, effective, ingestion and knowledge times.", "serial_naming_rule": "Use {case-id}--{plan-or-stage}--{artifact-kind}--{assertion-or-event-id}.", "integrity_rule": "Store digest, media type, case and release binding, source versions, actor, event and knowledge times, access marking and provenance." }, "policies": [ "The transition case is not Employment, Person, Role, Account, Access Grant, Asset, Training, Agreement, Record or Audit master.", "Request, execution, verification and effective state remain separate.", "Case ownership never transfers or cascades master ownership.", "Agents cannot grant access, terminate employment, disclose protected data or delete records without delegated authority." ], "crud": { "read": [ "Resolve policies, case, profile, plan, tasks, masters, evidence, exceptions and access purpose." ], "create": [ "Bind stable identity, profile, trigger, authority, employment and role before tasks." ], "update": [ "Append task and lifecycle events with authority, reason, times and expected revision." ], "delete": [ "Apply privacy, employment, security, records, hold and retention policy; archive case separately and never cascade." ] }, "roles": [ { "name": "Employment or transition authority", "responsibilities": [ "Own trigger and effective transition." ] }, { "name": "Manager and HR steward", "responsibilities": [ "Own plan, role readiness and worker communication." ] }, { "name": "Identity and access steward", "responsibilities": [ "Own accounts, credentials, grants and revocation evidence." ] }, { "name": "Asset and workplace steward", "responsibilities": [ "Own custody, workspace and physical access." ] }, { "name": "Data and knowledge steward", "responsibilities": [ "Own record custody and handover." ] }, { "name": "Training and support steward", "responsibilities": [ "Own induction, competence and support." ] }, { "name": "Privacy and security steward", "responsibilities": [ "Own protected views, incidents and residual risk." ] }, { "name": "Records and audit steward", "responsibilities": [ "Own retention, holds, disposition and auditability." ] } ], "access": { "default_rule": "Deny personal, employment, compensation, health, accommodation, security, access, credential and exit data unless purpose-bound policy permits the minimum necessary view.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Worker, manager, HR, security, support, auditor, regulator or court access cites authority and is time-limited and logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, case, operation, policy, RFC 3339 time, affected fields, source revision and outcome without unnecessary protected data." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension employment, access, asset, privacy, security, retention and agent policies.", "Read this model and linked person, employment, role, account, grant, asset, training, agreement, data and audit models before mutation." ] } }, "coverage": { "claim": "Covers join, move, leave and rejoin transition cases from trigger and plan through identity, access, workplace, assets, data, knowledge, training, execution, verification, closure, quality and lifecycle events with 24 source-qualified findings and 10 governed operations. It remains a reviewable draft with explicit relation, regional, ISO-access and independent-review limits.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Identity is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "classification and definition", "status": "covered", "notes": "Classification and definition is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "direct properties", "status": "covered", "notes": "Direct properties is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Recognition and observation is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Capabilities and possible actions is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "composition", "status": "gap", "notes": "Composition is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "lifecycle", "status": "covered", "notes": "Lifecycle is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "relationships", "status": "covered", "notes": "Relationships is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "temporal", "status": "covered", "notes": "Temporal is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "spatial", "status": "covered", "notes": "Spatial is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "provenance", "status": "covered", "notes": "Provenance is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Ownership and stewardship is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "validation and quality", "status": "covered", "notes": "Validation and quality is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "access and privacy", "status": "covered", "notes": "Access and privacy is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retention and deletion is explicit; candidate relations and mappings remain held where applicable." }, { "dimension": "interoperability", "status": "gap", "notes": "Interoperability is explicit; candidate relations and mappings remain held where applicable." } ], "known_omissions": [ "Claude and Grok each timed out on one bounded attempt; no independent external result was admitted.", "No approved relation rows were supplied; the Employment parent and proposed master relations remain candidate holds.", "ISO 30414 is represented only by its public abstract; no normative conformance is claimed.", "OPM and CISA are United States profiles, NCSC is United Kingdom guidance and GDPR is European Union law; none is universal.", "Payroll, benefits, labour law, collective consultation, immigration, records, safety, accessibility and involuntary-separation rules vary by jurisdiction." ], "conflicts": [ "Onboarding, induction, provisioning and employment commencement are not synonymous.", "Offboarding, termination, transfer, revocation, return, archival and deletion have different authorities and times.", "Continuity, privacy, evidence retention, least privilege, worker rights and urgent containment can conflict." ], "regional_assumptions": [ "Employee, contractor, volunteer, contingent worker, public officer and third party require different profiles.", "Planned and emergency or involuntary separations require different notice, timing and access controls.", "SCIM expresses exchange and administrative status but does not define authorization semantics." ], "adversarial_checks": [ "Reject a case without stable identity, mandatory profile, trigger, authority, master bindings and lifecycle head.", "Reject employment inferred from onboarding, authority from group membership, completion from checklist state, revocation from request or deletion from disablement.", "Reject corrections that overwrite plans, tasks, access evidence, asset custody, handovers or closure history.", "Reject copied person, employment, account, grant, asset, training or record masters.", "Reject autonomous access grants, employment termination, protected disclosure or deletion outside delegated authority." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "Entry kind aggregate correctly selected from schema enum. Frozen registry value 'standalone-mm' is a record-plane classifier, not a subject-model kind. Aggregate is defensible: the model owns transition case identity, lineage, profile, plans, tasks, evidence and lifecycle while maintaining explicit boundaries with external Person, Employment, Role, Account, Access Grant, Asset, Training, Agreement, Dataset, Record, Communication and Audit masters. Boundary notes with SRC-001, SRC-005, SRC-006, SRC-010 distinguish case bindings (owned) from master lifecycles (delegated)." }, "decisions": [ { "concept": "Aggregate Root Stability and Mandatory Profile", "disposition": "accepted", "rationale": "Model's CRUD.create rule establishes that stable identity, mandatory profile (join/move/leave/rejoin), trigger and authority bind before any task or event mutations. Findings on case-identifier-source-version-predecessor-successor-and-lineage establish lineage head. Source support: SRC-001, SRC-005, SRC-006, SRC-010. This prevents unauthenticated case creation and inference of employment from onboarding completion." }, { "concept": "Employment and Role Master Boundary Distinction", "disposition": "deferred", "rationale": "The model correctly declares that a case binds external Employment and Role relationships without owning either master. Boundary notes supported by SRC-001, SRC-005, SRC-006 and SRC-010 distinguish case transitions from master creation or termination. No approved relation row was supplied, so the proposed parent and related-master links remain candidate metadata and composition-completeness claims remain deferred." }, { "concept": "Access Revocation and Verified Evidence Protocol", "disposition": "accepted", "rationale": "Model establishes clear distinctions: access revocation *request* (finding disable-revoke-terminate-session-rotate-secret-remove-group-and-verify-access-loss) is separate from verified access *loss*, and both are separate from employment termination or deletion. Functions provision-identity-access-and-workplace and revoke-access-and-recover-assets both require 'attributable evidence and no hidden master-system mutation.' Policy enforces: 'Agents cannot grant access, terminate employment, disclose protected data or delete records without delegated authority.' Source support: SRC-001, SRC-002, SRC-003, SRC-004, SRC-006, SRC-007." }, { "concept": "Regional Jurisdiction and Payroll Scope Deferral", "disposition": "reclassified", "rationale": "The result distinguishes United States OPM and CISA profiles, United Kingdom NCSC guidance and European Union GDPR requirements. Payroll, benefits, labour law, consultation, immigration, records, safety, accessibility and involuntary-separation requirements vary by jurisdiction. The generic structure is publishable as a reviewable draft, while any operational deployment must bind an applicable regional profile and authority." }, { "concept": "Single-Provider Adjudication and Claude Timeout Pattern", "disposition": "reclassified", "rationale": "For WM-ACT-040, one Claude Sonnet attempt and one Grok 4.6 attempt each timed out after 120 seconds. No external result was admitted. The source-grounded Codex result passed local validation and this separate no-tools audit found no critical conflict. The provider absence remains visible, and the published lifecycle is limited to assurance level reviewable-draft." }, { "concept": "Composition Layer Gap and Interoperability Gap", "disposition": "accepted", "rationale": "Model explicitly marks composition and interoperability as 'gap' in coverage checklist. Coverage notes state 'Composition is explicit; candidate relations and mappings remain held where applicable' and 'Interoperability is explicit; candidate relations and mappings remain held where applicable.' This is honest. The gaps exist because relation rows to linked models are not supplied. This is acceptable as a frozen model plane; it flags what downstream synthesizer must complete." }, { "concept": "Source Authority Verification and ISO 30414 Conformance Limit", "disposition": "accepted", "rationale": "All 14 sources are authority tier 1 and URLs are present. However, ISO 30414:2025 is represented 'only by its public abstract; no normative conformance is claimed.' This explicitly limits HR capital reporting scope. OPM, CISA, NCSC, GDPR are cited but are regional/sectoral, not universal standards. Source support is adequate for a jurisdiction-instantiable skeleton but insufficient for a universal model. Accept with regional instantiation required." }, { "concept": "Artifact Identity Serial Naming and Timeline Separation", "disposition": "accepted", "rationale": "Artifact rules establish serial naming {case-id}--{plan-or-stage}--{artifact-kind}--{assertion-or-event-id} and timestamp rule 'Use RFC 3339 timestamps with seconds and explicit offset or Z; separate planned, requested, executed, verified, effective, ingestion and knowledge times.' This prevents person-name and date-based identity (which is correct for privacy). Multiple timestamps (planned vs. executed vs. verified vs. effective) enable auditing of drift, delay and reversal. Source support: SRC-003, SRC-004, SRC-010, SRC-014." }, { "concept": "Autonomous Operation Prevention and Delegated Authority Enforcement", "disposition": "accepted", "rationale": "Model policy: 'Agents cannot grant access, terminate employment, disclose protected data or delete records without delegated authority.' Adversarial checks declare: 'Reject corrections that overwrite plans, tasks, access evidence, asset custody, handovers or closure history' and 'Reject autonomous access grants, employment termination, protected disclosure or deletion outside delegated authority.' Service_layers.policies establish that 'Case ownership never transfers or cascades master ownership.' This prevents a compromised onboarding case from cascading mutations. Accept." }, { "concept": "Known Omissions and Adversarial Check Integrity", "disposition": "accepted", "rationale": "Model declares known_omissions and adversarial_checks explicitly: Claude/Grok timeouts, relation rows absent, regional assumptions, ISO 30414 limited scope. Adversarial checks list criteria for rejection (inferred employment, authority from group membership, completion from checklist state, copied masters, autonomous operations). These are self-protective. Model integrity is maintained by stating what it does not cover rather than hiding gaps. Accept as framework for synthesizer to enforce." } ], "publicationHolds": [ "Independent provider absence: one Claude Sonnet attempt and one Grok 4.6 attempt for WM-ACT-040 each timed out after 120 seconds. No external result was admitted; the completed separate no-tools audit supports publication only as reviewable-draft.", "Approved relation rows are absent. Cross-model links to Person, Employment, Role, Account, Access Grant, Asset, Training, Agreement, Data and Audit remain candidate metadata and block only composition-completeness claims, not publication of this reviewable draft.", "Regional operational use requires an applicable jurisdiction profile. OPM and CISA are United States profiles, NCSC is United Kingdom guidance and GDPR is European Union law; none is treated as universal.", "ISO 30414 representation limited: Only public abstract available. 'No normative conformance is claimed.' HR capital reporting conformance cannot be validated without full standard access.", "The owner-authorized external-provider waiver and the actual bounded attempt outcomes must remain visible in the publication artifacts.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify relation rows and cross-model consistency once Employment, Role, Account, Access Grant, Asset, Training, Agreement and Audit parent models are supplied with explicit foreign keys, ownership rules and lifecycle bindings to enable aggregate composition validation.", "Instantiate region-specific profiles for applicable jurisdictions (US federal with OPM/CISA rules, UK public sector with NCSC rules, EU member states with GDPR rules) with local labour law counsel review of confidentiality, access control, record retention, involuntary separation notice and worker rights variations.", "Obtain ISO 30414:2025 full normative standard and integrate HR capital reporting conformance requirements into findings and service layer policies; currently represented only by public abstract, limiting organizational reporting scope.", "Conduct secondary-provider independent review (Claude or Grok) on final relation rows and region-specific instantiations if model scope changes materially after deferred research completion; document provider selection rationale and any further timeouts." ] }, "statistics": { "sources": 14, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }