# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T15:13:03Z", "synthesisSha256": "1d354b846b049a4cdcedc5c2d7527c7baf0c77245202acf4ec14d90136623cbd", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ORG-008", "registryId": "vr.wm-org-008", "name": "Vacancy / Matching", "version": "0.3.0-draft", "previousVersions": [ { "version": "0.2.0-legacy", "url": "https://github.com/ver-cy/world-models/blob/feat/mega-model-registry/models/organizations/O6-labor-market-and-vacancy.md" } ], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ORG.VAC" ], "tags": [ "vacancy", "matching", "soc.org.vac" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-org-008-vacancy-matching/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-org-008", "model": { "registry_id": "vr.wm-org-008", "model_id": "WM-ORG-008", "name": "Vacancy / Matching", "entry_kind": "aggregate", "purpose": "Describe a vacancy-centered market interaction: advertised demand, scoped candidacies, match proposals and evidence of offers and placement outcomes.", "scope_statement": "One aggregate is anchored to one vacancy master identity, with zero or more channel postings and candidate-vacancy interaction records. It governs the local consistency of those records and their evidence references, not the whole labor market, an entire person dossier, a recruitment workflow or an employment relationship. All hierarchy and operation choices are proposed design informed by sources, not source-mandated schemas.", "in_scope": [ "Vacancy identity, authenticity review, publication aliases, advertised requirements and conditions.", "Purpose-limited candidacy snapshots, applications, withdrawals, match rationale and referenced screening outcomes.", "Offer-version and response evidence, placement assertions, partial filling and separate observed-start evidence.", "Side-specific stewardship, disclosure, contestation, retention and source lineage for these records." ], "out_of_scope": [ "Recruitment / Hiring Process WM-ACT-039 owns stages, interview scheduling, selection workflow and operational hiring decisions.", "Person WM-PER-001 owns person identity and reusable profile masters; Organization WM-ORG-001 and Organizational Unit WM-ORG-002 own organizational structures.", "Employment WM-ORG-005 owns the employment relationship and post-start lifecycle; Membership WM-ORG-006 is not implied by the legacy O3 alias.", "Algorithm training, psychometric test design, background-check execution, payroll, immigration adjudication and legal compliance engines.", "Population-wide labor-market statistics, autonomous rejection, autonomous offer issuance and external posting delivery." ], "boundary_notes": [ { "neighbor": "WM-ACT-039 Recruitment / Hiring Process", "distinction": "The registry lists WM-ORG-008 as a parent candidate. Treat this as domain alignment, not runtime inheritance: this aggregate stores scoped outcome references, while the process model owns stage transitions and decision execution.", "source_refs": [ "SRC-003", "SRC-005" ] }, { "neighbor": "WM-PER-001 Person and WM-ORG-001 Organization", "distinction": "References resolve separately stewarded masters. Local candidate snapshots do not confer ownership of the person or unrestricted rights over personal information.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "WM-ORG-005 Employment", "distinction": "Placement, accepted terms, planned start and observed start are separate assertions. A local placement record never creates an employment relationship or proves legal formation.", "source_refs": [ "SRC-003", "SRC-007" ] }, { "neighbor": "Position, occupation and classification", "distinction": "A posting may advertise several openings; an occupation code describes work rather than identifying a position slot or proving a candidate skill. Location eligibility is separate from work authorization.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "O6 legacy specification and unreviewed card supplement", "distinction": "Retain the demand/supply interaction lead. Replace wildcard imports, mandatory one-to-one offer/placement links, consent-only assumptions and employment COMPOSE with explicit profile decisions and external references. No inherited conformance claim is admitted.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "JobPosting", "organization": "Schema.org community", "url": "https://schema.org/JobPosting", "version_or_date": "Development page observed 2026-10-06; no stable release pin", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:11:42Z", "relevance": "Public posting identity and advertised terms; vocabulary alignment only." }, { "id": "SRC-002", "title": "The ESCO Classification", "organization": "European Commission", "url": "https://esco.ec.europa.eu/en/classification", "version_or_date": "Page displays ESCO v1.2.1, last update 10/12/2025; dataset not downloaded", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:11:42Z", "relevance": "Occupation and skill concepts, multilingual labels and classification mappings; not evidence of individual competence." }, { "id": "SRC-003", "title": "General principles and operational guidelines for fair recruitment", "organization": "International Labour Organization", "url": "https://www.ilo.org/sites/default/files/wcmsp5/groups/public/@ed_protect/@protrav/@migrant/documents/publication/wcms_536263.pdf", "version_or_date": "2016 guidelines, publication page dated 2016-11-25", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T15:11:42Z", "relevance": "Non-binding international guidance on recruitment actors, transparent terms, fees, voluntary agreement and grievances." }, { "id": "SRC-004", "title": "Employment Tests and Selection Procedures", "organization": "U.S. Equal Employment Opportunity Commission", "url": "https://www.eeoc.gov/laws/guidance/employment-tests-and-selection-procedures", "version_or_date": "Technical assistance issued 2007-12-01; current legal applicability not verified", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T15:11:42Z", "relevance": "US example of selection validity, job relevance, adverse impact and accommodation review." }, { "id": "SRC-005", "title": "Recruitment rewired: an update on the fair and responsible use of automation in recruitment", "organization": "Information Commissioner's Office", "url": "https://ico.org.uk/about-the-ico/what-we-do/recruitment-rewired/", "version_or_date": "2026 report; voluntary engagement March 2025 to January 2026; executive summary", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T15:11:42Z", "relevance": "Meaningful human involvement, transparency and fairness in automated recruitment; UK-specific regulatory discussion." }, { "id": "SRC-006", "title": "Recruitment rewired: Lawful basis", "organization": "Information Commissioner's Office", "url": "https://ico.org.uk/about-the-ico/what-we-do/recruitment-rewired/key-findings-how-are-employers-automating-their-recruitment-processes/lawful-basis/", "version_or_date": "2026 report section, includes discussion of changed UK legislation", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T15:11:42Z", "relevance": "Purpose-specific processing basis and limits of assuming consent; not a universal lawful-basis determination." }, { "id": "SRC-007", "title": "Keeping recruitment records", "organization": "Information Commissioner's Office", "url": "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/employment/recruitment-and-selection/keeping-recruitment-records/", "version_or_date": "Draft guidance under review, observed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T15:11:42Z", "relevance": "Purpose-based retention, selective employment handoff and distinction between anonymisation and pseudonymisation." }, { "id": "SRC-008", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation 2013-04-30; sections 3.1 and 3.2", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:11:42Z", "relevance": "Entity, activity, attribution, derivation and revision concepts for evidence lineage; no truth or authority certification." } ], "structure": { "bundles": [ { "id": "bundle-vacancy", "name": "Vacancy identity and publication", "description": "Vacancy identity and publication for a single vacancy-centered interaction aggregate.", "rationale": "Group related local evidence and references while preserving external masters and scoped authority.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "layers": [ { "id": "layer-identity", "name": "Identity and authenticity", "description": "Anchor aliases and publication copies to a scoped vacancy identity; distinguish an authorized opening from an unverified advertisement or a general talent-pool invitation.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "finding-vacancy-identity", "name": "Recognized vacancy", "description": "Anchor aliases and publication copies to a scoped vacancy identity; distinguish an authorized opening from an unverified advertisement or a general talent-pool invitation.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "questions": [ { "id": "vacancy-identity-q1", "text": "Which master identity distinguishes this vacancy from its channel postings and possible duplicates?", "kind": "identity", "answer_data": [ "vacancy_id", "master_namespace", "posting_aliases", "duplicate_review" ] }, { "id": "vacancy-identity-q2", "text": "What evidence identifies the hiring party and the authority of the posting intermediary?", "kind": "authority", "answer_data": [ "hiring_party_ref", "poster_ref", "delegation_evidence", "verification_state" ] }, { "id": "vacancy-identity-q3", "text": "Is this a specific opening, an evergreen interest invitation or an unverified claim of demand?", "kind": "quality", "answer_data": [ "demand_kind", "opening_count_or_unknown", "authenticity_review", "evidence_ref" ] } ], "data_elements": [ { "id": "data-vacancy-key", "name": "Vacancy key", "description": "Candidate field group for recognized vacancy. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "data-posting-aliases", "name": "Posting aliases and authority evidence", "description": "Candidate field group for recognized vacancy. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-vacancy-identity", "name": "Vacancy identity dossier", "description": "A scoped evidence representation of recognized vacancy, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-publication", "name": "Publication lifecycle", "description": "Track source and channel observations separately. Closing a master does not prove all syndicated copies have been removed, and expiry of a posting does not prove the vacancy was filled.", "source_refs": [ "SRC-001", "SRC-008" ], "findings": [ { "id": "finding-posting-state", "name": "Publication state", "description": "Track source and channel observations separately. Closing a master does not prove all syndicated copies have been removed, and expiry of a posting does not prove the vacancy was filled.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "posting-state-q1", "text": "What is the master vacancy state and which channel copies still report a different state?", "kind": "state", "answer_data": [ "master_state", "channel_states", "disagreement_reason" ] }, { "id": "posting-state-q2", "text": "Which publication and expiry instants or date-only values govern each advertised revision?", "kind": "temporal", "answer_data": [ "posted_at", "valid_through", "time_precision", "zone", "observed_at" ] }, { "id": "posting-state-q3", "text": "What evidence explains closure, reopening or partial filling without reusing a different vacancy identity?", "kind": "lifecycle", "answer_data": [ "transition", "reason", "prior_revision", "filled_count", "remaining_count", "evidence_ref" ] } ], "data_elements": [ { "id": "data-publication-revisions", "name": "Publication revisions", "description": "Candidate field group for publication state. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "data-vacancy-status", "name": "Vacancy status and capacity", "description": "Candidate field group for publication state. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-posting-state", "name": "Posting revision record", "description": "A scoped evidence representation of publication state, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-requirements", "name": "Advertised work and terms", "description": "Advertised work and terms for a single vacancy-centered interaction aggregate.", "rationale": "Group related local evidence and references while preserving external masters and scoped authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ], "layers": [ { "id": "layer-competence", "name": "Requirements and equivalence", "description": "Preserve required versus preferred criteria, alternatives and evidence expectations. Classifications assist interpretation; they do not establish equivalence, competence or lawful exclusion.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "finding-requirements-profile", "name": "Versioned requirements", "description": "Preserve required versus preferred criteria, alternatives and evidence expectations. Classifications assist interpretation; they do not establish equivalence, competence or lawful exclusion.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "requirements-profile-q1", "text": "Which occupation and skill concepts describe the work, using which vocabulary release and language?", "kind": "classification", "answer_data": [ "occupation_uri", "skill_uris", "vocabulary_version", "language", "local_labels" ] }, { "id": "requirements-profile-q2", "text": "Which requirements are mandatory, preferred or alternative routes and what evidence is acceptable?", "kind": "requirement", "answer_data": [ "criterion_id", "priority", "alternatives", "evidence_expectation", "equivalence_review" ] }, { "id": "requirements-profile-q3", "text": "What job-relevance review and accommodation route apply before a criterion can exclude a candidate?", "kind": "constraint", "answer_data": [ "job_relevance_basis", "applicable_profile", "reviewer", "accommodation_route", "review_state" ] } ], "data_elements": [ { "id": "data-criteria", "name": "Requirement criteria and alternatives", "description": "Candidate field group for versioned requirements. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-classification-bindings", "name": "Versioned classification bindings", "description": "Candidate field group for versioned requirements. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-requirements-profile", "name": "Requirement profile revision", "description": "A scoped evidence representation of versioned requirements, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-conditions", "name": "Conditions and location", "description": "Keep advertiser-stated compensation distinct from third-party estimates. Preserve unit, currency, hours, location and remote constraints without equating geographic eligibility with legal work authorization.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "finding-advertised-terms", "name": "Advertised conditions", "description": "Keep advertiser-stated compensation distinct from third-party estimates. Preserve unit, currency, hours, location and remote constraints without equating geographic eligibility with legal work authorization.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "advertised-terms-q1", "text": "What compensation is advertised, in what currency and time basis, and is it an estimate or an employer statement?", "kind": "measurement", "answer_data": [ "amount_or_range", "currency", "pay_period", "gross_net_or_unknown", "estimate_flag", "source" ] }, { "id": "advertised-terms-q2", "text": "Where may the work be performed and which location restrictions differ from work-authorization conditions?", "kind": "spatial", "answer_data": [ "work_locations", "remote_mode", "applicant_location_rule", "authorization_rule_ref" ] }, { "id": "advertised-terms-q3", "text": "What duties, hours, duration, benefits and contract category are offered in this revision?", "kind": "definition", "answer_data": [ "duties", "schedule", "duration", "contract_category", "benefits", "revision_id" ] } ], "data_elements": [ { "id": "data-terms", "name": "Advertised terms with units and attribution", "description": "Candidate field group for advertised conditions. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-location-policy", "name": "Work and applicant location rules", "description": "Candidate field group for advertised conditions. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-advertised-terms", "name": "Advertised terms snapshot", "description": "A scoped evidence representation of advertised conditions, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-candidacy", "name": "Candidacy and disclosure", "description": "Candidacy and disclosure for a single vacancy-centered interaction aggregate.", "rationale": "Group related local evidence and references while preserving external masters and scoped authority.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-submission", "name": "Submission and withdrawal", "description": "Distinguish an initiated application, a referral and a match suggestion. Candidate identity stays in its master; each local candidacy identifies the vacancy and the actual evidence of submission or withdrawal.", "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ], "findings": [ { "id": "finding-application-record", "name": "Scoped candidacy", "description": "Distinguish an initiated application, a referral and a match suggestion. Candidate identity stays in its master; each local candidacy identifies the vacancy and the actual evidence of submission or withdrawal.", "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ], "questions": [ { "id": "application-record-q1", "text": "Which candidate and vacancy does this candidacy link, and was it submitted, referred or merely proposed?", "kind": "relationship", "answer_data": [ "candidate_ref", "vacancy_ref", "candidacy_kind", "submission_evidence" ] }, { "id": "application-record-q2", "text": "What receipt and dossier revision establish the actual application submission?", "kind": "event", "answer_data": [ "application_id", "received_at", "submitted_at_or_unknown", "dossier_revision_ref", "receipt_ref" ] }, { "id": "application-record-q3", "text": "How are withdrawal, duplicate submission or transfer to another vacancy recorded without erasing earlier evidence?", "kind": "exception", "answer_data": [ "withdrawal_event", "duplicate_links", "transfer_authorization", "new_candidacy_ref", "retention_review" ] } ], "data_elements": [ { "id": "data-candidacy-key", "name": "Candidacy identity and relationship", "description": "Candidate field group for scoped candidacy. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] }, { "id": "data-submission-events", "name": "Submission and withdrawal assertions", "description": "Candidate field group for scoped candidacy. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-application-record", "name": "Candidacy receipt record", "description": "A scoped evidence representation of scoped candidacy, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-disclosure", "name": "Dossier disclosure", "description": "A candidate-directed dossier view is distinct from the processing basis relied on by a recipient. Do not assume universal consent, shared ownership of every note, or entitlement to another candidacy.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-disclosure-scope", "name": "Purpose-limited candidate view", "description": "A candidate-directed dossier view is distinct from the processing basis relied on by a recipient. Do not assume universal consent, shared ownership of every note, or entitlement to another candidacy.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "disclosure-scope-q1", "text": "Who stewards the original dossier and who is accountable for this recipient copy and its purpose?", "kind": "ownership", "answer_data": [ "source_steward_ref", "recipient_ref", "accountability_role", "purpose", "copy_id" ] }, { "id": "disclosure-scope-q2", "text": "What processing basis, notice and disclosure scope support each use of candidate information?", "kind": "privacy", "answer_data": [ "lawful_basis_ref", "notice_version", "fields_disclosed", "purpose", "consent_record_if_applicable" ] }, { "id": "disclosure-scope-q3", "text": "Which recipient may read which dossier revision, and what happens when permission or purpose changes?", "kind": "access", "answer_data": [ "recipient_grants", "artifact_scope", "expiry", "revocation_effect", "residual_copy_review" ] } ], "data_elements": [ { "id": "data-disclosure-register", "name": "Scoped disclosure and processing basis records", "description": "Candidate field group for purpose-limited candidate view. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-dossier-links", "name": "Authorized dossier revision references", "description": "Candidate field group for purpose-limited candidate view. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-disclosure-scope", "name": "Disclosure receipt", "description": "A scoped evidence representation of purpose-limited candidate view, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-matching", "name": "Matching and assessment evidence", "description": "Matching and assessment evidence for a single vacancy-centered interaction aggregate.", "rationale": "Group related local evidence and references while preserving external masters and scoped authority.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-008" ], "layers": [ { "id": "layer-proposal", "name": "Match proposals", "description": "A proposal links one candidate view to one vacancy revision. It carries evidence and uncertainty; a score is neither an application nor permission to reject. Candidate preference may differ from employer ranking.", "source_refs": [ "SRC-002", "SRC-005", "SRC-008" ], "findings": [ { "id": "finding-match-rationale", "name": "Qualified match proposal", "description": "A proposal links one candidate view to one vacancy revision. It carries evidence and uncertainty; a score is neither an application nor permission to reject. Candidate preference may differ from employer ranking.", "source_refs": [ "SRC-002", "SRC-005", "SRC-008" ], "questions": [ { "id": "match-rationale-q1", "text": "Which actor or method proposed this pair using which candidate, vacancy and rule revisions?", "kind": "provenance", "answer_data": [ "proposer_ref", "method_version", "candidate_view_ref", "vacancy_revision", "rule_revision" ] }, { "id": "match-rationale-q2", "text": "What does a reported match score measure and how are missing evidence, ties and uncertainty represented?", "kind": "measurement", "answer_data": [ "score_or_absent", "scale", "interpretation", "missing_fields", "tie_rule", "uncertainty" ] }, { "id": "match-rationale-q3", "text": "What candidate preferences and unmet conditions qualify the proposal before a person acts on it?", "kind": "decision", "answer_data": [ "preference_snapshot", "unmet_conditions", "explanation", "review_state", "permitted_next_action" ] } ], "data_elements": [ { "id": "data-match-proposal", "name": "Proposal identity and revision inputs", "description": "Candidate field group for qualified match proposal. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005", "SRC-008" ] }, { "id": "data-match-explanation", "name": "Score and explanation evidence", "description": "Candidate field group for qualified match proposal. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-match-rationale", "name": "Match proposal record", "description": "A scoped evidence representation of qualified match proposal, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-002", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-assessment", "name": "Assessment outcome references", "description": "Reference assessments and decisions owned by the hiring process. A local summary records method, stage, evidence quality and review; it does not execute tests, advance candidates or certify nondiscrimination.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008" ], "findings": [ { "id": "finding-screening-evidence", "name": "Assessment and review evidence", "description": "Reference assessments and decisions owned by the hiring process. A local summary records method, stage, evidence quality and review; it does not execute tests, advance candidates or certify nondiscrimination.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008" ], "questions": [ { "id": "screening-evidence-q1", "text": "Which process-owned assessment supports the recorded screening outcome and which version was used?", "kind": "evidence", "answer_data": [ "process_ref", "assessment_ref", "stage_ref", "outcome", "method_version" ] }, { "id": "screening-evidence-q2", "text": "What validation, job-relevance and adverse-impact review supports the use of this assessment in this context?", "kind": "validation", "answer_data": [ "validation_ref", "job_context", "impact_review_ref", "limitations", "review_date" ] }, { "id": "screening-evidence-q3", "text": "What meaningful reviewer involvement and accessible alternative applied at the relevant decision stage?", "kind": "process", "answer_data": [ "reviewer_ref", "reviewed_inputs", "ability_to_change", "review_rationale", "accommodation_evidence_ref" ] } ], "data_elements": [ { "id": "data-assessment-links", "name": "Process-owned assessment links", "description": "Candidate field group for assessment and review evidence. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-008" ] }, { "id": "data-review-summary", "name": "Bounded assessment review summary", "description": "Candidate field group for assessment and review evidence. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-screening-evidence", "name": "Assessment evidence index", "description": "A scoped evidence representation of assessment and review evidence, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-outcome", "name": "Offers and placement evidence", "description": "Offers and placement evidence for a single vacancy-centered interaction aggregate.", "rationale": "Group related local evidence and references while preserving external masters and scoped authority.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-offer", "name": "Offer revisions and responses", "description": "Record links to authorized offer versions and actual responses. Multiple or revised offers are possible; a match need not originate in a formal application. A receipt is not acceptance, and local state is not a legal formation judgment.", "source_refs": [ "SRC-003", "SRC-008" ], "findings": [ { "id": "finding-offer-response", "name": "Offer and response evidence", "description": "Record links to authorized offer versions and actual responses. Multiple or revised offers are possible; a match need not originate in a formal application. A receipt is not acceptance, and local state is not a legal formation judgment.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "offer-response-q1", "text": "Which authorized issuer and offer revision underpin the terms communicated to this candidate?", "kind": "authority", "answer_data": [ "offer_master_ref", "issuer_ref", "authority_ref", "terms_revision", "communication_evidence" ] }, { "id": "offer-response-q2", "text": "What response deadline, conditions and later term changes applied to the offer being considered?", "kind": "temporal", "answer_data": [ "response_deadline", "timezone_or_date_precision", "conditions", "supersedes", "changed_terms" ] }, { "id": "offer-response-q3", "text": "What evidence distinguishes acceptance, decline, lapse, withdrawal or an unresolved response?", "kind": "state", "answer_data": [ "response_kind", "response_evidence", "actor_ref", "event_time", "observation_time", "disputed_state" ] } ], "data_elements": [ { "id": "data-offer-references", "name": "Offer versions and response references", "description": "Candidate field group for offer and response evidence. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "data-term-differences", "name": "Differences from advertised conditions", "description": "Candidate field group for offer and response evidence. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-offer-response", "name": "Offer response evidence record", "description": "A scoped evidence representation of offer and response evidence, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-placement", "name": "Placement and handoff", "description": "Preserve placement assertions, planned starts and observed starts independently. Successful matching does not automatically create employment. Unsuccessful, withdrawn and unknown outcomes remain representable.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "findings": [ { "id": "finding-placement-assertion", "name": "Observed placement outcome", "description": "Preserve placement assertions, planned starts and observed starts independently. Successful matching does not automatically create employment. Unsuccessful, withdrawn and unknown outcomes remain representable.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "questions": [ { "id": "placement-assertion-q1", "text": "Who confirms the placement and what separate evidence establishes a planned or actual start?", "kind": "evidence", "answer_data": [ "placement_assertor", "confirmation_ref", "planned_start", "actual_start_or_unknown", "start_evidence" ] }, { "id": "placement-assertion-q2", "text": "Which independently mastered employment record is linked, if any, and what minimum information is authorized for handoff?", "kind": "composition", "answer_data": [ "employment_ref_or_absent", "handoff_fields", "purpose", "authorization_ref", "receipt" ] }, { "id": "placement-assertion-q3", "text": "How do failed starts, rescinded offers or partial fills change the outcome without inflating placement totals?", "kind": "quality", "answer_data": [ "outcome_kind", "correction_ref", "count_basis", "vacancy_capacity_revision", "uncertainty" ] } ], "data_elements": [ { "id": "data-placement-record", "name": "Placement assertion and start evidence", "description": "Candidate field group for observed placement outcome. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] }, { "id": "data-handoff-receipts", "name": "Employment handoff references", "description": "Candidate field group for observed placement outcome. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-placement-assertion", "name": "Placement outcome record", "description": "A scoped evidence representation of observed placement outcome, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Fairness and record continuity", "description": "Fairness and record continuity for a single vacancy-centered interaction aggregate.", "rationale": "Group related local evidence and references while preserving external masters and scoped authority.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-challenge", "name": "Concerns and contestation", "description": "Record policy-level concerns about fees, misrepresentation, coercion, discriminatory criteria or inaccessible assessment. Case investigation and remedies remain with the competent external process; no blacklisting follows from a concern.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-concern-review", "name": "Recruitment concern route", "description": "Record policy-level concerns about fees, misrepresentation, coercion, discriminatory criteria or inaccessible assessment. Case investigation and remedies remain with the competent external process; no blacklisting follows from a concern.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "concern-review-q1", "text": "What recruitment-fee and intermediary-conduct policy applies, and what evidence raises a concern?", "kind": "constraint", "answer_data": [ "policy_ref", "intermediary_ref", "fee_or_conduct_concern", "evidence_ref" ] }, { "id": "concern-review-q2", "text": "What accessible explanation and challenge route can the affected candidate use?", "kind": "access", "answer_data": [ "notice_ref", "explanation_view", "accessible_channel", "challenge_process_ref" ] }, { "id": "concern-review-q3", "text": "How are sensitive concern records separated from routine ranking and protected against retaliatory use?", "kind": "security", "answer_data": [ "restricted_scope", "authorized_roles", "prohibited_uses", "escalation_ref", "access_audit_ref" ] } ], "data_elements": [ { "id": "data-concern-links", "name": "Restricted concern and remedy process references", "description": "Candidate field group for recruitment concern route. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "id": "data-fairness-review", "name": "Policy and fairness review references", "description": "Candidate field group for recruitment concern route. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-concern-review", "name": "Restricted concern receipt", "description": "A scoped evidence representation of recruitment concern route, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-continuity", "name": "Retention and interchange", "description": "Keep attributable revisions only for justified periods. Employment handoff is selective; a talent pool is a new purpose requiring review. Pseudonymous records are not automatically anonymous.", "source_refs": [ "SRC-007", "SRC-008", "SRC-001" ], "findings": [ { "id": "finding-record-continuity", "name": "Record continuity and disposal", "description": "Keep attributable revisions only for justified periods. Employment handoff is selective; a talent pool is a new purpose requiring review. Pseudonymous records are not automatically anonymous.", "source_refs": [ "SRC-007", "SRC-008", "SRC-001" ], "questions": [ { "id": "record-continuity-q1", "text": "Which retention trigger, period and hold apply to each local recruitment record and its copies?", "kind": "retention", "answer_data": [ "record_category", "trigger", "duration", "hold_ref", "review_at", "disposition_owner" ] }, { "id": "record-continuity-q2", "text": "Which identifiers and meanings are lost when exporting a posting or exchanging recruitment evidence?", "kind": "interoperability", "answer_data": [ "mapping_version", "source_target_ids", "loss_report", "vocabulary_pin", "recipient_scope" ] }, { "id": "record-continuity-q3", "text": "What confirms authorized disposal or a justified residual record after a purpose ends?", "kind": "lifecycle", "answer_data": [ "disposition_decision", "executor_ref", "receipt", "residual_fields", "tombstone_basis", "downstream_status" ] } ], "data_elements": [ { "id": "data-retention-register", "name": "Record-category retention decisions", "description": "Candidate field group for record continuity and disposal. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008", "SRC-001" ] }, { "id": "data-mapping-evidence", "name": "Mapping and disposition receipts", "description": "Candidate field group for record continuity and disposal. Preserve source reference, revision, unknown values and field-level access; nested schema requires an adopting profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008", "SRC-001" ] } ], "artifacts": [ { "id": "artifact-record-continuity", "name": "Continuity and disposition record", "description": "A scoped evidence representation of record continuity and disposal, with issuer, source revision, event and observation time, access class and retention decision.", "media_or_form": [ "structured record", "controlled document reference" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier and revision; otherwise a governed IRI, then a Dimension-assigned UUID. Link vacancy and local record IDs; dates and content digests are not identity.", "source_refs": [ "SRC-007", "SRC-008", "SRC-001" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-register-vacancy", "name": "Register a local vacancy revision", "description": "Proposed, unimplemented local operation. Record a scoped master reference and posting aliases after identity review.", "inputs": [ "vacancy identity", "authority evidence", "source revision" ], "outputs": [ "local revision receipt", "duplicate or authority refusal" ], "preconditions": [ "Authorized local role, purpose and expected record revision are supplied.", "A duplicate check and posting authority review are recorded.", "Reject unresolved authority or stale revision; do not infer missing facts." ], "effects": [ "Create local evidence only; no public posting is transmitted.", "Record actor, input revisions and result evidence under applicable retention policy." ], "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "function-record-candidacy", "name": "Record candidacy evidence", "description": "Proposed, unimplemented local operation. Link a permitted candidate view and actual submission or referral evidence.", "inputs": [ "candidate reference", "vacancy reference", "disclosure scope", "receipt" ], "outputs": [ "candidacy receipt", "unresolved reference refusal" ], "preconditions": [ "Authorized local role, purpose and expected record revision are supplied.", "The purpose, recipient access and actual candidacy kind are known.", "Reject unresolved authority or stale revision; do not infer missing facts." ], "effects": [ "Create a scoped local record; do not submit an application or copy the full person master.", "Record actor, input revisions and result evidence under applicable retention policy." ], "source_refs": [ "SRC-003", "SRC-006", "SRC-008" ] }, { "id": "function-record-match", "name": "Record a match proposal", "description": "Proposed, unimplemented local operation. Store an externally produced or human-authored proposal with its method and uncertainty.", "inputs": [ "pair references", "input revisions", "rationale", "score meaning" ], "outputs": [ "proposal receipt", "missing provenance refusal" ], "preconditions": [ "Authorized local role, purpose and expected record revision are supplied.", "The candidate view is authorized and a score, if present, has a defined scale.", "Reject unresolved authority or stale revision; do not infer missing facts." ], "effects": [ "No ranking engine runs and no candidate is advanced or rejected.", "Record actor, input revisions and result evidence under applicable retention policy." ], "source_refs": [ "SRC-002", "SRC-005", "SRC-008" ] }, { "id": "function-link-offer-response", "name": "Link offer response evidence", "description": "Proposed, unimplemented local operation. Attach a response to an exact externally authorized offer revision.", "inputs": [ "offer revision reference", "response evidence", "issuer authority" ], "outputs": [ "linked response receipt", "ambiguous-version refusal" ], "preconditions": [ "Authorized local role, purpose and expected record revision are supplied.", "Issuer and respondent identities and permissions are resolved.", "Reject unresolved authority or stale revision; do not infer missing facts." ], "effects": [ "Record an assertion only; do not issue, accept, revoke or legally interpret an offer.", "Record actor, input revisions and result evidence under applicable retention policy." ], "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "function-record-placement", "name": "Record a placement assertion", "description": "Proposed, unimplemented local operation. Preserve independently evidenced placement and start observations.", "inputs": [ "placement evidence", "planned and observed start", "optional employment reference" ], "outputs": [ "placement receipt", "conflicting-evidence report" ], "preconditions": [ "Authorized local role, purpose and expected record revision are supplied.", "The evidence distinguishes a prediction, confirmation and observed event.", "Reject unresolved authority or stale revision; do not infer missing facts." ], "effects": [ "Update local outcome evidence and capacity assertion only; no employment master is created.", "Record actor, input revisions and result evidence under applicable retention policy." ], "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] }, { "id": "function-prepare-scoped-view", "name": "Prepare a scoped evidence view", "description": "Proposed, unimplemented local operation. Project permitted records for a named recipient and report omitted or stale fields.", "inputs": [ "recipient", "purpose", "access decision", "record revisions", "mapping" ], "outputs": [ "local view", "loss report", "access refusal" ], "preconditions": [ "Authorized local role, purpose and expected record revision are supplied.", "Applicable grants, retention and mapping versions are resolved.", "Reject unresolved authority or stale revision; do not infer missing facts." ], "effects": [ "Generate a local projection only; no delivery, disposal or access expansion is executed.", "Record actor, input revisions and result evidence under applicable retention policy." ], "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ] } ], "composition": [ { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Resolve hiring party and intermediary master identity; do not duplicate organizational lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-ORG-002", "relation": "REFERENCE", "purpose": "Optional organizational-unit or position-context reference; no mandatory pre-existing position is assumed.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-PER-001", "relation": "REFERENCE", "purpose": "Resolve candidate identity and permission-scoped profile revisions without importing an entire person master.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "target": "WM-ACT-039", "relation": "REFERENCE", "purpose": "Candidate boundary binding: stage, assessment and hiring decision execution remain in Recruitment / Hiring Process; incoming registry parent hint does not grant shared operational ownership.", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] }, { "target": "WM-ORG-005", "relation": "REFERENCE", "purpose": "Optional independently mastered employment relationship; replaces legacy O3 COMPOSE and excludes membership inference.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "WM-XCT-001", "relation": "REFERENCE", "purpose": "Bind side-specific stewardship and accountability without asserting personal-data property rights.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-XCT-002", "relation": "REFERENCE", "purpose": "Bind access and consent evidence where applicable; processing basis is a separate profile determination.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "target": "WM-XCT-004", "relation": "REFERENCE", "purpose": "Reference access-audit records; this model does not implement generic audit storage or monitoring.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "Schema.org JobPosting", "relation": "ALIGN", "purpose": "Map public posting descriptions only after pinning a release and testing loss; no full recruiting interchange claim.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "ESCO", "relation": "ALIGN", "purpose": "Bind occupation and skill URIs with a dataset version; no automatic equivalence or qualification recognition.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "PROV-O", "relation": "ALIGN", "purpose": "Candidate alignment for attribution and derivation; an ontology mapping is not implemented conformance.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Designate the adopting Dimension and vacancy steward by role or governed identifier, without a brand owner.", "Declare candidate-side stewardship, recipient accountability, jurisdiction, purpose and field-level access rules.", "Provide authoritative identity namespaces, schema and vocabulary pins, retention rules and external process bindings." ], "namespace_guidance": "Use a governed Dimension namespace plus stable vacancy and interaction IDs. A posting URL, date, name, email address or content hash alone must not become the vacancy or person identity.", "registry_links": [ "vr.wm-org-008", "WM-ACT-039", "WM-ORG-005", "WM-PER-001", "WM-ORG-001" ] }, "canon_and_patch": { "canonicalization_rules": [ "This research package is a noncanonical reviewable draft. Instance authority belongs to the designated master for each assertion.", "Preserve original statements, source revision and unknown values. Never merge persons or vacancies solely by label similarity.", "Distinguish score, recommendation, review, decision, offer response, placement and observed start." ], "patch_rules": [ "Apply expected-revision checks; corrections link superseded assertions and explain the change.", "Reassess disclosure when purpose or recipient changes. Keep only lawful minimum history, not perpetual personal-data copies." ], "compatibility_rules": [ "Pin vocabulary and neighbor bindings; reject silent wildcard upgrades or new mandatory fields.", "Changing vacancy identity, candidacy meaning or score interpretation requires explicit migration and loss reporting." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with issuer namespace and revision.", "Governed global identifier or IRI with documented equivalence.", "UUID or ULID assigned by the adopting Dimension when no master identity exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and an explicit offset or Z; separate event time from observation and ingestion time. Preserve date-only deadlines and planned starts with their precision and jurisdictional interpretation rather than inventing midnight instants.", "serial_naming_rule": "Serial records keep stable logical identity plus revision or sequence; filenames may aid display but dates never establish identity.", "integrity_rule": "Bind digest, media type, source and revision to an authorized evidence reference. Hashes prove byte consistency only; they do not prove authenticity, consent, job suitability or legal effect." }, "policies": [ "Restrict processing to justified recruitment purposes and reviewed legal profiles; consent is neither presumed nor the sole possible processing basis.", "Separate public posting data, private candidate data, confidential assessments and restricted fairness or concern data.", "Do not use protected traits or unreviewed proxies for adverse ranking; legal exceptions and monitoring data require qualified profile review and separate access.", "Use ILO fair recruitment guidance as a non-binding policy reference; fee, coercion and misrepresentation concerns require review, not automated guilt or blacklisting.", "Agents may record verified facts and unknowns; external publication, messages, offers, hiring decisions, training reuse and broader disclosure require separate authority.", "ICO material is UK-specific and partly draft or under revision. US technical assistance and international guidance are not universal law." ], "crud": { "read": [ "Read only authorized vacancy, candidacy and artifact scopes for the declared purpose; a public vacancy exposes no applicant list." ], "create": [ "Create local evidence records after master identity, purpose, actor and source checks; mark unverified claims explicitly." ], "update": [ "Require expected revision and authority; preserve correction links, notification needs and disputed evidence without inventing agreement." ], "delete": [ "The adopting Dimension retention/disposition executor owns physical deletion. Record category-specific decisions, scoped holds, execution receipts and justified minimal tombstones for this model.", "Do not erase another master or infer erasure from candidate withdrawal. Do not retain personal payload forever to preserve an audit trail; inspect replicas, exports and derived views." ] }, "roles": [ { "name": "Vacancy steward", "responsibilities": [ "Maintain authoritative demand statements and publication aliases." ] }, { "name": "Candidate representative", "responsibilities": [ "Control permitted candidate disclosures and submit correction or withdrawal evidence within authority." ] }, { "name": "Recruitment reviewer", "responsibilities": [ "Review match and process-owned assessment evidence; keep actual hiring authority distinct." ] }, { "name": "Data protection steward", "responsibilities": [ "Approve purpose, lawful basis, retention and restricted disclosure profiles." ] }, { "name": "Evidence auditor", "responsibilities": [ "Inspect permitted lineage and access records without changing hiring outcomes." ] } ], "access": { "default_rule": "Deny by default; authorize by recipient, purpose, record scope and current policy. Bilateral participation does not imply both parties may read every internal note.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Rights requests, investigations and legal holds follow applicable authority and qualified review; no blanket denial or blanket disclosure is inferred.", "Concern and equality-monitoring evidence use segregated permissions; do not feed unrestricted candidate ranking." ], "audit_requirements": [ "Reference external audit records for actor, purpose, grant, input revision, fields disclosed, time and outcome.", "Log denial, export, correction and disposition events while minimizing personal content in logs." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read owner and Dimension policies and this package AGENTS.md.", "Read spec.yaml, provider/source holds and pinned neighbor bindings.", "Resolve authority, purpose, evidence and retention before any local record mutation." ] } }, "coverage": { "claim": "Source-grounded proposed structure for a vacancy-centered interaction aggregate. A separate frozen local no-tools self-audit found no critical contradictions. Selected international, US and UK evidence informs the design; independent review, source/version checks, regional applicability and executable conformance remain holds. This is a noncanonical reviewable draft, not a universal hiring workflow or legal rules engine.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Vacancy, posting alias, candidacy, proposal and artifact identities remain distinct." }, { "dimension": "lifecycle", "status": "covered", "notes": "Local assertions separate publication, withdrawal, offer response and placement." }, { "dimension": "relationships", "status": "covered", "notes": "Scoped pair records and candidate neighbor bindings preserve external masters." }, { "dimension": "temporal", "status": "covered", "notes": "Event, observation, deadline and date-only precision are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Every structural node cites evidence; local records preserve derivation and attribution." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based stewardship does not claim ownership of persons or unrestricted data rights." }, { "dimension": "validation", "status": "covered", "notes": "Local schema validation plus proposed evidence and profile checks; no operational certification." }, { "dimension": "access", "status": "covered", "notes": "Recipient-purpose scopes and restricted concern records." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Local retention decisions delegate disposal execution and retain only justified evidence." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual mappings only; no tested exchange implementation." }, { "dimension": "direct properties", "status": "covered", "notes": "Terms, criteria, capacity and location are properties; physical dimensions of the aggregate are inapplicable." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Authenticity review and source/channel disagreements are preserved." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Six proposed local operations declare preconditions, effects and refusal outcomes." }, { "dimension": "independent review", "status": "gap", "notes": "External review waived; local self-audit is not a second provider." }, { "dimension": "source verification", "status": "gap", "notes": "Browser text reviewed; direct HTTP status, complete version pins and current-law applicability remain unresolved." } ], "known_omissions": [ "Independent external review and direct HTTP/version verification.", "Nested instance schemas, executable mappings, score validation fixtures and multilingual equivalence tests.", "Country-specific employment formation, recruitment fees, automated decision rules, retention periods and cross-border requirements.", "Sector-specific or high-risk recruitment, agency contracts, talent pools and aggregate labor-market statistics.", "HR Open recruiting schemas and O*NET/ISCO release crosswalks were not admitted; the legacy wildcard imports are not verified." ], "conflicts": [], "regional_assumptions": [ "ILO 2016 guidance is non-binding and supplies policy leads rather than universally operative legal requirements.", "EEOC technical assistance is a US example; ICO report and draft guidance are UK-specific and partly under review.", "No claim is made about EU GDPR current text because browser retrieval did not supply substantive text." ], "adversarial_checks": [ "A copied posting, stale channel or fraudulent advertisement must not manufacture an authorized vacancy.", "Missing qualification evidence is unknown, not proof that a candidate lacks a skill.", "An automated shortlist can have significant effects before a final human hiring decision; record stage-specific review.", "A match without an application and a placement without an observed start remain representable.", "Withdrawal and disposal, pseudonymisation and anonymisation, consent and lawful basis remain different concepts.", "No blanket one-to-one application-offer-placement chain or automatic employment creation is accepted." ] }, "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": "The proposed root is one vacancy master with scoped publication and candidate-interaction records whose local references and evidence must remain consistent. This explicit aggregate boundary excludes global person profiles, operational hiring workflows and employment masters. The registry standalone-mm value classifies the record plane, not the subject kind; the aggregate is a design proposal rather than a source-mandated ontology." }, "decisions": [ { "concept": "Vacancy-centered aggregate", "disposition": "accepted", "rationale": "Stable vacancy identity anchors local child interaction records; the proposal does not attempt to model the entire labor market or reproduce a hiring workflow." }, { "concept": "Recruitment process parent hint", "disposition": "qualified", "rationale": "The relation ledger is empty and the incoming registry parent hint is explicitly recorded. Assessment, stage and decision execution remain external; domain alignment is not executable inheritance." }, { "concept": "Posting identity and vacancy capacity", "disposition": "accepted", "rationale": "Channel aliases, unverified advertisements, evergreen invitations, multiple openings and partial fills are distinguished rather than collapsed into one public URL or closure state." }, { "concept": "Requirements and classification", "disposition": "qualified", "rationale": "Vocabulary versions and alternatives are explicit. Codes do not prove competence, equivalence or lawful exclusion; missing evidence remains unknown and job relevance requires review." }, { "concept": "Advertised terms", "disposition": "accepted", "rationale": "Pay units, employer statements, estimates, remote location and work-authorization references remain distinct, avoiding misleading equivalence between different kinds of conditions." }, { "concept": "Mandatory application-offer-placement chain", "disposition": "rejected", "rationale": "Optional candidacies, proposal evidence, revised offers and unobserved starts are representable. No one-to-one chain or guaranteed successful outcome is imposed." }, { "concept": "Consent-only processing and bilateral ownership", "disposition": "rejected", "rationale": "The proposal separates candidate-directed disclosure from recipient accountability and processing basis. Regional evidence does not establish universal consent or equal access to every internal note." }, { "concept": "Automated assessment and meaningful review", "disposition": "accepted with profile hold", "rationale": "Stage-specific review and score interpretation are requested without certifying fairness or imposing a universal legal rule. Final human involvement does not erase earlier automated effects." }, { "concept": "Employment creation and legacy O3", "disposition": "rejected", "rationale": "Placement and start assertions only reference an independently mastered employment relationship. Legacy O3 ambiguity does not authorize importing Membership or automatically creating Employment." }, { "concept": "Concerns and sensitive evidence", "disposition": "accepted", "rationale": "Policy-level fee and fairness concerns link to external review processes, use restricted access and do not automatically blacklist candidates or determine legal culpability." }, { "concept": "Local functions and external authority", "disposition": "accepted as proposed only", "rationale": "Six functions state local effects, revision and authority preconditions, and refusal outcomes. None executes ranking, messages, offers, hiring decisions, employment creation or disposal." }, { "concept": "Retention, history and artifact identity", "disposition": "accepted with adoption dependency", "rationale": "Master identifiers precede local ones; digests are not truth. Revision history is limited by lawful retention and selective disposal, with minimal justified residual records rather than perpetual payload retention." }, { "concept": "Source and regional assurance", "disposition": "limited", "rationale": "Substantive browser readings support selected claims only. No direct HTTP status was measured, ICO records guidance is draft and under review, and the posting vocabulary is a development page." }, { "concept": "Instance schemas and independent review", "disposition": "deferred", "rationale": "Nested schema constraints, mapping tests and pinned neighbor bindings are incomplete. A separate local Codex self-audit supplies no independent second-provider evidence and cannot close that hold." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; this separate local Codex no-tools self-audit is not an independent second-provider review.", "Live source and version verification remains incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox restriction, so no HTTP status was measured. Eight sources supplied browser text; complete release pins and current applicability remain unverified. The coordinator can run check_sources.py. ICO retention guidance is draft and under review; Schema.org is a development page.", "Jurisdiction and sector profiles require qualified review of privacy, lawful basis, recruitment fees, discrimination, accessibility, automated decisions, work authorization, offer effects, retention and cross-border recruitment before operational use. International guidance and selected US/UK examples are not universal law.", "Nested instance schemas, versioned neighbor bindings, vocabulary mappings, algorithm and assessment validation evidence, exchange fixtures and adversarial conformance cases remain incomplete. The proposed functions are unimplemented local operations; no runtime, legal-compliance or fairness certification is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify source responses, immutable release pins, licensing and current regional applicability; reconcile the UK guidance revision before any operational rule is adopted.", "Develop nested schemas and fixtures covering syndicated duplicates, multi-opening vacancies, missing skills, referral without application, revised offers, failed starts, partial fills, withdrawal, disclosure changes and lawful disposal.", "Pin neighbor contracts and implement loss-aware posting and recruitment exchange mappings; review legacy HR Open and classification leads before admitting them.", "Restore independent external review before promotion beyond reviewable-draft." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }