# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-08-24T01:09:19Z", "synthesisSha256": "276439f4a06ed634dda2e84d4bb34499a521d08dbb31eab9d5dfe8fb041466e0", "providers": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ORG-004", "registryId": "vr.wm-org-004", "name": "Position", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ORG.POS" ], "tags": [ "position", "soc.org.pos" ], "status": "research draft" }, "canonicalUrl": "https://ver.cy/models/wm-org-004-position/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-org-004", "model": { "registry_id": "vr.wm-org-004", "model_id": "WM-ORG-004", "name": "Position", "entry_kind": "entity", "purpose": "Model the position as a durable, addressable organizational construct that exists independently of any occupant: the work assigned by competent authority, classified, placed, funded, requirement-bearing and lifecycle-governed, so agents can create, inspect, classify, staff and retire positions without conflating them with people, jobs or contracts.", "scope_statement": "In scope is everything that is true of a position while it is vacant. A position is the bundle of duties and responsibilities assigned by competent authority (5 CFR 511.101) and modelled as org:Post, which W3C defines as a position existing independently of the person or persons filling it. The model owns identity, titling, duty content, occupational and grade classification, structural placement and reporting, location and work arrangement, capacity (FTE/headcount) and funding, requirements and essential functions, delegated and prescribed authority, risk/screening designations, working conditions, lifecycle and effective-dated change, governance and evidence, and outbound interoperability. It does not own the person, the occupancy relationship, the employment contract, the recruiting workflow, or the taxonomies it aligns to.", "in_scope": [ "Position identity, keys, official and working titles, and language-tagged alternative labels", "Assigned duties, responsibilities and essential functions attributed to the position rather than to an incumbent", "Occupational classification, job/class membership, grade or level and job-evaluation outcome", "Placement in an organizational unit, cost centre, reporting and supervisory structure", "Work location, work arrangement and schedule attributes attached to the seat", "Capacity and occupancy control: FTE, headcount, single vs pooled, overlap tolerance, vacancy state", "Budget, funding source and the pay range or grade ladder framing the seat", "Qualification, competency, credential, screening, clearance and approval requirements", "Delegated decision rights and externally prescribed regulatory responsibilities allocated to the seat", "Lifecycle states, effective-dated versioning, classification authority, certification, appeal and retention" ], "out_of_scope": [ "The natural person, worker or agent identity that may occupy the position", "The occupancy relationship itself (appointment, assignment, tenure, occupancy dates) — owned by WM-ORG-016", "The organizational unit as an entity, its charter and its own hierarchy — owned by WM-ORG-002", "Team formation and team-level goals — owned by WM-ORG-003", "Employment contract terms, payroll processing, absence and time records", "Recruiting workflow: requisition approval chain, candidate pipeline, interview and selection records", "The occupation, skill and competency taxonomies themselves (ISCO-08, ESCO, O*NET-SOC, NICE) — referenced, not owned", "Individual performance appraisal, development plans and remuneration paid to an incumbent", "Compensation plan and pay-structure master data (grade ladders and steps are referenced by key)" ], "boundary_notes": [ { "neighbor": "WM-ORG-016 Assignment / occupancy", "distinction": "The position persists while vacant; the assignment exists only while an agent occupies it. W3C separates org:Post (independent of holder) from org:Membership, which exists only when an agent occupies a role. Occupancy dates, tenure and incumbent-specific terms belong to the assignment, not the position.", "source_refs": [ "SRC-001" ] }, { "neighbor": "WM-ORG-002 Organizational unit", "distinction": "A unit is a collection of people and functions with its own recognition inside a larger organization; a position is a single seat that is contained in exactly one unit at a time via org:postIn / org:hasPost. Unit charter, mandate and unit hierarchy stay with WM-ORG-002.", "source_refs": [ "SRC-001", "SRC-009" ] }, { "neighbor": "Job / class / occupation classifier", "distinction": "A position is an instance; a class is 'all positions which are sufficiently similar as to kind of work, level of difficulty and responsibility, and qualification requirements' (5 CFR 511.101), and an occupation is 'a set of jobs whose main tasks and duties are characterised by a high degree of similarity' (ISCO-08). Classifier definitions, code lists and hierarchies are external registries; the position holds only the coded reference and the evaluation evidence.", "source_refs": [ "SRC-005", "SRC-007" ] }, { "neighbor": "Position opening / job advertisement", "distinction": "A vacancy notice is a published recruiting artifact with its own validity window, datePosted, validThrough and application channel; it is a projection referencing zero, one or many positions. HR Open keeps PositionOpening in the recruiting domain and organizational structure with incumbents in OrganizationChart.", "source_refs": [ "SRC-002", "SRC-004" ] }, { "neighbor": "org:Role (abstract role)", "distinction": "W3C org:Role denotes the abstract role and requires a Membership instance to link a person, whereas org:Post is a concrete organizational seat. Role vocabularies (NICE work roles, ESCO occupations) are alignments, not the position itself.", "source_refs": [ "SRC-001", "SRC-010" ] }, { "neighbor": "Employment contract and payroll", "distinction": "Pay range, grade ladder and budget frame the seat; actual remuneration, contractual clauses and payroll results attach to the occupant's employment relation. EU pay-transparency duties bind the employer's disclosure at recruitment and reporting, not the position record's internal semantics.", "source_refs": [ "SRC-012", "SRC-009" ] } ] }, "sources": [ { "id": "SRC-001", "title": "The Organization Ontology (org:)", "organization": "World Wide Web Consortium (W3C)", "url": "https://www.w3.org/TR/vocab-org/", "version_or_date": "W3C Recommendation, 16 January 2014", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:05:00Z", "relevance": "Normative definitions of org:Post ('some position within an organization that exists independently of the person or persons filling it'), org:Role, org:Membership, org:holds/heldBy, org:postIn/hasPost, org:reportsTo and time-bounded membership. Primary basis for position-vs-person separation and vacancy modelling." }, { "id": "SRC-002", "title": "HR Open Standards — Standards", "organization": "HR Open Standards Consortium, Inc.", "url": "https://www.hropenstandards.org/standards", "version_or_date": "Release 4.5 Final; page updated 2026-02-05", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:07:00Z", "relevance": "Specification families (recruiting, compensation, provisioning, contingent staffing, time, assessments) and the objects PositionOpening, PositionCompetencyModel, OrganizationChart (units, positions, incumbents) and HRMasterData; defines the interoperable exchange boundary for position data." }, { "id": "SRC-003", "title": "ESCO — Occupations pillar", "organization": "European Commission (DG EMPL), ESCO", "url": "https://esco.ec.europa.eu/en/classification/occupation_main", "version_or_date": "ESCO v1.2.1, updated 10 December 2025", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:10:00Z", "relevance": "3039 occupation concepts at ISCO level 5 and below, each mapped to exactly one ISCO-08 code, with preferred/alternative/hidden labels in 28 languages, scope notes, regulatory-aspect metadata and essential/optional skills. Source for multilingual titling and competency requirement references." }, { "id": "SRC-004", "title": "schema.org JobPosting", "organization": "Schema.org Community Group", "url": "https://schema.org/JobPosting", "version_or_date": "schema.org v30.0, 2026-03-19", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:12:00Z", "relevance": "Publication-facing vocabulary: title, occupationalCategory (O*NET-SOC or ISCO-08), employmentType, hiringOrganization, employmentUnit, jobLocation, jobLocationType, baseSalary, qualifications, responsibilities, skills, experienceRequirements, totalJobOpenings, jobStartDate, datePosted, validThrough, identifier. Evidence that the advertisement is a distinct projection of the position." }, { "id": "SRC-005", "title": "International Standard Classification of Occupations: ISCO-08 (UN classifications registry entry)", "organization": "United Nations Statistics Division / International Labour Organization", "url": "https://unstats.un.org/unsd/classifications/Family/Detail/1067", "version_or_date": "ISCO-08, adopted 2007", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:15:00Z", "relevance": "Defines job as 'a set of tasks and duties performed, or meant to be performed, by one person for a single economic unit', occupation as 'a set of jobs whose main tasks and duties are characterised by a high degree of similarity', skill level and skill specialisation, and the 10/43/130/436 four-level hierarchy." }, { "id": "SRC-006", "title": "O*NET Content Model", "organization": "U.S. Department of Labor / National Center for O*NET Development", "url": "https://www.onetcenter.org/content.html", "version_or_date": "O*NET Content Model, retrieved 24 August 2026", "source_type": "classifier", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:18:00Z", "relevance": "Six domains — worker characteristics, worker requirements, experience requirements, occupational requirements (generalized and detailed work activities, work context and environmental conditions), workforce characteristics, occupation-specific tasks/tools. Source for duty decomposition, requirement typing and working-condition attributes." }, { "id": "SRC-007", "title": "5 CFR § 511.101 — Definitions (Classification under the General Schedule)", "organization": "U.S. Office of Personnel Management (regulation text reproduced by Cornell Legal Information Institute)", "url": "https://www.law.cornell.edu/cfr/text/5/511.101", "version_or_date": "Current text as published, retrieved 24 August 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:22:00Z", "relevance": "Legal definition of position as 'the work, consisting of the duties and responsibilities, assigned by competent authority for performance by an employee', plus class, classification and grade. Anchors duty-based identity and the competent-authority assignment act." }, { "id": "SRC-008", "title": "5 CFR Part 511 — Classification Under the General Schedule", "organization": "U.S. Office of Personnel Management (regulation text reproduced by Cornell Legal Information Institute)", "url": "https://www.law.cornell.edu/cfr/text/5/part-511", "version_or_date": "Current text as published, retrieved 24 August 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:24:00Z", "relevance": "Subpart structure: general provisions (511.101), coverage (511.201–203), classification appeals (511.601–616) and effective dates of position classification actions or decisions (511.701–703). Basis for appeal rights and for dating classification decisions distinctly from record creation." }, { "id": "SRC-009", "title": "REST API for Oracle Fusion Cloud HCM — Get all positions", "organization": "Oracle Corporation", "url": "https://docs.oracle.com/en/cloud/saas/human-resources/farws/op-positions-get.html", "version_or_date": "HCM REST API version 11.13.18.05, retrieved 24 August 2026", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 3, "accessed_at": "2026-08-24T09:28:00Z", "relevance": "Operational attribute set of a production position record: PositionId/PositionCode, PositionType SINGLE|POOLED, BusinessUnitId, DepartmentId, JobId, LocationId, FTE, HeadCount, OverlapAllowedFlag, HiringStatus PROPOSED|FROZEN|APPROVED, ActiveStatus, EffectiveStartDate/EffectiveEndDate with effectiveDate query, BudgetedPositionFlag, BudgetAmount, CostCenter, GradeLadderId/EntryGradeId/EntryStepId, validGrades, SeasonalFlag, ProbationPeriod, SecurityClearance, CreationDate/LastUpdateDate." }, { "id": "SRC-010", "title": "NIST SP 800-181 Rev. 1 — Workforce Framework for Cybersecurity (NICE Framework)", "organization": "National Institute of Standards and Technology (NIST)", "url": "https://csrc.nist.gov/pubs/sp/800/181/r1/final", "version_or_date": "Revision 1, November 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:32:00Z", "relevance": "Task, Knowledge and Skill statements as reusable building blocks composed into Work Roles and Competency Areas that organizations map onto job descriptions and positions; supports treating requirement sets as referenced, versioned components rather than free text." }, { "id": "SRC-011", "title": "FCA Handbook SYSC 24 — Senior managers and certification regime: allocation of prescribed responsibilities", "organization": "Financial Conduct Authority (UK)", "url": "https://www.handbook.fca.org.uk/handbook/SYSC/24/", "version_or_date": "FCA Handbook, page last updated 10 July 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:36:00Z", "relevance": "Requires a firm to allocate each FCA-prescribed senior management responsibility to one or more SMF managers, held by the most senior person responsible with sufficient resources and authority, documented in statements of responsibilities and management responsibilities maps. Primary evidence that regulatory accountability attaches to a designated position." }, { "id": "SRC-012", "title": "EU action on equal pay — Pay Transparency Directive (EU) 2023/970", "organization": "European Commission", "url": "https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/gender-equality/equal-pay/eu-action-equal-pay_en", "version_or_date": "Directive adopted May 2023; transposition deadline 7 June 2026; page retrieved 24 August 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:40:00Z", "relevance": "Right to pay information prior to employment, prohibition on asking salary history and on pay non-disclosure clauses, employer gender pay-gap reporting at 100+ employees, joint pay assessment triggers, clarified 'work of equal value', and EU-wide guidelines on gender-neutral job evaluation systems issued March 2026." }, { "id": "SRC-013", "title": "RFC 3339 — Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "July 2002, Proposed Standard (updated by RFC 9557)", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T09:43:00Z", "relevance": "Internet date/time profile of ISO 8601: full-date, full-time with mandatory time-offset of 'Z' or ±HH:MM, seconds (60 permitted for leap seconds), optional fractional seconds, and the -00:00 unknown-local-offset convention distinct from Z." }, { "id": "SRC-014", "title": "29 CFR § 1630.2 — Definitions (ADA regulations), including 'essential functions'", "organization": "U.S. Equal Employment Opportunity Commission (regulation text reproduced by Cornell Legal Information Institute)", "url": "https://www.law.cornell.edu/cfr/text/29/1630.2", "version_or_date": "Current text as published, retrieved 24 August 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T09:47:00Z", "relevance": "Essential functions are 'the fundamental job duties of the employment position'; factors include the reason the position exists, limited number of employees available, and specialization; evidence includes 'written job descriptions prepared before advertising or interviewing applicants for the job', time spent, consequences of not requiring performance, CBA terms and incumbent experience. Establishes duty-level granularity, essential/marginal distinction and pre-recruitment documentation as evidence." }, { "id": "SRC-015", "title": "Popolo Post data specification", "organization": "Popolo Project", "url": "https://www.popoloproject.com/specs/post.html", "version_or_date": "Popolo data specification, accessed 2026-08-24", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Civic Post as a position independent of its holder; distinguishes post from role; requires organization; records creation and elimination dates, geographic area, contact and labels; rejects direct org:holds occupancy." }, { "id": "SRC-016", "title": "5 U.S. Code § 5102 - Definitions; application", "organization": "United States Congress / Legal Information Institute", "url": "https://www.law.cornell.edu/uscode/text/5/5102", "version_or_date": "5 U.S.C. § 5102, current text as presented 2026-08-24", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Statutory definition of position as the work consisting of the duties and responsibilities assignable to an employee, plus class of positions and grade, with enumerated exclusions (unpaid, fee-basis, seasonal, experts, trades and others)." }, { "id": "SRC-017", "title": "5 CFR 511.101 Definitions (Classification Under the General Schedule)", "organization": "U.S. Office of Personnel Management / National Archives Office of the Federal Register", "url": "https://www.ecfr.gov/current/title-5/chapter-I/subchapter-B/part-511/subpart-A", "version_or_date": "5 CFR Part 511 Subpart A, eCFR current as of 2026-08-20", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Regulatory definition: Position means the work, consisting of the duties and responsibilities, assigned by competent authority for performance by an employee; plus class, grade and classification." }, { "id": "SRC-018", "title": "Introduction to the Position Classification Standards", "organization": "U.S. Office of Personnel Management", "url": "https://www.opm.gov/policy-data-oversight/classification-qualifications/classifying-general-schedule-positions/introduction-to-position-classification-standards.pdf", "version_or_date": "TS-134 July 1995, TS-107 August 1991, revised August 2009", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Federal definition of Position and Position Description; official titles; classification of work; requirement that the PD be kept current and certified by the immediate supervisor." }, { "id": "SRC-019", "title": "HL7 FHIR Resource PractitionerRole", "organization": "HL7 International", "url": "https://hl7.org/fhir/R5/practitionerrole.html", "version_or_date": "FHIR R5 v5.0.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Period-bounded role at an organization and location, identifiers, active flag, empty-practitioner unnamed-slot pattern, specialty, location and healthcareService; boundary with CareTeam and Practitioner qualifications." }, { "id": "SRC-020", "title": "schema.org Occupation", "organization": "Schema.org", "url": "https://schema.org/Occupation", "version_or_date": "Schema.org V30.0, 2026-03-19", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Occupation as a profession with occupationalCategory (O*NET-SOC, ISCO-08), education and qualification requirements, responsibilities, skills, estimatedSalary and occupationLocation; used on JobPosting and Person.hasOccupation, not as an org-specific slot." }, { "id": "SRC-021", "title": "International Standard Classification of Occupations (ISCO-08)", "organization": "International Labour Organization", "url": "https://isco-ilo.netlify.app/en/isco-08/", "version_or_date": "ISCO-08, adopted December 2007 and endorsed by the ILO Governing Body March 2008", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Normative job versus occupation versus skill definitions; four-level structure used to classify jobs worldwide, including Armed Forces Occupations as Major Group 0." }, { "id": "SRC-022", "title": "ISO 30400:2022 Human resource management — Vocabulary", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/78044.html", "version_or_date": "ISO 30400:2022, published 2022-11-15", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "ISO/TC 260 HR vocabulary covering organization, workforce composition, workforce planning and allocation, recruitment and related terms. Exact published definitions of job, role and position were not inspectable in full text during this run and must not be treated as quoted." }, { "id": "SRC-023", "title": "schema.org EmployeeRole", "organization": "Schema.org", "url": "https://schema.org/EmployeeRole", "version_or_date": "Schema.org V30.0, 2026-03-19", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Employee relationship with baseSalary, salaryCurrency, startDate, endDate and roleName; numberedPosition on OrganizationRole. Distinguishes occupancy-pay from the standing Position and shows sports namedPosition as a conflicting sense." }, { "id": "SRC-024", "title": "Popolo Membership data specification", "organization": "Popolo Project", "url": "https://www.popoloproject.com/specs/membership.html", "version_or_date": "Popolo data specification, accessed 2026-08-24", "source_type": "schema", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Occupancy of a Post occurs through Membership with start and end dates, optional post, role, on-behalf-of organization and geographic area; used to bound WM-ORG-016 against this Position model." }, { "id": "SRC-025", "title": "HRDG 4511 Section B - Position Descriptions", "organization": "USDA Animal and Plant Health Inspection Service", "url": "https://www.aphis.usda.gov/organization/business-services/hr-desk-guide/HRDG-4511/hrdg-4511-Secb", "version_or_date": "APHIS HRDG 4511 Section B, page dated 2020-06-02", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-08-24T12:00:00Z", "relevance": "Operational definition of the Position Description as the official record of management’s assignment of duties, responsibilities and supervisory relationships; legal basis for appointment, pay, qualifications, selection and performance plans." } ], "structure": { "bundles": [ { "id": "position-identity-and-definition", "name": "Position identity and definition", "description": "What uniquely designates this position, what it is called, what work is assigned to it, and how that work is classified and levelled.", "rationale": "A position is legally and ontologically defined by the work assigned to it, not by its holder or its label; identity, titling and classification must therefore be modelled before any staffing concern.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "layers": [ { "id": "identity-and-designation", "name": "Identity and designation", "description": "Keys, namespaces and names that let an agent address exactly one position across systems and languages.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-013" ], "findings": [ { "id": "position-identifier-and-keys", "name": "Position identifier and key set", "description": "The authoritative identifier for the seat, the secondary business codes that are unique only within a scope, and the external identifiers that make it resolvable outside the master system.", "source_refs": [ "SRC-001", "SRC-009", "SRC-004", "SRC-013" ], "questions": [ { "id": "q-pid-1", "text": "Which system is the master of record for this position and what identifier does it assign?", "kind": "identity", "answer_data": [ "master system reference", "master position identifier", "identifier assignment instant" ] }, { "id": "q-pid-2", "text": "Is the human-facing position code unique globally or only within a business unit or legal entity?", "kind": "constraint", "answer_data": [ "position code", "uniqueness scope reference", "collision policy" ] }, { "id": "q-pid-3", "text": "What resolvable IRI, if any, publishes this position as an org:Post in the organization graph?", "kind": "interoperability", "answer_data": [ "position IRI", "graph publication endpoint", "rdf type assertion" ] }, { "id": "q-pid-4", "text": "When a position is split, merged or renumbered, how are prior identifiers preserved and redirected?", "kind": "provenance", "answer_data": [ "superseded identifier list", "succession relation type", "succession effective date" ] } ], "data_elements": [ { "id": "de-position-id", "name": "Master position identifier", "description": "Identifier assigned by the authoritative HRIS or position-control system; never a title or a date.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-009", "SRC-001" ] }, { "id": "de-position-code", "name": "Position code", "description": "Human-readable code unique within a declared scope such as business unit; Oracle constrains PositionCode to uniqueness within the business unit.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-position-iri", "name": "Published position IRI", "description": "Governed global identifier used when the position is exposed as an org:Post in a linked-data organization graph.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-external-ids", "name": "External identifier set", "description": "Scheme-qualified identifiers used by payroll, recruiting, finance and directory systems, each with the owning system reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "de-identity-assigned-at", "name": "Identifier assignment instant", "description": "RFC 3339 instant at which the identifier was minted, recorded separately from the business effective date of the position.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013", "SRC-009" ] } ], "artifacts": [ { "id": "position-master-record", "name": "Position master record", "description": "The authoritative, effective-dated record of the seat held by the master system, carrying identifiers, placement, capacity and status.", "media_or_form": [ "structured record in a system of record", "exported dataset row", "graph node typed as org:Post" ], "serial": true, "identity_strategy": "Master-system position identifier; fall back to governed IRI, then to a Dimension-minted ULID when no upstream key exists.", "source_refs": [ "SRC-009", "SRC-001" ] } ], "inline_only_rationale": null }, { "id": "position-title-and-labels", "name": "Position title and labels", "description": "Official title, working title and multilingual alternative labels, including the gender-neutral titling duty that applies to advertised seats in the EU.", "source_refs": [ "SRC-003", "SRC-012", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-ttl-1", "text": "What is the official title of the position and which authority approved it?", "kind": "authority", "answer_data": [ "official title", "approving authority reference", "title approval date" ] }, { "id": "q-ttl-2", "text": "Which working or marketing titles may be used publicly and where do they diverge from the official title?", "kind": "definition", "answer_data": [ "working title", "publication channel", "divergence note" ] }, { "id": "q-ttl-3", "text": "In which languages is the title published and what are the language-tagged alternative labels?", "kind": "interoperability", "answer_data": [ "label value", "BCP 47 language tag", "label role such as preferred or alternative" ] }, { "id": "q-ttl-4", "text": "Has the title been checked as gender-neutral before the vacancy is advertised?", "kind": "validation", "answer_data": [ "neutrality check outcome", "checker identity", "check instant" ] } ], "data_elements": [ { "id": "de-official-title", "name": "Official title", "description": "The title of record used in classification, contracts and organization charts.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-009" ] }, { "id": "de-working-title", "name": "Working title", "description": "Alternative internal or market-facing title that does not change classification.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-label-set", "name": "Language-tagged label set", "description": "Preferred, alternative and hidden labels with language tags, mirroring ESCO's multilingual labelling of occupations.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "de-title-neutrality-check", "name": "Gender-neutral titling check", "description": "Recorded outcome of the neutrality review required for recruitment under the EU pay-transparency regime.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "position-title-register-entry", "name": "Position title register entry", "description": "Governed entry binding official title, permitted variants and language-tagged labels to the position and its classification.", "media_or_form": [ "controlled title register", "reference table export", "label graph fragment" ], "serial": false, "identity_strategy": "Composite of position identifier and title effective-start date; labels keyed by language tag and label role.", "source_refs": [ "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "work-content-and-classification", "name": "Work content and classification", "description": "The duties assigned to the seat and how those duties place it in occupational and grade classification systems.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-012", "SRC-014" ], "findings": [ { "id": "assigned-duties-and-responsibilities", "name": "Assigned duties and responsibilities", "description": "The decomposed work content of the seat: duty statements, their weight, and the essential-versus-marginal distinction that determines what the position exists to do.", "source_refs": [ "SRC-007", "SRC-014", "SRC-006", "SRC-010" ], "questions": [ { "id": "q-dut-1", "text": "What discrete duties and responsibilities has competent authority assigned to this position?", "kind": "definition", "answer_data": [ "duty statement", "assigning authority reference", "assignment effective date" ] }, { "id": "q-dut-2", "text": "Which duties are essential because the position exists to perform them, and which are marginal?", "kind": "classification", "answer_data": [ "essentiality flag", "essentiality rationale code", "supporting evidence reference" ] }, { "id": "q-dut-3", "text": "How much of the position's time or effort does each duty consume?", "kind": "measurement", "answer_data": [ "time or effort share", "measurement basis", "measurement date" ] }, { "id": "q-dut-4", "text": "Which duty statements are drawn from a governed catalogue rather than written free-hand?", "kind": "provenance", "answer_data": [ "catalogue scheme reference", "catalogue version", "catalogue item code" ] } ], "data_elements": [ { "id": "de-duty-statement", "name": "Duty statement", "description": "A single assigned duty or responsibility expressed at task or work-activity granularity.", "value_kind": "text", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-007", "SRC-006" ] }, { "id": "de-duty-essential-flag", "name": "Essential function flag", "description": "Whether the duty is a fundamental job duty of the position under the essential-functions test.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "de-duty-time-share", "name": "Duty time or effort share", "description": "Proportion of the position's work attributable to the duty; an explicit evidentiary factor in essential-function determination.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "de-duty-catalogue-ref", "name": "Duty catalogue reference", "description": "Scheme, version and code of a reusable task or work-activity statement, for example a NICE Task statement or an O*NET detailed work activity.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010", "SRC-006" ] } ], "artifacts": [ { "id": "position-description", "name": "Official position description", "description": "The certified statement of the duties and responsibilities assigned to the position; also the evidentiary written job description prepared before advertising or interviewing.", "media_or_form": [ "certified document", "structured duty record set", "exported description text" ], "serial": true, "identity_strategy": "Position identifier plus description version number and RFC 3339 certification instant; superseded versions retained, never overwritten.", "source_refs": [ "SRC-007", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "occupational-classification", "name": "Occupational and job classification", "description": "Placement of the position in occupational taxonomies and in the organization's internal job or class structure, with each code carrying its scheme and version.", "source_refs": [ "SRC-005", "SRC-003", "SRC-006", "SRC-004", "SRC-009", "SRC-007" ], "questions": [ { "id": "q-occ-1", "text": "Which internal job or class does this position belong to, and is that assignment mandatory?", "kind": "classification", "answer_data": [ "job or class reference", "assignment mandatory flag", "class definition source" ] }, { "id": "q-occ-2", "text": "Which external occupational codes are asserted, under which scheme and version?", "kind": "interoperability", "answer_data": [ "scheme identifier", "scheme version", "occupation code" ] }, { "id": "q-occ-3", "text": "On what evidence was the occupational classification determined, and by whom?", "kind": "evidence", "answer_data": [ "classification rationale", "classifier identity", "decision instant" ] }, { "id": "q-occ-4", "text": "What triggers a review of the occupational classification of this position?", "kind": "lifecycle", "answer_data": [ "review trigger code", "last review date", "next review due date" ] } ], "data_elements": [ { "id": "de-job-ref", "name": "Job or class reference", "description": "Reference to the internal job/class grouping positions that are sufficiently similar in kind of work, difficulty, responsibility and qualification requirements; mandatory in position-managed HCM configurations.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-009" ] }, { "id": "de-occupation-code", "name": "External occupation code", "description": "Coded occupational category expressed as a scheme/version/code triple such as ISCO-08 unit group, ESCO concept or O*NET-SOC code.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-003", "SRC-004" ] }, { "id": "de-skill-level", "name": "Asserted skill level", "description": "ISCO-08 skill level and skill specialisation attribution supporting comparability of the seat across statistics.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "de-classification-decision", "name": "Classification decision record reference", "description": "Pointer to the analysis that placed the position in a class, with decision maker and instant.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "classification-evaluation-record", "name": "Classification evaluation record", "description": "Documented analysis identifying the position and placing it in a class under the applicable classification plan, including scheme versions applied.", "media_or_form": [ "evaluation document", "structured decision record", "classification appeal exhibit" ], "serial": true, "identity_strategy": "Position identifier plus decision sequence number and RFC 3339 decision instant; the effective date of the classification action is recorded separately.", "source_refs": [ "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "grade-level-and-job-evaluation", "name": "Grade, level and job evaluation", "description": "The levelling of the position and the gender-neutral evaluation criteria that justify it, distinct from the occupational category of the work.", "source_refs": [ "SRC-007", "SRC-012", "SRC-009" ], "questions": [ { "id": "q-grd-1", "text": "What grade, band or level is assigned to the position and under which grade ladder?", "kind": "classification", "answer_data": [ "grade reference", "grade ladder reference", "entry grade and step" ] }, { "id": "q-grd-2", "text": "Which evaluation criteria produced the level, and were skills, effort, responsibility and working conditions all applied?", "kind": "measurement", "answer_data": [ "criterion identifier", "criterion score or rating", "evaluation method reference" ] }, { "id": "q-grd-3", "text": "Which other positions are treated as the same category of workers or as work of equal value?", "kind": "relationship", "answer_data": [ "equal-value peer group reference", "comparability basis", "determination date" ] }, { "id": "q-grd-4", "text": "Is the evaluation system documented as objective and gender-neutral, and when was it last validated?", "kind": "validation", "answer_data": [ "evaluation system reference", "neutrality validation outcome", "validation date" ] } ], "data_elements": [ { "id": "de-grade-ref", "name": "Grade or level reference", "description": "Assigned grade, band or level; a grade groups classes equivalent in difficulty, responsibility and qualification requirements for pay administration.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-009" ] }, { "id": "de-grade-ladder", "name": "Grade ladder and valid grades", "description": "The ladder and the effective-dated set of grades valid for the position, including entry grade and entry step.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-evaluation-criteria", "name": "Job evaluation criteria scores", "description": "Ratings against objective criteria including skills, effort, responsibility and working conditions, used to establish work of equal value.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "de-worker-category", "name": "Category of workers reference", "description": "The grouping used for pay comparison and gender pay-gap reporting to which this position is allocated.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "job-evaluation-statement", "name": "Job evaluation statement", "description": "Record of the gender-neutral evaluation that levelled the position and allocated it to a category of workers.", "media_or_form": [ "evaluation scoring sheet", "structured criterion record set", "pay-assessment exhibit" ], "serial": true, "identity_strategy": "Position identifier plus evaluation scheme version and evaluation instant; retained to evidence objectivity of the criteria.", "source_refs": [ "SRC-012", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "structural-placement-and-relations", "name": "Structural placement and relations", "description": "Where the seat sits in the organization, who it reports to, and where and how the work is performed.", "rationale": "Positions are only meaningful inside a containing organization and a reporting structure; W3C models both org:postIn and org:reportsTo, and production systems make unit placement mandatory.", "source_refs": [ "SRC-001", "SRC-009", "SRC-004" ], "layers": [ { "id": "organizational-placement", "name": "Organizational placement", "description": "Containment in a unit and cost centre, and the reporting relations depicted on an organization chart.", "source_refs": [ "SRC-001", "SRC-009", "SRC-002" ], "findings": [ { "id": "unit-and-cost-center-placement", "name": "Unit and cost centre placement", "description": "The single organizational unit that holds the position, the legal entity and business unit context, and the cost centre that carries it financially.", "source_refs": [ "SRC-001", "SRC-009", "SRC-002" ], "questions": [ { "id": "q-plc-1", "text": "Which organizational unit holds this position at a given effective date?", "kind": "composition", "answer_data": [ "unit reference", "effective start date", "effective end date" ] }, { "id": "q-plc-2", "text": "Which legal entity and business unit govern the position for employment and payroll purposes?", "kind": "ownership", "answer_data": [ "legal entity reference", "business unit reference", "jurisdiction code" ] }, { "id": "q-plc-3", "text": "Which cost centre bears the position and does it differ from the holding unit?", "kind": "ownership", "answer_data": [ "cost centre code", "divergence reason", "finance owner reference" ] }, { "id": "q-plc-4", "text": "How is a position moved between units without losing its identity or history?", "kind": "lifecycle", "answer_data": [ "transfer effective date", "prior unit reference", "transfer authorization reference" ] } ], "data_elements": [ { "id": "de-unit-ref", "name": "Holding organizational unit reference", "description": "The unit in which the post exists, corresponding to org:postIn / org:hasPost; mandatory department reference in production systems.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-009" ] }, { "id": "de-business-unit", "name": "Business unit reference", "description": "Mandatory business-unit scope that also bounds position-code uniqueness.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "de-cost-center", "name": "Cost centre code", "description": "Financial owner of the seat, distinct from the organizational holder.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-placement-window", "name": "Placement validity window", "description": "Effective start and end dates for the placement of the position in this unit.", "value_kind": "date", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "organization-chart-extract", "name": "Organization chart extract", "description": "Structural view containing units, positions and incumbents as exchanged in HR Open's OrganizationChart object.", "media_or_form": [ "structured org-chart payload", "rendered chart", "graph export" ], "serial": true, "identity_strategy": "Root unit reference plus as-of effective date and generation instant; regenerated rather than edited in place.", "source_refs": [ "SRC-002", "SRC-001" ] } ], "inline_only_rationale": null }, { "id": "reporting-and-supervisory-relations", "name": "Reporting and supervisory relations", "description": "Post-to-post reporting lines, supervisory span and matrix or dotted-line relations that survive changes of occupant.", "source_refs": [ "SRC-001", "SRC-009", "SRC-011" ], "questions": [ { "id": "q-rep-1", "text": "To which position does this position report, and is the relation defined post-to-post or person-to-person?", "kind": "relationship", "answer_data": [ "reports-to target reference", "relation subject type", "relation effective window" ] }, { "id": "q-rep-2", "text": "Which positions report to this one, and does that make it a supervisory position?", "kind": "composition", "answer_data": [ "subordinate position references", "supervisory flag", "span of control count" ] }, { "id": "q-rep-3", "text": "Are there secondary, functional or matrix reporting lines and what do they authorize?", "kind": "relationship", "answer_data": [ "secondary relation type", "counterparty position reference", "authorized scope" ] }, { "id": "q-rep-4", "text": "Who acts for this position when it is vacant or its holder is unavailable?", "kind": "exception", "answer_data": [ "delegate position reference", "delegation trigger", "delegation window" ] } ], "data_elements": [ { "id": "de-reports-to", "name": "Reports-to relation", "description": "Reporting relation as depicted on an organization chart, expressible between posts rather than only between agents.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-supervisory-flag", "name": "Supervisory indicator", "description": "Whether the position supervises other positions, which materially affects classification and levelling.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-001" ] }, { "id": "de-delegate-position", "name": "Delegate position reference", "description": "Position designated to act for this one, mirroring the delegate-position attribute in production position records.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-relation-window", "name": "Relation validity window", "description": "Effective interval for each reporting relation, held separately from occupancy intervals.", "value_kind": "date", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-009" ] } ], "artifacts": [], "inline_only_rationale": "Reporting structure is expressed as typed edges between position nodes and is fully carried by the position master record and the organization chart extract; a separate persisted artifact would duplicate those and risk divergence between the graph and the rendered chart." } ] }, { "id": "work-location-and-arrangement", "name": "Work location and arrangement", "description": "Where the seat is located, whether it is remote-eligible, and the working pattern attached to it.", "source_refs": [ "SRC-004", "SRC-009", "SRC-006" ], "findings": [ { "id": "work-location-and-work-arrangement", "name": "Work location and work arrangement", "description": "Primary and alternate work locations, remote or hybrid eligibility, mobility expectations and any jurisdictional constraint that follows from location.", "source_refs": [ "SRC-004", "SRC-009", "SRC-006", "SRC-012" ], "questions": [ { "id": "q-loc-1", "text": "What is the primary work location of the position and which jurisdiction does it place it in?", "kind": "spatial", "answer_data": [ "location reference", "address or geography", "jurisdiction code" ] }, { "id": "q-loc-2", "text": "Is the position remote-eligible, hybrid or site-bound, and who decides?", "kind": "classification", "answer_data": [ "work arrangement code", "eligibility decision authority", "decision date" ] }, { "id": "q-loc-3", "text": "Does the position require travel, shift work or seasonal presence, and within what bounds?", "kind": "constraint", "answer_data": [ "travel expectation", "seasonal window", "shift pattern reference" ] }, { "id": "q-loc-4", "text": "Which location-driven obligations, such as pay-range disclosure or local labour rules, attach to this seat?", "kind": "requirement", "answer_data": [ "obligation reference", "triggering jurisdiction", "obligation effective date" ] } ], "data_elements": [ { "id": "de-location-ref", "name": "Work location reference", "description": "Location assigned to the position, distinct from the incumbent's residence.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-004" ] }, { "id": "de-work-arrangement", "name": "Work arrangement code", "description": "Site-based, hybrid or telecommute arrangement as published in job postings.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-seasonal-window", "name": "Seasonal window", "description": "Seasonal flag with start and end dates when the seat only exists or operates for part of the year.", "value_kind": "date", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-environmental-context", "name": "Environmental work context", "description": "Physical and environmental conditions of the work setting, drawn from the occupational-requirements domain.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "position-location-profile", "name": "Position location and arrangement profile", "description": "Record binding the seat to locations, arrangement type, seasonal windows and the jurisdictional obligations they trigger.", "media_or_form": [ "structured location record", "geocoded reference", "posting location fragment" ], "serial": false, "identity_strategy": "Position identifier plus location reference and effective-start date; jurisdiction derived from the location, never asserted independently.", "source_refs": [ "SRC-009", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "area-jurisdiction-and-constituency", "name": "Area and jurisdiction", "description": "Popolo geographic area relates a post to a constituency or territory. schema.org occupationLocation is the region for which an occupational description is appropriate because requirements vary by jurisdiction.", "source_refs": [ "SRC-015", "SRC-020" ], "questions": [ { "id": "area-jurisdiction-and-constituency-q01", "text": "What geographic area, constituency or jurisdiction is this Position related to, and from which area register?", "kind": "spatial", "answer_data": [ "area_ref", "area_identifier", "area_name", "area_scheme" ] }, { "id": "area-jurisdiction-and-constituency-q02", "text": "Which qualification or licence requirements of this Position are jurisdiction-specific?", "kind": "constraint", "answer_data": [ "jurisdiction_ref", "jurisdiction_specific_requirements" ] }, { "id": "area-jurisdiction-and-constituency-q03", "text": "Did elimination of an electoral or administrative area abolish this Position, as in the Popolo Annapolis example?", "kind": "lifecycle", "answer_data": [ "area_abolished_flag", "position_eliminated_with_area", "elimination_event_time" ] } ], "data_elements": [ { "id": "area-jurisdiction-and-constituency-data01", "name": "Geographic area reference", "description": "Area or constituency to which the post is related.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] }, { "id": "area-jurisdiction-and-constituency-data02", "name": "Occupation location", "description": "Region or country for which occupational requirements of this Position are stated.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-020" ] } ], "artifacts": [], "inline_only_rationale": "Area references point at a geographic or jurisdiction model; geometry is not stored here." } ] } ] }, { "id": "capacity-funding-and-occupancy", "name": "Capacity, funding and occupancy control", "description": "How much work the seat represents, how many holders it admits, who pays for it, and whether it is currently filled.", "rationale": "Position control is the operational reason positions exist as separate records: FTE, headcount, overlap rules, budget and vacancy state are enforced independently of any person.", "source_refs": [ "SRC-009", "SRC-001", "SRC-012" ], "layers": [ { "id": "capacity-and-occupancy-control", "name": "Capacity and occupancy control", "description": "Quantified capacity of the seat and the derived vacancy state, including pooled positions with multiple holders.", "source_refs": [ "SRC-009", "SRC-001" ], "findings": [ { "id": "capacity-fte-and-schedule", "name": "Capacity, FTE and working pattern", "description": "The full-time equivalence, headcount allowance, single or pooled type and scheduled working pattern that quantify the seat.", "source_refs": [ "SRC-009", "SRC-001", "SRC-004" ], "questions": [ { "id": "q-cap-1", "text": "What FTE and headcount does this position authorize, and are they consistent?", "kind": "measurement", "answer_data": [ "FTE value", "headcount value", "consistency rule reference" ] }, { "id": "q-cap-2", "text": "Is the position single or pooled, and may more than one holder occupy it at once?", "kind": "constraint", "answer_data": [ "position type code", "overlap allowed flag", "maximum concurrent holders" ] }, { "id": "q-cap-3", "text": "Is the position full-time or part-time, regular or temporary, and for how long?", "kind": "classification", "answer_data": [ "full or part time code", "regular or temporary code", "expected duration" ] }, { "id": "q-cap-4", "text": "How is FTE derived when working hours differ from the standard for the jurisdiction?", "kind": "measurement", "answer_data": [ "standard hours basis", "calculation method flag", "derivation date" ] } ], "data_elements": [ { "id": "de-fte", "name": "Authorized FTE", "description": "Full-time equivalent authorized for the seat, defaulting to 1 and used to standardize workload across differing hours.", "value_kind": "quantity", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "de-headcount", "name": "Authorized headcount", "description": "Number of holders the seat admits; greater than one only for pooled positions.", "value_kind": "number", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "de-position-type", "name": "Position type", "description": "Single or pooled; W3C also permits a post to be held by more than one person, so single occupancy must never be assumed.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009", "SRC-001" ] }, { "id": "de-employment-pattern", "name": "Employment pattern codes", "description": "Full-time or part-time and regular or temporary indicators attached to the seat, plus any probation period in days.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-004" ] } ], "artifacts": [ { "id": "position-capacity-authorization", "name": "Position capacity authorization", "description": "Approved record of FTE, headcount, type and overlap tolerance against which occupancy is validated.", "media_or_form": [ "structured authorization record", "establishment control listing" ], "serial": true, "identity_strategy": "Position identifier plus authorization effective-start date and approval instant; each change creates a new dated authorization.", "source_refs": [ "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "vacancy-and-occupancy-state", "name": "Vacancy and occupancy state", "description": "The derived state of the seat with respect to its holders: vacant, partly filled, fully filled or over-established, computed against authorized capacity.", "source_refs": [ "SRC-001", "SRC-009" ], "questions": [ { "id": "q-vac-1", "text": "Is the position vacant, and how is vacancy derived rather than asserted?", "kind": "state", "answer_data": [ "open FTE", "open headcount", "derivation as-of instant" ] }, { "id": "q-vac-2", "text": "Which assignments currently consume the capacity of this position?", "kind": "relationship", "answer_data": [ "assignment references", "consumed FTE per assignment", "occupancy window" ] }, { "id": "q-vac-3", "text": "What happens when an incoming holder would exceed authorized capacity?", "kind": "exception", "answer_data": [ "overlap allowed flag", "warning or block outcome", "override authority reference" ] }, { "id": "q-vac-4", "text": "How long has the position been vacant and does that trigger review or lapse?", "kind": "temporal", "answer_data": [ "vacancy start instant", "vacancy duration", "lapse or review trigger" ] } ], "data_elements": [ { "id": "de-open-capacity", "name": "Open capacity", "description": "Remaining unconsumed FTE and headcount at an as-of instant; the basis for incumbent validation.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-occupancy-links", "name": "Occupancy links", "description": "References to the assignment records that hold the post, corresponding to org:heldBy; the occupancy itself is owned by the assignment model.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-vacancy-since", "name": "Vacant since instant", "description": "RFC 3339 instant from which the seat has had unconsumed capacity, distinct from the ingestion instant of the computation.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013", "SRC-001" ] }, { "id": "de-overlap-outcome", "name": "Overlap validation outcome", "description": "Whether exceeding capacity produced a warning or a hard block, and who overrode it.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [], "inline_only_rationale": "Vacancy is a derived state, not a stored assertion: it is computed from authorized capacity in the position master record minus capacity consumed by assignment records owned by WM-ORG-016. Persisting it as an independent artifact would create a second, drift-prone source of truth; only the computation's as-of instant and inputs are recorded." } ] }, { "id": "funding-and-pay-framing", "name": "Funding and pay framing", "description": "The money attached to the seat: budget and funding source, and the pay range that must be disclosable at recruitment.", "source_refs": [ "SRC-009", "SRC-012", "SRC-004" ], "findings": [ { "id": "budget-and-funding-source", "name": "Budget and funding source", "description": "Whether the position is budgeted, what amount and currency it carries, and which funding source or existing position finances it.", "source_refs": [ "SRC-009" ], "questions": [ { "id": "q-bud-1", "text": "Is this position budgeted, and for what amount and currency in which fiscal period?", "kind": "requirement", "answer_data": [ "budgeted flag", "budget amount and currency", "fiscal period reference" ] }, { "id": "q-bud-2", "text": "Is the position funded by an existing position, a grant or a new allocation?", "kind": "provenance", "answer_data": [ "funding source type", "funding source reference", "funding end date" ] }, { "id": "q-bud-3", "text": "Who authorizes budget changes for the seat and what evidence is retained?", "kind": "authority", "answer_data": [ "budget authority reference", "authorization instant", "authorization document reference" ] }, { "id": "q-bud-4", "text": "What happens to the position when its funding lapses?", "kind": "lifecycle", "answer_data": [ "funding lapse action code", "grace period", "resulting position status" ] } ], "data_elements": [ { "id": "de-budgeted-flag", "name": "Budgeted indicator", "description": "Whether the seat is included in the approved establishment budget.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-budget-amount", "name": "Budget amount and currency", "description": "Monetary allocation attached to the position with an explicit currency code.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-funding-source", "name": "Funding source reference", "description": "Reference to the grant, cost centre or existing position that finances the seat, including the funded-by-existing-position case.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-funding-window", "name": "Funding validity window", "description": "Dates over which funding is committed, distinct from the position's own effective window.", "value_kind": "date", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "position-funding-authorization", "name": "Position funding authorization", "description": "Approval record committing budget to the seat for a defined period and source.", "media_or_form": [ "finance approval record", "establishment budget line", "structured funding record" ], "serial": true, "identity_strategy": "Position identifier plus fiscal period and approval instant; approvals are appended, never replaced.", "source_refs": [ "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "pay-range-and-transparency", "name": "Pay range and transparency obligations", "description": "The pay range or grade-derived pay framing of the seat and the disclosure duties that attach to it before employment and in periodic reporting.", "source_refs": [ "SRC-012", "SRC-004", "SRC-009" ], "questions": [ { "id": "q-pay-1", "text": "What initial pay level or range applies to this position and how was it derived?", "kind": "measurement", "answer_data": [ "pay range minimum and maximum", "currency and period", "derivation basis such as grade ladder" ] }, { "id": "q-pay-2", "text": "Must the pay range be disclosed to applicants before interview, and under which jurisdiction's rule?", "kind": "requirement", "answer_data": [ "disclosure obligation flag", "jurisdiction reference", "disclosure channel" ] }, { "id": "q-pay-3", "text": "To which category of workers is the position allocated for pay-gap reporting?", "kind": "classification", "answer_data": [ "worker category reference", "allocation rationale", "reporting period" ] }, { "id": "q-pay-4", "text": "Which pay-related fields are restricted from general read access and why?", "kind": "privacy", "answer_data": [ "restricted field list", "restriction basis", "approved reader roles" ] } ], "data_elements": [ { "id": "de-pay-range", "name": "Pay range", "description": "Initial pay level or range for the seat, disclosable prior to employment under the EU pay-transparency regime.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012", "SRC-004" ] }, { "id": "de-pay-derivation", "name": "Pay derivation basis", "description": "Link from the pay range to the grade ladder, entry grade and entry step or to an explicit market decision.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-disclosure-obligation", "name": "Disclosure obligation record", "description": "Jurisdiction-specific duty to publish the range in the vacancy notice or before interview, with its effective date.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "de-salary-history-ban", "name": "Salary-history prohibition flag", "description": "Whether asking applicants about pay history is prohibited for this seat's jurisdiction.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "pay-range-disclosure-record", "name": "Pay range disclosure record", "description": "Evidence of the range published or communicated for the seat, with channel, audience and instant, retained for pay-transparency enforcement.", "media_or_form": [ "published vacancy notice fragment", "structured disclosure record", "reporting extract" ], "serial": true, "identity_strategy": "Position identifier plus disclosure channel and RFC 3339 publication instant; superseded ranges retained for the statutory look-back.", "source_refs": [ "SRC-012", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "requirements-authority-and-risk", "name": "Requirements, authority and risk", "description": "What the seat demands of any holder, what it empowers the holder to do, and what risk and conditions it carries.", "rationale": "Requirements, delegated authority, prescribed regulatory responsibilities and risk designations are properties of the seat that must be determined before recruitment and survive turnover.", "source_refs": [ "SRC-014", "SRC-011", "SRC-010", "SRC-009" ], "layers": [ { "id": "requirements-and-competency", "name": "Requirements and competency", "description": "Essential functions with accommodation logic, and the competencies, credentials and experience the seat requires.", "source_refs": [ "SRC-014", "SRC-003", "SRC-006", "SRC-010", "SRC-002" ], "findings": [ { "id": "essential-functions-and-accommodation", "name": "Essential functions and accommodation", "description": "Which duties are fundamental to the position, the evidence supporting that determination, and how requirements are stated so that accommodation remains possible.", "source_refs": [ "SRC-014", "SRC-006" ], "questions": [ { "id": "q-ess-1", "text": "Which functions are essential and on which of the recognized factors does each determination rest?", "kind": "evidence", "answer_data": [ "essential function reference", "factor code such as reason-position-exists or specialization", "determination instant" ] }, { "id": "q-ess-2", "text": "Was the written description prepared before advertising or interviewing for the position?", "kind": "provenance", "answer_data": [ "description authored instant", "first advertisement instant", "precedence check outcome" ] }, { "id": "q-ess-3", "text": "What are the consequences if a holder does not perform the function?", "kind": "constraint", "answer_data": [ "consequence statement", "severity rating", "dependent process reference" ] }, { "id": "q-ess-4", "text": "Do collective agreement terms or incumbent work experience contradict the stated essential functions?", "kind": "exception", "answer_data": [ "collective agreement reference", "incumbent experience evidence", "conflict resolution note" ] } ], "data_elements": [ { "id": "de-essential-function", "name": "Essential function statement", "description": "Fundamental job duty of the position, distinguished from marginal duties.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "de-essentiality-factor", "name": "Essentiality factor code", "description": "Recognized basis: the position exists to perform the function, few employees are available to distribute it, or it is highly specialized.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "de-description-precedence", "name": "Description precedence evidence", "description": "Recorded authoring instant of the written description relative to advertising or interviewing, which determines its evidentiary weight.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-014", "SRC-013" ] }, { "id": "de-cba-reference", "name": "Collective agreement reference", "description": "Terms of any applicable collective bargaining agreement bearing on the duties of the seat.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] } ], "artifacts": [ { "id": "essential-functions-analysis", "name": "Essential functions analysis", "description": "Dated analysis recording each function, its essentiality factor, time share and consequence of non-performance.", "media_or_form": [ "analysis document", "structured function record set" ], "serial": true, "identity_strategy": "Position identifier plus analysis version and authoring instant; the pre-advertisement version is preserved as the evidentiary baseline.", "source_refs": [ "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "competency-and-credential-requirements", "name": "Competency, credential and experience requirements", "description": "Referenced skills, knowledge, qualifications, licences and experience the seat requires, expressed as versioned catalogue references rather than free text.", "source_refs": [ "SRC-003", "SRC-006", "SRC-010", "SRC-002", "SRC-004" ], "questions": [ { "id": "q-req-1", "text": "Which competencies are required versus preferred, and from which catalogue and version?", "kind": "requirement", "answer_data": [ "competency reference", "requirement strength code", "catalogue version" ] }, { "id": "q-req-2", "text": "Which licences, certifications or regulated qualifications must a holder possess before occupancy?", "kind": "constraint", "answer_data": [ "credential reference", "regulatory basis", "verification method" ] }, { "id": "q-req-3", "text": "What experience level and prior-role expectations apply, and how are they measured?", "kind": "measurement", "answer_data": [ "experience quantity and unit", "equivalence rule", "assessment method reference" ] }, { "id": "q-req-4", "text": "How are requirement sets kept aligned when the underlying catalogue is re-versioned?", "kind": "interoperability", "answer_data": [ "pinned catalogue version", "re-mapping decision", "re-mapping instant" ] } ], "data_elements": [ { "id": "de-competency-ref", "name": "Competency requirement reference", "description": "Scheme-qualified reference to a skill, knowledge or task statement, for example an ESCO essential skill or a NICE Knowledge/Skill statement.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-010" ] }, { "id": "de-requirement-strength", "name": "Requirement strength", "description": "Whether the competency is essential or optional for the seat.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "de-credential-req", "name": "Credential requirement", "description": "Licence, certification or regulated qualification with issuing body and any regulatory basis noted in occupational scope notes.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "de-experience-req", "name": "Experience requirement", "description": "Required prior experience expressed with quantity, unit and any equivalence rule, aligning with published experienceRequirements.", "value_kind": "quantity", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-004" ] } ], "artifacts": [ { "id": "position-competency-model", "name": "Position competency model", "description": "The collection of competency information associated with the position or job, exchangeable as an HR Open PositionCompetencyModel.", "media_or_form": [ "structured competency payload", "competency matrix", "catalogue-linked requirement set" ], "serial": true, "identity_strategy": "Position identifier plus competency-model version and the pinned catalogue scheme versions it references.", "source_refs": [ "SRC-002", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "authority-and-accountability", "name": "Authority and accountability", "description": "Decision rights delegated to the seat and externally prescribed responsibilities allocated to it.", "source_refs": [ "SRC-011", "SRC-007", "SRC-001" ], "findings": [ { "id": "delegated-authority-and-decision-rights", "name": "Delegated authority and decision rights", "description": "The approval limits, signing powers and decision scopes attached to the seat by competent authority, independent of who holds it.", "source_refs": [ "SRC-007", "SRC-001", "SRC-011" ], "questions": [ { "id": "q-aut-1", "text": "Which decisions may the holder of this position take, and up to what limit?", "kind": "authority", "answer_data": [ "decision scope reference", "monetary or scope limit", "limit currency or unit" ] }, { "id": "q-aut-2", "text": "Which competent authority conferred each delegation and when does it expire?", "kind": "provenance", "answer_data": [ "conferring authority reference", "conferral instant", "expiry or review date" ] }, { "id": "q-aut-3", "text": "Do the delegations lapse, transfer or escalate when the position is vacant?", "kind": "exception", "answer_data": [ "vacancy behaviour code", "escalation target position", "interim authority window" ] }, { "id": "q-aut-4", "text": "Does the position have sufficient seniority and resources to exercise its authority?", "kind": "validation", "answer_data": [ "seniority assessment outcome", "resource sufficiency evidence", "assessment date" ] } ], "data_elements": [ { "id": "de-decision-right", "name": "Decision right", "description": "A named authority conferred on the seat, with scope and any quantitative limit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-011" ] }, { "id": "de-conferring-authority", "name": "Conferring authority reference", "description": "The competent authority that assigned the work and its associated powers to the position.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-vacancy-authority-rule", "name": "Vacancy authority rule", "description": "What happens to each delegation while the seat is unoccupied: lapse, escalate to the reports-to post, or transfer to a delegate.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011", "SRC-009" ] } ], "artifacts": [ { "id": "delegation-of-authority-schedule", "name": "Delegation of authority schedule", "description": "Governed schedule mapping decision rights and limits to positions, with conferral and expiry dates.", "media_or_form": [ "authority matrix", "structured delegation record set", "approved schedule document" ], "serial": true, "identity_strategy": "Schedule identifier plus version and effective-start date; position-level entries keyed by position identifier.", "source_refs": [ "SRC-011", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "prescribed-regulatory-responsibilities", "name": "Prescribed regulatory responsibilities", "description": "Responsibilities that a regulator requires to be allocated to a designated senior position, together with the documentation that evidences allocation without gaps.", "source_refs": [ "SRC-011" ], "questions": [ { "id": "q-prs-1", "text": "Which prescribed regulatory responsibilities are allocated to this position?", "kind": "requirement", "answer_data": [ "prescribed responsibility identifier", "regulator reference", "allocation effective date" ] }, { "id": "q-prs-2", "text": "Is this position the most senior one responsible for the area, and is the allocation gap-free across the firm?", "kind": "validation", "answer_data": [ "seniority justification", "gap analysis outcome", "reviewer identity" ] }, { "id": "q-prs-3", "text": "Is the responsibility shared or split with other positions, and on what justification?", "kind": "composition", "answer_data": [ "co-holding position references", "split justification", "split effective window" ] }, { "id": "q-prs-4", "text": "Which statement of responsibilities and responsibilities map record this allocation?", "kind": "evidence", "answer_data": [ "statement reference", "responsibilities map reference", "submission instant" ] } ], "data_elements": [ { "id": "de-prescribed-responsibility", "name": "Prescribed responsibility allocation", "description": "Regulator-defined responsibility allocated to the designated function held through this position.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "de-regulated-function", "name": "Regulated function designation", "description": "The designated senior management or controlled function that this position corresponds to.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "de-allocation-justification", "name": "Allocation justification", "description": "Recorded reasoning that the holder is the most senior person responsible with sufficient resources and authority.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] } ], "artifacts": [ { "id": "statement-of-responsibilities", "name": "Statement of responsibilities and responsibilities map", "description": "Documents recording which responsibilities are allocated to which senior position and how governance responsibilities are distributed firm-wide.", "media_or_form": [ "regulatory submission document", "structured responsibility allocation record", "governance map" ], "serial": true, "identity_strategy": "Firm reference plus position identifier plus version and RFC 3339 effective instant; every reallocation produces a new version.", "source_refs": [ "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "risk-screening-and-conditions", "name": "Risk, screening and working conditions", "description": "Pre-occupancy screening and clearance demands, and the physical and environmental conditions of the seat.", "source_refs": [ "SRC-009", "SRC-011", "SRC-006", "SRC-012" ], "findings": [ { "id": "screening-clearance-and-approval", "name": "Screening, clearance and approval requirements", "description": "Requirements that must be satisfied about any prospective holder because of what the seat can access or decide, determined before recruitment begins.", "source_refs": [ "SRC-009", "SRC-011", "SRC-010" ], "questions": [ { "id": "q-scr-1", "text": "What clearance, vetting or background screening level does this position require?", "kind": "security", "answer_data": [ "clearance or screening level code", "issuing regime reference", "re-screening interval" ] }, { "id": "q-scr-2", "text": "Does occupancy require prior regulatory approval or fitness assessment of the individual?", "kind": "authority", "answer_data": [ "approval regime reference", "approval prerequisite flag", "approval evidence reference" ] }, { "id": "q-scr-3", "text": "Which systems, data classifications or facilities does the seat inherently access?", "kind": "access", "answer_data": [ "access entitlement reference", "data classification level", "entitlement review date" ] }, { "id": "q-scr-4", "text": "What happens if a holder's clearance or approval lapses while occupying the seat?", "kind": "exception", "answer_data": [ "lapse action code", "interim restriction", "notification target" ] } ], "data_elements": [ { "id": "de-clearance-req", "name": "Security clearance requirement", "description": "Clearance level attached to the position record and required of any holder.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] }, { "id": "de-approval-prerequisite", "name": "Regulatory approval prerequisite", "description": "Whether an individual must be approved by a regulator before holding the designated function of this seat.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "de-access-entitlement", "name": "Position-derived access entitlement", "description": "Entitlements provisioned because of the seat rather than the person, supporting role-based provisioning.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-010" ] }, { "id": "de-rescreening-interval", "name": "Re-screening interval", "description": "Period after which screening or clearance must be revalidated for the seat.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [ { "id": "position-risk-designation-record", "name": "Position risk and screening designation record", "description": "Dated designation of the risk, sensitivity and screening level of the seat, produced before recruitment and revisited on material change.", "media_or_form": [ "designation record", "structured risk assessment", "provisioning rule entry" ], "serial": true, "identity_strategy": "Position identifier plus designation version and RFC 3339 designation instant; prior designations retained for audit.", "source_refs": [ "SRC-009", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "working-conditions-and-hazard-profile", "name": "Working conditions and hazard profile", "description": "Physical demands, environmental conditions and hazards attributable to the seat, which also feed job evaluation as a recognized criterion.", "source_refs": [ "SRC-006", "SRC-012", "SRC-014" ], "questions": [ { "id": "q-cnd-1", "text": "What physical, environmental and contextual conditions characterize the work of this position?", "kind": "classification", "answer_data": [ "work context descriptor", "descriptor scheme reference", "observed or estimated flag" ] }, { "id": "q-cnd-2", "text": "Which hazards or exposures require controls or protective equipment for any holder?", "kind": "constraint", "answer_data": [ "hazard reference", "control measure", "control verification date" ] }, { "id": "q-cnd-3", "text": "How do working conditions enter the job evaluation that levels this position?", "kind": "measurement", "answer_data": [ "working-conditions criterion rating", "evaluation reference", "rating date" ] }, { "id": "q-cnd-4", "text": "Which physical demands are essential functions and which can be restructured?", "kind": "exception", "answer_data": [ "demand statement", "essentiality flag", "restructuring option" ] } ], "data_elements": [ { "id": "de-work-context", "name": "Work context descriptor", "description": "Environmental and contextual condition of the seat drawn from the occupational-requirements domain.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "de-hazard-control", "name": "Hazard and control record", "description": "Identified hazard with its required control or protective equipment for the seat.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "de-conditions-rating", "name": "Working conditions evaluation rating", "description": "Rating of working conditions as one of the four objective job-evaluation criteria.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "position-conditions-profile", "name": "Position working-conditions profile", "description": "Structured profile of physical demands, environmental context and hazard controls attributable to the seat.", "media_or_form": [ "structured context record", "hazard assessment document", "evaluation input sheet" ], "serial": true, "identity_strategy": "Position identifier plus assessment version and assessment instant; linked to the location profile because conditions are location-dependent.", "source_refs": [ "SRC-006", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-governance-and-recordkeeping", "name": "Lifecycle, governance and recordkeeping", "description": "How positions come into existence, change, are contested, and end, and how the record is kept and disposed of.", "rationale": "Classification actions have their own effective dates and appeal routes distinct from record timestamps; without effective-dated governance an agent cannot reconstruct what the seat was at a past date.", "source_refs": [ "SRC-008", "SRC-009", "SRC-007", "SRC-013" ], "layers": [ { "id": "lifecycle-and-effective-dating", "name": "Lifecycle and effective dating", "description": "Status transitions of the seat and the bitemporal discipline that separates business effect from record capture.", "source_refs": [ "SRC-009", "SRC-008", "SRC-013" ], "findings": [ { "id": "position-lifecycle-states", "name": "Position lifecycle states", "description": "The permitted status values of a seat — proposed, approved, frozen, active, inactive, abolished — and the transitions and authorities that move between them.", "source_refs": [ "SRC-009", "SRC-008" ], "questions": [ { "id": "q-lif-1", "text": "What is the current hiring status and activity status of the position, and are they independent?", "kind": "state", "answer_data": [ "hiring status code", "active status code", "status as-of date" ] }, { "id": "q-lif-2", "text": "Which transitions are permitted and who may authorize each one?", "kind": "lifecycle", "answer_data": [ "from and to status", "authorizing role", "transition precondition" ] }, { "id": "q-lif-3", "text": "May a position be frozen or abolished while occupied, and what must happen first?", "kind": "constraint", "answer_data": [ "occupancy precondition", "required prior action", "exception approval reference" ] }, { "id": "q-lif-4", "text": "Can an abolished position be reinstated, or must a new identity be minted?", "kind": "decision", "answer_data": [ "reinstatement policy code", "identity continuity rule", "precedent reference" ] } ], "data_elements": [ { "id": "de-hiring-status", "name": "Hiring status", "description": "Whether the seat is proposed, approved or frozen for staffing purposes.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "de-active-status", "name": "Active status", "description": "Whether the position record is active or inactive, held separately from hiring status.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "de-transition-authority", "name": "Transition authorization", "description": "Role and identity that authorized a status transition, with the authorization instant.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-007" ] }, { "id": "de-abolition-date", "name": "Abolition effective date", "description": "Business date on which the seat ceases to exist, distinct from the date the record was closed.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008", "SRC-013" ] } ], "artifacts": [ { "id": "position-status-decision", "name": "Position status decision record", "description": "Record of each establishment, approval, freeze, reinstatement or abolition decision with its authority and effective date.", "media_or_form": [ "decision record", "establishment action document", "structured status event" ], "serial": true, "identity_strategy": "Position identifier plus monotonically increasing decision sequence and RFC 3339 decision instant.", "source_refs": [ "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "effective-dated-change-and-history", "name": "Effective-dated change and history", "description": "Version history of the seat where every attribute set is bounded by effective dates and queryable as of a date, with record instants kept separate.", "source_refs": [ "SRC-009", "SRC-013", "SRC-008" ], "questions": [ { "id": "q-hst-1", "text": "What did this position look like as of a given effective date?", "kind": "temporal", "answer_data": [ "as-of date", "attribute snapshot", "version identifier" ] }, { "id": "q-hst-2", "text": "When was each version recorded, as distinct from when it took business effect?", "kind": "provenance", "answer_data": [ "effective start and end dates", "record creation instant", "last update instant" ] }, { "id": "q-hst-3", "text": "Is a change a correction of an erroneous record or a genuine change in the work?", "kind": "quality", "answer_data": [ "change type code", "reason code", "correcting actor identity" ] }, { "id": "q-hst-4", "text": "How are open-ended versions terminated and what end-date sentinel is used?", "kind": "constraint", "answer_data": [ "end-date sentinel value", "termination rule", "sentinel interpretation note" ] } ], "data_elements": [ { "id": "de-effective-window", "name": "Effective start and end dates", "description": "Business validity window of a version; production systems use a far-future sentinel for open-ended versions.", "value_kind": "date", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "de-record-instants", "name": "Record creation and update instants", "description": "RFC 3339 instants with explicit offsets recording when the version was captured and last modified.", "value_kind": "timestamp", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-009", "SRC-013" ] }, { "id": "de-change-type", "name": "Change type", "description": "Correction versus substantive change, which determines whether prior versions remain assertable.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-change-reason", "name": "Change reason code", "description": "Governed reason for the change, such as reorganization, reclassification, funding change or appeal outcome.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "position-change-history", "name": "Position change history", "description": "Append-only sequence of effective-dated versions and the record instants at which each was captured.", "media_or_form": [ "version history table", "event log", "as-of query result set" ], "serial": true, "identity_strategy": "Position identifier plus version sequence; each entry carries both its effective window and its RFC 3339 record instants.", "source_refs": [ "SRC-009", "SRC-013" ] } ], "inline_only_rationale": null } ] }, { "id": "governance-assurance-and-retention", "name": "Governance, assurance and retention", "description": "Who may establish and classify positions, how the description is kept accurate and contestable, and how records are retained and disposed of.", "source_refs": [ "SRC-007", "SRC-008", "SRC-011", "SRC-014" ], "findings": [ { "id": "establishment-and-classification-authority", "name": "Establishment and classification authority", "description": "The competent authority that assigns work to a seat and the separate authority that classifies it, including the split between local and central classification powers.", "source_refs": [ "SRC-007", "SRC-008", "SRC-011" ], "questions": [ { "id": "q-gov-1", "text": "Which competent authority assigned the duties to this position?", "kind": "authority", "answer_data": [ "assigning authority identity", "authority basis reference", "assignment instant" ] }, { "id": "q-gov-2", "text": "Who holds classification authority, and is it delegated or reserved centrally?", "kind": "ownership", "answer_data": [ "classification authority reference", "delegation scope", "reservation conditions" ] }, { "id": "q-gov-3", "text": "Which approvals are prerequisites before a proposed position can be approved?", "kind": "process", "answer_data": [ "approval step reference", "approver role", "approval instant" ] }, { "id": "q-gov-4", "text": "How are classification decisions kept consistent across comparable positions?", "kind": "validation", "answer_data": [ "consistency review method", "comparator position references", "review outcome" ] } ], "data_elements": [ { "id": "de-assigning-authority", "name": "Assigning competent authority", "description": "The authority whose assignment of duties and responsibilities constitutes the position.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-classification-authority", "name": "Classification authority", "description": "The party empowered to place the position in a class under the applicable classification plan.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "de-approval-chain", "name": "Approval chain record", "description": "Ordered approvals required to move the seat from proposed to approved.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-011" ] } ], "artifacts": [ { "id": "position-establishment-authorization", "name": "Position establishment authorization", "description": "Authorization instrument evidencing that competent authority created the seat and assigned its duties.", "media_or_form": [ "authorization document", "structured approval record", "establishment register entry" ], "serial": true, "identity_strategy": "Position identifier plus authorization instant and authorizing party reference.", "source_refs": [ "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "description-accuracy-certification-and-appeal", "name": "Description accuracy, certification and appeal", "description": "Keeping the position description accurate and current, certifying it, and the routes by which its classification can be challenged and redetermined.", "source_refs": [ "SRC-008", "SRC-007", "SRC-014" ], "questions": [ { "id": "q-acc-1", "text": "Who certified that the position description accurately states the assigned duties, and when?", "kind": "validation", "answer_data": [ "certifier identity and role", "certification instant", "certification scope" ] }, { "id": "q-acc-2", "text": "When was the description last reviewed and what interval or trigger governs review?", "kind": "lifecycle", "answer_data": [ "last review date", "review interval", "review trigger code" ] }, { "id": "q-acc-3", "text": "Who may appeal the classification of this position, and what is excluded from appeal?", "kind": "exception", "answer_data": [ "eligible appellant category", "excluded matter list", "appeal forum reference" ] }, { "id": "q-acc-4", "text": "From what date does a corrected classification take effect, and is it retroactive?", "kind": "temporal", "answer_data": [ "decision instant", "classification effective date", "retroactivity rule reference" ] } ], "data_elements": [ { "id": "de-certification", "name": "Description certification", "description": "Attestation by the responsible official that the description is accurate and current.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-014" ] }, { "id": "de-review-cycle", "name": "Review cycle", "description": "Interval or event trigger requiring re-examination of the description and its classification.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-appeal-record", "name": "Appeal record reference", "description": "Reference to a classification appeal, its forum and its outcome.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-classification-effective-date", "name": "Classification action effective date", "description": "Effective date of a classification action or decision, governed separately from the decision instant.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "classification-appeal-decision", "name": "Classification appeal decision", "description": "Decision resolving a challenge to the classification of the position, with its own effective date.", "media_or_form": [ "decision document", "structured appeal outcome record" ], "serial": true, "identity_strategy": "Appeal case identifier plus position identifier and decision instant; effective date recorded independently.", "source_refs": [ "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "retention-disposition-and-privacy", "name": "Retention, disposition and privacy boundary", "description": "How long position records and their evidentiary artifacts are kept, what must be preserved for statutory look-back, and where personal data of incumbents must be separated from the seat record.", "source_refs": [ "SRC-008", "SRC-011", "SRC-012", "SRC-001" ], "questions": [ { "id": "q-ret-1", "text": "What retention period applies to the position record, its descriptions and its decisions, and under which rule?", "kind": "retention", "answer_data": [ "retention period", "legal basis reference", "jurisdiction code" ] }, { "id": "q-ret-2", "text": "Which artifacts must be preserved beyond position abolition to support appeals, pay-gap reporting or regulatory maps?", "kind": "evidence", "answer_data": [ "artifact class", "preservation trigger", "minimum preservation window" ] }, { "id": "q-ret-3", "text": "Which fields carry personal data about incumbents and must be excluded from the seat record or minimized?", "kind": "privacy", "answer_data": [ "personal data field list", "minimization rule", "separation target model" ] }, { "id": "q-ret-4", "text": "What is the disposition action at end of retention: destruction, anonymization or transfer to archive?", "kind": "decision", "answer_data": [ "disposition action code", "approving role", "disposition instant" ] } ], "data_elements": [ { "id": "de-retention-rule", "name": "Retention rule reference", "description": "Governed retention rule applied to the position record class, with jurisdiction and legal basis.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008", "SRC-012" ] }, { "id": "de-preservation-hold", "name": "Preservation hold", "description": "Hold preventing disposition while an appeal, investigation or regulatory review is open.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008", "SRC-011" ] }, { "id": "de-personal-data-boundary", "name": "Personal data boundary marker", "description": "Marker identifying fields that reference identifiable incumbents and therefore belong to the assignment model rather than the seat.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-disposition-record", "name": "Disposition record", "description": "Recorded destruction, anonymization or archival transfer with actor and RFC 3339 instant.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] } ], "artifacts": [ { "id": "retention-schedule-entry", "name": "Retention and disposition schedule entry", "description": "Entry binding the position record class and its artifacts to a retention period, hold conditions and disposition action.", "media_or_form": [ "records schedule entry", "structured retention policy record" ], "serial": false, "identity_strategy": "Record class identifier plus schedule version; positions reference the schedule rather than carrying periods inline.", "source_refs": [ "SRC-008", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interoperability-measurement-and-evidence", "name": "Interoperability, measurement and evidence", "description": "How the position is expressed to the outside world, what is measured about it, and how the record's quality is evidenced.", "rationale": "Positions are consumed by recruiting, statistics, regulators and linked-data graphs; each consumer needs versioned crosswalks and provenance rather than reinterpretation of internal labels.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-001" ], "layers": [ { "id": "alignment-and-exchange", "name": "Alignment and exchange", "description": "Crosswalks to external classification schemes and the payloads by which position information leaves the model.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-010", "SRC-001" ], "findings": [ { "id": "crosswalks-and-alignment", "name": "Classification crosswalks and alignment", "description": "Declared mappings from the internal job and grade structure to external schemes, with mapping strength, version pinning and known conflicts recorded rather than asserted as conformance.", "source_refs": [ "SRC-005", "SRC-003", "SRC-006", "SRC-004", "SRC-010" ], "questions": [ { "id": "q-xwk-1", "text": "To which external schemes is this position mapped and at which level of each hierarchy?", "kind": "interoperability", "answer_data": [ "scheme identifier", "scheme version", "target code and level" ] }, { "id": "q-xwk-2", "text": "Is each mapping exact, broader, narrower or approximate?", "kind": "quality", "answer_data": [ "mapping strength code", "mapping rationale", "mapper identity" ] }, { "id": "q-xwk-3", "text": "Where do schemes disagree about this position, and how is the disagreement recorded?", "kind": "exception", "answer_data": [ "conflicting scheme pair", "conflict description", "resolution stance" ] }, { "id": "q-xwk-4", "text": "What evidence supports a claim of conformance to any external scheme?", "kind": "evidence", "answer_data": [ "conformance evidence reference", "assessment method", "assessment date" ] } ], "data_elements": [ { "id": "de-crosswalk-entry", "name": "Crosswalk entry", "description": "Mapping from the internal job or position to an external code, carrying scheme, version, level and strength.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-003" ] }, { "id": "de-scheme-version-pin", "name": "Scheme version pin", "description": "Exact version of each external scheme applied, since ESCO and occupational classifications are re-versioned over time.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] }, { "id": "de-conflict-note", "name": "Alignment conflict note", "description": "Recorded disagreement between schemes about the position, kept instead of silently choosing one.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-001" ] } ], "artifacts": [ { "id": "position-crosswalk-table", "name": "Position crosswalk table", "description": "Versioned mapping table from internal jobs and positions to ISCO-08, ESCO, O*NET-SOC, NICE work roles and internal categories of workers.", "media_or_form": [ "mapping table", "structured alignment record set", "published concordance" ], "serial": true, "identity_strategy": "Crosswalk identifier plus source-scheme and target-scheme versions and publication instant.", "source_refs": [ "SRC-005", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "exchange-payloads-and-publication", "name": "Exchange payloads and publication", "description": "The outbound projections of the position — organization chart exchange, provisioning payloads, published advertisements and linked-data graph nodes — and what each is permitted to expose.", "source_refs": [ "SRC-002", "SRC-004", "SRC-001", "SRC-009" ], "questions": [ { "id": "q-exc-1", "text": "Which outbound payloads carry this position and which fields does each include?", "kind": "interoperability", "answer_data": [ "payload type reference", "included field list", "recipient class" ] }, { "id": "q-exc-2", "text": "How does the published advertisement relate to the underlying position and its openings count?", "kind": "relationship", "answer_data": [ "position reference", "total openings value", "posting validity window" ] }, { "id": "q-exc-3", "text": "Which fields must be suppressed or generalized before external publication?", "kind": "access", "answer_data": [ "suppressed field list", "suppression basis", "approver role" ] }, { "id": "q-exc-4", "text": "How are downstream consumers notified when the position changes materially?", "kind": "event", "answer_data": [ "change event type", "notification channel", "emission instant" ] } ], "data_elements": [ { "id": "de-payload-profile", "name": "Exchange payload profile", "description": "Named outbound profile such as an organization-chart payload, a provisioning master-data payload or a public posting projection.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "de-openings-count", "name": "Total openings advertised", "description": "Number of openings published for the position, which may differ from authorized headcount.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-009" ] }, { "id": "de-publication-window", "name": "Publication window", "description": "Posting instant and validity end for any published projection, expressed as RFC 3339 values.", "value_kind": "timestamp", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-013" ] }, { "id": "de-change-event", "name": "Position change event", "description": "Emitted event describing a material change with its type and emission instant.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] } ], "artifacts": [ { "id": "position-exchange-payload", "name": "Position exchange payload", "description": "Serialized outbound projection of the position for a named recipient profile, format-neutral in semantics and format-specific only in encoding.", "media_or_form": [ "structured interchange payload", "published posting record", "graph serialization" ], "serial": true, "identity_strategy": "Position identifier plus payload profile name and RFC 3339 generation instant; content hash recorded for integrity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-001" ] } ], "inline_only_rationale": null }, { "id": "abstract-role-binding", "name": "Role or function of the post", "description": "Popolo: many people fulfil the role CEO, but only one holds the post CEO at a named organization. ORG org:role on a Post indicates the role any holder plays. schema.org roleName is the occupancy-side analogue and must not replace the Post.", "source_refs": [ "SRC-001", "SRC-015", "SRC-023" ], "questions": [ { "id": "abstract-role-binding-q01", "text": "What abstract role or function does any holder of this Position fulfil, and from which controlled vocabulary is it taken?", "kind": "classification", "answer_data": [ "role_ref", "role_label", "role_scheme_iri", "skos_concept_ref" ] }, { "id": "abstract-role-binding-q02", "text": "Is this organization using role-only memberships (for example club membership) for some relationships, and is this record still a true Position?", "kind": "definition", "answer_data": [ "post_required_flag", "membership_without_post_allowed", "profile_choice" ] }, { "id": "abstract-role-binding-q03", "text": "How is this Position’s role mapped to equivalent roles in other organizations for interoperability?", "kind": "interoperability", "answer_data": [ "role_mapping_collection", "target_role_ref", "mapping_authority" ] } ], "data_elements": [ { "id": "abstract-role-binding-data01", "name": "Abstract role reference", "description": "org:Role or equivalent SKOS concept the holder of the Position plays.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-015" ] }, { "id": "abstract-role-binding-data02", "name": "Role label", "description": "Lexical label of the function, used only when a Role resource is not yet minted.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-015" ] } ], "artifacts": [], "inline_only_rationale": "Role bindings are references into a role or SKOS scheme owned outside this model." }, { "id": "interoperability-profile-declaration", "name": "Profile and alignment choices", "description": "ORG says profiles may prefer Post or Membership. Popolo forbids org:holds and person-only holders. FHIR PractitionerRole is occupancy-leaning. schema.org Occupation is a profession. Conformance to any of these is claimed only when evidence of a chosen profile exists.", "source_refs": [ "SRC-001", "SRC-015", "SRC-019", "SRC-020" ], "questions": [ { "id": "interoperability-profile-declaration-q01", "text": "Which interoperability profile is in force for this Position (ORG-Post-first, Popolo-membership-mediated, FHIR-role, local-HR), and where is it documented?", "kind": "interoperability", "answer_data": [ "profile_id", "profile_url", "holds_property_allowed", "membership_required_for_occupancy" ] }, { "id": "interoperability-profile-declaration-q02", "text": "Which external identifiers or sameAs links assert equivalence to org:Post, Popolo Post, FHIR PractitionerRole or a local HRIS row, and are they same, close or related?", "kind": "interoperability", "answer_data": [ "same_as_links", "equivalence_relation", "conflicting_mapping_flag" ] }, { "id": "interoperability-profile-declaration-q03", "text": "Which known conflicts (direct holds versus membership; Post as Organization; PractitionerRole as assignment) are unresolved for this instance?", "kind": "decision", "answer_data": [ "unresolved_conflicts", "chosen_disambiguation", "review_state" ] } ], "data_elements": [ { "id": "interoperability-profile-declaration-data01", "name": "Interoperability profile", "description": "Chosen profile governing occupancy and typing rules.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-015" ] }, { "id": "interoperability-profile-declaration-data02", "name": "Same-as links", "description": "External identifiers and equivalence relations.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-019" ] }, { "id": "interoperability-profile-declaration-data03", "name": "Direct holds allowed", "description": "Whether org:holds/heldBy may be materialized; Popolo says they should not.", "value_kind": "boolean", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-015" ] } ], "artifacts": [ { "id": "interoperability-profile-declaration-artifact01", "name": "Interoperability profile declaration", "description": "Documented choice of ORG, Popolo, FHIR or local-HR profile for this Dimension’s Position records.", "media_or_form": [ "markdown", "html", "json", "turtle" ], "serial": true, "identity_strategy": "Profile IRI or Dimension profile id plus version; not a Position instance id.", "source_refs": [ "SRC-001", "SRC-015" ] } ], "inline_only_rationale": null } ] }, { "id": "measurement-and-evidence", "name": "Measurement and evidence", "description": "Metrics computed over positions and the provenance and quality controls that make the record trustworthy.", "source_refs": [ "SRC-009", "SRC-012", "SRC-006", "SRC-013" ], "findings": [ { "id": "position-metrics-and-reporting", "name": "Position-level metrics and reporting", "description": "Counts and rates that are only computable because positions exist as records — establishment, vacancy, time-to-fill, span of control, category-level pay gaps — with defined denominators and as-of dates.", "source_refs": [ "SRC-009", "SRC-012", "SRC-001" ], "questions": [ { "id": "q-met-1", "text": "Which metrics are computed over positions and what is the exact denominator of each?", "kind": "measurement", "answer_data": [ "metric identifier", "denominator definition", "computation as-of date" ] }, { "id": "q-met-2", "text": "Is a metric counted in FTE, headcount or authorized establishment, and are these reconciled?", "kind": "validation", "answer_data": [ "unit of count", "reconciliation rule", "variance tolerance" ] }, { "id": "q-met-3", "text": "Which reporting obligations require aggregation by category of workers rather than by unit?", "kind": "requirement", "answer_data": [ "obligation reference", "aggregation key", "reporting period" ] }, { "id": "q-met-4", "text": "How are frozen, proposed and unbudgeted positions treated in establishment counts?", "kind": "exception", "answer_data": [ "inclusion rule per status", "exclusion rationale", "rule version" ] } ], "data_elements": [ { "id": "de-metric-definition", "name": "Metric definition reference", "description": "Governed definition of a position-level metric including its numerator, denominator and unit.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-012" ] }, { "id": "de-metric-asof", "name": "Metric as-of date", "description": "Effective date at which the position population was evaluated, distinct from the computation instant.", "value_kind": "date", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-013" ] }, { "id": "de-aggregation-key", "name": "Aggregation key", "description": "Grouping used for reporting, such as category of workers, unit, grade or occupational code.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "position-metrics-extract", "name": "Position metrics extract", "description": "Reproducible extract of position-population metrics with pinned definitions, as-of date and computation instant.", "media_or_form": [ "structured metrics dataset", "reporting submission extract" ], "serial": true, "identity_strategy": "Metric set identifier plus as-of date and computation instant; definitions pinned by version so figures remain reproducible.", "source_refs": [ "SRC-009", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "evidence-provenance-and-quality", "name": "Evidence, provenance and data quality", "description": "Where each assertion about the position came from, how confident it is, and which validations must pass before the record is treated as authoritative.", "source_refs": [ "SRC-013", "SRC-008", "SRC-014", "SRC-009" ], "questions": [ { "id": "q-evd-1", "text": "For each material assertion, which source system, document or decision is its provenance?", "kind": "provenance", "answer_data": [ "assertion reference", "source reference", "observation or ingestion instant" ] }, { "id": "q-evd-2", "text": "Which validations must pass before a position is publishable or staffable?", "kind": "validation", "answer_data": [ "validation rule identifier", "severity", "last execution instant" ] }, { "id": "q-evd-3", "text": "How is a disputed or low-confidence attribute flagged rather than silently corrected?", "kind": "quality", "answer_data": [ "confidence level", "dispute marker", "resolution owner" ] }, { "id": "q-evd-4", "text": "How are conflicting assertions between the master system and downstream copies reconciled?", "kind": "exception", "answer_data": [ "conflict detection rule", "authoritative source precedence", "reconciliation instant" ] } ], "data_elements": [ { "id": "de-assertion-provenance", "name": "Assertion provenance", "description": "Source reference and observation or ingestion instant for an individual attribute value, separate from its business effective date.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013", "SRC-009" ] }, { "id": "de-validation-result", "name": "Validation result", "description": "Outcome of a named validation rule with severity and execution instant.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-008" ] }, { "id": "de-confidence", "name": "Confidence marker", "description": "Declared confidence in an attribute, used where evidence is indirect or contested.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-014" ] }, { "id": "de-integrity-hash", "name": "Artifact integrity hash", "description": "Content hash over the canonical serialization of an artifact, enabling detection of drift between copies.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] } ], "artifacts": [ { "id": "position-evidence-ledger", "name": "Position evidence ledger", "description": "Append-only ledger of assertions, their sources, validation outcomes and integrity hashes for the position record and its artifacts.", "media_or_form": [ "append-only ledger", "audit log", "structured provenance record set" ], "serial": true, "identity_strategy": "Position identifier plus ledger entry sequence and RFC 3339 entry instant; entries are immutable and superseded only by later entries.", "source_refs": [ "SRC-013", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "establish-position", "name": "Establish position", "description": "Create a new seat by recording the duties assigned by competent authority, mint its identifier and place it in a unit.", "inputs": [ "assigned duty statements", "holding unit and business unit references", "assigning authority reference", "proposed effective date" ], "outputs": [ "position master record in proposed status", "minted position identifier", "establishment authorization artifact" ], "preconditions": [ "competent authority has assigned the duties", "holding unit exists and is active", "identifier namespace is declared by the owner package" ], "effects": [ "a new position identity exists and is addressable", "hiring status is set to proposed", "an establishment decision is appended to the change history" ], "source_refs": [ "SRC-007", "SRC-009", "SRC-001" ] }, { "id": "classify-position", "name": "Classify position", "description": "Analyse the assigned duties and place the position in an internal class and one or more external occupational codes.", "inputs": [ "position description", "classification plan or job catalogue reference", "external scheme versions" ], "outputs": [ "job or class assignment", "occupation code assertions with scheme and version", "classification evaluation record" ], "preconditions": [ "a current position description exists", "the classifier holds classification authority", "scheme versions are pinned" ], "effects": [ "position becomes comparable across statistics and systems", "classification effective date is recorded separately from the decision instant" ], "source_refs": [ "SRC-007", "SRC-008", "SRC-005", "SRC-003" ] }, { "id": "evaluate-and-level-position", "name": "Evaluate and level position", "description": "Apply objective, gender-neutral evaluation criteria to assign a grade and allocate the position to a category of workers.", "inputs": [ "duty and responsibility set", "working-conditions profile", "evaluation scheme reference" ], "outputs": [ "grade or level assignment", "criterion ratings", "category of workers allocation", "job evaluation statement" ], "preconditions": [ "evaluation scheme is documented as objective and gender-neutral", "skills, effort, responsibility and working conditions are all assessable" ], "effects": [ "position is levelled and comparable for equal-value analysis", "pay range derivation basis becomes available" ], "source_refs": [ "SRC-012", "SRC-007", "SRC-009" ] }, { "id": "set-capacity-and-funding", "name": "Set capacity and funding", "description": "Authorize FTE, headcount, position type and overlap tolerance, and bind the seat to a budget and funding source.", "inputs": [ "requested FTE and headcount", "position type", "budget amount, currency and fiscal period", "funding source reference" ], "outputs": [ "capacity authorization artifact", "funding authorization artifact", "updated position master record" ], "preconditions": [ "budget authority approval is present", "capacity values are internally consistent" ], "effects": [ "occupancy validation gains an enforceable ceiling", "establishment and budget reporting can include the seat" ], "source_refs": [ "SRC-009" ] }, { "id": "specify-requirements", "name": "Specify requirements and essential functions", "description": "Record essential and marginal functions, competencies, credentials and experience required of any holder, using versioned catalogue references.", "inputs": [ "duty statements with time shares", "competency catalogue references", "credential and experience requirements" ], "outputs": [ "essential functions analysis", "position competency model", "requirement strength assignments" ], "preconditions": [ "duties are decomposed at task granularity", "catalogue versions are pinned", "analysis is authored before advertising or interviewing" ], "effects": [ "requirements become auditable evidence for selection and accommodation decisions" ], "source_refs": [ "SRC-014", "SRC-010", "SRC-003", "SRC-002" ] }, { "id": "allocate-authority-and-responsibilities", "name": "Allocate authority and prescribed responsibilities", "description": "Confer decision rights on the seat and allocate any regulator-prescribed responsibilities to it without leaving gaps.", "inputs": [ "decision scopes and limits", "prescribed responsibility list", "seniority and resource assessment" ], "outputs": [ "delegation of authority schedule entries", "statement of responsibilities", "responsibilities map update" ], "preconditions": [ "the position is sufficiently senior for the responsibilities", "gap analysis across the firm has been performed" ], "effects": [ "accountability is attributable to a designated seat independent of turnover", "vacancy behaviour for each delegation is defined" ], "source_refs": [ "SRC-011", "SRC-007" ] }, { "id": "designate-risk-and-screening", "name": "Designate risk and screening requirements", "description": "Determine the clearance, vetting, regulatory approval and access requirements that attach to the seat before recruitment starts.", "inputs": [ "access entitlements implied by the duties", "applicable screening regime", "regulatory approval regime" ], "outputs": [ "position risk and screening designation record", "re-screening interval", "approval prerequisite flag" ], "preconditions": [ "duties and access entitlements are known", "the applicable regime is identified for the seat's jurisdiction" ], "effects": [ "recruitment and provisioning can enforce prerequisites", "lapse handling rules become executable" ], "source_refs": [ "SRC-009", "SRC-011", "SRC-010" ] }, { "id": "reconcile-occupancy-and-vacancy", "name": "Reconcile occupancy and vacancy", "description": "Compute consumed and open capacity from assignment records and validate incoming occupancy against the authorization.", "inputs": [ "authorized FTE and headcount", "overlap allowed flag", "current assignment references and consumed capacity", "as-of instant" ], "outputs": [ "open FTE and open headcount", "vacancy state and vacant-since instant", "overlap validation outcome" ], "preconditions": [ "assignment records are readable from the occupancy model", "capacity authorization is current at the as-of date" ], "effects": [ "vacancy is derived rather than asserted", "capacity breaches are warned or blocked per the overlap flag" ], "source_refs": [ "SRC-009", "SRC-001" ] }, { "id": "amend-or-reclassify-position", "name": "Amend or reclassify position", "description": "Apply an effective-dated change to duties, placement, capacity or classification, distinguishing correction from substantive change.", "inputs": [ "proposed attribute changes", "effective date", "change type and reason code", "authorizing party" ], "outputs": [ "new effective-dated version", "updated change history entry", "re-issued description or evaluation where triggered" ], "preconditions": [ "authorizing party holds the relevant authority", "effective date does not silently overwrite prior versions" ], "effects": [ "prior versions remain queryable as of their effective windows", "dependent artifacts are flagged for review" ], "source_refs": [ "SRC-009", "SRC-008", "SRC-013" ] }, { "id": "certify-and-appeal", "name": "Certify description and process appeals", "description": "Certify the accuracy of the position description and administer challenges to its classification, applying decision effective dates.", "inputs": [ "current position description", "certifier identity and role", "appeal submission where present" ], "outputs": [ "certification record", "classification appeal decision", "corrected classification with its effective date" ], "preconditions": [ "the description states the duties actually assigned", "the appellant and the matter are within scope of appeal" ], "effects": [ "the record becomes evidentiary", "corrected classifications take effect on their own governed date" ], "source_refs": [ "SRC-007", "SRC-008", "SRC-014" ] }, { "id": "publish-position-projection", "name": "Publish position projection", "description": "Generate an outbound projection of the position for a named recipient profile, applying suppression rules and disclosure duties.", "inputs": [ "position master record", "payload profile name", "jurisdictional disclosure obligations", "suppression rules" ], "outputs": [ "position exchange payload", "pay range disclosure record where required", "publication window values" ], "preconditions": [ "position is in an approved status for staffing projections", "required pay-range disclosure has been determined for the jurisdiction" ], "effects": [ "downstream systems and the public receive a governed subset", "disclosure evidence is retained" ], "source_refs": [ "SRC-002", "SRC-004", "SRC-012" ] }, { "id": "freeze-abolish-or-dispose", "name": "Freeze, abolish or dispose position", "description": "Move the seat to frozen or abolished status and, at the end of retention, apply the governed disposition action to its records.", "inputs": [ "target status and effective date", "occupancy state", "retention rule and hold status", "disposition action" ], "outputs": [ "position status decision record", "closed effective windows", "disposition record" ], "preconditions": [ "occupancy preconditions are satisfied or explicitly overridden", "no preservation hold is active before disposition" ], "effects": [ "the seat stops consuming establishment and budget", "history is preserved until retention expiry, then disposed with an auditable record" ], "source_refs": [ "SRC-009", "SRC-008", "SRC-011" ] }, { "id": "authorize-fill", "name": "Authorize fill or freeze", "description": "Permit or withhold recruitment against a vacant Position, producing a fill-authorization that a JobPosting or requisition may reference.", "inputs": [ "Position id", "occupancy state", "freeze or fill decision", "deciding authority" ], "outputs": [ "freeze flag or fill-authorization id", "decision timestamps" ], "preconditions": [ "Position is established and not abolished.", "Classification and PD are adequate if the local regime requires them before advertisement." ], "effects": [ "A JobPosting may be linked as an advertisement of this vacancy; the posting is not the Position.", "Freeze withholds fill without abolishing the slot." ], "source_refs": [ "SRC-020", "SRC-022", "SRC-025" ] } ], "composition": [ { "target": "WM-ORG-002 Organizational unit", "relation": "CHILD", "purpose": "Every position is contained in exactly one organizational unit at a given effective date, matching org:postIn / org:hasPost and the mandatory department reference in production position records.", "required": true, "source_refs": [ "SRC-001", "SRC-009" ] }, { "target": "WM-ORG-003 Team", "relation": "REFERENCE", "purpose": "Teams are composed through positions and their assignments; positions remain reusable across team formations and are referenced, not owned, by the team model.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-ORG-016 Assignment / occupancy", "relation": "COMPOSE", "purpose": "A position is occupied through a scoped assignment; occupancy, tenure and incumbent-specific terms live there, mirroring the org:Post versus org:Membership separation, and supply the consumed capacity used to derive vacancy.", "required": true, "source_refs": [ "SRC-001", "SRC-009" ] }, { "target": "Job / class / occupation classifier model (sibling; registry entry not yet identified)", "relation": "REFERENCE", "purpose": "The class grouping similar positions and the occupational category are external classifier concepts; the position holds only coded references, not the class definitions or hierarchies.", "required": true, "source_refs": [ "SRC-007", "SRC-005" ] }, { "target": "Person / worker identity model (sibling; registry entry not yet identified)", "relation": "REFERENCE", "purpose": "Incumbents are referenced only indirectly through assignments so that the position record carries no personal data of its own.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "ISCO-08 (International Standard Classification of Occupations)", "relation": "ALIGN", "purpose": "Alignment target for occupational coding and for the job-versus-occupation distinction; mapping strength and version are recorded and conformance is not claimed without assessment evidence.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "ESCO occupations pillar", "relation": "ALIGN", "purpose": "Alignment target for multilingual labels, scope notes, regulatory aspects and essential or optional skills at ISCO level 5 and below.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "O*NET Content Model", "relation": "ALIGN", "purpose": "Alignment target for duty decomposition into work activities, for requirement typing and for environmental work-context descriptors.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "W3C Organization Ontology (org:Post)", "relation": "ALIGN", "purpose": "Ontological alignment for publishing positions as graph nodes with postIn, heldBy and reportsTo edges, and for the vacancy-independent semantics of a post.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "HR Open Standards 4.5 (OrganizationChart, PositionOpening, PositionCompetencyModel, HRMasterData)", "relation": "ALIGN", "purpose": "Exchange alignment for organizational structure, recruiting projections, competency models and provisioning payloads.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "schema.org JobPosting", "relation": "ALIGN", "purpose": "Publication alignment for the advertisement projection only; the posting is a time-bounded document about the position, not the position itself.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "NICE Workforce Framework work roles (NIST SP 800-181 Rev.1)", "relation": "ALIGN", "purpose": "Alignment for composing Task, Knowledge and Skill statements into reusable requirement sets that organizations map onto positions.", "required": false, "source_refs": [ "SRC-010" ] }, { "target": "Effective-dated versioning and provenance mixin", "relation": "MIX-IN", "purpose": "Supplies the bitemporal pattern separating business effective windows from RFC 3339 record and observation instants, reused by every attribute group in this model.", "required": true, "source_refs": [ "SRC-009", "SRC-013" ] }, { "target": "Regulated-firm accountability extension (SM&CR-style designated functions)", "relation": "EXTEND", "purpose": "Adds prescribed responsibility allocation, statements of responsibilities and responsibilities maps for positions in regulated firms without imposing them on all adopters.", "required": false, "source_refs": [ "SRC-011" ] }, { "target": "Statutory position-classification extension (General Schedule style)", "relation": "EXTEND", "purpose": "Adds statutory class, grade, official position description certification, classification appeal and effective-date rules for public-sector adopters bound by such a plan.", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "The adopting Dimension must name one owner package that is master for position identity, declare the master system of record, and state whether position codes are unique globally or only within a business unit.", "The owner package must publish who holds establishment authority, who holds classification authority and which approvals gate the proposed-to-approved transition, since the definition of a position depends on assignment by competent authority.", "The owner package must register every external scheme it maps to, pin the scheme version in use, and maintain the crosswalk table with mapping strength and recorded conflicts.", "The owner package must declare the retention and disposition schedule for position records and artifacts, and the personal-data boundary that keeps incumbent data in the assignment model." ], "namespace_guidance": "Use one namespace per Dimension and per master system, for example vr:wm-org-004/{dimension}/{master-system}/position/{position-key}. Publish a resolvable IRI per position when the organization graph is exposed, typed as org:Post. Never encode title, grade, unit or date into the identifier, because all four are effective-dated and mutable; codes may appear in a separate human-facing position code field whose uniqueness scope is declared.", "registry_links": [ "vr.wm-org-004 (this entry; nav path NAV.SOC.ORG.POS)", "planning/VERCY-MODEL-RELATIONS.csv for CONTAINS from WM-ORG-002, COMPOSE from WM-ORG-003 and COMPOSE to WM-ORG-016", "External registries referenced by pinned version: ISCO-08, ESCO occupations, O*NET-SOC, NICE work roles, HR Open Standards 4.5" ] }, "canon_and_patch": { "canonicalization_rules": [ "The canonical form is a format-neutral record; JSON, YAML, Markdown, HTML, Git, MCP and MongoDB are encodings that must round-trip the same canonical content.", "Every coded value is stored as a scheme, version and code triple; a bare label is never canonical and never sufficient for a classification assertion.", "Every label carries a language tag; the official title is distinguished from working and alternative labels by an explicit label role.", "All instants are RFC 3339 with seconds and an explicit offset or Z; business effective dates may be full-date values and are held in fields distinct from record instants.", "Collections are ordered deterministically by a stable key so that content hashes are reproducible across systems." ], "patch_rules": [ "Changes to duty content, classification, grade, capacity, funding or authority create a new effective-dated version; in-place mutation of a closed version is prohibited.", "Every patch declares its effective date, its change type as correction or substantive change, a governed reason code and the authorizing party.", "Corrections restate what the record should always have said and must preserve the erroneous version with a superseding marker; substantive changes open a new business validity window.", "Deletion of history is prohibited; a position is ended by closing its effective window and recording an abolition decision, and records leave only through governed disposition at retention expiry.", "A patch that changes classification must carry the classification action effective date separately from the decision instant, since the two are governed differently." ], "compatibility_rules": [ "Adding optional attributes or new crosswalk entries is a minor change; changing identity semantics, uniqueness scope, capacity units or a pinned scheme version is breaking.", "Consumers must tolerate unknown codes and unknown optional fields rather than rejecting the record.", "Re-versioning an external scheme requires an explicit re-mapping decision with its own instant; silent code carry-over across scheme versions is prohibited.", "Derived values such as vacancy state must never be treated as stable inputs by consumers; they are valid only for the as-of instant at which they were computed." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system position identifier assigned by the HRIS or position-control system of record.", "Governed global identifier or resolvable IRI, such as the org:Post IRI published in the organization graph.", "UUID or ULID minted by the adopting Dimension only where no upstream authoritative identifier exists, recorded together with the reason no upstream key was available.", "Never an identifier: official or working title, grade, unit, cost centre, incumbent name, or any date." ], "timestamp_rule": "All instants use RFC 3339 date-time with seconds and an explicit offset or Z, per the Internet date/time profile of ISO 8601; -00:00 is used only for the unknown-local-offset case and is not equivalent to Z. Event time, business effective date and observation or ingestion instant are recorded in separate fields and never conflated.", "serial_naming_rule": "Serial artifacts are named wm-org-004--{dimension}--{position-key}--{artifact-kind}--{effective-or-instant}--v{n}, lower-kebab-case throughout, with the instant in RFC 3339 basic-safe form so that lexical order equals chronological order. Version numbers increase monotonically and are never reused after disposition.", "integrity_rule": "Each serial artifact records a content hash over its canonical serialization plus the identity of the certifying or authorizing party. Certified position descriptions, evaluation statements, statements of responsibilities and appeal decisions are immutable once certified; any change produces a new version that references the hash of the version it supersedes." }, "policies": [ "Position records must remain occupant-free: no attribute of a position may identify a natural person, because a post exists independently of the person or persons filling it and occupancy belongs to the assignment model.", "Single occupancy must never be assumed. Concurrency is governed explicitly by position type, headcount and the overlap-allowed flag, since both the ontology and production systems permit a post to be held by more than one holder.", "A position may not be advertised or staffed until its classification, requirements, risk and screening designation and any pay-range disclosure duty have been determined and recorded.", "External standards are alignments, not conformance claims; a conformance assertion requires named assessment evidence with a method and date, and unresolved disagreements between schemes are recorded rather than silently resolved.", "Derived state such as vacancy is computed, timestamped and never persisted as an independent assertion that could diverge from its inputs.", "Classification, grade, pay-range and risk-designation fields are governed reads: access is role-scoped and every read of pay or sensitivity data is logged.", "A Position may be created, classified, frozen, published and abolished without an occupant.", "Occupant personal data, actual salary and tenure live on assignment records; access and retention of those fields follow privacy law, not the PD schedule.", "Public official Posts may publish label, organization, area and vacancy while withholding HR evaluation content.", "Reclassification, abolishment and fill-freeze are privileged operations with named competent authorities and audit." ], "crud": { "read": [ "Read a position as of a business effective date, returning the version whose effective window contains that date together with its record instants.", "Read the change history of a position, including superseded versions, change types and reason codes.", "Read derived occupancy and open capacity for an as-of instant, with the assignment references that were consulted.", "Read outbound projections filtered by payload profile and by the suppression rules applicable to the recipient class." ], "create": [ "Create a position only through the establish function, with duties assigned by a named competent authority and a holding unit reference present.", "Mint the identifier under the owner package namespace following the identity priority order and record the assignment instant.", "Create derived artifacts such as evaluation statements, designations and certifications as new serial versions, never as edits." ], "update": [ "Update only by appending a new effective-dated version carrying effective date, change type, reason code and authorizing party.", "Update classification only through the classification authority, recording the classification action effective date separately from the decision instant.", "Update capacity or funding only with the corresponding authorization artifact present.", "Reject updates that would place personal data of an incumbent on the position record." ], "delete": [ "Hard deletion of position records or their history is prohibited while any retention period or preservation hold applies.", "End a position by closing its effective window and recording an abolition decision with its effective date; the identifier is retired and not reused.", "Dispose records only at retention expiry, by the governed disposition action, with an auditable disposition record naming the approving role and the RFC 3339 instant.", "Erasure requests concerning a person are satisfied in the assignment or worker model, not by deleting the position." ] }, "roles": [ { "name": "Position owner (competent authority)", "responsibilities": [ "Assign and revise the duties and responsibilities that constitute the position", "Authorize establishment, freeze, reinstatement and abolition decisions", "Certify that the position description states the duties actually assigned" ] }, { "name": "Classification and evaluation authority", "responsibilities": [ "Place the position in a class and assign occupational codes with pinned scheme versions", "Apply objective, gender-neutral evaluation criteria and record criterion ratings", "Maintain consistency across comparable positions and administer redetermination after appeals" ] }, { "name": "Position control and budget steward", "responsibilities": [ "Authorize FTE, headcount, position type and overlap tolerance", "Bind the seat to budget and funding source and manage funding lapse handling", "Reconcile establishment counts, open capacity and budget reporting" ] }, { "name": "Model data steward", "responsibilities": [ "Own the identifier namespace, uniqueness scope and crosswalk tables", "Enforce canonicalization, patch and retention rules and run validation suites", "Maintain the evidence ledger, integrity hashes and conflict records" ] }, { "name": "Compliance and regulatory officer", "responsibilities": [ "Allocate prescribed responsibilities without gaps and maintain statements of responsibilities and the responsibilities map", "Determine risk, screening, clearance and approval prerequisites for the seat", "Determine jurisdictional pay-transparency and reporting duties and retain disclosure evidence" ] }, { "name": "Consuming agent", "responsibilities": [ "Read positions as of a stated effective date and honour pinned scheme versions", "Treat derived state as valid only for its as-of instant and tolerate unknown codes and optional fields", "Never infer classification, exemption status or authority from a title alone" ] } ], "access": { "default_rule": "Position structural data is internal to the organization by default and readable by authenticated organizational agents at bundle and layer scope; pay, evaluation, risk, screening and authority data are restricted to named roles, and no scope grants access to identifiable incumbent data, which is governed by the assignment model.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Published vacancy projections are public for their publication window and expose only the fields permitted by the payload profile.", "Pay range must be disclosed to applicants prior to employment where the jurisdiction requires it, overriding the default restriction on pay data for that audience and purpose.", "Aggregate pay information by category of workers is disclosable to workers and to regulators under pay-transparency and reporting duties, in aggregate form only.", "Statements of responsibilities and responsibilities maps are disclosable to the relevant regulator on request, including superseded versions.", "Risk, sensitivity and clearance designations are restricted to compliance, security and staffing roles and are excluded from public and general internal projections.", "Preservation holds override retention-driven disposition and suspend deletion until the hold is lifted.", "Public-office transparency for elected or gazette Posts.", "Named audit or legal-hold access to historical PDs.", "Emergency fill against a vacant essential Position under recorded authority.", "Unnamed FHIR-style clinical slots may expose service and location without a person." ], "audit_requirements": [ "Log every classification, evaluation, capacity, funding, authority and status decision with the actor identity, the decision instant in RFC 3339 and the separately recorded effective date.", "Log every read of pay-range, evaluation-criterion, risk-designation and screening fields with the reader identity, purpose and instant.", "Log every outbound projection with its payload profile, recipient class, suppression rules applied, content hash and generation instant.", "Log overlap and capacity-validation outcomes, including warnings, blocks and any override with the overriding authority.", "Log disposition actions and preservation holds with approving role and instant, and retain the log beyond the disposition of the records it describes.", "Record who classified, certified, froze, authorized fill, abolished or hard-deleted a Position, with event time and ingestion time.", "Record access to occupant-derived views and to sensitivity-coded Positions.", "Retain audit independently of occupant PII deletion." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Model ID", "Registry ID", "Identity and namespace rules URL", "Access policy URL", "Retention and disposition schedule URL", "Crosswalk and scheme version pin URL" ], "read_order": [ "AGENTS.md — resolve Name, Type, Model ID and Registry ID, then the Specification URL", "Specification URL — scope, boundaries and the Bundle to Layer to Finding to Question structure before any read or write", "Identity and namespace rules URL — identifier priority, uniqueness scope and timestamp rules before minting or matching any position", "Storage type URL — how the format-neutral canonical record is projected into the storage in use, including effective-dated query semantics", "Interface URL — read, create, update and delete operations, as-of query parameters and change-event emission", "Processes URL — establishment, classification, evaluation, capacity, authority, designation, projection and disposition procedures with their required authorities", "Access policy URL and Retention and disposition schedule URL — scopes, exceptions, audit duties and disposition actions before exporting or deleting anything" ] } }, "coverage": { "claim": "Covers the position as an occupant-independent work-slot: identity and keys, official and working titles, assigned duty content and essential functions, occupational classification and grade evaluation, unit/cost-centre placement and post-to-post reporting, work location plus geographic area or constituency, capacity and derived vacancy, funding and pay framing, requirements, delegated and prescribed authority, risk and screening, working conditions, lifecycle and effective-dated change, governance, evidence, and interoperability including declared profile choice and abstract-role binding. Evidence is the fourteen base sources plus grok-sourced Popolo, HL7 FHIR and schema.org Occupation/EmployeeRole references. No claim of universal completeness: occupancy, employment contract, payroll, recruiting workflow and the referenced taxonomies are owned elsewhere, and retention periods, unpaid/honorary posts, military billets, academic lines and most non-US civil-service regimes remain declared gaps.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Master-system identifier, scoped position code, published IRI and external identifier set, with an explicit rule that title, grade, unit and date are never identifiers. Grounded in org:Post and in production position-record keys where PositionCode is unique only within a business unit." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposed, approved, frozen, active, inactive and abolished states with transition authorities, occupancy preconditions and a reinstatement-versus-new-identity decision. Hiring status and activity status are modelled as independent, following observed production semantics." }, { "dimension": "relationships", "status": "covered", "notes": "Containment in a unit (org:postIn), post-to-post reporting (org:reportsTo), delegate positions, occupancy links to assignments (org:heldBy), equal-value peer groups and team references. Reporting is deliberately modelled post-to-post so it survives turnover." }, { "dimension": "temporal", "status": "covered", "notes": "Bitemporal discipline throughout: effective windows for business validity, RFC 3339 instants with explicit offsets for record and observation time, separate classification-action effective dates, publication windows, vacancy-since instants and metric as-of dates." }, { "dimension": "provenance", "status": "covered", "notes": "Per-assertion source references with observation or ingestion instants, an append-only evidence ledger, description-precedence evidence relative to advertising, and content hashes over canonical serializations." }, { "dimension": "ownership", "status": "covered", "notes": "Distinguishes assigning competent authority, classification authority, holding unit, business unit, legal entity, cost centre and funding source, and requires the adopting Dimension to name one owner package and master system." }, { "dimension": "validation", "status": "covered", "notes": "Capacity and overlap validation, gap analysis for prescribed responsibilities, gender-neutrality checks on titles and evaluation systems, description certification, consistency review across comparable positions and named validation rules with severity and execution instants." }, { "dimension": "access", "status": "covered", "notes": "Default internal-only rule with role-scoped restriction of pay, evaluation, risk and authority data across all four scopes, plus named exceptions for applicant pay disclosure, aggregate reporting and regulator access, and read-logging duties for sensitive fields." }, { "dimension": "retention and deletion", "status": "gap", "notes": "The structure, preservation holds, disposition actions and personal-data boundary are modelled, but no fetched primary source states retention periods for position records. Periods must be supplied per jurisdiction by the adopting Dimension; treat the retention finding as a required local determination, not as canonical guidance." }, { "dimension": "interoperability", "status": "covered", "notes": "Version-pinned crosswalks to ISCO-08, ESCO, O*NET-SOC and NICE work roles with mapping strength and recorded conflicts, HR Open exchange objects, schema.org publication projection and org: graph publication, with conformance claims requiring assessment evidence." }, { "dimension": "classification and levelling", "status": "covered", "notes": "Separates what kind of work (class and occupation) from how much (grade and evaluation), aligning the class definition, the ISCO job-versus-occupation distinction and the four objective evaluation criteria." }, { "dimension": "authority and accountability", "status": "covered", "notes": "Internal delegated decision rights with limits and vacancy behaviour, plus externally prescribed responsibilities allocated to designated senior positions with seniority justification and gap analysis." }, { "dimension": "capacity and funding", "status": "covered", "notes": "FTE, headcount, single versus pooled, overlap tolerance, budgeted flag, budget amount and currency, funding source including funded-by-existing-position, and derived open capacity." }, { "dimension": "spatial", "status": "covered", "notes": "Work location, arrangement type, seasonal windows and environmental context, with jurisdiction derived from location rather than asserted independently." }, { "dimension": "measurement", "status": "covered", "notes": "Metric definitions with explicit denominators, unit reconciliation between FTE, headcount and authorized establishment, aggregation by category of workers, and inclusion rules for frozen, proposed and unbudgeted seats." }, { "dimension": "privacy", "status": "covered", "notes": "Occupant-free rule for the position record, personal-data boundary markers, and routing of erasure requests to the worker or assignment model. Specific lawful-basis analysis is left to the adopting Dimension." }, { "dimension": "security", "status": "covered", "notes": "Position-derived access entitlements, clearance and screening levels with re-screening intervals, regulatory approval prerequisites and lapse handling, sourced from production position attributes and regulated-firm approval requirements." } ], "known_omissions": [ "ISO 30414 human capital reporting metrics could not be verified: iso.org returned HTTP 403, so no ISO metric definitions are cited and the measurement layer relies on production attributes and EU reporting duties instead.", "Official US federal sources were unreachable (opm.gov connection resets; ecfr.gov, bls.gov and several .gov hosts returned 403 or redirected to an unblock gateway), so 5 CFR and 29 CFR text is cited from the Cornell LII reproduction rather than from eCFR, and OPM's position-designation guidance is not cited at all.", "Works council, co-determination and collective consultation duties on position creation and change (for example German BetrVG-style participation rights) are not modelled; no primary source was verified.", "Public-sector establishment ceilings, headcount control legislation and civil-service staffing plans beyond the General Schedule pattern are not covered.", "Military billets, ranks, elected and appointed public offices, board directorships, honorary and volunteer positions are only partially served by this structure; their appointment and eligibility rules are not modelled.", "Occupancy of positions by non-human agents (software agents, robots) is unresolved. The registry records a robotics factor of zero, and no fetched source addresses whether a post may be held by a non-person agent, although org:holds is defined over agents rather than persons.", "Job architecture and career-path concepts (job families, career streams, progression ladders as structures rather than as grade ladders referenced by key) are deliberately left to the sibling job classifier model.", "Contingent, agency and outsourced work arrangements are only referenced through HR Open's contingent staffing family; the boundary between a position and a supplier-provided service is not resolved.", "Full ISO 30400:2022 term entries for job, role, position and FTE were not inspectable; only the standard’s existence, date and chapter map were confirmed.", "HR Open Standards / HR-XML Position and PositionOpening schemas were not retrieved as open full text.", "Military billet versus rank, NATO manning, and academic faculty-line or endowed-chair semantics lack primary sources in this run and are gaps rather than canonical layers.", "National archives retention schedules (for example NARA GRS) and GDPR storage-limitation periods are not cited as specific durations.", "Dual-incumbency overlap windows for succession, career-ladder intern positions, and union-exclusivity of a slot are widely practised but not given primary support here.", "Corporate statutory officer roles (director, company secretary) as Positions versus board membership remain unresolved against a possible sibling governance model.", "ESCO occupation pillar beyond its ISCO mapping was not fetched." ], "conflicts": [ "Occupancy cardinality: W3C states a post may be held by one or more persons, while classical position control treats a SINGLE position as admitting one holder and only POOLED positions as admitting several. Resolved here by making concurrency explicit through position type, headcount and an overlap flag rather than by assuming either default.", "Terminology: ISCO-08 defines a job as the tasks performed by one person for a single economic unit, which is close to what this model calls a position, while ESCO and O*NET reserve occupation for the class and production HCM systems use Job for the class and Position for the instance. The same word therefore denotes an instance in one standard and a class in another; every coded reference must carry its scheme.", "Advertisement versus seat: schema.org JobPosting merges the advertisement with the described role and carries totalJobOpenings, whereas HR Open separates PositionOpening from OrganizationChart. This model treats the posting as a projection with its own validity window, and permits advertised openings to differ from authorized headcount.", "Nature of a position: the regulatory definition treats a position as the work assigned to be performed by an employee, whereas production systems treat it as a container with capacity, budget and possibly many holders. The model keeps duty content as the definitional core and capacity as an authorization layer on top.", "Title versus substance: titles are governed and publishable, but essential-function determinations and occupational classification rest on duties actually performed, so a title can never be used to infer legal status, exemption, seniority or classification.", "W3C ORG models occupancy as org:holds/heldBy on Post and treats Post as a subclass of Organization so a group may hold it; Popolo forbids org:holds/heldBy, requires occupancy through Membership, and restricts holders to persons.", "HL7 FHIR PractitionerRole is primarily a period-bounded practitioner-at-organization-and-location record (assignment-shaped) that can also represent an unnamed slot; it is not equivalent to a classified HR Position or to org:Post.", "ISCO ‘job’ (tasks of one person) and ‘occupation’ (set of similar jobs) are not the same as a US ‘position’ (work assignable to an employee) or a civic ‘post’ (organization-specific slot). schema.org Occupation is the profession kind; EmployeeRole is occupancy-and-pay.", "schema.org Role.roleName / numberedPosition includes sports playing-position, which must not be imported as WM-ORG-004.", "US GS class/grade/title rules are jurisdiction-specific; using them as if they were global would be a false conformance claim." ], "regional_assumptions": [ "Pay-range disclosure prior to employment, the salary-history prohibition, gender pay-gap reporting at 100+ employees and gender-neutral job evaluation guidance follow Directive (EU) 2023/970, whose transposition deadline was 7 June 2026; national implementations differ in thresholds and timing, and comparable US state and municipal pay-transparency laws are not modelled.", "The essential-functions construct, its factor tests and the evidentiary weight of a written job description prepared before advertising are US ADA regulatory concepts; other jurisdictions impose different accommodation and documentation duties.", "The position, class and grade definitions and the classification appeal and effective-date machinery are drawn from the US federal General Schedule plan and apply directly only to positions covered by it; they are offered as an extension, not as a universal requirement.", "Allocation of prescribed responsibilities, statements of responsibilities and responsibilities maps follow the UK FCA senior managers regime and apply only to firms within its scope.", "ISCO-08 skill levels reference ISCED-97 education categories, so cross-national comparisons depend on the education mapping in force in each country.", "Currency, working-time standards used to derive FTE, probation periods and seasonal patterns are jurisdiction-dependent and must be declared by the adopting Dimension.", "US Title 5 and OPM PD practice are used as a high-resolution public-service profile, not as a world default.", "Popolo geographic-area and abolished-constituency examples are civic/legislative and may be unused in private-sector HR.", "Ex officio Cabinet membership is a Westminster illustration in ORG; the pattern is reusable but the example is regional.", "FHIR unnamed-surgeon pattern is healthcare-specific.", "ISCO skill-level to ISCED-97 mapping is an ILO statistical convention and is not a hiring rule." ], "adversarial_checks": [ "Tested the assumption that one position equals one incumbent and rejected it: W3C explicitly allows a post held by one or more persons, and production records expose POOLED position types, headcount above one and an overlap-allowed flag. The model therefore treats capacity as data rather than as an invariant.", "Tested whether a position record is universally required and rejected the assumption: many organizations run job-based configurations in which assignments attach to a job with no position record at all. The composition link to the assignment model is therefore required from the position side but the model does not assert that every assignment must reference a position.", "Tested whether a title can carry semantics and rejected it: essential-function determination rests on fundamental duties and on evidence such as time spent and consequences of non-performance, and occupational classification rests on work performed, so no consumer may infer classification, exemption or authority from a title.", "Tested whether vacancy is an attribute and rejected it: vacancy is derivable from authorized capacity minus capacity consumed by assignments owned by another model. Persisting it would create a second source of truth, so it is modelled as a computed value with an as-of instant and no artifact.", "Tested whether a published job advertisement is the position and rejected it: postings carry their own datePosted, validThrough, application channel and openings count, may reference many positions or none, and are governed by disclosure duties that bind the recruitment event rather than the seat.", "Tested whether classification decision time equals effective time and rejected it: the governing regulation places effective dates of classification actions in a separate subpart from the decisions themselves, so the model records decision instant and classification effective date as distinct fields.", "Tested whether external standards can be claimed as conformance and rejected it: all external schemes are modelled as ALIGN links with pinned versions, mapping strength and recorded conflicts, and a conformance assertion requires named assessment evidence with a method and date.", "Tested whether identity could be carried by a stable-looking business code and rejected it: position codes were found to be unique only within a business unit, so the code is retained as a scoped label while identity priority runs master-system identifier, then governed IRI, then a Dimension-minted UUID or ULID.", "If a record cannot exist when vacant, it is an assignment or membership, not a Position.", "If the only identifier is a person’s name, employee number or a start date, identity is wrongly sourced.", "If CEO is modelled once globally rather than as CEO-at-organization, a Role has been stored as a Position.", "If ISCO unit group is used as the Position id, an occupation has replaced the slot.", "If a JobPosting is treated as the Position, a recruitment advertisement has replaced establishment.", "If acting coverage rewrites official title or grade, occupancy has leaked into the slot.", "If financial holdings, map coordinates or Quarterback are accepted as instances, the wrong sense of position has been admitted.", "If org:holds is persisted under a Popolo profile, the declared interoperability profile is violated." ] }, "researchAdjudication": { "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "Both providers independently classify WM-ORG-004 as an entity and both anchor it on the same test: the record must be able to exist while vacant. That test is decidable, is grounded in W3C ORG (org:Post exists independently of the person filling it) and in the regulatory definition of a position as work assigned by competent authority, and it cleanly separates the seat from occupancy (WM-ORG-016), from the unit (WM-ORG-002), from the abstract role, and from the recruitment advertisement. No split or reclassification is warranted; the base boundary is adopted as written, with grok's word-sense and FHIR disambiguations carried forward as boundary annotations rather than as new structure." }, "decisions": [ { "concept": "Base provider selection", "disposition": "claude as base", "rationale": "Claude offers a single decidable boundary test (everything true of a position while it is vacant), names the owning sibling model for each exclusion, carries roughly 1.4 times the base's own layer count in findings with four questions each, and declares one honest gap. Grok has more bundles and layers but nineteen findings across nineteen layers, so its topology is thinner per node despite the larger frame." }, { "concept": "Entry kind", "disposition": "entity, accepted", "rationale": "Independent agreement between providers plus the vacant-existence test grounded in W3C ORG and the regulatory definition of assigned work; nothing in either pack suggests an event, service or relationship framing would fit better." }, { "concept": "Grok eight-bundle topology", "disposition": "rejected in favour of base topology", "rationale": "Grok's split of location, compensation and establishment into separate top-level bundles fragments concerns the base already integrates, and re-parenting the base's twenty-seven findings into nineteen thin layers would lose the base's explicit inline-only rationales without adding evidence." }, { "concept": "Abstract role binding", "disposition": "accepted into alignment-and-exchange", "rationale": "Materially absent from the base, evidence-backed on ORG, Popolo and schema.org, and consistent with the base's own statement that role vocabularies are alignments rather than the position itself." }, { "concept": "Geographic area and constituency", "disposition": "accepted into work-location-and-arrangement", "rationale": "Distinct from duty station and work arrangement; Popolo ties post existence to area existence and schema.org scopes occupational description by region, and the base's omissions list already concedes elected and appointed offices are underserved." }, { "concept": "Interoperability profile declaration", "disposition": "accepted into alignment-and-exchange", "rationale": "The ORG-versus-Popolo disagreement about direct holds is genuine and source-backed; recording the profile in force per instance is the mechanism that keeps it a declared configuration rather than an unresolved contradiction." }, { "concept": "Fill authorization", "disposition": "accepted as a narrowed function", "rationale": "Closes the only real hole in the base function set and marks the boundary handoff to the excluded recruiting domain; narrowed to fill so it does not duplicate the base freeze and abolish function." }, { "concept": "Grok class, series and grade finding", "disposition": "rejected as duplicative", "rationale": "The base already separates occupational classification from grade and job evaluation across two findings with twelve questions and both a classification evaluation record and a job evaluation statement; grok adds no evidence the base lacks." }, { "concept": "Grok occupation code alignment finding", "disposition": "rejected as duplicative", "rationale": "Covered by the base occupational-classification finding plus the version-pinned crosswalk finding, both of which already require scheme, version and mapping strength; the ISCO armed-forces-major-group nuance is deferred instead." }, { "concept": "Grok position remuneration band finding", "disposition": "rejected as duplicative", "rationale": "The base pay-range-and-transparency finding already fixes the position band against occupant pay and adds disclosure and reporting duties; only the unpaid, nominal-pay and fee-basis case is genuinely new and it is too thin to stand as structure, so it is deferred." }, { "concept": "Grok hosting organization finding", "disposition": "rejected as duplicative", "rationale": "The base unit-and-cost-centre finding covers holding unit, legal entity, business unit and cost centre with movement semantics; the residual ex officio and Post-as-Organization dual-typing questions are deferred rather than injected." }, { "concept": "Grok constraints-on-the-position finding", "disposition": "rejected as split across existing layers", "rationale": "Its three elements land separately in the base screening-and-clearance, retention-and-privacy and pay findings; injecting it whole would create overlapping ownership of sensitivity and privacy rules across two bundles." }, { "concept": "Vacancy as derived state", "disposition": "retained from base, corroborated", "rationale": "Both providers independently refuse to persist occupancy on the seat and both cite ORG and the assignment boundary; the base's no-artifact rationale is kept because a stored vacancy flag would create a second source of truth against WM-ORG-016." }, { "concept": "Retention dimension status", "disposition": "retained as gap, not upgraded", "rationale": "Grok marks retention covered while its own notes concede national schedules were not fetched; the base's gap marking is the accurate one and no fetched primary source in either pack states a retention period for position records." }, { "concept": "Source identifier collision", "disposition": "re-key all source ids on merge", "rationale": "SRC-002 denotes HR Open in the base and Popolo in grok, and several other identifiers collide across providers while pointing at different documents; the synthesizer must re-key rather than union by identifier or every accepted addition will carry the wrong citation." }, { "concept": "FHIR and word-sense disambiguation", "disposition": "carried as boundary annotation, not structure", "rationale": "Grok's align-not-equate treatment of PractitionerRole and its exclusion of financial, geospatial and sports senses of position are correct and useful, but they are boundary prose rather than findings; they are recorded as a publication hold on the boundary notes instead of being injected as nodes." } ], "publicationHolds": [ "Source verification is incomplete: every base URL and version pin must be re-resolved at publication time. In particular the base cites 5 CFR and 29 CFR from the Cornell LII reproduction because eCFR and opm.gov were unreachable in its run, while grok reached eCFR current as of 2026-08-20 and the OPM classification standards PDF; re-verify and dual-cite or swap to the official host before publishing.", "Source identifiers collide across providers with different underlying documents (SRC-002 is HR Open in the base and Popolo in grok, among others). All sources must be re-keyed during merge and every accepted addition re-pointed, and the merged source list re-verified as live, before any draft is published.", "ISO 30400:2022 must not be cited as defining position, job, role or FTE: grok's own note concedes the term text was not inspectable behind the paywall, so only the standard's existence, date and scope are supportable. The ISCO-08 citation must likewise resolve to an authoritative ILO or UNSD host rather than the third-party netlify mirror used by grok.", "Retention and disposition periods remain a declared gap. No fetched primary source in either pack states a retention period for position records, descriptions or classification decisions; the structure may be published only as a required local determination, never as canonical guidance.", "Multi-profile domain validation is outstanding. Evidence concentrates on US federal General Schedule classification, UK FCA prescribed responsibilities, EU pay transparency and a single HCM vendor API. Before publication the model must be exercised against at least a civic or legislative profile (Popolo post with constituency), a healthcare profile (FHIR PractitionerRole unnamed slot) and a non-US private-sector profile, and every regional assumption must be labelled a jurisdiction profile rather than a universal requirement.", "Published boundary notes must carry grok's disambiguations verbatim in substance: HL7 FHIR PractitionerRole is aligned, not equated, to a classified position, and the financial, geospatial and sports senses of the word position are excluded, including schema.org's Quarterback example of a named position." ], "deferredResearch": [ "Post-as-Organization dual typing and ex officio membership conferred by holding a post (W3C ORG and Popolo), unresolved against the WM-ORG-002 unit and WM-ORG-003 team boundaries and against corporate statutory officer roles versus board membership.", "Unpaid, honorary, nominal-pay, fee-basis, piece-work and volunteer positions, and statutory exclusions from classification and pay statutes such as 5 U.S.C. section 5102(c); currently only reachable through grok's rejected remuneration finding.", "Military billets versus rank as personal status (including ISCO Major Group 0 alignment), academic faculty lines and endowed chairs, and elected or appointed public office appointment and eligibility rules.", "Works council, co-determination and collective consultation duties triggered by position creation, reclassification and abolition; no primary source was verified by either provider.", "Occupancy of a position by a non-human agent, unresolved in both packs even though org:holds is defined over agents rather than persons.", "National retention schedules (for example NARA GRS) and GDPR storage-limitation periods as concrete durations for position descriptions, classification files and occupant-linked records.", "Unfetched standard texts that would strengthen weakly supported areas: HR Open Position and PositionOpening full schemas, the ESCO occupation pillar beyond its ISCO mapping, ISO 30414 human capital metrics, and ISO 30400 term entries.", "Dual-incumbency overlap windows for succession, career-ladder or intern positions, job-share fractions and union exclusivity of a slot, all widely practised but without primary support in either run." ] }, "statistics": { "sources": 25, "bundles": 6, "layers": 13, "findings": 30, "questions": 117, "artifacts": 26, "functions": 13 } }