# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T07:37:41Z", "synthesisSha256": "6c8469006cc08f5a8d06adc08c70b53980296d7eced02300f1f39ed8f9e8c1cd", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ACT-039", "registryId": "vr.wm-act-039", "name": "Recruitment / Hiring Process", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Activities and processes", "industry": [ "Cross-industry" ], "domain": [ "ACT.HR" ], "tags": [ "recruitment", "hiring", "process", "act.hr" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-act-039-recruitment-hiring-process/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-act-039", "model": { "registry_id": "vr.wm-act-039", "model_id": "WM-ACT-039", "name": "Recruitment / Hiring Process", "entry_kind": "aggregate", "purpose": "Represent one governed recruitment process aggregate for a bounded hiring need or campaign, connecting an authorized requisition and frozen selection design to source-qualified candidate participation, accountable decisions, offers and closure.", "scope_statement": "Owns recruitment-process identity and lineage, mandatory process profile, authorized need and exact requisition and criterion bindings, posting and sourcing activity, process-scoped candidate-case links, stage design and occurrences, bounded screening, assessment, interview, verification, recommendation, decision, offer, response, closure, quality, fairness, lifecycle, interoperability, access and retention assertions. Organization, Unit, Position, Vacancy, Person, Candidate, Application, Qualification, Competency, Assessment Definition, Assessment Result, Interview, Evidence, Decision, Offer, Contract, Employment, Communication, Dataset, Artifact and Audit masters remain external.", "in_scope": [ "Process identity, profile, lineage, hiring need, requisition, authority, job analysis, competencies, qualifications, criteria and policy bindings", "Posting, channels, sourcing, referrals, agencies, fees, candidate notices, application and candidate-case references, eligibility, accessibility, accommodations and protected-data controls", "Screening, assessments, interviews, verification, ranking, recommendation, accountable selection, offers, responses, closure, complaints, quality, fairness, lifecycle, interoperability, retention and safe agents" ], "out_of_scope": [ "Independent organization, unit, position, vacancy, person, candidate, application, competency, qualification, assessment, interview, evidence, decision, offer, contract, employment, communication, dataset, artifact or audit master lifecycles", "Inferring consent, qualification, eligibility, suitability, fairness, employment, legality or future performance from participation, one document, score, ratio, offer response or opaque model", "Implementing an applicant-tracking system, job board, assessment platform, background-check service, HR information system, payroll system or universal employment and equality law" ], "boundary_notes": [ { "neighbor": "Position, Vacancy / Matching and Job Posting", "distinction": "The position and vacancy define the opportunity and a posting is one published representation. The recruitment aggregate binds exact external revisions and coordinates a bounded hiring realization.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-010" ] }, { "neighbor": "Person, Candidate and Application", "distinction": "The process owns source-qualified participation and stage assertions. Person, candidate identity and application evidence retain independent ownership, rights and lifecycle.", "source_refs": [ "SRC-002", "SRC-005", "SRC-008", "SRC-012", "SRC-014" ] }, { "neighbor": "Assessment, Interview, Verification and Evidence", "distinction": "The process binds exact definitions and records occurrences and bounded use. Instruments, observations, source evidence and result records retain their own identity, authority and correction history.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-012" ] }, { "neighbor": "Recommendation, Decision and Offer", "distinction": "Scores and recommendations inform but do not become the accountable selection decision. An offer is a separately versioned proposal with its own issuer, terms, response and withdrawal history.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-012" ] }, { "neighbor": "Contract, Employment and Onboarding", "distinction": "Offer acceptance and recruitment closure may trigger governed handoffs but do not create the contract, employment relation or onboarding lifecycle inside this model.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ISO 30405:2023 Human resource management: Guidelines on recruitment", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/79488.html", "version_or_date": "ISO 30405:2023, edition 2, published June 2023; public abstract only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Frames recruitment as preparing and planning, attracting and sourcing, assessing and employing, managing phases and stakeholders, and reviewing and learning." }, { "id": "SRC-002", "title": "General principles and operational guidelines for fair recruitment and definition of recruitment fees and related costs", "organization": "International Labour Organization", "url": "https://www.ilo.org/publications/general-principles-and-operational-guidelines-fair-recruitment-and", "version_or_date": "ILO guidance and definition, 2019", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Provides an international fair-recruitment baseline, worker-rights safeguards, recruiter responsibilities, transparency, remedy and the principle that workers should not bear recruitment fees or related costs." }, { "id": "SRC-003", "title": "Questions and Answers on the Uniform Guidelines on Employee Selection Procedures", "organization": "U.S. Equal Employment Opportunity Commission", "url": "https://www.eeoc.gov/laws/guidance/questions-and-answers-clarify-and-provide-common-interpretation-uniform-guidelines", "version_or_date": "EEOC-NVTA-1979-1, issued 1 March 1979, explaining 29 CFR Part 1607", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Defines the total selection process, selection procedures, recordkeeping, adverse-impact analysis, validation evidence and the limited role of the four-fifths rule in the United States." }, { "id": "SRC-004", "title": "End-to-End Hiring Initiative: Hiring Process Roadmap", "organization": "U.S. Office of Personnel Management", "url": "https://www.opm.gov/policy-data-oversight/human-capital-management/hiring-reform/reference/end-to-end-hiring-initiative.pdf", "version_or_date": "Federal hiring roadmap, official PDF accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Supplies a concrete public-sector flow from workforce need and job analysis through announcement, application review, assessment, interviews, selection, offer and onboarding handoff." }, { "id": "SRC-005", "title": "General Data Protection Regulation", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=celex%3A32016R0679", "version_or_date": "Regulation (EU) 2016/679, consolidated official text accessed 6 September 2026", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Grounds lawful, fair and transparent processing, purpose limitation, minimization, accuracy, information duties, data-subject rights, special-category safeguards, security, impact assessment and automated-decision constraints." }, { "id": "SRC-006", "title": "Guidelines on Automated individual decision-making and Profiling", "organization": "European Data Protection Board", "url": "https://www.edpb.europa.eu/documents/guideline/automated-decision-making-and-profiling_en", "version_or_date": "WP251rev.01 endorsed 25 May 2018", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Clarifies profiling, solely automated decisions with legal or similarly significant effects, meaningful information, human intervention and safeguards under GDPR." }, { "id": "SRC-007", "title": "Artificial Intelligence Act", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2024/1689/oj?locale=en", "version_or_date": "Regulation (EU) 2024/1689, Official Journal text", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Classifies certain AI used for recruitment and selection as high-risk and supplies provider and deployer governance, logging, human-oversight and risk-control context within its scope." }, { "id": "SRC-008", "title": "Employment practices and data protection: recruitment and selection", "organization": "Information Commissioner's Office", "url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/employment/recruitment-and-selection", "version_or_date": "UK draft guidance, consultation closed; page accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Covers candidate discovery, notices, automated decisions, applications, shortlisting, testing, interviewing, verification, vetting and recruitment-record retention; draft status limits authority." }, { "id": "SRC-009", "title": "JobPosting", "organization": "Schema.org Community Group", "url": "https://schema.org/JobPosting", "version_or_date": "Schema.org current vocabulary page accessed 6 September 2026", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Provides a web-discovery projection for hiring organization, job location, duties, requirements, compensation, employment type, dates and applicant-location constraints." }, { "id": "SRC-010", "title": "ESCO API", "organization": "European Commission", "url": "https://esco.ec.europa.eu/en/about-esco/escopedia/escopedia/esco-api", "version_or_date": "ESCO v1.2.1, updated 10 December 2025", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Provides persistent URI identifiers and multilingual machine access for occupations, knowledge, skills, competences and qualifications used in job matching." }, { "id": "SRC-011", "title": "Standards Downloads", "organization": "HR Open Standards Consortium", "url": "https://www.hropenstandards.org/standards-downloads", "version_or_date": "Current HR-JSON and HR-XML download page accessed 6 September 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Identifies consensus HR exchange libraries covering recruiting and related records; downloads require acceptance or registration and no round-trip conformance was tested." }, { "id": "SRC-012", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Defines entities, activities, agents, plans, usage, generation, attribution, derivation, revision and invalidation for hiring evidence and decisions." }, { "id": "SRC-013", "title": "Web Content Accessibility Guidelines 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/WCAG22/", "version_or_date": "W3C Recommendation, 12 December 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Provides testable accessibility criteria for digital postings, application paths, assessments, interview tools and candidate communications." }, { "id": "SRC-014", "title": "NIST Privacy Framework", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/privacy-framework", "version_or_date": "Privacy Framework 1.0 with later evolution materials", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Provides a voluntary risk-based structure for identifying and managing privacy risk across candidate-data collection, analysis, sharing and retention." }, { "id": "SRC-015", "title": "Disposing of records", "organization": "The National Archives, United Kingdom", "url": "https://www.nationalarchives.gov.uk/information-management/manage-information/policy-process/disposal/", "version_or_date": "Official records-management guidance accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Grounds retention and disposition decisions in business, legal, accountability and historical requirements rather than application-system convenience." }, { "id": "SRC-016", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T07:24:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit UTC offset for process, evidence, decision and knowledge times." } ], "structure": { "bundles": [ { "id": "process-identity-authorization-and-design", "name": "Process identity, authorization and design", "description": "Defines one bounded recruitment aggregate and the authorized hiring need it serves.", "rationale": "Stable process identity, a mandatory profile and frozen requisition and criterion revisions prevent a campaign from collapsing into a vacancy, candidate or later employment record.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-016" ], "layers": [ { "id": "process-profile-identity-and-lineage", "name": "Process profile, identity and lineage", "description": "Establishes the aggregate boundary, identity, aliases, profile and successor history.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-016" ], "findings": [ { "id": "recruitment-profile-boundary-and-neighbor-separation", "name": "Recruitment profile, boundary and neighbor separation", "description": "Mandatory profile for single-vacancy, pooled or evergreen, internal mobility, contingent, agency, public-sector or cross-border recruitment, with separate vacancy, candidate-case and employment masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012" ], "questions": [ { "id": "recruitment-profile-boundary-and-neighbor-separation-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish recruitment profile, boundary and neighbor separation?", "kind": "classification", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "recruitment-profile-boundary-and-neighbor-separation-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support recruitment profile, boundary and neighbor separation?", "kind": "provenance", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "recruitment-profile-boundary-and-neighbor-separation-q03", "text": "How may recruitment profile, boundary and neighbor separation be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "validation", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "recruitment-profile-boundary-and-neighbor-separation-data", "name": "Recruitment profile, boundary and neighbor separation data", "description": "Structured recruitment-process data for recruitment profile, boundary and neighbor separation with scope, provenance, time, confidence and access marking.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012" ] } ], "artifacts": [ { "id": "recruitment-profile-boundary-and-neighbor-separation-record", "name": "Recruitment profile, boundary and neighbor separation record", "description": "Versioned evidence-bearing recruitment-process record for recruitment profile, boundary and neighbor separation with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus recruitment-profile-boundary-and-neighbor-separation assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "process-identifier-name-source-version-predecessor-successor-and-lineage", "name": "Process identifier, name, source, version, predecessor, successor and lineage", "description": "Authoritative and alternate identifiers, title, source-system key, profile and schema versions, reopened or repeat relation, correction and supersession lineage.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-016" ], "questions": [ { "id": "process-identifier-name-source-version-predecessor-successor-and-lineage-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish process identifier, name, source, version, predecessor, successor and lineage?", "kind": "identity", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "process-identifier-name-source-version-predecessor-successor-and-lineage-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support process identifier, name, source, version, predecessor, successor and lineage?", "kind": "process", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "process-identifier-name-source-version-predecessor-successor-and-lineage-q03", "text": "How may process identifier, name, source, version, predecessor, successor and lineage be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "composition", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "process-identifier-name-source-version-predecessor-successor-and-lineage-data", "name": "Process identifier, name, source, version, predecessor, successor and lineage data", "description": "Structured recruitment-process data for process identifier, name, source, version, predecessor, successor and lineage with scope, provenance, time, confidence and access marking.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-016" ] } ], "artifacts": [ { "id": "process-identifier-name-source-version-predecessor-successor-and-lineage-record", "name": "Process identifier, name, source, version, predecessor, successor and lineage record", "description": "Versioned evidence-bearing recruitment-process record for process identifier, name, source, version, predecessor, successor and lineage with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus process-identifier-name-source-version-predecessor-successor-and-lineage assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "hiring-need-requisition-job-analysis-and-criteria", "name": "Hiring need, requisition, job analysis and criteria", "description": "Pins why hiring is authorized and which exact role requirements govern selection.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010" ], "findings": [ { "id": "workforce-need-position-vacancy-headcount-budget-owner-authority-and-scope", "name": "Workforce need, position, vacancy, headcount, budget, owner, authority and scope", "description": "External organization, unit, position and vacancy references, requested headcount, employment profile, location, budget, sponsor, approval, urgency, inclusions and exclusions.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012" ], "questions": [ { "id": "workforce-need-position-vacancy-headcount-budget-owner-authority-and-scope-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish workforce need, position, vacancy, headcount, budget, owner, authority and scope?", "kind": "authority", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "workforce-need-position-vacancy-headcount-budget-owner-authority-and-scope-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support workforce need, position, vacancy, headcount, budget, owner, authority and scope?", "kind": "validation", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "workforce-need-position-vacancy-headcount-budget-owner-authority-and-scope-q03", "text": "How may workforce need, position, vacancy, headcount, budget, owner, authority and scope be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "process", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "workforce-need-position-vacancy-headcount-budget-owner-authority-and-scope-data", "name": "Workforce need, position, vacancy, headcount, budget, owner, authority and scope data", "description": "Structured recruitment-process data for workforce need, position, vacancy, headcount, budget, owner, authority and scope with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-012" ] } ], "artifacts": [ { "id": "workforce-need-position-vacancy-headcount-budget-owner-authority-and-scope-record", "name": "Workforce need, position, vacancy, headcount, budget, owner, authority and scope record", "description": "Versioned evidence-bearing recruitment-process record for workforce need, position, vacancy, headcount, budget, owner, authority and scope with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus workforce-need-position-vacancy-headcount-budget-owner-authority-and-scope assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "job-analysis-duties-competencies-qualifications-criteria-weighting-version-and-validity", "name": "Job analysis, duties, competencies, qualifications, criteria, weighting, version and validity", "description": "Job-analysis evidence, occupation and skill URIs, essential duties, lawful prerequisites, assessment criteria, weights, scoring or decision rules, validation evidence and immutable release version.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010" ], "questions": [ { "id": "job-analysis-duties-competencies-qualifications-criteria-weighting-version-and-validity-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish job analysis, duties, competencies, qualifications, criteria, weighting, version and validity?", "kind": "requirement", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "job-analysis-duties-competencies-qualifications-criteria-weighting-version-and-validity-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support job analysis, duties, competencies, qualifications, criteria, weighting, version and validity?", "kind": "exception", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "job-analysis-duties-competencies-qualifications-criteria-weighting-version-and-validity-q03", "text": "How may job analysis, duties, competencies, qualifications, criteria, weighting, version and validity be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "interoperability", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "job-analysis-duties-competencies-qualifications-criteria-weighting-version-and-validity-data", "name": "Job analysis, duties, competencies, qualifications, criteria, weighting, version and validity data", "description": "Structured recruitment-process data for job analysis, duties, competencies, qualifications, criteria, weighting, version and validity with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010" ] } ], "artifacts": [ { "id": "job-analysis-duties-competencies-qualifications-criteria-weighting-version-and-validity-record", "name": "Job analysis, duties, competencies, qualifications, criteria, weighting, version and validity record", "description": "Versioned evidence-bearing recruitment-process record for job analysis, duties, competencies, qualifications, criteria, weighting, version and validity with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus job-analysis-duties-competencies-qualifications-criteria-weighting-version-and-validity assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "posting-sourcing-and-fair-recruitment", "name": "Posting, sourcing and fair recruitment", "description": "Makes the opportunity discoverable and governs how candidate pools are formed.", "rationale": "Posting content, channels, sourcing actions, referrals, agencies, fees and cross-border safeguards shape access to opportunity before formal selection begins.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-009", "SRC-010", "SRC-013" ], "layers": [ { "id": "job-posting-publication-and-candidate-access", "name": "Job posting, publication and candidate access", "description": "Records the released opportunity description and each publication occurrence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-010", "SRC-013", "SRC-016" ], "findings": [ { "id": "posting-title-description-duties-terms-location-compensation-requirements-and-accessibility", "name": "Posting title, description, duties, terms, location, compensation, requirements and accessibility", "description": "Versioned candidate-facing content, employer and position bindings, employment type, workplace and applicant location, compensation, duties, qualifications, application method, notices, accessibility and closing conditions.", "source_refs": [ "SRC-001", "SRC-009", "SRC-010", "SRC-013" ], "questions": [ { "id": "posting-title-description-duties-terms-location-compensation-requirements-and-accessibility-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish posting title, description, duties, terms, location, compensation, requirements and accessibility?", "kind": "definition", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "posting-title-description-duties-terms-location-compensation-requirements-and-accessibility-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support posting title, description, duties, terms, location, compensation, requirements and accessibility?", "kind": "classification", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "posting-title-description-duties-terms-location-compensation-requirements-and-accessibility-q03", "text": "How may posting title, description, duties, terms, location, compensation, requirements and accessibility be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "provenance", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "posting-title-description-duties-terms-location-compensation-requirements-and-accessibility-data", "name": "Posting title, description, duties, terms, location, compensation, requirements and accessibility data", "description": "Structured recruitment-process data for posting title, description, duties, terms, location, compensation, requirements and accessibility with scope, provenance, time, confidence and access marking.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-009", "SRC-010", "SRC-013" ] } ], "artifacts": [ { "id": "posting-title-description-duties-terms-location-compensation-requirements-and-accessibility-record", "name": "Posting title, description, duties, terms, location, compensation, requirements and accessibility record", "description": "Versioned evidence-bearing recruitment-process record for posting title, description, duties, terms, location, compensation, requirements and accessibility with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus posting-title-description-duties-terms-location-compensation-requirements-and-accessibility assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-009", "SRC-010", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "publication-channel-audience-release-window-language-reach-correction-and-withdrawal", "name": "Publication channel, audience, release window, language, reach, correction and withdrawal", "description": "Channel and publisher, target audience, language and accessible rendition, posted and closing times, campaign code, reach observation, correction, withdrawal and source capture.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-012", "SRC-013", "SRC-016" ], "questions": [ { "id": "publication-channel-audience-release-window-language-reach-correction-and-withdrawal-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish publication channel, audience, release window, language, reach, correction and withdrawal?", "kind": "event", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "publication-channel-audience-release-window-language-reach-correction-and-withdrawal-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support publication channel, audience, release window, language, reach, correction and withdrawal?", "kind": "temporal", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "publication-channel-audience-release-window-language-reach-correction-and-withdrawal-q03", "text": "How may publication channel, audience, release window, language, reach, correction and withdrawal be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "security", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "publication-channel-audience-release-window-language-reach-correction-and-withdrawal-data", "name": "Publication channel, audience, release window, language, reach, correction and withdrawal data", "description": "Structured recruitment-process data for publication channel, audience, release window, language, reach, correction and withdrawal with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-012", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "publication-channel-audience-release-window-language-reach-correction-and-withdrawal-record", "name": "Publication channel, audience, release window, language, reach, correction and withdrawal record", "description": "Versioned evidence-bearing recruitment-process record for publication channel, audience, release window, language, reach, correction and withdrawal with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus publication-channel-audience-release-window-language-reach-correction-and-withdrawal assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-012", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "sourcing-referrals-agencies-fees-and-cross-border-controls", "name": "Sourcing, referrals, agencies, fees and cross-border controls", "description": "Preserves how people were identified or invited and which intermediaries acted.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-008", "SRC-010", "SRC-012" ], "findings": [ { "id": "sourcing-plan-channel-search-talent-pool-referral-outreach-origin-and-consent", "name": "Sourcing plan, channel, search, talent pool, referral, outreach, origin and consent", "description": "Planned sources, campaign parameters, talent-pool basis, referral relationship, outreach event, source provenance, notice, opt-out and limits on later reuse.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-008", "SRC-010", "SRC-012" ], "questions": [ { "id": "sourcing-plan-channel-search-talent-pool-referral-outreach-origin-and-consent-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish sourcing plan, channel, search, talent pool, referral, outreach, origin and consent?", "kind": "provenance", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "sourcing-plan-channel-search-talent-pool-referral-outreach-origin-and-consent-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support sourcing plan, channel, search, talent pool, referral, outreach, origin and consent?", "kind": "requirement", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "sourcing-plan-channel-search-talent-pool-referral-outreach-origin-and-consent-q03", "text": "How may sourcing plan, channel, search, talent pool, referral, outreach, origin and consent be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "relationship", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "sourcing-plan-channel-search-talent-pool-referral-outreach-origin-and-consent-data", "name": "Sourcing plan, channel, search, talent pool, referral, outreach, origin and consent data", "description": "Structured recruitment-process data for sourcing plan, channel, search, talent pool, referral, outreach, origin and consent with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-008", "SRC-010", "SRC-012" ] } ], "artifacts": [ { "id": "sourcing-plan-channel-search-talent-pool-referral-outreach-origin-and-consent-record", "name": "Sourcing plan, channel, search, talent pool, referral, outreach, origin and consent record", "description": "Versioned evidence-bearing recruitment-process record for sourcing plan, channel, search, talent pool, referral, outreach, origin and consent with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus sourcing-plan-channel-search-talent-pool-referral-outreach-origin-and-consent assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-008", "SRC-010", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "recruiter-agency-mandate-contract-fee-cost-payer-migration-risk-and-remedy", "name": "Recruiter, agency, mandate, contract, fee, cost, payer, migration risk and remedy", "description": "External intermediary identity, licence or authority, client mandate, contract, services, recruitment fees and related costs, payer, worker-charge exception basis, cross-border steps, complaint and remedy route.", "source_refs": [ "SRC-002", "SRC-012" ], "questions": [ { "id": "recruiter-agency-mandate-contract-fee-cost-payer-migration-risk-and-remedy-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish recruiter, agency, mandate, contract, fee, cost, payer, migration risk and remedy?", "kind": "constraint", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "recruiter-agency-mandate-contract-fee-cost-payer-migration-risk-and-remedy-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support recruiter, agency, mandate, contract, fee, cost, payer, migration risk and remedy?", "kind": "evidence", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "recruiter-agency-mandate-contract-fee-cost-payer-migration-risk-and-remedy-q03", "text": "How may recruiter, agency, mandate, contract, fee, cost, payer, migration risk and remedy be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "event", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "recruiter-agency-mandate-contract-fee-cost-payer-migration-risk-and-remedy-data", "name": "Recruiter, agency, mandate, contract, fee, cost, payer, migration risk and remedy data", "description": "Structured recruitment-process data for recruiter, agency, mandate, contract, fee, cost, payer, migration risk and remedy with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-012" ] } ], "artifacts": [ { "id": "recruiter-agency-mandate-contract-fee-cost-payer-migration-risk-and-remedy-record", "name": "Recruiter, agency, mandate, contract, fee, cost, payer, migration risk and remedy record", "description": "Versioned evidence-bearing recruitment-process record for recruiter, agency, mandate, contract, fee, cost, payer, migration risk and remedy with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus recruiter-agency-mandate-contract-fee-cost-payer-migration-risk-and-remedy assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-002", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "candidate-cases-applications-and-rights", "name": "Candidate cases, applications and rights", "description": "Binds separately governed people and applications to the process with transparent, minimal and accessible handling.", "rationale": "Candidate discovery, application, identity matching, eligibility, accommodations and sensitive information require source-qualified records and purpose-bound access.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008", "SRC-013", "SRC-014" ], "layers": [ { "id": "candidate-notice-application-and-identity-resolution", "name": "Candidate notice, application and identity resolution", "description": "Creates a process-scoped candidacy link without absorbing the person or application master.", "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-012", "SRC-014", "SRC-016" ], "findings": [ { "id": "candidate-reference-source-notice-lawful-basis-purpose-rights-and-contact", "name": "Candidate reference, source, notice, lawful basis, purpose, rights and contact", "description": "External person or candidate reference, discovery source, direct or indirect collection, controller and processor roles, notice version and delivery, lawful basis, purposes, rights route, contact preference and withdrawal or objection where applicable.", "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-014" ], "questions": [ { "id": "candidate-reference-source-notice-lawful-basis-purpose-rights-and-contact-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish candidate reference, source, notice, lawful basis, purpose, rights and contact?", "kind": "privacy", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "candidate-reference-source-notice-lawful-basis-purpose-rights-and-contact-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support candidate reference, source, notice, lawful basis, purpose, rights and contact?", "kind": "retention", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "candidate-reference-source-notice-lawful-basis-purpose-rights-and-contact-q03", "text": "How may candidate reference, source, notice, lawful basis, purpose, rights and contact be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "decision", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "candidate-reference-source-notice-lawful-basis-purpose-rights-and-contact-data", "name": "Candidate reference, source, notice, lawful basis, purpose, rights and contact data", "description": "Structured recruitment-process data for candidate reference, source, notice, lawful basis, purpose, rights and contact with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-014" ] } ], "artifacts": [ { "id": "candidate-reference-source-notice-lawful-basis-purpose-rights-and-contact-record", "name": "Candidate reference, source, notice, lawful basis, purpose, rights and contact record", "description": "Versioned evidence-bearing recruitment-process record for candidate reference, source, notice, lawful basis, purpose, rights and contact with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus candidate-reference-source-notice-lawful-basis-purpose-rights-and-contact assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-008", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "application-case-identifier-submission-route-documents-declarations-duplicates-and-status", "name": "Application case, identifier, submission route, documents, declarations, duplicates and status", "description": "External application and candidate-case IDs, vacancy binding, channel, submission and receipt times, document and answer references, declarations, deduplication evidence, merge refusal, completeness, withdrawal and status history.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-012", "SRC-016" ], "questions": [ { "id": "application-case-identifier-submission-route-documents-declarations-duplicates-and-status-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish application case, identifier, submission route, documents, declarations, duplicates and status?", "kind": "identity", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "application-case-identifier-submission-route-documents-declarations-duplicates-and-status-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support application case, identifier, submission route, documents, declarations, duplicates and status?", "kind": "definition", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "application-case-identifier-submission-route-documents-declarations-duplicates-and-status-q03", "text": "How may application case, identifier, submission route, documents, declarations, duplicates and status be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "ownership", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "application-case-identifier-submission-route-documents-declarations-duplicates-and-status-data", "name": "Application case, identifier, submission route, documents, declarations, duplicates and status data", "description": "Structured recruitment-process data for application case, identifier, submission route, documents, declarations, duplicates and status with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-012", "SRC-016" ] } ], "artifacts": [ { "id": "application-case-identifier-submission-route-documents-declarations-duplicates-and-status-record", "name": "Application case, identifier, submission route, documents, declarations, duplicates and status record", "description": "Versioned evidence-bearing recruitment-process record for application case, identifier, submission route, documents, declarations, duplicates and status with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus application-case-identifier-submission-route-documents-declarations-duplicates-and-status assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008", "SRC-012", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "eligibility-accommodation-sensitive-data-and-access", "name": "Eligibility, accommodation, sensitive data and access", "description": "Controls minimum necessary eligibility checks and equitable participation in selection.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-008", "SRC-013", "SRC-014" ], "findings": [ { "id": "eligibility-work-authorization-qualification-licence-location-availability-and-exception", "name": "Eligibility, work authorization, qualification, licence, location, availability and exception", "description": "Criterion-bound eligibility assertions and evidence references for authorization to work, qualifications, licences, location and availability, including rule version, verifier, uncertainty and authorized exceptions.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-010", "SRC-012" ], "questions": [ { "id": "eligibility-work-authorization-qualification-licence-location-availability-and-exception-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish eligibility, work authorization, qualification, licence, location, availability and exception?", "kind": "validation", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "eligibility-work-authorization-qualification-licence-location-availability-and-exception-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support eligibility, work authorization, qualification, licence, location, availability and exception?", "kind": "state", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "eligibility-work-authorization-qualification-licence-location-availability-and-exception-q03", "text": "How may eligibility, work authorization, qualification, licence, location, availability and exception be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "privacy", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "eligibility-work-authorization-qualification-licence-location-availability-and-exception-data", "name": "Eligibility, work authorization, qualification, licence, location, availability and exception data", "description": "Structured recruitment-process data for eligibility, work authorization, qualification, licence, location, availability and exception with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-010", "SRC-012" ] } ], "artifacts": [ { "id": "eligibility-work-authorization-qualification-licence-location-availability-and-exception-record", "name": "Eligibility, work authorization, qualification, licence, location, availability and exception record", "description": "Versioned evidence-bearing recruitment-process record for eligibility, work authorization, qualification, licence, location, availability and exception with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus eligibility-work-authorization-qualification-licence-location-availability-and-exception assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-010", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "accessibility-accommodation-health-diversity-criminal-data-separation-and-disclosure", "name": "Accessibility, accommodation, health, diversity, criminal data, separation and disclosure", "description": "Accommodation request and authorized decision references, accessible alternatives, restricted health, diversity or criminal-data compartments, purpose, lawful condition, recusal, minimum disclosure and deletion eligibility.", "source_refs": [ "SRC-003", "SRC-005", "SRC-008", "SRC-013", "SRC-014" ], "questions": [ { "id": "accessibility-accommodation-health-diversity-criminal-data-separation-and-disclosure-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish accessibility, accommodation, health, diversity, criminal data, separation and disclosure?", "kind": "access", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "accessibility-accommodation-health-diversity-criminal-data-separation-and-disclosure-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support accessibility, accommodation, health, diversity, criminal data, separation and disclosure?", "kind": "ownership", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "accessibility-accommodation-health-diversity-criminal-data-separation-and-disclosure-q03", "text": "How may accessibility, accommodation, health, diversity, criminal data, separation and disclosure be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "state", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "accessibility-accommodation-health-diversity-criminal-data-separation-and-disclosure-data", "name": "Accessibility, accommodation, health, diversity, criminal data, separation and disclosure data", "description": "Structured recruitment-process data for accessibility, accommodation, health, diversity, criminal data, separation and disclosure with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-008", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "accessibility-accommodation-health-diversity-criminal-data-separation-and-disclosure-record", "name": "Accessibility, accommodation, health, diversity, criminal data, separation and disclosure record", "description": "Versioned evidence-bearing recruitment-process record for accessibility, accommodation, health, diversity, criminal data, separation and disclosure with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus accessibility-accommodation-health-diversity-criminal-data-separation-and-disclosure assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-008", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "selection-evidence-evaluation-and-decision", "name": "Selection evidence, evaluation and decision", "description": "Captures selection procedures and accountable decisions without turning observations or scores into automatic truth.", "rationale": "Screening, assessment, interview, references, vetting, ranking and selection require frozen criteria, attributable evidence, accommodations, review and conflict controls.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ], "layers": [ { "id": "screening-assessment-and-interview", "name": "Screening, assessment and interview", "description": "Records each criterion-bound evaluation occurrence and its evidence.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-012", "SRC-013", "SRC-016" ], "findings": [ { "id": "screening-rule-criterion-evidence-outcome-reason-review-and-human-oversight", "name": "Screening rule, criterion, evidence, outcome, reason, review and human oversight", "description": "Exact screening-rule and criterion version, required inputs, evidence references, result, reason, confidence, automated-system role, human oversight, exception, review and correction lineage.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012" ], "questions": [ { "id": "screening-rule-criterion-evidence-outcome-reason-review-and-human-oversight-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish screening rule, criterion, evidence, outcome, reason, review and human oversight?", "kind": "decision", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "screening-rule-criterion-evidence-outcome-reason-review-and-human-oversight-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support screening rule, criterion, evidence, outcome, reason, review and human oversight?", "kind": "event", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "screening-rule-criterion-evidence-outcome-reason-review-and-human-oversight-q03", "text": "How may screening rule, criterion, evidence, outcome, reason, review and human oversight be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "measurement", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "screening-rule-criterion-evidence-outcome-reason-review-and-human-oversight-data", "name": "Screening rule, criterion, evidence, outcome, reason, review and human oversight data", "description": "Structured recruitment-process data for screening rule, criterion, evidence, outcome, reason, review and human oversight with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012" ] } ], "artifacts": [ { "id": "screening-rule-criterion-evidence-outcome-reason-review-and-human-oversight-record", "name": "Screening rule, criterion, evidence, outcome, reason, review and human oversight record", "description": "Versioned evidence-bearing recruitment-process record for screening rule, criterion, evidence, outcome, reason, review and human oversight with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus screening-rule-criterion-evidence-outcome-reason-review-and-human-oversight assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "assessment-interview-plan-instrument-question-panel-accommodation-observation-and-score", "name": "Assessment, interview plan, instrument, question, panel, accommodation, observation and score", "description": "External assessment or interview definition and exact revision, job-related rationale, administration, panel roles, questions or exercises, accommodation, observations, ratings, scale, scorer, evidence, moderation and dispute.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013", "SRC-016" ], "questions": [ { "id": "assessment-interview-plan-instrument-question-panel-accommodation-observation-and-score-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish assessment, interview plan, instrument, question, panel, accommodation, observation and score?", "kind": "measurement", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "assessment-interview-plan-instrument-question-panel-accommodation-observation-and-score-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support assessment, interview plan, instrument, question, panel, accommodation, observation and score?", "kind": "security", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "assessment-interview-plan-instrument-question-panel-accommodation-observation-and-score-q03", "text": "How may assessment, interview plan, instrument, question, panel, accommodation, observation and score be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "definition", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "assessment-interview-plan-instrument-question-panel-accommodation-observation-and-score-data", "name": "Assessment, interview plan, instrument, question, panel, accommodation, observation and score data", "description": "Structured recruitment-process data for assessment, interview plan, instrument, question, panel, accommodation, observation and score with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "assessment-interview-plan-instrument-question-panel-accommodation-observation-and-score-record", "name": "Assessment, interview plan, instrument, question, panel, accommodation, observation and score record", "description": "Versioned evidence-bearing recruitment-process record for assessment, interview plan, instrument, question, panel, accommodation, observation and score with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus assessment-interview-plan-instrument-question-panel-accommodation-observation-and-score assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-008", "SRC-012", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "verification-ranking-shortlist-and-accountable-selection", "name": "Verification, ranking, shortlist and accountable selection", "description": "Preserves verification evidence and distinguishes recommendations from the authorized hiring decision.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012" ], "findings": [ { "id": "reference-background-credential-vetting-check-purpose-source-result-and-retention", "name": "Reference, background, credential and vetting check purpose, source, result and retention", "description": "Check type and job relevance, candidate notice, lawful authority, source, request and response references, verifier, result and limits, adverse information response, restricted content, retention trigger and destruction evidence.", "source_refs": [ "SRC-005", "SRC-008", "SRC-012", "SRC-014", "SRC-015" ], "questions": [ { "id": "reference-background-credential-vetting-check-purpose-source-result-and-retention-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish reference, background, credential and vetting check purpose, source, result and retention?", "kind": "evidence", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "reference-background-credential-vetting-check-purpose-source-result-and-retention-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support reference, background, credential and vetting check purpose, source, result and retention?", "kind": "interoperability", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "reference-background-credential-vetting-check-purpose-source-result-and-retention-q03", "text": "How may reference, background, credential and vetting check purpose, source, result and retention be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "authority", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "reference-background-credential-vetting-check-purpose-source-result-and-retention-data", "name": "Reference, background, credential and vetting check purpose, source, result and retention data", "description": "Structured recruitment-process data for reference, background, credential and vetting check purpose, source, result and retention with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-008", "SRC-012", "SRC-014", "SRC-015" ] } ], "artifacts": [ { "id": "reference-background-credential-vetting-check-purpose-source-result-and-retention-record", "name": "Reference, background, credential and vetting check purpose, source, result and retention record", "description": "Versioned evidence-bearing recruitment-process record for reference, background, credential and vetting check purpose, source, result and retention with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus reference-background-credential-vetting-check-purpose-source-result-and-retention assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-005", "SRC-008", "SRC-012", "SRC-014", "SRC-015" ] } ], "inline_only_rationale": null }, { "id": "ranking-shortlist-recommendation-recusal-decision-authority-rationale-and-appeal", "name": "Ranking, shortlist, recommendation, recusal, decision authority, rationale and appeal", "description": "Comparison set and stage, criterion and weight versions, ranking or shortlist output, uncertainty, reviewer conflicts and recusals, recommendation, accountable decision, selected and alternate candidates, rationale, notification and challenge route.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012" ], "questions": [ { "id": "ranking-shortlist-recommendation-recusal-decision-authority-rationale-and-appeal-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish ranking, shortlist, recommendation, recusal, decision authority, rationale and appeal?", "kind": "authority", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "ranking-shortlist-recommendation-recusal-decision-authority-rationale-and-appeal-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support ranking, shortlist, recommendation, recusal, decision authority, rationale and appeal?", "kind": "composition", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "ranking-shortlist-recommendation-recusal-decision-authority-rationale-and-appeal-q03", "text": "How may ranking, shortlist, recommendation, recusal, decision authority, rationale and appeal be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "retention", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "ranking-shortlist-recommendation-recusal-decision-authority-rationale-and-appeal-data", "name": "Ranking, shortlist, recommendation, recusal, decision authority, rationale and appeal data", "description": "Structured recruitment-process data for ranking, shortlist, recommendation, recusal, decision authority, rationale and appeal with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012" ] } ], "artifacts": [ { "id": "ranking-shortlist-recommendation-recusal-decision-authority-rationale-and-appeal-record", "name": "Ranking, shortlist, recommendation, recusal, decision authority, rationale and appeal record", "description": "Versioned evidence-bearing recruitment-process record for ranking, shortlist, recommendation, recusal, decision authority, rationale and appeal with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus ranking-shortlist-recommendation-recusal-decision-authority-rationale-and-appeal assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-012" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "offer-employment-handoff-and-closure", "name": "Offer, employment handoff and closure", "description": "Controls offers and terminal process outcomes while preserving the boundary to contract and employment masters.", "rationale": "An offer, acceptance, contract, employment relation and onboarding are separate states and records; unsuccessful outcomes require notice, remedy and policy-bound retention.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-008", "SRC-012", "SRC-015", "SRC-016" ], "layers": [ { "id": "offer-negotiation-acceptance-and-contingencies", "name": "Offer, negotiation, acceptance and contingencies", "description": "Tracks attributable offer versions and candidate responses without inferring employment.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-016" ], "findings": [ { "id": "offer-identifier-position-terms-compensation-conditions-authority-version-and-expiry", "name": "Offer identifier, position, terms, compensation, conditions, authority, version and expiry", "description": "External offer reference, selected candidate and position bindings, proposed terms, compensation, location and start, contingencies, issuer authority, approval, issue and expiry times, version, withdrawal and supersession.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-016" ], "questions": [ { "id": "offer-identifier-position-terms-compensation-conditions-authority-version-and-expiry-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish offer identifier, position, terms, compensation, conditions, authority, version and expiry?", "kind": "definition", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "offer-identifier-position-terms-compensation-conditions-authority-version-and-expiry-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support offer identifier, position, terms, compensation, conditions, authority, version and expiry?", "kind": "spatial", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "offer-identifier-position-terms-compensation-conditions-authority-version-and-expiry-q03", "text": "How may offer identifier, position, terms, compensation, conditions, authority, version and expiry be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "lifecycle", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "offer-identifier-position-terms-compensation-conditions-authority-version-and-expiry-data", "name": "Offer identifier, position, terms, compensation, conditions, authority, version and expiry data", "description": "Structured recruitment-process data for offer identifier, position, terms, compensation, conditions, authority, version and expiry with scope, provenance, time, confidence and access marking.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-016" ] } ], "artifacts": [ { "id": "offer-identifier-position-terms-compensation-conditions-authority-version-and-expiry-record", "name": "Offer identifier, position, terms, compensation, conditions, authority, version and expiry record", "description": "Versioned evidence-bearing recruitment-process record for offer identifier, position, terms, compensation, conditions, authority, version and expiry with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus offer-identifier-position-terms-compensation-conditions-authority-version-and-expiry assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "candidate-response-negotiation-counteroffer-acceptance-decline-rescission-and-reason", "name": "Candidate response, negotiation, counteroffer, acceptance, decline, rescission and reason", "description": "Response event, offer version, negotiation and counteroffer references, actor and authority, response, reason category, event and knowledge times, evidence, rescission, dispute and correction history.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-016" ], "questions": [ { "id": "candidate-response-negotiation-counteroffer-acceptance-decline-rescission-and-reason-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish candidate response, negotiation, counteroffer, acceptance, decline, rescission and reason?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "candidate-response-negotiation-counteroffer-acceptance-decline-rescission-and-reason-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support candidate response, negotiation, counteroffer, acceptance, decline, rescission and reason?", "kind": "constraint", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "candidate-response-negotiation-counteroffer-acceptance-decline-rescission-and-reason-q03", "text": "How may candidate response, negotiation, counteroffer, acceptance, decline, rescission and reason be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "evidence", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "candidate-response-negotiation-counteroffer-acceptance-decline-rescission-and-reason-data", "name": "Candidate response, negotiation, counteroffer, acceptance, decline, rescission and reason data", "description": "Structured recruitment-process data for candidate response, negotiation, counteroffer, acceptance, decline, rescission and reason with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-016" ] } ], "artifacts": [ { "id": "candidate-response-negotiation-counteroffer-acceptance-decline-rescission-and-reason-record", "name": "Candidate response, negotiation, counteroffer, acceptance, decline, rescission and reason record", "description": "Versioned evidence-bearing recruitment-process record for candidate response, negotiation, counteroffer, acceptance, decline, rescission and reason with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus candidate-response-negotiation-counteroffer-acceptance-decline-rescission-and-reason assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-012", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "employment-handoff-notification-remedy-and-process-closure", "name": "Employment handoff, notification, remedy and process closure", "description": "Separates the recruitment outcome from later contractual and employment lifecycles.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-008", "SRC-012", "SRC-015", "SRC-016" ], "findings": [ { "id": "contract-employment-onboarding-handoff-start-confirmation-and-boundary", "name": "Contract, employment and onboarding handoff, start confirmation and boundary", "description": "Authorized handoff references to contract, employment, pre-employment clearance and onboarding, required conditions, responsible recipients, transfer minimization, acknowledgement and start confirmation without copying downstream masters.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-012" ], "questions": [ { "id": "contract-employment-onboarding-handoff-start-confirmation-and-boundary-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish contract, employment and onboarding handoff, start confirmation and boundary?", "kind": "relationship", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "contract-employment-onboarding-handoff-start-confirmation-and-boundary-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support contract, employment and onboarding handoff, start confirmation and boundary?", "kind": "quality", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "contract-employment-onboarding-handoff-start-confirmation-and-boundary-q03", "text": "How may contract, employment and onboarding handoff, start confirmation and boundary be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "identity", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "contract-employment-onboarding-handoff-start-confirmation-and-boundary-data", "name": "Contract, employment and onboarding handoff, start confirmation and boundary data", "description": "Structured recruitment-process data for contract, employment and onboarding handoff, start confirmation and boundary with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-012" ] } ], "artifacts": [ { "id": "contract-employment-onboarding-handoff-start-confirmation-and-boundary-record", "name": "Contract, employment and onboarding handoff, start confirmation and boundary record", "description": "Versioned evidence-bearing recruitment-process record for contract, employment and onboarding handoff, start confirmation and boundary with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus contract-employment-onboarding-handoff-start-confirmation-and-boundary assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "rejection-withdrawal-no-show-cancellation-notification-complaint-remedy-and-closure", "name": "Rejection, withdrawal, no-show, cancellation, notification, complaint, remedy and closure", "description": "Terminal or interrupted outcome, responsible actor, reason classification and disclosure policy, candidate notice, feedback, complaint, appeal or remedy, vacancy disposition, unfilled need, closure approval, retained evidence and tombstone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-012", "SRC-015", "SRC-016" ], "questions": [ { "id": "rejection-withdrawal-no-show-cancellation-notification-complaint-remedy-and-closure-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish rejection, withdrawal, no-show, cancellation, notification, complaint, remedy and closure?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "rejection-withdrawal-no-show-cancellation-notification-complaint-remedy-and-closure-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support rejection, withdrawal, no-show, cancellation, notification, complaint, remedy and closure?", "kind": "access", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "rejection-withdrawal-no-show-cancellation-notification-complaint-remedy-and-closure-q03", "text": "How may rejection, withdrawal, no-show, cancellation, notification, complaint, remedy and closure be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "requirement", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "rejection-withdrawal-no-show-cancellation-notification-complaint-remedy-and-closure-data", "name": "Rejection, withdrawal, no-show, cancellation, notification, complaint, remedy and closure data", "description": "Structured recruitment-process data for rejection, withdrawal, no-show, cancellation, notification, complaint, remedy and closure with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-012", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "rejection-withdrawal-no-show-cancellation-notification-complaint-remedy-and-closure-record", "name": "Rejection, withdrawal, no-show, cancellation, notification, complaint, remedy and closure record", "description": "Versioned evidence-bearing recruitment-process record for rejection, withdrawal, no-show, cancellation, notification, complaint, remedy and closure with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus rejection-withdrawal-no-show-cancellation-notification-complaint-remedy-and-closure assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-012", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "quality-lifecycle-interoperability-and-safe-agents", "name": "Quality, lifecycle, interoperability and safe agents", "description": "Makes recruitment history, aggregate performance, fairness, exchange and machine action inspectable.", "rationale": "Recruitment quality and fairness are source-qualified observations, not labels on people. Every projection and agent action must preserve purpose, authority, evidence, history and loss.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016" ], "layers": [ { "id": "process-lifecycle-quality-fairness-and-improvement", "name": "Process lifecycle, quality, fairness and improvement", "description": "Preserves state transitions and evaluates process performance without causal overclaiming.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-012", "SRC-016" ], "findings": [ { "id": "draft-authorized-open-paused-closed-filled-cancelled-corrected-superseded-and-archived-event", "name": "Draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded and archived event", "description": "Typed lifecycle event, prior and next state, actor, authority, rationale, affected scope, effective and recorded times, evidence, correction, reopening and successor identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-016" ], "questions": [ { "id": "draft-authorized-open-paused-closed-filled-cancelled-corrected-superseded-and-archived-event-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded and archived event?", "kind": "lifecycle", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "draft-authorized-open-paused-closed-filled-cancelled-corrected-superseded-and-archived-event-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded and archived event?", "kind": "identity", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "draft-authorized-open-paused-closed-filled-cancelled-corrected-superseded-and-archived-event-q03", "text": "How may draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded and archived event be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "access", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "draft-authorized-open-paused-closed-filled-cancelled-corrected-superseded-and-archived-event-data", "name": "Draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded and archived event data", "description": "Structured recruitment-process data for draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded and archived event with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-016" ] } ], "artifacts": [ { "id": "draft-authorized-open-paused-closed-filled-cancelled-corrected-superseded-and-archived-event-record", "name": "Draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded and archived event record", "description": "Versioned evidence-bearing recruitment-process record for draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded and archived event with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus draft-authorized-open-paused-closed-filled-cancelled-corrected-superseded-and-archived-event assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-012", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "stage-volume-time-conversion-quality-experience-fairness-adverse-impact-and-improvement", "name": "Stage volume, time, conversion, quality, experience, fairness, adverse impact and improvement", "description": "Denominators and cohort definitions, stage counts and durations, conversion and offer acceptance, source-qualified quality and candidate-experience measures, group selection rates where lawful, four-fifths indicator, statistical and practical context, limitations and improvement actions.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014", "SRC-016" ], "questions": [ { "id": "stage-volume-time-conversion-quality-experience-fairness-adverse-impact-and-improvement-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish stage volume, time, conversion, quality, experience, fairness, adverse impact and improvement?", "kind": "quality", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "stage-volume-time-conversion-quality-experience-fairness-adverse-impact-and-improvement-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support stage volume, time, conversion, quality, experience, fairness, adverse impact and improvement?", "kind": "lifecycle", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "stage-volume-time-conversion-quality-experience-fairness-adverse-impact-and-improvement-q03", "text": "How may stage volume, time, conversion, quality, experience, fairness, adverse impact and improvement be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "temporal", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "stage-volume-time-conversion-quality-experience-fairness-adverse-impact-and-improvement-data", "name": "Stage volume, time, conversion, quality, experience, fairness, adverse impact and improvement data", "description": "Structured recruitment-process data for stage volume, time, conversion, quality, experience, fairness, adverse impact and improvement with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014", "SRC-016" ] } ], "artifacts": [ { "id": "stage-volume-time-conversion-quality-experience-fairness-adverse-impact-and-improvement-record", "name": "Stage volume, time, conversion, quality, experience, fairness, adverse impact and improvement record", "description": "Versioned evidence-bearing recruitment-process record for stage volume, time, conversion, quality, experience, fairness, adverse impact and improvement with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus stage-volume-time-conversion-quality-experience-fairness-adverse-impact-and-improvement assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-014", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "provenance-interoperability-access-retention-and-agent-controls", "name": "Provenance, interoperability, access, retention and agent controls", "description": "Creates loss-aware views and governs protected data and automation.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016" ], "findings": [ { "id": "schemaorg-esco-hropen-provenance-and-system-crosswalk", "name": "Schema.org, ESCO, HR Open, provenance and system crosswalk", "description": "Pinned source and target versions, process, vacancy, posting, occupation, skill, candidate-case, application, stage, assessment, decision and offer mappings, identifiers, omissions, semantic conflicts and round-trip classification.", "source_refs": [ "SRC-009", "SRC-010", "SRC-011", "SRC-012" ], "questions": [ { "id": "schemaorg-esco-hropen-provenance-and-system-crosswalk-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish schema.org, esco, hr open, provenance and system crosswalk?", "kind": "interoperability", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "schemaorg-esco-hropen-provenance-and-system-crosswalk-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support schema.org, esco, hr open, provenance and system crosswalk?", "kind": "authority", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "schemaorg-esco-hropen-provenance-and-system-crosswalk-q03", "text": "How may schema.org, esco, hr open, provenance and system crosswalk be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "quality", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "schemaorg-esco-hropen-provenance-and-system-crosswalk-data", "name": "Schema.org, ESCO, HR Open, provenance and system crosswalk data", "description": "Structured recruitment-process data for schema.org, esco, hr open, provenance and system crosswalk with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] } ], "artifacts": [ { "id": "schemaorg-esco-hropen-provenance-and-system-crosswalk-record", "name": "Schema.org, ESCO, HR Open, provenance and system crosswalk record", "description": "Versioned evidence-bearing recruitment-process record for schema.org, esco, hr open, provenance and system crosswalk with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus schemaorg-esco-hropen-provenance-and-system-crosswalk assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-009", "SRC-010", "SRC-011", "SRC-012" ] } ], "inline_only_rationale": null }, { "id": "purpose-access-redaction-retention-hold-agent-authority-idempotency-and-postcheck", "name": "Purpose, access, redaction, retention, hold, agent authority, idempotency and post-check", "description": "Purpose-bound role views, field and cohort redaction, disclosure and export decisions, retention per data class and outcome, hold, deletion eligibility, minimum tombstone, delegated agent scope, preconditions, dry run, idempotency key, expected revision and post-condition verification.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-016" ], "questions": [ { "id": "purpose-access-redaction-retention-hold-agent-authority-idempotency-and-postcheck-q01", "text": "What process-scoped identities, classifications, criteria, roles, versions, values and explicit unknowns establish purpose, access, redaction, retention, hold, agent authority, idempotency and post-check?", "kind": "access", "answer_data": [ "identifiers and classifications", "criteria, roles and scope", "versions, values and explicit unknowns" ] }, { "id": "purpose-access-redaction-retention-hold-agent-authority-idempotency-and-postcheck-q02", "text": "Which authority, source, method, evidence, event time, knowledge time, confidence and limitations support purpose, access, redaction, retention, hold, agent authority, idempotency and post-check?", "kind": "measurement", "answer_data": [ "authority and source", "method and evidence", "event and knowledge time", "confidence, contradiction and limitations" ] }, { "id": "purpose-access-redaction-retention-hold-agent-authority-idempotency-and-postcheck-q03", "text": "How may purpose, access, redaction, retention, hold, agent authority, idempotency and post-check be validated, accessed, challenged, corrected, related, retained or disposed without losing prior recruitment history?", "kind": "classification", "answer_data": [ "validation and access rules", "challenge and authorized correction", "relations and lineage", "retention, hold and disposition" ] } ], "data_elements": [ { "id": "purpose-access-redaction-retention-hold-agent-authority-idempotency-and-postcheck-data", "name": "Purpose, access, redaction, retention, hold, agent authority, idempotency and post-check data", "description": "Structured recruitment-process data for purpose, access, redaction, retention, hold, agent authority, idempotency and post-check with scope, provenance, time, confidence and access marking.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-016" ] } ], "artifacts": [ { "id": "purpose-access-redaction-retention-hold-agent-authority-idempotency-and-postcheck-record", "name": "Purpose, access, redaction, retention, hold, agent authority, idempotency and post-check record", "description": "Versioned evidence-bearing recruitment-process record for purpose, access, redaction, retention, hold, agent authority, idempotency and post-check with authority, time, provenance and access marking.", "media_or_form": [ "logical recruitment assertion", "plan, reference, event, evidence, decision, outcome or governance record" ], "serial": true, "identity_strategy": "Recruitment process identifier plus purpose-access-redaction-retention-hold-agent-authority-idempotency-and-postcheck assertion, artifact or event identifier; title, candidate name, date, timestamp and digest never identify the process alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015", "SRC-016" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-recruitment-process", "name": "Register recruitment process", "description": "Create a stable aggregate identity and mandatory profile while resolving duplicate or reopened hiring processes.", "inputs": [ "authorized hiring need", "vacancy references", "process profile" ], "outputs": [ "versioned recruitment-process root" ], "preconditions": [ "identity, duplicate, profile, authority and boundary checks pass" ], "effects": [ "one process aggregate exists without copying vacancy, person or employment masters" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-012" ] }, { "id": "authorize-requisition-and-freeze-criteria", "name": "Authorize requisition and freeze criteria", "description": "Bind the approved need, position, headcount, budget, job analysis, criteria, policy and decision rules.", "inputs": [ "process root", "requisition", "job analysis", "approvals" ], "outputs": [ "authorized design release" ], "preconditions": [ "authority, funding, criteria, validity, scope and version checks pass" ], "effects": [ "later selection can be evaluated against the exact released basis" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012" ] }, { "id": "publish-and-source-candidates", "name": "Publish and source candidates", "description": "Release accessible postings and record source-qualified campaigns, referrals and outreach.", "inputs": [ "design release", "posting content", "channels", "sourcing plan" ], "outputs": [ "posting and sourcing event set" ], "preconditions": [ "content, channel, notice, accessibility, fee and source checks pass" ], "effects": [ "opportunity access and candidate origins remain inspectable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-009", "SRC-010", "SRC-013" ] }, { "id": "open-candidacy-and-control-data", "name": "Open candidacy and control data", "description": "Link a person and external application to the process with notice, lawful basis, minimization and rights routes.", "inputs": [ "candidate reference", "application", "notice", "purpose" ], "outputs": [ "process-scoped candidate-case link" ], "preconditions": [ "identity, duplicate, notice, purpose, access and consent-where-required checks pass" ], "effects": [ "candidate participation is recorded without absorbing the person master" ], "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-008", "SRC-012", "SRC-014" ] }, { "id": "screen-assess-and-interview", "name": "Screen, assess and interview", "description": "Execute frozen, job-related selection procedures with accessible alternatives and attributable evidence.", "inputs": [ "candidate-case link", "criterion release", "assessment and interview definitions" ], "outputs": [ "screening, assessment and interview evidence" ], "preconditions": [ "version, relevance, accommodation, authority, evidence and human-oversight checks pass" ], "effects": [ "observations and scores remain distinct from selection decisions" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-012", "SRC-013" ] }, { "id": "verify-rank-and-recommend", "name": "Verify, rank and recommend", "description": "Perform authorized checks and produce bounded rankings, shortlists or recommendations with conflicts and uncertainty visible.", "inputs": [ "selection evidence", "verification mandate", "criteria", "comparison set" ], "outputs": [ "verification evidence and recommendation" ], "preconditions": [ "purpose, legality, source, criterion, recusal, uncertainty and review checks pass" ], "effects": [ "recommendation does not become an automatic hiring decision" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012" ] }, { "id": "decide-and-issue-offer", "name": "Decide and issue offer", "description": "Record an accountable selection decision and issue a versioned, authorized offer with explicit contingencies.", "inputs": [ "shortlist or recommendation", "decision authority", "offer terms" ], "outputs": [ "selection decision and offer release" ], "preconditions": [ "authority, recusal, rationale, notice, approval, version and expiry checks pass" ], "effects": [ "decision and offer are attributable and remain separate from employment" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-012", "SRC-016" ] }, { "id": "record-response-and-close-or-handoff", "name": "Record response and close or hand off", "description": "Append acceptance, decline, withdrawal, rescission or cancellation and hand off only approved minimum data to contract, employment or onboarding masters.", "inputs": [ "offer release", "candidate response", "conditions", "handoff policy" ], "outputs": [ "response event, closure or governed handoff" ], "preconditions": [ "offer-version, authority, condition, minimization, acknowledgement and boundary checks pass" ], "effects": [ "offer acceptance is not silently converted into employment" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012", "SRC-016" ] }, { "id": "evaluate-fairness-quality-and-remedies", "name": "Evaluate fairness, quality and remedies", "description": "Calculate process-scoped metrics and adverse-impact indicators, preserve limitations and route complaints or improvements.", "inputs": [ "process events", "cohort definitions", "metric policy", "complaints" ], "outputs": [ "quality and fairness observations, remedy or improvement action" ], "preconditions": [ "denominator, small-sample, privacy, four-fifths, statistical-context and authority checks pass" ], "effects": [ "aggregate monitoring does not label individuals or claim legality from one ratio" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-014" ] }, { "id": "project-disclose-retain-and-audit", "name": "Project, disclose, retain and audit", "description": "Create version-pinned external views and perform controlled access, export, correction and information-lifecycle operations.", "inputs": [ "process revision", "target profile", "purpose", "policy" ], "outputs": [ "projection, disclosure, disposition or audit event" ], "preconditions": [ "mapping loss, privacy, redaction, hold, tombstone, idempotency and post-checks validate" ], "effects": [ "recruitment context remains interoperable, protected and accountable" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-015", "SRC-016" ] } ], "composition": [ { "target": "Organization, Organizational Unit, Position, Vacancy and Workforce Plan models", "relation": "REFERENCE", "purpose": "Resolve the authorized need and opportunity without copying organizational or vacancy masters.", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-010", "SRC-012" ] }, { "target": "Person, Candidate, Application, Qualification and Competency models", "relation": "REFERENCE", "purpose": "Bind candidate participation and evidence while preserving identity, rights and independent application lifecycles.", "required": true, "source_refs": [ "SRC-002", "SRC-005", "SRC-008", "SRC-010", "SRC-012", "SRC-014" ] }, { "target": "Assessment Definition, Assessment Result, Interview, Verification and Evidence models", "relation": "COMPOSE", "purpose": "Relate governed selection occurrences and evidence without absorbing their source identity, authority or correction history.", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-012" ] }, { "target": "Decision, Offer, Contract, Employment and Onboarding models", "relation": "REFERENCE", "purpose": "Link accountable decisions and controlled handoffs while keeping later proposal, agreement and work relationships independent.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-012" ] }, { "target": "Communication, Dataset, Artifact and Audit models", "relation": "REFERENCE", "purpose": "Keep messages, protected evidence, aggregate metrics, files and access logs in their authoritative systems.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-012", "SRC-014", "SRC-015" ] }, { "target": "ISO 30405:2023, ILO fair recruitment, EEOC UGESP, Schema.org JobPosting, ESCO and HR Open Standards", "relation": "ALIGN", "purpose": "Project process, fairness, posting, occupation, skill and HR exchange views through version-pinned mappings with declared legal and semantic loss.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-009", "SRC-010", "SRC-011" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, recruiting authority, hiring manager, human-resources, privacy, accessibility, equality, security, data and records stewards", "Hiring-need, requisition, vacancy, process, posting, sourcing, candidate-case, selection, decision, offer, outcome, complaint, interoperability, access and retention registries", "Master mappings for organizations, units, positions, vacancies, people, candidates, applications, competencies, qualifications, assessments, interviews, evidence, decisions, offers, contracts, employment, communications, datasets, artifacts and audit records", "Requisition approval, posting, sourcing, fair recruitment, candidate notice, accommodation, selection, automated decision, offer, handoff, complaint, correction, disclosure, retention and agent-operation policies" ], "namespace_guidance": "Mint stable IDs for process roots, design releases, postings, sourcing events, process-scoped candidacy links, selection occurrences, recommendations, decisions, offers, responses, closures, quality observations and lifecycle events. Preserve authoritative external vacancy, person, application, assessment, interview, evidence, offer, contract and employment identities; never use a candidate name, job title, requisition code, date or digest alone as process identity.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local hiring, vacancy, candidate, decision, offer and policy registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative source plus process identifier, mandatory process profile and lineage head, not by job title, requisition code, candidate, posting URL, date or digest.", "Keep vacancy, posting, candidate discovery, application, eligibility, assessment, interview, verification, recommendation, selection decision, offer, acceptance, contract and employment as distinct assertion classes." ], "patch_rules": [ "Extensions declare recruitment profile and jurisdiction, target finding, semantics, authority, lifecycle, fairness, privacy, accessibility, automation and interoperability effects.", "Released requisitions, criteria, postings, applications, evidence, recommendations, decisions, offers and outcomes are immutable; corrections create attributable successors and materially new or reopened hiring needs receive new or successor roots.", "A patch must never silently change job requirements, criteria, weights, candidate identity, accommodations, evidence, outcome, reason, notice or original event history." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when process identity, profile, requisition, criteria, candidate-case links, stages, evidence, decisions, outcomes, lifecycle and provenance remain intact.", "Schema.org, ESCO and HR Open mappings pin versions and declare omissions, semantic conflicts, access limits and round-trip loss." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system recruitment-process or hiring-campaign identifier qualified by source and process profile.", "Governed globally resolvable process IRI under a controlled namespace.", "Dimension UUID when no authoritative or governed global identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z; separate planned, effective, publication, submission, assessment, interview, decision, offer, response, event, ingestion and knowledge times and preserve source precision.", "serial_naming_rule": "Use {process-id}--{design-release-or-stage}--{artifact-kind}--{assertion-or-event-id}; never use candidate name, job title, requisition code, date, timestamp or digest alone.", "integrity_rule": "Store digest, media type, process and release binding, source and profile versions, requisition, criterion, posting, assessment and offer revisions, generating actor or tool, event and knowledge times, access marking and provenance." }, "policies": [ "Recruitment / Hiring Process is not the vacancy, candidate, application, selection instrument, interview, decision, offer, contract, employment relationship or onboarding process.", "Discovery, application, eligibility, qualification evidence, score, recommendation, selection, offer, acceptance, contract, employment and later performance remain separate source-qualified assertions.", "Process ownership does not transfer ownership of organization, position, vacancy, person, candidate, application, competency, qualification, assessment, interview, evidence, decision, offer, contract, employment, communication, dataset, artifact or audit masters. Process disposition never cascades to linked masters.", "Agents may validate, link, schedule and project allowlisted data, but candidate outreach, sensitive-data access, eligibility exceptions, adverse actions, rejection, final selection, offer issue, protected disclosure and disposition require delegated authority and applicable policies." ], "crud": { "read": [ "Resolve Dimension policies, process identity and lineage, profile, requisition and criterion bindings, postings, sourcing, candidate-case links, stages, evidence, decisions, offers, outcomes, complaints, provenance and access purpose." ], "create": [ "Record process identity and profile, exact hiring need, requisition, vacancy, job-analysis, criteria, authority, privacy, accessibility and policy bindings before publication or candidate processing." ], "update": [ "Append posting, sourcing, application, screening, assessment, interview, verification, recommendation, decision, offer, response, complaint, correction, cancellation, closure or supersession events with actor, authority, rationale, event and knowledge time and expected revision; never overwrite released history." ], "delete": [ "Apply candidate rights, employment, equality, privacy, records, retention and legal-hold policy; close or archive the process separately from deleting eligible working copies, destroy sensitive vetting data when required, preserve necessary decision evidence and minimum tombstone, and never cascade deletion to linked masters." ] }, "roles": [ { "name": "Hiring sponsor or accountable authority", "responsibilities": [ "Own the hiring mandate, approved need, resource envelope, responsible-party appointment and accountable closure." ] }, { "name": "Hiring manager or position steward", "responsibilities": [ "Own role need, duties, job analysis, position requirements and operational participation within delegated limits." ] }, { "name": "Recruitment or talent-acquisition steward", "responsibilities": [ "Own process design, posting, sourcing, candidate communications, stage coordination and source-system quality." ] }, { "name": "Selection and assessment authority", "responsibilities": [ "Own criterion releases, instrument validity, assessors, interview panels, moderation and bounded recommendations." ] }, { "name": "Authorized hiring decision-maker", "responsibilities": [ "Make and record the final selection and offer authorization with rationale, conflicts and applicable review routes." ] }, { "name": "Candidate-rights, accessibility and equality steward", "responsibilities": [ "Control notices, accommodations, fair access, complaints, remedies and aggregate adverse-impact review." ] }, { "name": "Privacy and security steward", "responsibilities": [ "Control lawful basis, sensitive-data compartments, processors, automation, protected views, disclosures and incidents." ] }, { "name": "Data, interoperability and records steward", "responsibilities": [ "Protect identity, mappings, versions, provenance, retention, holds, correction lineage and disposition evidence." ] } ], "access": { "default_rule": "Deny direct candidate identifiers, contact details, compensation history, health or accommodation data, diversity data, criminal or background information, references, assessment content, interview notes, rankings, predictions and decision rationale unless a purpose-bound Dimension policy permits the minimum necessary view. Aggregate fairness analysis uses governed de-identification or restricted statistics and never creates a public candidate label.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Candidate, recruiter, hiring manager, assessor, decision-maker, support worker, auditor, regulator or court access cites authority and remains minimum-necessary, time-limited and separately logged." ], "audit_requirements": [ "Log actor, agent, role, purpose, process, candidate-case scope, operation, policy, RFC 3339 time, release or affected fields, source revision and outcome without copying protected candidate data unnecessarily." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension hiring, equality, candidate-rights, fair-recruitment, accessibility, privacy, access, assessment, automated-decision, retention and agent-operation policies.", "Read this model and linked organization, position, vacancy, person, candidate, application, competency, qualification, assessment, interview, evidence, decision, offer, contract, employment, communication, dataset, artifact and audit models before mutation." ] } }, "coverage": { "claim": "Covers Recruitment / Hiring Process aggregate identity, profile, lifecycle, authorized need, requisition, job-analysis binding, posting, sourcing, candidate-case linking, screening, assessment, interview, verification, recommendation, accountable selection, offer, acceptance, closure, quality, fairness, interoperability roadmap and governed disposition with explicit boundary preservation, source-qualified evidence retention, privacy-access-redaction controls, and non-cascading external master ownership. Known gaps: approved composition-relation definitions, full source-text availability, jurisdiction-specific legal alignment, and independent provider review remain as documented deferred holds.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Process, design release, posting, candidate-case link, stage event, evidence, decision, offer, outcome and lifecycle identities are distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Single-vacancy, pooled, internal, contingent, agency, public-sector and cross-border profiles and neighboring boundaries are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Need, requisition, criteria, posting, sourcing, stages, evidence, decisions, offers, closure and quality are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Candidate discovery, selection observations, scores, verifications, metrics and fairness indicators retain source, method, time, confidence and limitations." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, authorize, publish, source, accept, evaluate, verify, decide, offer, close, review, project and retain are governed." }, { "dimension": "composition", "status": "gap", "notes": "Organizations, positions, vacancies, people, applications, assessments, interviews, decisions, offers, contracts and employment remain external masters. Proposed relations or mapping versions remain held for review." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, authorization, opening, pause, closure, fill, cancellation, correction, supersession and archive preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Need, position, vacancy, candidate-case, evidence, recommendation, decision, offer and handoff links are typed." }, { "dimension": "temporal", "status": "covered", "notes": "Planned, publication, submission, assessment, interview, decision, offer, response, effective, ingestion and knowledge times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Work location, applicant location, interview venue, remote context, jurisdiction and cross-border route remain source-qualified." }, { "dimension": "provenance", "status": "covered", "notes": "Plans, criteria, agents, sources, activities, evidence, decisions, offers, revisions and invalidations preserve provenance." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Sponsor, hiring manager, recruiter, assessor, decision-maker, rights, accessibility, privacy, data and records duties are separated." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, criterion revision, job relevance, evidence, authority, fairness, small-sample, offer and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose-bound views, candidate rights, accommodations, sensitive evidence and redacted projections are explicit." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Process archive, candidate-data deletion, vetting destruction, retained decision evidence, holds and tombstones are distinguished." }, { "dimension": "interoperability", "status": "gap", "notes": "Schema.org, ESCO and HR Open mappings are versioned and loss-aware. Proposed relations or mapping versions remain held for review." } ], "known_omissions": [ "No successful independent Claude or Grok result was available; recruitment, occupational-psychology, equality, accessibility, candidate-rights, regional and legal review is required before canonical promotion.", "The slash name covers multiple recruitment forms through a mandatory profile. Single-vacancy, pooled or evergreen, internal mobility, contingent, agency, public-sector and cross-border profiles require their own invariants.", "No approved relation rows were supplied. The registry parent link to Vacancy / Matching and proposed organization, person, application, assessment, decision, offer, contract and employment relations remain candidate holds.", "ISO 30405 full normative text was not available from the public abstract. HR Open downloads require registration or terms acceptance. ICO recruitment guidance remains draft. No full conformance or round-trip claim is made.", "EEOC UGESP and OPM apply to United States and federal contexts respectively; GDPR, EDPB and the AI Act are European Union sources; ICO guidance is United Kingdom specific. None supplies a universal hiring regime.", "Protected-class definitions, affirmative-action duties, accessibility, criminal checks, work authorization, automated decisions, notice, appeal, retention and recruitment-fee exceptions vary by jurisdiction and role." ], "conflicts": [ "Recruitment process, vacancy, requisition, campaign, candidate case, application, selection and hiring decision are used differently across systems. The mandatory profile and source mappings preserve those distinctions.", "Eligibility, qualification evidence, assessment score, recommendation, suitability, selection, offer, acceptance, contract, employment and performance can disagree and must not be collapsed.", "Candidate privacy and minimization, fairness monitoring, transparency, trade-secret or test security, auditability and hiring-manager discretion can impose competing requirements." ], "regional_assumptions": [ "Private, public, internal, contingent, agency, volunteer, platform, migrant and cross-border recruitment have different authority, equality, notice, screening, record and remedy rules.", "The EEOC four-fifths rule is a United States enforcement rule of thumb, not a legal definition of discrimination, a universal threshold or proof that a process is fair.", "The EU AI Act high-risk classification and GDPR automated-decision safeguards apply only within their legal scope; local profile and legal review remain mandatory." ], "adversarial_checks": [ "Reject a process without stable identity, mandatory profile, authorized need, exact requisition and criterion revisions, accountable owner and lifecycle head.", "Reject consent inferred from application, qualification inferred from a resume, eligibility inferred from sourcing, suitability inferred from one score, fairness inferred from an 80 percent ratio, employment inferred from offer acceptance or job performance inferred from an opaque model.", "Reject a reopened process, criterion change, correction or adverse action that overwrites prior postings, applications, evidence, recommendations, decisions, offers, notices or reasons.", "Reject copied person, vacancy, application, assessment, interview, offer, contract or employment masters whose independent identity, authority and lifecycle are lost.", "Reject agent outreach, sensitive-data access, eligibility exception, rejection, final selection, offer issue, protected disclosure or disposition outside delegated authority and applicable candidate-rights, equality, accessibility, privacy and retention controls." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "accepted", "rationale": "WM-ACT-039 correctly identifies as aggregate: owns bounded recruitment-process identity and lineage, mandatory profile, lifecycle, orchestrates external entities (Position, Vacancy, Person, Candidate, Application, Assessment, Interview, Offer, Contract, Employment) while preserving their independent ownership and identity, maintains typed neighbor relations with documented source support, and enforces non-cascading composition semantics. The frozen registry classification 'standalone-mm' refers to the record plane, not the subject model entry kind; schema enum 'aggregate' is the most defensible alternative within the required kinds (entity, event, relationship, mixin, pattern, registry, classifier, aggregate)." }, "decisions": [ { "concept": "Entry kind (aggregate) and mandatory profile", "disposition": "accepted", "rationale": "The model owns recruitment-process identity, design release, lifecycle state transitions (draft, authorized, open, paused, closed, filled, cancelled, corrected, superseded, archived), requisition and criterion bindings, posting versions, sourcing campaign references, process-scoped candidate-case links, stage orchestration, evidence and decision records, offer versioning, and closure lineage. This satisfies aggregate semantics: a bounded root with identity, lineage, composition relations, and governed lifecycle. The mandatory profile pattern supports single-vacancy, pooled, internal, contingent, agency, public-sector, and cross-border variants with shared orchestration semantics." }, { "concept": "Ownership boundary and neighbor separation", "disposition": "accepted", "rationale": "The model explicitly separates process ownership from external master ownership: process owns orchestration, evidence binding, and lifecycle assertions; Position, Vacancy, Person, Candidate, Application, Competency, Assessment, Interview, Offer, Contract, Employment remain external masters with independent authority and correction history. Non-cascading deletion rules, purpose-bound access controls, and minimum-tombstone preservation prevent master-lifecycle transfer and maintain audit evidence. Five documented neighbor boundaries (Position/Vacancy, Person/Candidate, Assessment/Interview, Recommendation/Decision/Offer, Contract/Employment) with source refs (SRC-001, 004, 012) are sound." }, { "concept": "Source authority tier and accessibility", "disposition": "accepted-with-publication-hold", "rationale": "All 16 sources are first-party official materials for their respective standards, laws, frameworks or guidance. ISO 30405 is available here only through its public catalogue abstract, HR Open downloads require registration or terms acceptance, and ICO recruitment guidance remains draft after consultation closed. EEOC and OPM are United States and United States federal sources, while GDPR, EDPB guidance and the AI Act are European Union sources. WCAG coverage describes the digital accessibility baseline but does not prove implementation conformance. Accept for reviewable draft with source-access, regional and interoperability holds." }, { "concept": "Composition relations and external master mappings", "disposition": "deferred", "rationale": "The model correctly identifies five neighbor boundaries with source support but states 'No approved relation rows were supplied. The registry parent link to Vacancy / Matching and proposed organization, person, application, assessment, decision, offer, contract and employment relations remain candidate holds.' Composition-relation definitions (cardinality, optionality, temporal ordering, deletion cascade limits) must be approved and synchronized with external master models before schema merge. Proposed relations list: Organization, Unit, Position, Vacancy (as neighbors), Person, Candidate, Application, Competency, Qualification, Assessment, Interview, Evidence, Decision, Offer, Contract, Employment. Deferral gate: approved relation contract signatures." }, { "concept": "Privacy, sensitive data, and access control architecture", "disposition": "accepted", "rationale": "Default-deny access model with purpose-bound role views (hiring sponsor, manager, recruiter, assessor, decision-maker, rights steward, privacy steward, records steward). Sensitive-data compartments (health, accommodation, diversity, criminal, background) with restricted access, minimum disclosure, and deletion eligibility rules. Candidate rights routes (notice, opt-out, correction, deletion, appeal, redaction) are explicit. Redaction strategy includes candidate-identifier, contact-detail, compensation, health, diversity, assessment-content, interview-note, ranking, and rationale redaction policies. Audit logging requirement for actor, role, purpose, process scope, operation, policy, RFC 3339 time, affected fields, and source revision without unnecessary protected-data copy." }, { "concept": "Adversarial check enforcement: inference rejection rules", "disposition": "accepted", "rationale": "The model explicitly rejects five inference collapses: (1) consent inferred from application, (2) qualification inferred from résumé or single document, (3) eligibility inferred from sourcing or discovery, (4) suitability inferred from one score, offer acceptance, or opaque model, (5) fairness inferred from 80-percent ratio or single metric without statistical and practical context. These rules are actionable, prevent category collapse, and block deterministic claims. Four-fifths rule cited as US enforcement heuristic, not universal proof of discrimination. Fairness indicators include conversion, stage volumes, candidate experience, adverse-impact measures with small-sample and limitations caveats." }, { "concept": "Interoperability and schema crosswalk (Schema.org, ESCO, HR Open)", "disposition": "deferred", "rationale": "Mappings are versioned (Schema.org current, ESCO v1.2.1, HR Open unversioned-requires-download) and loss-aware: document process, vacancy, posting, occupation, skill, candidate-case, application, stage, assessment, decision, offer mappings with declared omissions, semantic conflicts, access limits, and round-trip loss. Pinned source and target versions required. No full conformance or round-trip claim made. ICO guidance is draft. Round-trip testing must validate before interoperability claim; proposed relations held for standards review." }, { "concept": "Regional scope and jurisdiction-specific legal alignment", "disposition": "deferred", "rationale": "Model cites EEOC (US) and OPM (US federal) for selection procedures and hiring reform; GDPR, EDPB, and EU AI Act (European Union only); ICO (United Kingdom draft guidance). Private, public, internal, contingent, agency, volunteer, platform, and cross-border recruitment have different authority, equality, notice, screening, record and remedy rules per jurisdiction. Protected-class definitions, affirmative-action duties, accessibility (ADA vs. Equality Act 2010 vs. EU accessibility directives), criminal checks, work authorization, automated-decision safeguards, notice, appeal, and retention vary by region. Legal review required for each operational jurisdiction before promotion from reviewable-draft." }, { "concept": "Lifecycle and state-transition invariants", "disposition": "accepted", "rationale": "Lifecycle records typed events for draft, authorization, opening, pause, closure, fill, cancellation, correction, supersession and archive. Each transition records actor, authority, rationale, effective and recorded times, evidence and correction lineage. Reopened or repeat relations, predecessor and successor identity and version management preserve earlier released history. These are model rules and validation obligations, not a claim that every implementation already enforces immutability technically." }, { "concept": "Quality, fairness, and adverse-impact measurement framework", "disposition": "accepted-with-measurement-constraints", "rationale": "Process owns stage volume, time, conversion, source-qualified process quality, candidate-experience, fairness and adverse-impact observations at process scope. Group selection rates may be computed only where lawful, and the four-fifths rule is retained as a United States enforcement heuristic rather than a universal definition or proof of discrimination. Denominators, cohort definitions, statistical and practical context, sample-size limitations and improvement actions remain explicit. Downstream job performance is outside this aggregate and must not be inferred from process metrics." } ], "publicationHolds": [ "Codex single-provider fallback research: Claude Sonnet and Grok 4.6 each timed out on their one bounded 120-second attempt for WM-ACT-039. No external provider result was admitted. The source-grounded Codex fallback passed local schema validation and the required separate no-tools adversarial audit. The result remains reviewable-draft pending independent review or explicit owner authorization for canonical promotion, and this hold must remain visible.", "Source access and version verification: official public pages were consulted for all 16 sources, but ISO 30405 was available only as a catalogue abstract, HR Open downloads require registration or terms acceptance, and ICO recruitment guidance remains draft. Re-fetch and pin every accepted source at canonical promotion. GDPR and the AI Act are final official EU regulations, not draft texts.", "Composition relation definitions and the registry parent link to Vacancy / Matching remain candidate proposals because no approved relation rows were supplied. Synchronize typed identity, cardinality, ownership, temporal and no-cascade contracts with the external masters before claiming composition completeness; this does not block publication of the internally valid reviewable draft.", "Jurisdiction-specific legal alignment review across United States, European Union, United Kingdom and other regional profiles is required before canonical promotion. Protected-class definitions, affirmative-action duties, accessibility, criminal checks, work authorization, automated-decision notice and appeal, retention, recruitment-fee exceptions and remedy routes vary by region. No universal hiring regime is claimed.", "Interoperability schema-version pins and round-trip testing: Schema.org current, ESCO v1.2.1 (updated 2025-12-10), HR Open (unversioned, requires download and terms review). Semantic conflicts, access limits, and loss-aware mappings documented; pinned versions required before certification. ICO guidance remains draft.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Detailed recruitment-profile variant invariants per form class: single-vacancy, pooled/evergreen, internal mobility, contingent, agency, public-sector, cross-border. Mandatory profile addresses shared orchestration but variants require distinct closed-world assumptions, approval authority, retention, remedy, and fairness-metric constraints per form.", "Full ISO 30405:2023 normative text retrieval and normative conformance validation; HR Open schema structure, versioning discipline, and round-trip cardinality validation; ICO recruitment guidance promotion from draft to final with UK equality and data-protection specifics.", "Independent occupational psychology, assessment-science, and test-validity review: criterion development methods, job-relevance documentation, predictive-validity evidence, differential-prediction analysis, adverse-impact indicators, alternative-assessment recommendations per role and jurisdiction.", "Candidate-experience audit and WCAG 2.2 accessibility conformance testing: posting language and simplicity, application-process friction, assessment-alternative provision, interview accommodation, feedback timing, rejection-reason disclosure, appeal-route clarity, communication accessibility (audio/video/text/plain-language variants).", "Independent external-provider review (Claude, Grok, or equivalent) after publication hold expires or owner reauthorizes. Single-provider artifact is time-bounded reviewable-draft." ] }, "statistics": { "sources": 16, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }