# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T01:11:05Z", "synthesisSha256": "29400ff51ee64aa2cc3439c57d093efed88f3ce9310ce8b0ea9792034969ad5d", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ORG-005", "registryId": "vr.wm-org-005", "name": "Employment", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "relationship", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ORG.EMP" ], "tags": [ "employment", "soc.org.emp" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-org-005-employment/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-org-005", "model": { "registry_id": "vr.wm-org-005", "model_id": "WM-ORG-005", "name": "Employment", "entry_kind": "relationship", "purpose": "Represent one governed, jurisdiction-qualified employment relationship between a worker party and an employing party, including identity, classification evidence, terms, assignment realization, continuity, separation, disagreement and provenance without depending on storage or interface format.", "scope_statement": "Owns employment relationship identity, party-role topology, asserted basis and jurisdiction, purpose-qualified classification assertions and determinations, effective term bindings, assignment realization links, relationship state, continuity and separation events, party assertions, evidence quality, privacy and interoperability projections while external systems own parties, positions, assignments, occupations, contracts, payroll, attendance, benefits, tax, social insurance, qualifications, recruitment, access grants and evidence objects.", "in_scope": [ "Employment relationship identity, worker and employing-party bindings, multi-party roles, basis, jurisdiction, classification assertions, determinations and recognition indicators", "Commencement, probation, term bindings, working-time and workplace context, position, assignment, occupation and skill references", "Relationship state, continuity, interruption, succession, separation, disputes, evidence, privacy, retention, verification, provenance and exchange" ], "out_of_scope": [ "Generic organizational membership and affiliation, which belong to WM-ORG-006 Membership", "Person, organization, unit, position, occupation, assignment, contract, payroll, compensation, attendance, benefits, tax, social insurance, qualification, recruitment, performance and work-product master lifecycles", "A universal legal definition of employee, worker or self-employment, or automatic authority for an agent to determine status, change terms, disclose sensitive data or end employment" ], "boundary_notes": [ { "neighbor": "Membership", "distinction": "Employment is a work relationship with asserted legal or factual basis, terms and labour effects; generic belonging, affiliation and member standing are owned by WM-ORG-006.", "source_refs": [ "SRC-001", "SRC-009" ] }, { "neighbor": "Work Assignment", "distinction": "WM-ORG-016 owns assignment identity, scope, duties, execution and lifecycle; Employment owns only the typed, time-qualified link showing which assignments realize the relationship.", "source_refs": [ "SRC-004", "SRC-007", "SRC-009" ] }, { "neighbor": "Position, Role and Occupation", "distinction": "A position can exist vacant, a role is a reusable concept and an occupation classifies similar jobs; none is an employment relationship or proves its legal status.", "source_refs": [ "SRC-004", "SRC-005", "SRC-009" ] }, { "neighbor": "Contract, Policy, Law and Collective Agreement", "distinction": "Normative instruments retain independent identity, text, authority, version and lifecycle; Employment stores versioned applicability and precedence bindings.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] }, { "neighbor": "Payroll, Compensation, Attendance, Benefits, Tax and Social Insurance", "distinction": "Transactions and accounts remain external evidence or consequences; their existence or absence alone never proves relationship identity, status or continuity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "neighbor": "Recruitment and Onboarding", "distinction": "Candidate selection and operational onboarding or offboarding are processes that may create or implement employment but do not own the relationship's continuing legal and evidential record.", "source_refs": [ "SRC-001", "SRC-006" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Employment Relationship Recommendation, 2006 (No. 198)", "organization": "International Labour Organization", "url": "https://www.ilo.org/resource/other/r198-employment-relationship-recommendation-2006", "version_or_date": "Recommendation No. 198, 2006", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Requires national policy to clarify employment relationships, combat disguised relationships, use facts about work and remuneration over party labels, provide indicators, access to determination and effective dispute settlement." }, { "id": "SRC-002", "title": "International Classification of Status in Employment (ICSE-18) Manual", "organization": "International Labour Organization", "url": "https://www.ilo.org/publications/international-classification-status-employment-icse-18-manual", "version_or_date": "ICSE-18 Manual, 2023", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Defines statistical status categories using authority and economic-risk dimensions, including employees and dependent contractors; it informs classification evidence but is not a universal legal determination." }, { "id": "SRC-003", "title": "Resolution concerning statistics on work relationships", "organization": "International Labour Organization", "url": "https://www.ilo.org/resource/conference-paper/resolution-concerning-statistics-work-relationships", "version_or_date": "20th ICLS resolution, 17 October 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Provides the international statistical concepts of work relationships and the ICSE-18 and ICSaW-18 classifications, supporting explicit purpose and profile qualification." }, { "id": "SRC-004", "title": "International Standard Classification of Occupations 2008", "organization": "International Labour Organization", "url": "https://isco.ilo.org/en/isco-08/", "version_or_date": "ISCO-08, endorsed March 2008; current ILO edition", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Distinguishes a job as tasks and duties performed or meant to be performed by one person from an occupation as a class of similar jobs, preventing occupation concepts from becoming employment identity." }, { "id": "SRC-005", "title": "The ESCO Classification", "organization": "European Commission", "url": "https://esco.ec.europa.eu/en/classification", "version_or_date": "ESCO v1.2.1, updated 10 December 2025", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Provides versioned multilingual occupation and skill concepts mapped to ISCO-08; useful for typed occupation and skill references, not employment-status determination." }, { "id": "SRC-006", "title": "Directive (EU) 2019/1152 on transparent and predictable working conditions", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2019/1152/oj", "version_or_date": "Directive (EU) 2019/1152, 20 June 2019", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Provides an EU profile for timely information about parties, workplace, role, start, duration, probation, remuneration, working time, training and termination procedure while deferring worker status to Member State law and practice." }, { "id": "SRC-007", "title": "Directive 2008/104/EC on temporary agency work", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2008/104/oj", "version_or_date": "Directive 2008/104/EC, 19 November 2008", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Provides an EU multi-party profile distinguishing temporary-work agency, worker and user undertaking and supporting assignment-specific equal-treatment context." }, { "id": "SRC-008", "title": "Termination of Employment Convention, 1982 (No. 158)", "organization": "International Labour Organization", "url": "https://normlex.ilo.org/dyn/nrmlx_en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:C158", "version_or_date": "Convention No. 158, adopted 22 June 1982; in force 23 November 1985", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Defines a ratification-dependent profile for valid reason, procedure, notice, challenge and remedy around employer-initiated termination; applicability must be explicitly pinned." }, { "id": "SRC-009", "title": "The Organization Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-org/", "version_or_date": "W3C Recommendation, 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Provides interoperable organization, role, post, membership and interval patterns. Employment may align as a qualified relationship, but this model excludes generic membership and keeps posts and roles external." }, { "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-06T01:06:00Z", "relevance": "Supports agents, entities, activities, attribution, derivation, revision and qualified relationships for party assertions, evidence and immutable correction lineage." }, { "id": "SRC-011", "title": "General Data Protection Regulation", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2016/679/oj", "version_or_date": "Regulation (EU) 2016/679, 27 April 2016", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T01:06:00Z", "relevance": "Provides an EU privacy profile for purpose limitation, data minimization, accuracy, retention, security, access and rectification of person-linked employment records." }, { "id": "SRC-012", "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-06T01:06:00Z", "relevance": "Defines interoperable timestamps with seconds and an explicit relationship to UTC for lifecycle and knowledge-time records." } ], "structure": { "bundles": [ { "id": "relationship-identity-parties-and-authority", "name": "Relationship identity, parties and authority", "description": "Identifies the employment relationship and the parties and authorities around it.", "rationale": "A relationship must remain resolvable independently of mutable jobs, assignments, labels and organizations' internal records.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009", "SRC-010" ], "layers": [ { "id": "relationship-master-identity", "name": "Relationship master identity", "description": "Stable identity, aliases, source systems and duplicate or successor handling.", "source_refs": [ "SRC-001", "SRC-009", "SRC-010" ], "findings": [ { "id": "authoritative-relationship-identifier-and-master-system", "name": "Authoritative relationship identifier and master system", "description": "The stable identifier, issuer, namespace, master system, status and typed aliases for one employment relationship.", "source_refs": [ "SRC-001", "SRC-009", "SRC-010" ], "questions": [ { "id": "authoritative-relationship-identifier-and-master-system-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for authoritative relationship identifier and master system?", "kind": "identity", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "authoritative-relationship-identifier-and-master-system-q02", "text": "Which party, authority, source and evidence establishes authoritative relationship identifier and master system, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "authoritative-relationship-identifier-and-master-system-q03", "text": "How may authoritative relationship identifier and master system be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "authoritative-relationship-identifier-and-master-system-data", "name": "Authoritative relationship identifier and master system data", "description": "Structured, source-qualified answer data for authoritative relationship identifier and master system.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "authoritative-relationship-identifier-and-master-system-record", "name": "Authoritative relationship identifier and master system record", "description": "Versioned evidence-bearing record for authoritative relationship identifier and master system with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus authoritative-relationship-identifier-and-master-system assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "duplicate-merge-split-transfer-and-successor-lineage", "name": "Duplicate, merge, split, transfer and successor lineage", "description": "Rules and evidence that reconcile duplicates or create successors without erasing cited relationship identities.", "source_refs": [ "SRC-001", "SRC-010" ], "questions": [ { "id": "duplicate-merge-split-transfer-and-successor-lineage-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for duplicate, merge, split, transfer and successor lineage?", "kind": "lifecycle", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "duplicate-merge-split-transfer-and-successor-lineage-q02", "text": "Which party, authority, source and evidence establishes duplicate, merge, split, transfer and successor lineage, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "duplicate-merge-split-transfer-and-successor-lineage-q03", "text": "How may duplicate, merge, split, transfer and successor lineage be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "duplicate-merge-split-transfer-and-successor-lineage-data", "name": "Duplicate, merge, split, transfer and successor lineage data", "description": "Structured, source-qualified answer data for duplicate, merge, split, transfer and successor lineage.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-010" ] } ], "artifacts": [ { "id": "duplicate-merge-split-transfer-and-successor-lineage-record", "name": "Duplicate, merge, split, transfer and successor lineage record", "description": "Versioned evidence-bearing record for duplicate, merge, split, transfer and successor lineage with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus duplicate-merge-split-transfer-and-successor-lineage assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "party-topology-and-authority", "name": "Party topology and authority", "description": "Worker, employer and other party roles, their effective intervals and authority sources.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-010" ], "findings": [ { "id": "worker-and-employing-party-bindings", "name": "Worker and employing party bindings", "description": "Typed references to worker and employing party with asserted and effective role intervals and identity provenance.", "source_refs": [ "SRC-001", "SRC-006", "SRC-010" ], "questions": [ { "id": "worker-and-employing-party-bindings-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for worker and employing party bindings?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "worker-and-employing-party-bindings-q02", "text": "Which party, authority, source and evidence establishes worker and employing party bindings, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "worker-and-employing-party-bindings-q03", "text": "How may worker and employing party bindings be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "worker-and-employing-party-bindings-data", "name": "Worker and employing party bindings data", "description": "Structured, source-qualified answer data for worker and employing party bindings.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "worker-and-employing-party-bindings-record", "name": "Worker and employing party bindings record", "description": "Versioned evidence-bearing record for worker and employing party bindings with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus worker-and-employing-party-bindings assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "agency-host-client-paymaster-platform-and-authority-roles", "name": "Agency, host, client, paymaster, platform and authority roles", "description": "Allows multi-party work without treating every operational or payment party as the legal employer.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "agency-host-client-paymaster-platform-and-authority-roles-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for agency, host, client, paymaster, platform and authority roles?", "kind": "authority", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "agency-host-client-paymaster-platform-and-authority-roles-q02", "text": "Which party, authority, source and evidence establishes agency, host, client, paymaster, platform and authority roles, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "agency-host-client-paymaster-platform-and-authority-roles-q03", "text": "How may agency, host, client, paymaster, platform and authority roles be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "agency-host-client-paymaster-platform-and-authority-roles-data", "name": "Agency, host, client, paymaster, platform and authority roles data", "description": "Structured, source-qualified answer data for agency, host, client, paymaster, platform and authority roles.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "agency-host-client-paymaster-platform-and-authority-roles-record", "name": "Agency, host, client, paymaster, platform and authority roles record", "description": "Versioned evidence-bearing record for agency, host, client, paymaster, platform and authority roles with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus agency-host-client-paymaster-platform-and-authority-roles assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "legal-classification-jurisdiction-and-recognition", "name": "Legal classification, jurisdiction and recognition", "description": "Separates evidence, statistical classifications, party assertions and legally effective determinations.", "rationale": "Employment status is jurisdiction-bound and may be disputed, retroactively determined or different for different purposes.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "layers": [ { "id": "basis-jurisdiction-and-instruments", "name": "Basis, jurisdiction and instruments", "description": "The asserted basis, applicable territory, purpose and governing instruments.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ], "findings": [ { "id": "contractual-statutory-factual-and-appointment-basis", "name": "Contractual, statutory, factual and appointment basis", "description": "References the instrument or facts said to create employment and records who asserts that basis.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "contractual-statutory-factual-and-appointment-basis-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for contractual, statutory, factual and appointment basis?", "kind": "authority", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "contractual-statutory-factual-and-appointment-basis-q02", "text": "Which party, authority, source and evidence establishes contractual, statutory, factual and appointment basis, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "contractual-statutory-factual-and-appointment-basis-q03", "text": "How may contractual, statutory, factual and appointment basis be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "contractual-statutory-factual-and-appointment-basis-data", "name": "Contractual, statutory, factual and appointment basis data", "description": "Structured, source-qualified answer data for contractual, statutory, factual and appointment basis.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "contractual-statutory-factual-and-appointment-basis-record", "name": "Contractual, statutory, factual and appointment basis record", "description": "Versioned evidence-bearing record for contractual, statutory, factual and appointment basis with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus contractual-statutory-factual-and-appointment-basis assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "jurisdiction-scope-applicable-law-and-collective-instruments", "name": "Jurisdiction, scope, applicable law and collective instruments", "description": "Pins territorial, personal and subject scope plus applicable legal, collective, policy and ratification profiles.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ], "questions": [ { "id": "jurisdiction-scope-applicable-law-and-collective-instruments-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for jurisdiction, scope, applicable law and collective instruments?", "kind": "constraint", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "jurisdiction-scope-applicable-law-and-collective-instruments-q02", "text": "Which party, authority, source and evidence establishes jurisdiction, scope, applicable law and collective instruments, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "jurisdiction-scope-applicable-law-and-collective-instruments-q03", "text": "How may jurisdiction, scope, applicable law and collective instruments be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "jurisdiction-scope-applicable-law-and-collective-instruments-data", "name": "Jurisdiction, scope, applicable law and collective instruments data", "description": "Structured, source-qualified answer data for jurisdiction, scope, applicable law and collective instruments.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "jurisdiction-scope-applicable-law-and-collective-instruments-record", "name": "Jurisdiction, scope, applicable law and collective instruments record", "description": "Versioned evidence-bearing record for jurisdiction, scope, applicable law and collective instruments with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus jurisdiction-scope-applicable-law-and-collective-instruments assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "status-classification-and-indicators", "name": "Status classification and indicators", "description": "Records purpose-qualified categories and the evidence used for them.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "employee-worker-dependent-contractor-and-self-employed-assertions", "name": "Employee, worker, dependent-contractor and self-employed assertions", "description": "Parallel party, statistical, administrative and legal status assertions with scheme, purpose, time and confidence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "employee-worker-dependent-contractor-and-self-employed-assertions-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for employee, worker, dependent-contractor and self-employed assertions?", "kind": "classification", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "employee-worker-dependent-contractor-and-self-employed-assertions-q02", "text": "Which party, authority, source and evidence establishes employee, worker, dependent-contractor and self-employed assertions, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "employee-worker-dependent-contractor-and-self-employed-assertions-q03", "text": "How may employee, worker, dependent-contractor and self-employed assertions be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "employee-worker-dependent-contractor-and-self-employed-assertions-data", "name": "Employee, worker, dependent-contractor and self-employed assertions data", "description": "Structured, source-qualified answer data for employee, worker, dependent-contractor and self-employed assertions.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "employee-worker-dependent-contractor-and-self-employed-assertions-record", "name": "Employee, worker, dependent-contractor and self-employed assertions record", "description": "Versioned evidence-bearing record for employee, worker, dependent-contractor and self-employed assertions with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus employee-worker-dependent-contractor-and-self-employed-assertions assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "control-dependence-remuneration-risk-and-integration-indicators", "name": "Control, dependence, remuneration, risk and integration indicators", "description": "Observable indicators and counter-indicators with method, source and applicability, never a label-only conclusion.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "control-dependence-remuneration-risk-and-integration-indicators-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for control, dependence, remuneration, risk and integration indicators?", "kind": "evidence", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "control-dependence-remuneration-risk-and-integration-indicators-q02", "text": "Which party, authority, source and evidence establishes control, dependence, remuneration, risk and integration indicators, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "control-dependence-remuneration-risk-and-integration-indicators-q03", "text": "How may control, dependence, remuneration, risk and integration indicators be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "control-dependence-remuneration-risk-and-integration-indicators-data", "name": "Control, dependence, remuneration, risk and integration indicators data", "description": "Structured, source-qualified answer data for control, dependence, remuneration, risk and integration indicators.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "control-dependence-remuneration-risk-and-integration-indicators-record", "name": "Control, dependence, remuneration, risk and integration indicators record", "description": "Versioned evidence-bearing record for control, dependence, remuneration, risk and integration indicators with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus control-dependence-remuneration-risk-and-integration-indicators assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "determination-dispute-and-recognition", "name": "Determination, dispute and recognition", "description": "Recognition criteria, competent determinations, competing assertions and correction.", "source_refs": [ "SRC-001", "SRC-002", "SRC-010" ], "findings": [ { "id": "competent-status-determination-scope-and-effect", "name": "Competent status determination, scope and effect", "description": "Authority, decision reference, legal basis, effective period, appeal state and exact purposes for which a determination controls.", "source_refs": [ "SRC-001", "SRC-010" ], "questions": [ { "id": "competent-status-determination-scope-and-effect-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for competent status determination, scope and effect?", "kind": "decision", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "competent-status-determination-scope-and-effect-q02", "text": "Which party, authority, source and evidence establishes competent status determination, scope and effect, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "competent-status-determination-scope-and-effect-q03", "text": "How may competent status determination, scope and effect be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "competent-status-determination-scope-and-effect-data", "name": "Competent status determination, scope and effect data", "description": "Structured, source-qualified answer data for competent status determination, scope and effect.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-010" ] } ], "artifacts": [ { "id": "competent-status-determination-scope-and-effect-record", "name": "Competent status determination, scope and effect record", "description": "Versioned evidence-bearing record for competent status determination, scope and effect with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus competent-status-determination-scope-and-effect assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "misclassification-dispute-appeal-and-retroactive-correction", "name": "Misclassification dispute, appeal and retroactive correction", "description": "Contested status, claims, decisions, remedies and bitemporal corrections while prior assertions remain visible.", "source_refs": [ "SRC-001", "SRC-010" ], "questions": [ { "id": "misclassification-dispute-appeal-and-retroactive-correction-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for misclassification dispute, appeal and retroactive correction?", "kind": "validation", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "misclassification-dispute-appeal-and-retroactive-correction-q02", "text": "Which party, authority, source and evidence establishes misclassification dispute, appeal and retroactive correction, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "misclassification-dispute-appeal-and-retroactive-correction-q03", "text": "How may misclassification dispute, appeal and retroactive correction be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "misclassification-dispute-appeal-and-retroactive-correction-data", "name": "Misclassification dispute, appeal and retroactive correction data", "description": "Structured, source-qualified answer data for misclassification dispute, appeal and retroactive correction.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-010" ] } ], "artifacts": [ { "id": "misclassification-dispute-appeal-and-retroactive-correction-record", "name": "Misclassification dispute, appeal and retroactive correction record", "description": "Versioned evidence-bearing record for misclassification dispute, appeal and retroactive correction with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus misclassification-dispute-appeal-and-retroactive-correction assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "commencement-terms-and-working-context", "name": "Commencement, terms and working context", "description": "Captures when the relationship begins and which external terms and work-context assertions apply.", "rationale": "Transparent working conditions require versioned, time-qualified bindings rather than copied contract or payroll payloads.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "layers": [ { "id": "commencement-probation-and-time", "name": "Commencement, probation and time", "description": "Agreed, recorded, effective and recognized beginning and probation facts.", "source_refs": [ "SRC-006", "SRC-012" ], "findings": [ { "id": "agreement-appointment-start-and-antecedent-service", "name": "Agreement, appointment, start and antecedent service", "description": "Creation basis, agreed and actual start, credited prior service, seniority anchor and evidence references.", "source_refs": [ "SRC-006", "SRC-010", "SRC-012" ], "questions": [ { "id": "agreement-appointment-start-and-antecedent-service-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for agreement, appointment, start and antecedent service?", "kind": "temporal", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "agreement-appointment-start-and-antecedent-service-q02", "text": "Which party, authority, source and evidence establishes agreement, appointment, start and antecedent service, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "agreement-appointment-start-and-antecedent-service-q03", "text": "How may agreement, appointment, start and antecedent service be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "agreement-appointment-start-and-antecedent-service-data", "name": "Agreement, appointment, start and antecedent service data", "description": "Structured, source-qualified answer data for agreement, appointment, start and antecedent service.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-010", "SRC-012" ] } ], "artifacts": [ { "id": "agreement-appointment-start-and-antecedent-service-record", "name": "Agreement, appointment, start and antecedent service record", "description": "Versioned evidence-bearing record for agreement, appointment, start and antecedent service with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus agreement-appointment-start-and-antecedent-service assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006", "SRC-010", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "probation-trial-confirmation-and-rescission", "name": "Probation, trial, confirmation and rescission", "description": "Probation basis, limits, extensions, outcome and relationship effect without confusing probation with employment identity.", "source_refs": [ "SRC-006" ], "questions": [ { "id": "probation-trial-confirmation-and-rescission-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for probation, trial, confirmation and rescission?", "kind": "lifecycle", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "probation-trial-confirmation-and-rescission-q02", "text": "Which party, authority, source and evidence establishes probation, trial, confirmation and rescission, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "probation-trial-confirmation-and-rescission-q03", "text": "How may probation, trial, confirmation and rescission be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "probation-trial-confirmation-and-rescission-data", "name": "Probation, trial, confirmation and rescission data", "description": "Structured, source-qualified answer data for probation, trial, confirmation and rescission.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "probation-trial-confirmation-and-rescission-record", "name": "Probation, trial, confirmation and rescission record", "description": "Versioned evidence-bearing record for probation, trial, confirmation and rescission with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus probation-trial-confirmation-and-rescission assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "term-bindings-and-precedence", "name": "Term bindings and precedence", "description": "Versioned references to individual, collective, statutory and policy terms.", "source_refs": [ "SRC-006", "SRC-008", "SRC-010" ], "findings": [ { "id": "duration-renewal-notice-and-precedence", "name": "Duration, renewal, notice and precedence", "description": "Open-ended or fixed duration, end condition, renewal, notice method and precedence among applicable term sources.", "source_refs": [ "SRC-006", "SRC-008" ], "questions": [ { "id": "duration-renewal-notice-and-precedence-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for duration, renewal, notice and precedence?", "kind": "constraint", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "duration-renewal-notice-and-precedence-q02", "text": "Which party, authority, source and evidence establishes duration, renewal, notice and precedence, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "duration-renewal-notice-and-precedence-q03", "text": "How may duration, renewal, notice and precedence be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "duration-renewal-notice-and-precedence-data", "name": "Duration, renewal, notice and precedence data", "description": "Structured, source-qualified answer data for duration, renewal, notice and precedence.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "duration-renewal-notice-and-precedence-record", "name": "Duration, renewal, notice and precedence record", "description": "Versioned evidence-bearing record for duration, renewal, notice and precedence with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus duration-renewal-notice-and-precedence assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "remuneration-benefit-training-and-expense-references", "name": "Remuneration, benefit, training and expense references", "description": "Bindings to compensation, benefit, training and reimbursable-expense masters with effective time and disclosure class.", "source_refs": [ "SRC-005", "SRC-006" ], "questions": [ { "id": "remuneration-benefit-training-and-expense-references-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for remuneration, benefit, training and expense references?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "remuneration-benefit-training-and-expense-references-q02", "text": "Which party, authority, source and evidence establishes remuneration, benefit, training and expense references, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "remuneration-benefit-training-and-expense-references-q03", "text": "How may remuneration, benefit, training and expense references be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "remuneration-benefit-training-and-expense-references-data", "name": "Remuneration, benefit, training and expense references data", "description": "Structured, source-qualified answer data for remuneration, benefit, training and expense references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "remuneration-benefit-training-and-expense-references-record", "name": "Remuneration, benefit, training and expense references record", "description": "Versioned evidence-bearing record for remuneration, benefit, training and expense references with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus remuneration-benefit-training-and-expense-references assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "working-time-place-and-pattern", "name": "Working time, place and pattern", "description": "Capacity and location context that qualifies the relationship without replacing schedules or attendance.", "source_refs": [ "SRC-006", "SRC-007" ], "findings": [ { "id": "capacity-working-time-pattern-overtime-and-predictability", "name": "Capacity, working-time pattern, overtime and predictability", "description": "Contracted capacity, standard pattern, predictability, reference hours and applicable overtime or minimum-notice rules.", "source_refs": [ "SRC-006" ], "questions": [ { "id": "capacity-working-time-pattern-overtime-and-predictability-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for capacity, working-time pattern, overtime and predictability?", "kind": "measurement", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "capacity-working-time-pattern-overtime-and-predictability-q02", "text": "Which party, authority, source and evidence establishes capacity, working-time pattern, overtime and predictability, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "capacity-working-time-pattern-overtime-and-predictability-q03", "text": "How may capacity, working-time pattern, overtime and predictability be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "capacity-working-time-pattern-overtime-and-predictability-data", "name": "Capacity, working-time pattern, overtime and predictability data", "description": "Structured, source-qualified answer data for capacity, working-time pattern, overtime and predictability.", "value_kind": "quantity", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "capacity-working-time-pattern-overtime-and-predictability-record", "name": "Capacity, working-time pattern, overtime and predictability record", "description": "Versioned evidence-bearing record for capacity, working-time pattern, overtime and predictability with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus capacity-working-time-pattern-overtime-and-predictability assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "workplace-remote-mobile-and-cross-border-context", "name": "Workplace, remote, mobile and cross-border context", "description": "Primary and permitted places, remote or mobile mode, host territory, travel expectation and jurisdiction implications by reference.", "source_refs": [ "SRC-006", "SRC-007" ], "questions": [ { "id": "workplace-remote-mobile-and-cross-border-context-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for workplace, remote, mobile and cross-border context?", "kind": "spatial", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "workplace-remote-mobile-and-cross-border-context-q02", "text": "Which party, authority, source and evidence establishes workplace, remote, mobile and cross-border context, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "workplace-remote-mobile-and-cross-border-context-q03", "text": "How may workplace, remote, mobile and cross-border context be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "workplace-remote-mobile-and-cross-border-context-data", "name": "Workplace, remote, mobile and cross-border context data", "description": "Structured, source-qualified answer data for workplace, remote, mobile and cross-border context.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "workplace-remote-mobile-and-cross-border-context-record", "name": "Workplace, remote, mobile and cross-border context record", "description": "Versioned evidence-bearing record for workplace, remote, mobile and cross-border context with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus workplace-remote-mobile-and-cross-border-context assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "role-assignment-and-occupation-binding", "name": "Role, assignment and occupation binding", "description": "Connects employment to positions, assignments, occupations and skills without importing their lifecycles.", "rationale": "A relationship can continue through several jobs or assignments, and an occupation is a classifier rather than the relationship itself.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009" ], "layers": [ { "id": "position-role-and-assignment", "name": "Position, role and assignment", "description": "Time-qualified realization links to externally mastered organizational work records.", "source_refs": [ "SRC-007", "SRC-009" ], "findings": [ { "id": "position-unit-role-and-reporting-references", "name": "Position, unit, role and reporting references", "description": "References formal positions, organizational units, role concepts and reporting structures without copying them into employment.", "source_refs": [ "SRC-009" ], "questions": [ { "id": "position-unit-role-and-reporting-references-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for position, unit, role and reporting references?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "position-unit-role-and-reporting-references-q02", "text": "Which party, authority, source and evidence establishes position, unit, role and reporting references, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "position-unit-role-and-reporting-references-q03", "text": "How may position, unit, role and reporting references be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "position-unit-role-and-reporting-references-data", "name": "Position, unit, role and reporting references data", "description": "Structured, source-qualified answer data for position, unit, role and reporting references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "position-unit-role-and-reporting-references-record", "name": "Position, unit, role and reporting references record", "description": "Versioned evidence-bearing record for position, unit, role and reporting references with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus position-unit-role-and-reporting-references assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "assignment-realization-validity-and-concurrency", "name": "Assignment realization, validity and concurrency", "description": "Links one employment relationship to concurrent or sequential WM-ORG-016 assignments and records link validity only.", "source_refs": [ "SRC-007", "SRC-009" ], "questions": [ { "id": "assignment-realization-validity-and-concurrency-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for assignment realization, validity and concurrency?", "kind": "composition", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "assignment-realization-validity-and-concurrency-q02", "text": "Which party, authority, source and evidence establishes assignment realization, validity and concurrency, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "assignment-realization-validity-and-concurrency-q03", "text": "How may assignment realization, validity and concurrency be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "assignment-realization-validity-and-concurrency-data", "name": "Assignment realization, validity and concurrency data", "description": "Structured, source-qualified answer data for assignment realization, validity and concurrency.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "assignment-realization-validity-and-concurrency-record", "name": "Assignment realization, validity and concurrency record", "description": "Versioned evidence-bearing record for assignment realization, validity and concurrency with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus assignment-realization-validity-and-concurrency assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "job-occupation-and-skill-context", "name": "Job, occupation and skill context", "description": "Separates the concrete job from reusable occupation and skill concepts.", "source_refs": [ "SRC-004", "SRC-005" ], "findings": [ { "id": "job-task-duty-and-occupation-classification-reference", "name": "Job, task, duty and occupation-classification reference", "description": "Binds current or historic job and assignment references to versioned ISCO, ESCO or local occupation concepts.", "source_refs": [ "SRC-004", "SRC-005" ], "questions": [ { "id": "job-task-duty-and-occupation-classification-reference-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for job, task, duty and occupation-classification reference?", "kind": "classification", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "job-task-duty-and-occupation-classification-reference-q02", "text": "Which party, authority, source and evidence establishes job, task, duty and occupation-classification reference, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "job-task-duty-and-occupation-classification-reference-q03", "text": "How may job, task, duty and occupation-classification reference be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "job-task-duty-and-occupation-classification-reference-data", "name": "Job, task, duty and occupation-classification reference data", "description": "Structured, source-qualified answer data for job, task, duty and occupation-classification reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "job-task-duty-and-occupation-classification-reference-record", "name": "Job, task, duty and occupation-classification reference record", "description": "Versioned evidence-bearing record for job, task, duty and occupation-classification reference with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus job-task-duty-and-occupation-classification-reference assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "required-used-and-developed-skill-references", "name": "Required, used and developed skill references", "description": "Purpose-qualified links to skill concepts and evidence while qualifications and assessments remain external.", "source_refs": [ "SRC-004", "SRC-005" ], "questions": [ { "id": "required-used-and-developed-skill-references-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for required, used and developed skill references?", "kind": "relationship", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "required-used-and-developed-skill-references-q02", "text": "Which party, authority, source and evidence establishes required, used and developed skill references, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "required-used-and-developed-skill-references-q03", "text": "How may required, used and developed skill references be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "required-used-and-developed-skill-references-data", "name": "Required, used and developed skill references data", "description": "Structured, source-qualified answer data for required, used and developed skill references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "required-used-and-developed-skill-references-record", "name": "Required, used and developed skill references record", "description": "Versioned evidence-bearing record for required, used and developed skill references with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus required-used-and-developed-skill-references assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-continuity-and-separation", "name": "Lifecycle, continuity and separation", "description": "Represents relationship state and change independently of assignment, payroll or access-system activity.", "rationale": "Employment may continue through leave, transfer or employer succession and may end through several governed bases, so changes need explicit effect and authority.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-010" ], "layers": [ { "id": "status-continuity-and-succession", "name": "Status, continuity and succession", "description": "Current and historic relationship state, continuity and successor employer bindings.", "source_refs": [ "SRC-001", "SRC-006", "SRC-010" ], "findings": [ { "id": "active-inactive-disputed-and-unknown-relationship-state", "name": "Active, inactive, disputed and unknown relationship state", "description": "Time-qualified state assertion, source, confidence and validation that never derives state from one operational system alone.", "source_refs": [ "SRC-001", "SRC-010" ], "questions": [ { "id": "active-inactive-disputed-and-unknown-relationship-state-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for active, inactive, disputed and unknown relationship state?", "kind": "state", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "active-inactive-disputed-and-unknown-relationship-state-q02", "text": "Which party, authority, source and evidence establishes active, inactive, disputed and unknown relationship state, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "active-inactive-disputed-and-unknown-relationship-state-q03", "text": "How may active, inactive, disputed and unknown relationship state be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "active-inactive-disputed-and-unknown-relationship-state-data", "name": "Active, inactive, disputed and unknown relationship state data", "description": "Structured, source-qualified answer data for active, inactive, disputed and unknown relationship state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-010" ] } ], "artifacts": [ { "id": "active-inactive-disputed-and-unknown-relationship-state-record", "name": "Active, inactive, disputed and unknown relationship state record", "description": "Versioned evidence-bearing record for active, inactive, disputed and unknown relationship state with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus active-inactive-disputed-and-unknown-relationship-state assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "employer-succession-transfer-and-service-continuity", "name": "Employer succession, transfer and service continuity", "description": "Predecessor and successor parties, authority, continuity decision, credited service and unchanged or changed term bindings.", "source_refs": [ "SRC-006", "SRC-010" ], "questions": [ { "id": "employer-succession-transfer-and-service-continuity-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for employer succession, transfer and service continuity?", "kind": "lifecycle", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "employer-succession-transfer-and-service-continuity-q02", "text": "Which party, authority, source and evidence establishes employer succession, transfer and service continuity, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "employer-succession-transfer-and-service-continuity-q03", "text": "How may employer succession, transfer and service continuity be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "employer-succession-transfer-and-service-continuity-data", "name": "Employer succession, transfer and service continuity data", "description": "Structured, source-qualified answer data for employer succession, transfer and service continuity.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "employer-succession-transfer-and-service-continuity-record", "name": "Employer succession, transfer and service continuity record", "description": "Versioned evidence-bearing record for employer succession, transfer and service continuity with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus employer-succession-transfer-and-service-continuity assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "interruption-change-and-resumption", "name": "Interruption, change and resumption", "description": "Relationship-level effects of leave, suspension, secondment and material amendment.", "source_refs": [ "SRC-006", "SRC-007", "SRC-010" ], "findings": [ { "id": "leave-suspension-secondment-and-nonperformance-effect", "name": "Leave, suspension, secondment and nonperformance effect", "description": "References the external event and records whether employment, service, pay, benefits, assignment and notice clocks continue or pause.", "source_refs": [ "SRC-006", "SRC-007" ], "questions": [ { "id": "leave-suspension-secondment-and-nonperformance-effect-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for leave, suspension, secondment and nonperformance effect?", "kind": "event", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "leave-suspension-secondment-and-nonperformance-effect-q02", "text": "Which party, authority, source and evidence establishes leave, suspension, secondment and nonperformance effect, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "leave-suspension-secondment-and-nonperformance-effect-q03", "text": "How may leave, suspension, secondment and nonperformance effect be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "leave-suspension-secondment-and-nonperformance-effect-data", "name": "Leave, suspension, secondment and nonperformance effect data", "description": "Structured, source-qualified answer data for leave, suspension, secondment and nonperformance effect.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "leave-suspension-secondment-and-nonperformance-effect-record", "name": "Leave, suspension, secondment and nonperformance effect record", "description": "Versioned evidence-bearing record for leave, suspension, secondment and nonperformance effect with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus leave-suspension-secondment-and-nonperformance-effect assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "term-amendment-consent-authority-and-effective-change", "name": "Term amendment, consent, authority and effective change", "description": "The proposed and effective change, source instrument, affected bindings, party acknowledgements and dispute state.", "source_refs": [ "SRC-006", "SRC-010" ], "questions": [ { "id": "term-amendment-consent-authority-and-effective-change-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for term amendment, consent, authority and effective change?", "kind": "process", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "term-amendment-consent-authority-and-effective-change-q02", "text": "Which party, authority, source and evidence establishes term amendment, consent, authority and effective change, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "term-amendment-consent-authority-and-effective-change-q03", "text": "How may term amendment, consent, authority and effective change be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "term-amendment-consent-authority-and-effective-change-data", "name": "Term amendment, consent, authority and effective change data", "description": "Structured, source-qualified answer data for term amendment, consent, authority and effective change.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "term-amendment-consent-authority-and-effective-change-record", "name": "Term amendment, consent, authority and effective change record", "description": "Versioned evidence-bearing record for term amendment, consent, authority and effective change with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus term-amendment-consent-authority-and-effective-change assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "separation-and-post-employment", "name": "Separation and post-employment", "description": "End basis, procedure, contest and surviving bindings.", "source_refs": [ "SRC-006", "SRC-008", "SRC-010" ], "findings": [ { "id": "resignation-expiry-dismissal-mutual-end-and-other-basis", "name": "Resignation, expiry, dismissal, mutual end and other basis", "description": "Qualified separation basis, initiating party, decision or notice references, stated reason, effective time and uncertainty.", "source_refs": [ "SRC-006", "SRC-008" ], "questions": [ { "id": "resignation-expiry-dismissal-mutual-end-and-other-basis-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for resignation, expiry, dismissal, mutual end and other basis?", "kind": "lifecycle", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "resignation-expiry-dismissal-mutual-end-and-other-basis-q02", "text": "Which party, authority, source and evidence establishes resignation, expiry, dismissal, mutual end and other basis, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "resignation-expiry-dismissal-mutual-end-and-other-basis-q03", "text": "How may resignation, expiry, dismissal, mutual end and other basis be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "resignation-expiry-dismissal-mutual-end-and-other-basis-data", "name": "Resignation, expiry, dismissal, mutual end and other basis data", "description": "Structured, source-qualified answer data for resignation, expiry, dismissal, mutual end and other basis.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "resignation-expiry-dismissal-mutual-end-and-other-basis-record", "name": "Resignation, expiry, dismissal, mutual end and other basis record", "description": "Versioned evidence-bearing record for resignation, expiry, dismissal, mutual end and other basis with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus resignation-expiry-dismissal-mutual-end-and-other-basis assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "notice-challenge-remedy-and-surviving-obligation-references", "name": "Notice, challenge, remedy and surviving-obligation references", "description": "Notice compliance, appeal, reinstatement or compensation outcome and surviving confidentiality or other obligation bindings.", "source_refs": [ "SRC-008", "SRC-010" ], "questions": [ { "id": "notice-challenge-remedy-and-surviving-obligation-references-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for notice, challenge, remedy and surviving-obligation references?", "kind": "decision", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "notice-challenge-remedy-and-surviving-obligation-references-q02", "text": "Which party, authority, source and evidence establishes notice, challenge, remedy and surviving-obligation references, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "notice-challenge-remedy-and-surviving-obligation-references-q03", "text": "How may notice, challenge, remedy and surviving-obligation references be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "notice-challenge-remedy-and-surviving-obligation-references-data", "name": "Notice, challenge, remedy and surviving-obligation references data", "description": "Structured, source-qualified answer data for notice, challenge, remedy and surviving-obligation references.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-010" ] } ], "artifacts": [ { "id": "notice-challenge-remedy-and-surviving-obligation-references-record", "name": "Notice, challenge, remedy and surviving-obligation references record", "description": "Versioned evidence-bearing record for notice, challenge, remedy and surviving-obligation references with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus notice-challenge-remedy-and-surviving-obligation-references assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-008", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "assertions-evidence-privacy-and-trust", "name": "Assertions, evidence, privacy and trust", "description": "Keeps both parties' assertions, authoritative determinations and minimum-disclosure access auditable.", "rationale": "Employment data is sensitive and power-asymmetric; provenance and access rights cannot be collapsed into employer ownership of the truth.", "source_refs": [ "SRC-001", "SRC-010", "SRC-011" ], "layers": [ { "id": "party-assertions-evidence-and-quality", "name": "Party assertions, evidence and quality", "description": "Attribution, acknowledgement, discrepancies and evidence quality for relationship facts.", "source_refs": [ "SRC-001", "SRC-010" ], "findings": [ { "id": "worker-employer-third-party-and-authority-assertions", "name": "Worker, employer, third-party and authority assertions", "description": "Parallel attributable statements with purpose, valid time, knowledge time, confidence, acknowledgement and contest status.", "source_refs": [ "SRC-001", "SRC-010" ], "questions": [ { "id": "worker-employer-third-party-and-authority-assertions-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for worker, employer, third-party and authority assertions?", "kind": "provenance", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "worker-employer-third-party-and-authority-assertions-q02", "text": "Which party, authority, source and evidence establishes worker, employer, third-party and authority assertions, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "worker-employer-third-party-and-authority-assertions-q03", "text": "How may worker, employer, third-party and authority assertions be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "worker-employer-third-party-and-authority-assertions-data", "name": "Worker, employer, third-party and authority assertions data", "description": "Structured, source-qualified answer data for worker, employer, third-party and authority assertions.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-010" ] } ], "artifacts": [ { "id": "worker-employer-third-party-and-authority-assertions-record", "name": "Worker, employer, third-party and authority assertions record", "description": "Versioned evidence-bearing record for worker, employer, third-party and authority assertions with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus worker-employer-third-party-and-authority-assertions assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "evidence-attestation-freshness-quality-and-reconciliation", "name": "Evidence, attestation, freshness, quality and reconciliation", "description": "Evidence references, issuer, collection method, freshness, reliability, conflicts and explicit reconciliation outcome.", "source_refs": [ "SRC-001", "SRC-010" ], "questions": [ { "id": "evidence-attestation-freshness-quality-and-reconciliation-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for evidence, attestation, freshness, quality and reconciliation?", "kind": "quality", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "evidence-attestation-freshness-quality-and-reconciliation-q02", "text": "Which party, authority, source and evidence establishes evidence, attestation, freshness, quality and reconciliation, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "evidence-attestation-freshness-quality-and-reconciliation-q03", "text": "How may evidence, attestation, freshness, quality and reconciliation be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "evidence-attestation-freshness-quality-and-reconciliation-data", "name": "Evidence, attestation, freshness, quality and reconciliation data", "description": "Structured, source-qualified answer data for evidence, attestation, freshness, quality and reconciliation.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-010" ] } ], "artifacts": [ { "id": "evidence-attestation-freshness-quality-and-reconciliation-record", "name": "Evidence, attestation, freshness, quality and reconciliation record", "description": "Versioned evidence-bearing record for evidence, attestation, freshness, quality and reconciliation with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus evidence-attestation-freshness-quality-and-reconciliation assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "privacy-access-retention-and-verification", "name": "Privacy, access, retention and verification", "description": "Purpose-bound access, correction, retention and minimum employment verification.", "source_refs": [ "SRC-006", "SRC-011" ], "findings": [ { "id": "purpose-access-correction-portability-and-restriction", "name": "Purpose, access, correction, portability and restriction", "description": "Field and artifact access by role and purpose, worker access, correction route, portability profile and lawful restrictions.", "source_refs": [ "SRC-011" ], "questions": [ { "id": "purpose-access-correction-portability-and-restriction-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for purpose, access, correction, portability and restriction?", "kind": "access", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "purpose-access-correction-portability-and-restriction-q02", "text": "Which party, authority, source and evidence establishes purpose, access, correction, portability and restriction, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "purpose-access-correction-portability-and-restriction-q03", "text": "How may purpose, access, correction, portability and restriction be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "purpose-access-correction-portability-and-restriction-data", "name": "Purpose, access, correction, portability and restriction data", "description": "Structured, source-qualified answer data for purpose, access, correction, portability and restriction.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-011" ] } ], "artifacts": [ { "id": "purpose-access-correction-portability-and-restriction-record", "name": "Purpose, access, correction, portability and restriction record", "description": "Versioned evidence-bearing record for purpose, access, correction, portability and restriction with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus purpose-access-correction-portability-and-restriction assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "retention-deletion-legal-hold-and-minimal-verification", "name": "Retention, deletion, legal hold and minimal verification", "description": "Per-field retention and tombstone rules plus consent or authority bound verification of only necessary relationship facts.", "source_refs": [ "SRC-001", "SRC-011" ], "questions": [ { "id": "retention-deletion-legal-hold-and-minimal-verification-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for retention, deletion, legal hold and minimal verification?", "kind": "retention", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "retention-deletion-legal-hold-and-minimal-verification-q02", "text": "Which party, authority, source and evidence establishes retention, deletion, legal hold and minimal verification, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "retention-deletion-legal-hold-and-minimal-verification-q03", "text": "How may retention, deletion, legal hold and minimal verification be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "retention-deletion-legal-hold-and-minimal-verification-data", "name": "Retention, deletion, legal hold and minimal verification data", "description": "Structured, source-qualified answer data for retention, deletion, legal hold and minimal verification.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-011" ] } ], "artifacts": [ { "id": "retention-deletion-legal-hold-and-minimal-verification-record", "name": "Retention, deletion, legal hold and minimal verification record", "description": "Versioned evidence-bearing record for retention, deletion, legal hold and minimal verification with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus retention-deletion-legal-hold-and-minimal-verification assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interoperability-governance-and-agent-operations", "name": "Interoperability, governance and agent operations", "description": "Controls profiles, projections, autonomous checks and safe relationship change.", "rationale": "Machine exchange must preserve authority, time, disagreement, privacy and information-loss semantics across HR, statistical and linked-data projections.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-009", "SRC-010", "SRC-012" ], "layers": [ { "id": "profiles-projections-and-agent-control", "name": "Profiles, projections and agent control", "description": "Versioned mappings and permissioned agent actions.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-009", "SRC-010", "SRC-012" ], "findings": [ { "id": "jurisdiction-statistical-hr-and-linked-data-profiles", "name": "Jurisdiction, statistical, HR and linked-data profiles", "description": "Pinned source and target versions, mapping scope, transformed or omitted values, validation and non-round-trip declarations.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-009" ], "questions": [ { "id": "jurisdiction-statistical-hr-and-linked-data-profiles-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for jurisdiction, statistical, hr and linked-data profiles?", "kind": "interoperability", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "jurisdiction-statistical-hr-and-linked-data-profiles-q02", "text": "Which party, authority, source and evidence establishes jurisdiction, statistical, hr and linked-data profiles, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "jurisdiction-statistical-hr-and-linked-data-profiles-q03", "text": "How may jurisdiction, statistical, hr and linked-data profiles be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "jurisdiction-statistical-hr-and-linked-data-profiles-data", "name": "Jurisdiction, statistical, HR and linked-data profiles data", "description": "Structured, source-qualified answer data for jurisdiction, statistical, hr and linked-data profiles.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-009" ] } ], "artifacts": [ { "id": "jurisdiction-statistical-hr-and-linked-data-profiles-record", "name": "Jurisdiction, statistical, HR and linked-data profiles record", "description": "Versioned evidence-bearing record for jurisdiction, statistical, hr and linked-data profiles with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus jurisdiction-statistical-hr-and-linked-data-profiles assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "agent-operation-authority-validation-and-audit", "name": "Agent operation authority, validation and audit", "description": "Allowed read, append, reconcile, propose, confirm and forbidden actions with preconditions, effects, rollback and audit evidence.", "source_refs": [ "SRC-001", "SRC-010", "SRC-011" ], "questions": [ { "id": "agent-operation-authority-validation-and-audit-q01", "text": "What exact values, references, qualifiers and explicit unknowns must be recorded for agent operation authority, validation and audit?", "kind": "security", "answer_data": [ "value or reference", "scheme and scope", "valid time", "explicit unknowns" ] }, { "id": "agent-operation-authority-validation-and-audit-q02", "text": "Which party, authority, source and evidence establishes agent operation authority, validation and audit, at what asserted, effective and knowledge time, and with what confidence?", "kind": "evidence", "answer_data": [ "asserting party", "authority and basis", "source and evidence", "times", "confidence" ] }, { "id": "agent-operation-authority-validation-and-audit-q03", "text": "How may agent operation authority, validation and audit be validated, contested, corrected, superseded, retained or disclosed without erasing prior assertions or importing a neighboring model's lifecycle?", "kind": "validation", "answer_data": [ "validation rule", "challenge or correction route", "successor or tombstone", "access and retention effect" ] } ], "data_elements": [ { "id": "agent-operation-authority-validation-and-audit-data", "name": "Agent operation authority, validation and audit data", "description": "Structured, source-qualified answer data for agent operation authority, validation and audit.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "agent-operation-authority-validation-and-audit-record", "name": "Agent operation authority, validation and audit record", "description": "Versioned evidence-bearing record for agent operation authority, validation and audit with authority, valid time, knowledge time, provenance and access marking.", "media_or_form": [ "logical record", "signed or attributable evidence reference" ], "serial": true, "identity_strategy": "Employment relationship identifier plus agent-operation-authority-validation-and-audit assertion or event identifier; mutable names, dates and file hashes never identify the relationship.", "source_refs": [ "SRC-001", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-employment", "name": "Register employment", "description": "Create or attest one employment relationship with stable identity, party bindings, asserted basis and explicit unknowns.", "inputs": [ "worker and employer references", "basis and jurisdiction", "source evidence" ], "outputs": [ "employment relationship revision" ], "preconditions": [ "actor has register or attest authority", "duplicate check completed" ], "effects": [ "new relationship identity and provenance are recorded" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-010" ] }, { "id": "assert-or-determine-status", "name": "Assert or determine status", "description": "Record a purpose-qualified party assertion, statistical classification or competent legal determination without collapsing them.", "inputs": [ "relationship", "classification scheme", "indicator evidence", "authority" ], "outputs": [ "status assertion or determination" ], "preconditions": [ "scheme, purpose and jurisdiction are pinned" ], "effects": [ "parallel status views remain attributable and queryable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "bind-term-version", "name": "Bind term version", "description": "Attach a versioned external term source with precedence, validity and party acknowledgement.", "inputs": [ "relationship", "term source", "scope and precedence" ], "outputs": [ "term binding revision" ], "preconditions": [ "term source is resolvable", "authority and effective time are known" ], "effects": [ "prior binding remains preserved and the active view is recomputed" ], "source_refs": [ "SRC-006", "SRC-010" ] }, { "id": "link-assignment-realization", "name": "Link assignment realization", "description": "Link a WM-ORG-016 assignment that realizes the relationship without importing assignment execution.", "inputs": [ "relationship", "assignment reference", "valid interval" ], "outputs": [ "typed realization link" ], "preconditions": [ "identities and non-overlap policy validate" ], "effects": [ "assignment becomes discoverable from employment while retaining external mastership" ], "source_refs": [ "SRC-007", "SRC-009" ] }, { "id": "record-commencement", "name": "Record commencement", "description": "Append agreed, actual and effective start facts plus probation and credited-service references.", "inputs": [ "relationship", "commencement evidence" ], "outputs": [ "commencement event" ], "preconditions": [ "relationship exists", "times and sources are qualified" ], "effects": [ "relationship lifecycle begins without overwriting antecedent evidence" ], "source_refs": [ "SRC-006", "SRC-012" ] }, { "id": "suspend-or-resume", "name": "Suspend or resume", "description": "Record relationship-level effect of leave, suspension, secondment or resumption.", "inputs": [ "relationship", "external event", "effect map" ], "outputs": [ "interruption or resumption event" ], "preconditions": [ "authority and current state permit transition" ], "effects": [ "continuity, affected clocks and assignments are explicitly qualified" ], "source_refs": [ "SRC-006", "SRC-007", "SRC-010" ] }, { "id": "record-employer-succession", "name": "Record employer succession", "description": "Create a predecessor or successor employer binding with a continuity decision and changed-term map.", "inputs": [ "relationship", "predecessor and successor", "authority evidence" ], "outputs": [ "succession event and bindings" ], "preconditions": [ "party identities are distinct", "continuity basis is cited" ], "effects": [ "relationship history remains continuous or explicitly closes and succeeds" ], "source_refs": [ "SRC-006", "SRC-010" ] }, { "id": "amend-relationship", "name": "Amend relationship", "description": "Append an authorized relationship revision and preserve party acknowledgements and disagreement.", "inputs": [ "relationship", "proposed change", "authority" ], "outputs": [ "new relationship revision" ], "preconditions": [ "change scope and effective time are valid" ], "effects": [ "prior revision remains citable and contested fields stay visible" ], "source_refs": [ "SRC-006", "SRC-010" ] }, { "id": "record-separation", "name": "Record separation", "description": "Record end basis, notice, reason, effective time, challenge state and surviving references.", "inputs": [ "relationship", "separation basis", "notice or decision" ], "outputs": [ "separation event" ], "preconditions": [ "actor authority and applicable profile validate" ], "effects": [ "relationship enters ended or disputed-end state without cascading deletion" ], "source_refs": [ "SRC-006", "SRC-008", "SRC-010" ] }, { "id": "reconcile-assertions", "name": "Reconcile assertions", "description": "Compare party and authority assertions and append agreement, disagreement or unresolved reconciliation.", "inputs": [ "assertion set", "evidence", "reconciliation policy" ], "outputs": [ "reconciliation record" ], "preconditions": [ "sources and authority scopes are known" ], "effects": [ "no source is silently overwritten and conflict remains queryable" ], "source_refs": [ "SRC-001", "SRC-010" ] }, { "id": "issue-minimal-verification", "name": "Issue minimal verification", "description": "Create a purpose-bound projection of necessary employment facts under consent or legal authority.", "inputs": [ "relationship", "requester and purpose", "authority", "field policy" ], "outputs": [ "digest-pinned verification projection" ], "preconditions": [ "identity, authority and minimum-necessary fields validate" ], "effects": [ "disclosure is attributable, scoped, expiring and auditable" ], "source_refs": [ "SRC-001", "SRC-011" ] }, { "id": "project-employment-profile", "name": "Project employment profile", "description": "Transform a validated revision into a pinned statistical, HR or linked-data profile with declared loss.", "inputs": [ "relationship revision", "target profile" ], "outputs": [ "validated exchange projection" ], "preconditions": [ "source and target versions are pinned" ], "effects": [ "mapping lineage, omissions and round-trip limits are recorded" ], "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-009", "SRC-010" ] } ], "composition": [ { "target": "WM-ORG-016 Work Assignment", "relation": "COMPOSE", "purpose": "Represent assignments as typed external realizations of employment without importing their execution or lifecycle.", "required": false, "source_refs": [ "SRC-004", "SRC-007", "SRC-009" ] }, { "target": "Person, Organization, Organizational Unit, Position, Occupation, Skill, Contract, Policy, Payroll, Benefit, Tax, Social Insurance, Qualification, Evidence and Access models", "relation": "REFERENCE", "purpose": "Connect governed employment context while retaining source ownership and independent lifecycle.", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-010", "SRC-011" ] }, { "target": "ILO Recommendation No. 198", "relation": "ALIGN", "purpose": "Qualify employment-recognition indicators, disguised relationships, party labels, determination and dispute principles.", "required": true, "source_refs": [ "SRC-001" ] }, { "target": "ICSE-18 and ISCO-08", "relation": "ALIGN", "purpose": "Project statistical status and occupation classifications without granting them universal legal effect.", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "target": "ESCO", "relation": "ALIGN", "purpose": "Reference versioned multilingual occupation and skill concepts.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "W3C ORG and PROV-O", "relation": "ALIGN", "purpose": "Project qualified organization relationships, roles, intervals, assertions, derivation and revision while excluding generic membership from the Employment boundary.", "required": false, "source_refs": [ "SRC-009", "SRC-010" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, employment-record steward, worker-rights authority and namespace", "Person, organization, position, assignment, occupation, contract, policy, payroll, evidence, access and lifecycle-event registries", "Master-system mappings for worker, employer, relationship, assignment, status determination and authoritative instrument identifiers", "Jurisdiction, classification, privacy, correction, retention, federation and autonomous-agent policies" ], "namespace_guidance": "Mint employment relationship and assertion identifiers in the adopting Dimension namespace only when no authoritative master identifier exists; preserve parties, assignments, occupations, contracts, payroll, benefits, instruments, evidence and decisions as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local employment, relationship-assertion, status-determination, access and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative employment relationship identifier, issuer and master system, never by worker-employer pair, contract number, position, payroll account, start date or hash alone.", "Keep employment, membership, assignment, position, occupation, contract, payroll, attendance, benefit, tax, social-insurance and evidence lifecycles distinct." ], "patch_rules": [ "Additive extensions declare target bundle, layer or finding, jurisdiction and worker category, source, authority, privacy, rights and interoperability impact.", "Identity, party-role, status-effect or lifecycle-semantics changes require a successor version, bitemporal migration map, rollback path and continued resolution of prior records." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when relationship identity, party roles, classification scope, valid time, authority, disagreement, access and lifecycle meaning remain intact.", "Statistical, HR, legal and linked-data projections pin source and target versions and disclose transformed, omitted, aggregated or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative employment master-system identifier qualified by issuer and relationship namespace.", "Governed globally resolvable employment relationship IRI with explicit worker and employing-party references.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record event timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep asserted, agreed, effective, observed, decision, knowledge, notice and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {employment-id}--{artifact-kind}--{assertion-or-event-id}; never use a person's name, employer name, date, job title, contract number, filename or hash alone as relationship identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and profile versions, authority, valid and knowledge times, provenance, assurance, licence and access marking for every retained serial artifact." }, "policies": [ "The adopting Dimension declares who may attest, register, classify, determine, amend, suspend, transfer, separate, verify, disclose, correct, retain and tombstone employment records.", "Employment status is jurisdiction-bound: statistical categories, contract labels, payroll entries and operational indicators are evidence, not universally dispositive legal conclusions.", "The worker-employer relationship is power-asymmetric; bilateral provenance never grants either party unilateral authority to erase the other's lawful record, block access or suppress a dispute.", "Persons, organizations, positions, assignments, occupations, contracts, payroll, attendance, benefits, tax, social insurance, qualifications, recruitment and work products remain in their owning systems and are referenced.", "Automated agents may read, validate, reconcile and append low-risk observations within policy; legal-status determinations, adverse changes, wider disclosure, separation and destructive retirement require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, jurisdiction profile, requested valid and knowledge time, evidence freshness and access scope; return the minimum permitted projection with disputed and unknown fields intact." ], "create": [ "Create stable relationship identity, worker and employing-party references, asserted basis, jurisdiction, source provenance and explicit unknowns before attaching terms or assignments." ], "update": [ "Append an assertion, event or successor revision with actor, authority, reason, RFC 3339 time, evidence and before-and-after validation; never overwrite a cited assertion, determination or event." ], "delete": [ "Apply worker-rights, legal-hold, dispute, payroll, tax, social-insurance and retention policy; prefer end state or tombstone, preserve identity and history, and never cascade into referenced parties, assignments, contracts, payments or evidence." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Worker or worker-authorized steward", "responsibilities": [ "Attest worker-side facts, exercise access and correction rights, acknowledge changes and preserve contested assertions." ] }, { "name": "Employer or employing authority", "responsibilities": [ "Attest employer-side basis, terms, status events and statutory records within mandate." ] }, { "name": "HR or relationship registrar", "responsibilities": [ "Maintain identifiers, party bindings, effective terms, assignment links and lifecycle records without making unauthorized legal conclusions." ] }, { "name": "Competent status or labour authority", "responsibilities": [ "Determine status, scope, effective period, remedy and appeal effect within jurisdiction." ] }, { "name": "Worker representative or collective-bargaining steward", "responsibilities": [ "Maintain representative authority and collective-instrument bindings and support dispute evidence." ] }, { "name": "Privacy and access steward", "responsibilities": [ "Apply purpose limitation, minimum disclosure, access, correction, portability, retention and security rules." ] }, { "name": "Independent auditor", "responsibilities": [ "Review authority, changes, disclosures, corrections and provenance without rewriting party evidence." ] } ], "access": { "default_rule": "Deny mutation and disclosure of person-linked terms, compensation, health, dispute, separation or performance-related data unless active Dimension, role, purpose, jurisdiction and field policy grant it; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory, judicial, labour-inspection or emergency access must cite authority, be purpose-bound, attributable and reviewable, and must not erase original assertions, disputes, decisions or audit evidence." ], "audit_requirements": [ "Log actor, agent, role, purpose, relationship and party identities, action, policy and jurisdiction profile, RFC 3339 timestamp with offset, affected scope, requested and effective authority, evidence and outcome." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, employment mastership, worker-rights, jurisdiction, privacy, correction, retention, dispute and federation policies.", "Read this model AGENTS.md, pinned spec.yaml and required person, organization, assignment, position, occupation, contract, policy, payroll, evidence, access and decision model instructions before mutation or disclosure." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of one governed Employment relationship across ILO employment-relationship, work-status and occupation standards, selected EU working-condition, agency-work and privacy profiles, W3C organizational and provenance patterns, and RFC 3339 time, without a claim of universal legal-status, jurisdiction, labour-category, HR-schema or certified crosswalk completeness.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable relationship identity, issuer, aliases, duplicates and successor lineage are explicit." }, { "dimension": "classification and definition", "status": "covered", "notes": "Employment is separated from membership, assignment and self-employment while jurisdiction and purpose qualify status." }, { "dimension": "direct relational properties", "status": "covered", "notes": "Party topology, basis, terms, capacity and relationship-owned state are represented; physical properties are not applicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Indicators, counter-indicators, methods, determination authority, confidence and confusing neighboring classes are covered." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, classify, bind, link, amend, suspend, transfer, separate, reconcile, verify and project operations are governed." }, { "dimension": "composition", "status": "covered", "notes": "Assignments realize employment through a typed candidate relation while all neighboring master lifecycles remain external." }, { "dimension": "lifecycle", "status": "covered", "notes": "Commencement, probation, continuity, interruption, succession, amendment and separation retain immutable history." }, { "dimension": "relationships", "status": "covered", "notes": "Worker, employer, agency, host, client, paymaster, platform, authority, assignment and instrument roles are typed and time-qualified." }, { "dimension": "temporal", "status": "covered", "notes": "Asserted, agreed, effective, observed, decision, notice and knowledge times remain distinct and use RFC 3339 for events." }, { "dimension": "spatial", "status": "covered", "notes": "Workplace, remote, mobile, host-territory and cross-border context are referenced with jurisdiction implications." }, { "dimension": "provenance", "status": "covered", "notes": "Party and authority assertions, evidence, derivation, revision and reconciliation are attributable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Bilateral evidence and power asymmetry are explicit; each referenced record retains its master system." }, { "dimension": "validation and quality", "status": "covered", "notes": "Duplicates, status scope, indicator sufficiency, stale state, conflicting assertions and projection loss are checked." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose limitation, minimum disclosure, correction, restriction, worker access and audit are covered." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Per-field retention, legal hold, tombstone and non-cascading deletion preserve lawful evidence and history." }, { "dimension": "interoperability", "status": "covered", "notes": "ICSE, ISCO, ESCO, W3C ORG, HR and jurisdiction profiles are pinned and loss-aware." } ], "known_omissions": [ "National and subnational labour-law, public-service, military, seafarer, domestic-work, child-work, platform-work, apprenticeship and collective-bargaining profiles require specialist treatment.", "Contract, assignment, payroll, compensation, benefits, attendance, leave, tax, social insurance, qualification, recruitment and performance lifecycles remain in neighboring models.", "Certified HR-schema, ICSE-18, ISCO-08, ESCO and jurisdictional crosswalks, conformance suites and rights-impact fixtures remain future work." ], "conflicts": [ "Employment status may differ between statistical, tax, social-insurance and labour-law purposes and must never be collapsed into one unqualified category.", "The employer, agency, host, client, paymaster, platform and beneficial controller may differ in multi-party work.", "An assignment, payroll event, workplace credential or contract label may exist without proving current employment status or legal effect." ], "regional_assumptions": [ "EU Directives 2019/1152 and 2008/104/EC and the GDPR provide European profiles and do not create universal global legal obligations.", "ILO Convention No. 158 is applicable only where its ratification and implementation scope is verified; Recommendation No. 198 remains guidance for national policy.", "ICSE-18 and ISCO-08 are statistical classifications and ESCO is a European semantic classification, not direct legal-status authorities." ], "adversarial_checks": [ "Reject any Employment record that includes generic organizational membership or treats worker-employer pair, job title, contract number or payroll account as unique identity.", "Reject a legal-status conclusion inferred solely from party label, contract type, payment method, occupation, one control indicator or ICSE category.", "Reject ownership inferred from record custody and reject employer-only control over worker access, correction, dispute, portability or lawful retention.", "Reject active-status inference from an assignment, payroll event, building access or old contract without qualified current evidence.", "Reject mutation, verification or separation beyond the actor's jurisdiction, purpose, field scope and authority and preserve prior assertions bitemporally." ] }, "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": "relationship", "status": "accepted as a jurisdiction-qualified employment relationship", "rationale": "The model represents one work relationship between a worker party and an employing party. Membership, parties, positions, assignments, occupations, contracts, payroll, attendance, benefits, tax, social insurance, qualifications, recruitment and evidence remain distinct linked records or objects." }, "decisions": [ { "concept": "Employment and membership", "disposition": "accepted as separate models", "rationale": "The current registry explicitly requires Employment to exclude generic belonging and affiliation, which are owned by WM-ORG-006 Membership." }, { "concept": "Relationship identity", "disposition": "accepted as independently governed", "rationale": "A worker-employer pair may have several concurrent or successive relationships, so neither party pair, job title, assignment, contract number, payroll account, start date nor hash is sufficient identity." }, { "concept": "Employment status", "disposition": "accepted as purpose-qualified and jurisdiction-qualified assertions", "rationale": "Statistical, tax, social-insurance and labour-law status may differ, while ILO Recommendation No. 198 makes facts and national determination mechanisms more important than party labels." }, { "concept": "ICSE-18 categories", "disposition": "accepted as statistical classification only", "rationale": "ICSE-18 organizes jobs by authority and economic risk and helps recognize employees and dependent contractors, but it does not itself create universal legal status." }, { "concept": "Multi-party work", "disposition": "accepted with typed time-bound roles", "rationale": "Employer, agency, host, client, paymaster, platform and competent authority may differ, especially for temporary-agency, dispatched and platform-mediated work." }, { "concept": "Employment and assignment", "disposition": "accepted as relationship and realization", "rationale": "WM-ORG-016 owns assignment identity, scope, execution and lifecycle. Employment owns only the typed interval-qualified link showing that an assignment realizes the relationship." }, { "concept": "Job, position, role and occupation", "disposition": "accepted as distinct external concepts", "rationale": "ISCO-08 distinguishes a concrete job from an occupation class, and W3C ORG distinguishes posts and roles from qualified person-organization relationships." }, { "concept": "Terms and transactions", "disposition": "accepted as versioned references", "rationale": "Contracts, collective agreements, policies, payroll, attendance, benefits, tax and social-insurance records keep their own masters and lifecycles; Employment records applicability, precedence and evidential links." }, { "concept": "Bitemporal correction and dispute", "disposition": "accepted with immutable prior assertions", "rationale": "A competent determination may be retroactive, but it must not erase what parties or systems previously asserted or when the determination became known." }, { "concept": "Bilateral record and power asymmetry", "disposition": "accepted as multi-party provenance, not unilateral ownership", "rationale": "Both parties may contribute and hold evidence, but neither party automatically controls the other's lawful access, correction, portability, dispute record or retention duties." }, { "concept": "Lifecycle state", "disposition": "accepted as explicit relationship events", "rationale": "Assignments, payroll events, workplace access and old contracts may be evidence but never alone establish current employment, suspension, continuity or separation." }, { "concept": "Approved registry composition", "disposition": "held pending relation governance", "rationale": "The relation ledger contains a candidate WM-ORG-005 COMPOSE WM-ORG-016 row, not an approved relation, so the proposed assignment-realization link remains draft." } ], "publicationHolds": [ "Claude and Grok timed out during their bounded attempts, so independent external review is absent and explicitly waived for this published reviewable draft.", "The previous O3 card combined Employment and Membership, while the current registry requires separate WM-ORG-005 and WM-ORG-006 boundaries; this publication replaces that combined boundary only for WM-ORG-005.", "The relation ledger marks WM-ORG-005 COMPOSE WM-ORG-016 as candidate rather than approved, and other neighboring model relations are not approved, so all proposed composition remains draft.", "National labour-law, public-service, military, seafarer, domestic-work, child-work, platform-work, apprenticeship and collective-bargaining profiles require specialist review.", "Certified HR-schema, ICSE-18, ISCO-08, ESCO, W3C ORG and jurisdictional crosswalks, conformance fixtures and rights-impact suites remain unverified.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Develop jurisdiction-specific status, rights, termination, transfer, working-time, agency-work, platform-work and record-retention profiles.", "Approve model identifiers and relation cardinalities for parties, positions, assignments, occupations, contracts, policies, payroll, attendance, benefits, tax, social insurance, qualifications, recruitment, evidence and access.", "Create deterministic fixtures for duplicate relationships, concurrent employers, agency and host roles, status disputes, retroactive determinations, employer succession, separation challenges and minimum verification.", "Validate certified statistical, HR, linked-data and legal-document projections with explicit information-loss and round-trip tests." ] }, "statistics": { "sources": 12, "bundles": 7, "layers": 16, "findings": 32, "questions": 96, "artifacts": 32, "functions": 12 } }