# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T11:41:47Z", "synthesisSha256": "e72802acc6a8f7503e676340ef92e2315e53fee311cf22ff6bafa3d1652478a1", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-POL-018", "registryId": "vr.wm-pol-018", "name": "Public Service / Government Service", "version": "1.0.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.POL.SRV" ], "tags": [ "public", "service", "government", "soc.pol.srv" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-pol-018-public-service-government-service/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-pol-018", "model": { "registry_id": "vr.wm-pol-018", "model_id": "WM-POL-018", "name": "Public Service / Government Service", "entry_kind": "entity", "purpose": "Describe one public service offering, its responsible authority, eligibility and delivery design, with links to separately mastered transactions.", "scope_statement": "The root is an identifiable public service offering across description revisions and delivery channels. Entitlement, application and delivery lifecycle are represented as service-level rules and routes, with optional references to individual cases. This is a proposed research structure, not an entitlement engine or a case file.", "in_scope": [ "Service identity, purpose, audience, jurisdiction, competent authority and description lifecycle", "Versioned eligibility, evidence requirements, costs, time assertions, channels and output definitions", "Delivery dependencies, redress information, performance observations, provenance and controlled service metadata" ], "out_of_scope": [ "Applicant identity masters, individual eligibility decisions, application payloads, case files and delivered benefit or permit records", "Legislation authoring, public organization master data, executable adjudication, payment or enforcement", "Universal service taxonomy, universal legal duties, operational security instructions or certification of legal or accessibility compliance" ], "boundary_notes": [ { "neighbor": "WM-ACT-004 Service", "distinction": "Registry parent is a candidate alignment to generic service. This offering adds authority and public mandate context; inheritance is not asserted without a pinned compatible specification.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "neighbor": "WM-POL-017 Administrative Procedure / Case", "distinction": "A service definition can link many separately controlled cases or none. Case status, participant standing and legal decisions remain case-owned.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "neighbor": "WM-REC-009 Application / Request Record and WM-REC-010 Decision / Approval Record", "distinction": "Optional external references; service-level routes do not contain individual applications or decisions. Proactive or information-only profiles need not require an application or decision.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "Public authority, legal resource and delivery provider", "distinction": "Competence, legal mandate, cataloguing stewardship and operational participation are separate assertions. Outsourcing delivery does not transfer the competent authority role by implication.", "source_refs": [ "SRC-001", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Core Public Service Vocabulary Application Profile", "organization": "European Commission SEMIC", "url": "https://semiceu.github.io/CPSV-AP/releases/3.2.0/", "version_or_date": "3.2.0, 2024-05-06", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:40:27Z", "relevance": "Public Service and supportive entities: identifiers, competent authority, participation, requirements, channels, costs, outputs and related services. Browser document read; selected concepts support an authored hierarchy, not a claim of profile conformance." }, { "id": "SRC-002", "title": "Service Standard", "organization": "Government Digital Service", "url": "https://www.gov.uk/service-manual/service-standard", "version_or_date": "Undated live overview accessed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:40:27Z", "relevance": "Points 1-5, 8-10, 13-14 support user needs, joined channels, inclusion, improvement, privacy, performance, standards and reliability. UK practice example, not universal law." }, { "id": "SRC-003", "title": "Web Content Accessibility Guidelines 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/WCAG22/", "version_or_date": "Recommendation 2024-12-12 as displayed on retrieval", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:40:27Z", "relevance": "Abstract and section 5 support bounded accessibility assessment and complete-process conformance scope. A service description or self-declaration is not an accessibility certification." }, { "id": "SRC-004", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:40:27Z", "relevance": "Entity, activity, agent, derivation and qualified attribution support assertion provenance. Attribution is not proof of legal mandate, truth or deployment." }, { "id": "SRC-005", "title": "General Data Protection Regulation", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679", "version_or_date": "Regulation (EU) 2016/679, original act; selected indexed provisions only", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:40:27Z", "relevance": "Indexed Article 5 supports minimization, purpose and storage limitation within applicable scope. Full text and current consolidation could not be retrieved through the browser; not a universal records law." }, { "id": "SRC-006", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:40:27Z", "relevance": "Sections 4 and 5.6 support instants with seconds and explicit UTC offset. Does not define business calendars, date-only legal effectivity or duration calculations." }, { "id": "SRC-007", "title": "The European Code of Good Administrative Behaviour", "organization": "European Ombudsman", "url": "https://www.ombudsman.europa.eu/en/publication/en/3510", "version_or_date": "Official page 2002-03-01", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:40:27Z", "relevance": "Articles 2-5, 18-19 and 24 support scoped administrative responsibility, reasons, remedy information and records. EU institutional example only; historic data-protection citation not treated as current law." }, { "id": "SRC-008", "title": "Single Digital Gateway Regulation", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=celex%3A32018R1724", "version_or_date": "Regulation (EU) 2018/1724; selected original and consolidated indexed excerpts; current consolidation unresolved", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:40:27Z", "relevance": "Selected official indexed Article 10 material supports procedure information including time and redress within its scope. Browser full text retrieval failed; 2026-05-20 consolidation surfaced but was not substantively verified." } ], "structure": { "bundles": [ { "id": "bundle-definition", "name": "Service identity and authority", "description": "Service-level service identity and authority with scoped evidence and explicit unresolved assertions.", "rationale": "Authored grouping of source-supported concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "layers": [ { "id": "layer-identity", "name": "Identity and recognition", "description": "Keep an authority-qualified service identifier across revisions; names and catalogue entries alone do not establish equivalence.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "finding-identity", "name": "Service identity and catalogue context", "description": "Keep an authority-qualified service identifier across revisions; names and catalogue entries alone do not establish equivalence.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "q-identity-1", "text": "Which master namespace and stable identifier distinguish this offering from its catalogue record, channel and individual case?", "kind": "identity", "answer_data": [ "identity: master_namespace, service_id, catalogue_record_refs, reconciliation_status", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-2", "text": "Which purpose, audience and classification scheme identify the service, and which scheme version qualifies each code?", "kind": "classification", "answer_data": [ "classification: purpose, audience, concept_uri, scheme_version, language", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-3", "text": "What authority-backed evidence confirms the official service entry and separates aliases or related offerings from duplicates?", "kind": "validation", "answer_data": [ "recognition: official_reference, alias_relation, evidence_ref, reviewer, unresolved_matches", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-identity-1", "name": "identity", "description": "Proposed nested field group: identity: master_namespace, service_id, catalogue_record_refs, reconciliation_status. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "data-identity-2", "name": "classification", "description": "Proposed nested field group: classification: purpose, audience, concept_uri, scheme_version, language. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "data-identity-3", "name": "recognition", "description": "Proposed nested field group: recognition: official_reference, alias_relation, evidence_ref, reviewer, unresolved_matches. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Identity and recognition register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-mandate", "name": "Mandate and accountability", "description": "Record responsible public authority, legal resource and role-qualified participants separately; hosting or delivery contracts alone do not establish competence.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-mandate", "name": "Competent authority and delivery participation", "description": "Record responsible public authority, legal resource and role-qualified participants separately; hosting or delivery contracts alone do not establish competence.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "q-mandate-1", "text": "Which public authority is responsible for this service in each territory and period, and what source supports that responsibility?", "kind": "authority", "answer_data": [ "competence: authority_ref, jurisdiction, valid_period, legal_resource, review_state", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-mandate-2", "text": "Who stewards the description and who operates each delivery component under what recorded role or delegation?", "kind": "ownership", "answer_data": [ "stewardship: custodian_role, operator_ref, participation_role, mandate_ref, escalation_route", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-mandate-3", "text": "How are overlapping competence, delegated delivery and disputed or missing mandate evidence represented without assigning authority automatically?", "kind": "exception", "answer_data": [ "exceptions: overlap_scope, delegation_limits, dispute_status, unresolved_basis, review_owner", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-mandate-1", "name": "competence", "description": "Proposed nested field group: competence: authority_ref, jurisdiction, valid_period, legal_resource, review_state. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-mandate-2", "name": "stewardship", "description": "Proposed nested field group: stewardship: custodian_role, operator_ref, participation_role, mandate_ref, escalation_route. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-mandate-3", "name": "exceptions", "description": "Proposed nested field group: exceptions: overlap_scope, delegation_limits, dispute_status, unresolved_basis, review_owner. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-mandate", "name": "Mandate and accountability register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-conditions", "name": "Entitlement and evidence design", "description": "Service-level entitlement and evidence design with scoped evidence and explicit unresolved assertions.", "rationale": "Authored grouping of source-supported concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-eligibility", "name": "Eligibility and entitlement rules", "description": "Describe requirements at offering level with effective scope and exceptions. Do not infer an individual entitlement or assume every public service requires a means test or application.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-eligibility", "name": "Audience conditions and applicability", "description": "Describe requirements at offering level with effective scope and exceptions. Do not infer an individual entitlement or assume every public service requires a means test or application.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "q-eligibility-1", "text": "Which eligibility criteria or access conditions apply to each audience, jurisdiction and effective service version?", "kind": "requirement", "answer_data": [ "criteria: requirement_ref, audience, applicability, effective_version, legal_basis", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-eligibility-2", "text": "Which conditions are mandatory, discretionary or inapplicable, and how are exceptions and missing rule authority disclosed?", "kind": "constraint", "answer_data": [ "rule_status: obligation_kind, exception_basis, discretion_scope, unknown_reason, reviewer", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-eligibility-3", "text": "Where is an individual entitlement assessment performed, and how is general guidance distinguished from an authoritative determination?", "kind": "decision", "answer_data": [ "assessment_boundary: case_system_ref, decision_authority, guidance_label, automation_basis, contest_route", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-eligibility-1", "name": "criteria", "description": "Proposed nested field group: criteria: requirement_ref, audience, applicability, effective_version, legal_basis. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-eligibility-2", "name": "rule_status", "description": "Proposed nested field group: rule_status: obligation_kind, exception_basis, discretion_scope, unknown_reason, reviewer. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-eligibility-3", "name": "assessment_boundary", "description": "Proposed nested field group: assessment_boundary: case_system_ref, decision_authority, guidance_label, automation_basis, contest_route. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-eligibility", "name": "Eligibility and entitlement rules register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-evidence", "name": "Evidence and data requirements", "description": "List required evidence types and permitted alternatives at service level. Reuse routes and data exchange require their own authority; a description does not authorize access to personal records.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "finding-evidence", "name": "Evidence types and collection limits", "description": "List required evidence types and permitted alternatives at service level. Reuse routes and data exchange require their own authority; a description does not authorize access to personal records.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "q-evidence-1", "text": "Which evidence types support each requirement and which issuer, validity or alternative-evidence conditions are declared?", "kind": "evidence", "answer_data": [ "evidence_design: requirement_ref, evidence_type, issuer_class, validity_rule, alternative_route", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-evidence-2", "text": "What purpose and applicable processing basis justify each requested field or evidence category, including any proposed reuse?", "kind": "privacy", "answer_data": [ "data_policy: data_category, purpose, processing_basis, reuse_authority, recipient_role", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-evidence-3", "text": "Which retention, restricted-access and correction rules govern collected evidence in the external case system rather than the public catalogue?", "kind": "retention", "answer_data": [ "record_boundary: case_policy_ref, retention_trigger, access_scope, correction_route, public_exclusion", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-evidence-1", "name": "evidence_design", "description": "Proposed nested field group: evidence_design: requirement_ref, evidence_type, issuer_class, validity_rule, alternative_route. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "data-evidence-2", "name": "data_policy", "description": "Proposed nested field group: data_policy: data_category, purpose, processing_basis, reuse_authority, recipient_role. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "data-evidence-3", "name": "record_boundary", "description": "Proposed nested field group: record_boundary: case_policy_ref, retention_trigger, access_scope, correction_route, public_exclusion. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-evidence", "name": "Evidence and data requirements register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-access", "name": "Channels and inclusion", "description": "Service-level channels and inclusion with scoped evidence and explicit unresolved assertions.", "rationale": "Authored grouping of source-supported concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "layers": [ { "id": "layer-channels", "name": "Channels and territorial reach", "description": "Describe online and assisted routes with coverage and dependencies. Availability is an observed condition, not an assurance of eligibility or successful completion.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-channels", "name": "Official access routes and handoffs", "description": "Describe online and assisted routes with coverage and dependencies. Availability is an observed condition, not an assurance of eligibility or successful completion.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-channels-1", "text": "Which official channels serve each territory and audience, and what contact, opening-hours and language information is evidenced?", "kind": "spatial", "answer_data": [ "channels: channel_ref, official_endpoint, territory, opening_hours, timezone, language", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-channels-2", "text": "How can a user continue across digital, telephone, postal or in-person channels without creating an unexplained duplicate request?", "kind": "process", "answer_data": [ "handoff: route_pair, reference_policy, continuity_rule, support_contact, duplicate_warning", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-channels-3", "text": "Which access prerequisites, authentication or representation routes are required for each channel, and what assisted alternative is offered?", "kind": "access", "answer_data": [ "access_design: prerequisite, assurance_profile_ref, representation_route, assisted_route, exclusion_risk", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-channels-1", "name": "channels", "description": "Proposed nested field group: channels: channel_ref, official_endpoint, territory, opening_hours, timezone, language. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-channels-2", "name": "handoff", "description": "Proposed nested field group: handoff: route_pair, reference_policy, continuity_rule, support_contact, duplicate_warning. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-channels-3", "name": "access_design", "description": "Proposed nested field group: access_design: prerequisite, assurance_profile_ref, representation_route, assisted_route, exclusion_risk. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "artifact-channels", "name": "Channels and territorial reach register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-inclusion", "name": "Accessibility and user needs", "description": "Record user-needs evidence and accessibility assessments. WCAG applies to web content; it does not establish accessibility of offices or every part of a service.", "source_refs": [ "SRC-002", "SRC-003" ], "findings": [ { "id": "finding-inclusion", "name": "Inclusive delivery and scoped assessment", "description": "Record user-needs evidence and accessibility assessments. WCAG applies to web content; it does not establish accessibility of offices or every part of a service.", "source_refs": [ "SRC-002", "SRC-003" ], "questions": [ { "id": "q-inclusion-1", "text": "Which user groups and barriers informed service design, and what evidence shows that excluded or assisted users were considered?", "kind": "quality", "answer_data": [ "user_needs: group_scope, research_ref, barrier, accommodation, evidence_date", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-inclusion-2", "text": "What web pages and complete processes were assessed against which accessibility version and level, with what unresolved defects?", "kind": "validation", "answer_data": [ "accessibility: assessment_scope, standard_version, level, method, findings, assessed_at", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-inclusion-3", "text": "How are language needs, unavailable accommodations and failed assisted routes escalated without claiming universal accessibility?", "kind": "exception", "answer_data": [ "inclusion_gaps: need_category, unresolved_barrier, alternative, escalation_role, review_date", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-inclusion-1", "name": "user_needs", "description": "Proposed nested field group: user_needs: group_scope, research_ref, barrier, accommodation, evidence_date. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "data-inclusion-2", "name": "accessibility", "description": "Proposed nested field group: accessibility: assessment_scope, standard_version, level, method, findings, assessed_at. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "data-inclusion-3", "name": "inclusion_gaps", "description": "Proposed nested field group: inclusion_gaps: need_category, unresolved_barrier, alternative, escalation_role, review_date. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-inclusion", "name": "Accessibility and user needs register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-delivery", "name": "Costs and delivery design", "description": "Service-level costs and delivery design with scoped evidence and explicit unresolved assertions.", "rationale": "Authored grouping of source-supported concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "layers": [ { "id": "layer-costs", "name": "Costs and time assertions", "description": "Keep official charges, conditional waivers and estimates separate. A processing estimate is not a statutory deadline; zero, unknown and not applicable are different values.", "source_refs": [ "SRC-001", "SRC-008" ], "findings": [ { "id": "finding-costs", "name": "Fees, waivers and qualified time information", "description": "Keep official charges, conditional waivers and estimates separate. A processing estimate is not a statutory deadline; zero, unknown and not applicable are different values.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "q-costs-1", "text": "Which charges apply by channel or audience, with what currency, calculation basis, waiver and effective date?", "kind": "measurement", "answer_data": [ "fees: amount_or_formula, currency, payer_class, channel_ref, waiver_basis, valid_period", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-costs-2", "text": "Which stated times are estimates, service targets or legal limits, and what trigger, calendar and source qualify each?", "kind": "temporal", "answer_data": [ "time_rules: time_kind, duration, trigger, calendar_ref, pause_rule, source_ref", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-costs-3", "text": "How are unknown charges, changed fees, delayed service and disputed time rules disclosed and referred for review?", "kind": "exception", "answer_data": [ "cost_time_gaps: uncertainty, change_notice, delay_notice, dispute_route, responsible_role", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-costs-1", "name": "fees", "description": "Proposed nested field group: fees: amount_or_formula, currency, payer_class, channel_ref, waiver_basis, valid_period. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "data-costs-2", "name": "time_rules", "description": "Proposed nested field group: time_rules: time_kind, duration, trigger, calendar_ref, pause_rule, source_ref. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] }, { "id": "data-costs-3", "name": "cost_time_gaps", "description": "Proposed nested field group: cost_time_gaps: uncertainty, change_notice, delay_notice, dispute_route, responsible_role. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-costs", "name": "Costs and time assertions register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-routes", "name": "Initiation and delivery design", "description": "Describe entry triggers and expected outcomes without embedding a transaction. Outputs may be information, ongoing provision or a separately mastered record; application and formal decision are not mandatory.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "finding-routes", "name": "Service routes, outputs and dependencies", "description": "Describe entry triggers and expected outcomes without embedding a transaction. Outputs may be information, ongoing provision or a separately mastered record; application and formal decision are not mandatory.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-routes-1", "text": "Which requested, automatic or referral entry routes and completion conditions are actually supported by the service profile?", "kind": "lifecycle", "answer_data": [ "routes: entry_trigger, route_ref, authorization_basis, completion_condition, unsupported_route", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-routes-2", "text": "Which output types and upstream or related services are declared, and where do their identities and lifecycle remain mastered?", "kind": "composition", "answer_data": [ "delivery_design: output_type, master_ref, prerequisite_service, dependency_rule, responsibility", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-routes-3", "text": "How does a delivery case reference the service revision and its output without turning the service catalogue into a personal transaction store?", "kind": "relationship", "answer_data": [ "case_link: case_ref_policy, service_revision_ref, output_ref_policy, access_boundary, no_case_reason", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-routes-1", "name": "routes", "description": "Proposed nested field group: routes: entry_trigger, route_ref, authorization_basis, completion_condition, unsupported_route. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-routes-2", "name": "delivery_design", "description": "Proposed nested field group: delivery_design: output_type, master_ref, prerequisite_service, dependency_rule, responsibility. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "data-routes-3", "name": "case_link", "description": "Proposed nested field group: case_link: case_ref_policy, service_revision_ref, output_ref_policy, access_boundary, no_case_reason. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-routes", "name": "Initiation and delivery design register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Redress and service quality", "description": "Service-level redress and service quality with scoped evidence and explicit unresolved assertions.", "rationale": "Authored grouping of source-supported concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-redress", "name": "Support and redress information", "description": "Describe support and remedy routes with applicable scope and responsible bodies. Service feedback is not automatically a legal appeal, and sending a message does not prove valid filing.", "source_refs": [ "SRC-007", "SRC-008" ], "findings": [ { "id": "finding-redress", "name": "Distinct help, complaint and challenge routes", "description": "Describe support and remedy routes with applicable scope and responsible bodies. Service feedback is not automatically a legal appeal, and sending a message does not prove valid filing.", "source_refs": [ "SRC-007", "SRC-008" ], "questions": [ { "id": "q-redress-1", "text": "Which help, complaint, administrative review or judicial routes are identified for each issue and competent body?", "kind": "relationship", "answer_data": [ "redress_routes: issue_type, route_type, body_ref, official_contact, applicability", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-redress-2", "text": "What verified source governs any redress time limit and filing condition, and how is unresolved or case-specific advice labelled?", "kind": "temporal", "answer_data": [ "redress_rules: legal_ref, time_trigger, limit_ref, filing_condition, uncertainty_notice", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-redress-3", "text": "How does the description distinguish feedback or support contact from a legally effective appeal or suspension of a decision?", "kind": "constraint", "answer_data": [ "redress_boundary: communication_type, legal_effect_qualification, case_referral, warning, reviewer", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-redress-1", "name": "redress_routes", "description": "Proposed nested field group: redress_routes: issue_type, route_type, body_ref, official_contact, applicability. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "data-redress-2", "name": "redress_rules", "description": "Proposed nested field group: redress_rules: legal_ref, time_trigger, limit_ref, filing_condition, uncertainty_notice. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "data-redress-3", "name": "redress_boundary", "description": "Proposed nested field group: redress_boundary: communication_type, legal_effect_qualification, case_referral, warning, reviewer. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-redress", "name": "Support and redress information register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-performance", "name": "Performance and reliability", "description": "Separate intended service levels from measured experience, and retain scope, denominators and uncertainty. Aggregate publication must avoid exposing applicants or small identifiable groups.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-performance", "name": "Service observations and improvement evidence", "description": "Separate intended service levels from measured experience, and retain scope, denominators and uncertainty. Aggregate publication must avoid exposing applicants or small identifiable groups.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ], "questions": [ { "id": "q-performance-1", "text": "Which measures describe service completion, timeliness, reliability or satisfaction, using what population, period and denominator?", "kind": "measurement", "answer_data": [ "metrics: metric_definition, unit, population, numerator, denominator, period, method, uncertainty", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-performance-2", "text": "What evidence supports current service or channel availability, disruption and recovery status, and when was it observed?", "kind": "state", "answer_data": [ "availability: channel_ref, observed_state, observation_time, source, stale_after, recovery_note", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-performance-3", "text": "What suppression, aggregation and access checks protect people when performance evidence is shared or published?", "kind": "privacy", "answer_data": [ "metric_release: disclosure_assessment, aggregation_rule, suppression_rule, approval_role, release_scope", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-performance-1", "name": "metrics", "description": "Proposed nested field group: metrics: metric_definition, unit, population, numerator, denominator, period, method, uncertainty. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "data-performance-2", "name": "availability", "description": "Proposed nested field group: availability: channel_ref, observed_state, observation_time, source, stale_after, recovery_note. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "data-performance-3", "name": "metric_release", "description": "Proposed nested field group: metric_release: disclosure_assessment, aggregation_rule, suppression_rule, approval_role, release_scope. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-performance", "name": "Performance and reliability register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Lifecycle and interoperability", "description": "Service-level lifecycle and interoperability with scoped evidence and explicit unresolved assertions.", "rationale": "Authored grouping of source-supported concepts; no source mandates this hierarchy.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "layer-change", "name": "Description lifecycle and continuity", "description": "Keep service status, description revision, effective date and observation time distinct. Retiring catalogue content does not terminate entitlements or delete external case records.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-change", "name": "Versioned change, retirement and provenance", "description": "Keep service status, description revision, effective date and observation time distinct. Retiring catalogue content does not terminate entitlements or delete external case records.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "q-change-1", "text": "Which evidenced transition changes the service from proposed to active, suspended, replaced or retired, and who authorizes that transition?", "kind": "lifecycle", "answer_data": [ "service_state: prior_state, next_state, authority_ref, effective_date, transition_evidence", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-change-2", "text": "Which source, reviewer and derivation explain a changed rule, translation or public description, and what prior revision remains traceable?", "kind": "provenance", "answer_data": [ "revision: source_ref, agent_role, derivation, supersedes, change_reason, review_status", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-change-3", "text": "How are publication time, legal effectivity and observation time preserved when a service changes or a successor is introduced?", "kind": "temporal", "answer_data": [ "continuity: published_at, effective_period, observed_at, successor_ref, case_transition_policy", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-change-1", "name": "service_state", "description": "Proposed nested field group: service_state: prior_state, next_state, authority_ref, effective_date, transition_evidence. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-change-2", "name": "revision", "description": "Proposed nested field group: revision: source_ref, agent_role, derivation, supersedes, change_reason, review_status. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-change-3", "name": "continuity", "description": "Proposed nested field group: continuity: published_at, effective_period, observed_at, successor_ref, case_transition_policy. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-change", "name": "Description lifecycle and continuity register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-exchange", "name": "Interoperability and assurance", "description": "Treat CPSV-AP and provenance alignment as candidate mappings requiring pinned profiles and tests. Research schema validity proves structural completeness of this draft only.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-exchange", "name": "Loss-aware projection and bounded validation", "description": "Treat CPSV-AP and provenance alignment as candidate mappings requiring pinned profiles and tests. Research schema validity proves structural completeness of this draft only.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "q-exchange-1", "text": "Which pinned vocabulary and profile map each local service concept, with what cardinality, code-list and translation losses?", "kind": "interoperability", "answer_data": [ "mapping: target_profile, version, concept_map, cardinality_difference, loss_report", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-exchange-2", "text": "Which fixtures test proactive service, shared authority, offline-only access, conditional fees and retirement without a final case decision?", "kind": "validation", "answer_data": [ "fixtures: scenario_ref, expected_result, observed_result, failure, unresolved_reference", "Record source, review state and explicit unknown or not-applicable reason." ] }, { "id": "q-exchange-3", "text": "Which export and publication controls prevent restricted operational notes or linked personal records from entering a public service description?", "kind": "security", "answer_data": [ "release_controls: field_scope, classification, redaction_rule, approval, export_audit", "Record source, review state and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-exchange-1", "name": "mapping", "description": "Proposed nested field group: mapping: target_profile, version, concept_map, cardinality_difference, loss_report. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "data-exchange-2", "name": "fixtures", "description": "Proposed nested field group: fixtures: scenario_ref, expected_result, observed_result, failure, unresolved_reference. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "data-exchange-3", "name": "release_controls", "description": "Proposed nested field group: release_controls: field_scope, classification, redaction_rule, approval, export_audit. A profile-specific instance schema is required before execution.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-exchange", "name": "Interoperability and assurance register", "description": "Versioned service-level register of assertions and source references; individual case payloads remain in their authorized master systems.", "media_or_form": [ "structured register", "controlled document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision first; otherwise stable opaque local UUID with reconciliation status. Service key plus artifact type and immutable revision identifies the projection.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-resolve-service", "name": "Resolve a service reference", "description": "Proposed, unimplemented local operation. Resolve exact namespace and identifier; return ambiguous or unresolved matches instead of merging similar names.", "inputs": [ "master namespace", "service reference", "read scope" ], "outputs": [ "resolved reference or ambiguity report" ], "preconditions": [ "Actor and purpose are authorized for the exact data scope", "Input reference and source evidence are resolved or explicitly unresolved", "For local writes, expected revision matches and responsible steward approves; otherwise refuse" ], "effects": [ "Read-only resolution; no identity mutation" ], "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "function-record-description", "name": "Record a description revision", "description": "Proposed, unimplemented local operation. Propose a local service-description revision from attributed evidence; publication is a separately authorized action.", "inputs": [ "service reference", "source assertions", "expected revision" ], "outputs": [ "draft revision or refusal report" ], "preconditions": [ "Actor and purpose are authorized for the exact data scope", "Input reference and source evidence are resolved or explicitly unresolved", "For local writes, expected revision matches and responsible steward approves; otherwise refuse" ], "effects": [ "Append a reviewed-or-pending local revision; preserve prior provenance" ], "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "function-inspect-requirements", "name": "Inspect requirement coverage", "description": "Proposed, unimplemented local operation. Report missing rule sources, evidence types and explicit uncertainty without assessing a person or deciding entitlement.", "inputs": [ "service revision", "selected audience and jurisdiction profile" ], "outputs": [ "requirement coverage and unresolved-rule report" ], "preconditions": [ "Actor and purpose are authorized for the exact data scope", "Input reference and source evidence are resolved or explicitly unresolved", "For local writes, expected revision matches and responsible steward approves; otherwise refuse" ], "effects": [ "Read-only report; no eligibility decision or personal data collection" ], "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "function-record-channel-observation", "name": "Record channel status evidence", "description": "Proposed, unimplemented local operation. Append an attributed availability or accessibility observation without changing official service status.", "inputs": [ "channel reference", "observation evidence", "time and assessment scope" ], "outputs": [ "observation revision or refusal report" ], "preconditions": [ "Actor and purpose are authorized for the exact data scope", "Input reference and source evidence are resolved or explicitly unresolved", "For local writes, expected revision matches and responsible steward approves; otherwise refuse" ], "effects": [ "Local observation only; mark stale or unverified evidence explicitly" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "function-project-description", "name": "Project an authorized service description", "description": "Proposed, unimplemented local operation. Produce a local export for a pinned target profile with field redaction and mapping-loss disclosure.", "inputs": [ "service revision", "target profile", "approved public field scope" ], "outputs": [ "local projection and loss report or refusal report" ], "preconditions": [ "Actor and purpose are authorized for the exact data scope", "Input reference and source evidence are resolved or explicitly unresolved", "For local writes, expected revision matches and responsible steward approves; otherwise refuse" ], "effects": [ "Create local derived artifact; no remote write or conformance certification" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "function-propose-retirement", "name": "Propose service-description retirement", "description": "Proposed, unimplemented local operation. Record a proposed retirement or successor link from authority evidence; do not stop service, cancel rights or erase cases.", "inputs": [ "service reference", "transition evidence", "successor reference if known", "expected revision" ], "outputs": [ "retirement proposal or refusal report" ], "preconditions": [ "Actor and purpose are authorized for the exact data scope", "Input reference and source evidence are resolved or explicitly unresolved", "For local writes, expected revision matches and responsible steward approves; otherwise refuse" ], "effects": [ "Local proposal only; external authority must approve any operational transition" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "composition": [ { "target": "WM-ACT-004", "relation": "ALIGN", "purpose": "Candidate generic-service parent alignment only; verify version and compatibility before inheritance.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-POL-017", "relation": "REFERENCE", "purpose": "Optional separately mastered administrative case; pin service revision without importing case payloads.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "WM-REC-009", "relation": "REFERENCE", "purpose": "Optional application record for request-based routes; not required for every service.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-REC-010", "relation": "REFERENCE", "purpose": "Optional decision record where a service route produces a formal determination.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "CPSV-AP 3.2.0", "relation": "ALIGN", "purpose": "Conceptual public-service vocabulary mapping; conformance and data-shape bindings remain unimplemented.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "Authoritative public organization and legal resource masters", "relation": "REFERENCE", "purpose": "Competent authority and mandate evidence must be supplied for a verified operational profile; unresolved at research stage.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name the competent public authority and description custodian by verified role; no commercial owner assignment", "Declare jurisdiction, mandate references, authoritative master namespace and revision policy", "Declare public and restricted fields, licensing, retention and case-master boundaries" ], "namespace_guidance": "Use an authority-controlled namespace for the service; preserve external master IDs. Local UUIDs must carry provisional reconciliation status.", "registry_links": [ "vr.wm-pol-018", "WM-ACT-004 candidate alignment", "CPSV-AP 3.2.0 conceptual alignment" ] }, "canon_and_patch": { "canonicalization_rules": [ "Prefer a verified authoritative service identifier over name matching; keep catalogue record, offering and case identities distinct", "Preserve original source language and translated text with provenance; do not silently normalize legal meaning" ], "patch_rules": [ "Record source, actor, reason, expected revision and effective scope for each change", "Escalate mandate, entitlement, fee or access changes for profile review; do not execute them from a descriptive patch" ], "compatibility_rules": [ "A changed audience, mandate or route may require an explicit successor relationship rather than identity reuse", "Pin schema and vocabulary versions and report any lost requirement, scope or provenance during projection" ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace and revision", "Verified stable external resource URI and version", "Opaque local UUID with reconciliation status" ], "timestamp_rule": "Recording instants use RFC 3339 with seconds and explicit UTC offset. Preserve observation, publication and asserted effective time separately. Date-only legal values and opening-hour timezone rules remain separate; never invent a midnight instant.", "serial_naming_rule": "Use opaque service key, artifact type and immutable revision; avoid personal identifiers in filenames.", "integrity_rule": "Record source, content digest and derivation when available. A digest proves neither legal authority nor accuracy; preserve correction and verification status." }, "policies": [ "Reviewable draft under the single-provider waiver; independent external review and source/version verification remain open", "Public service metadata is separate from personal applications, case evidence and internal security notes; release only approved fields", "Jurisdiction-specific legal, privacy, records and accessibility review is required before operational adoption", "Proposed functions perform local descriptive work only; no filing, entitlement decision, payment, service shutdown or legal remedy execution", "Sensitive regulated services are represented only through mandate, access and oversight policy, without operational procedures" ], "crud": { "read": [ "Return approved public metadata or a purpose-authorized restricted view with version and uncertainty labels" ], "create": [ "Require provisional identity, steward, purpose and evidence references; mark unresolved mandate explicitly" ], "update": [ "Append authorized changes against expected revision and record effective scope; distinguish draft from approved public content" ], "delete": [ "Apply a scoped retention schedule, legal holds and lawful disposal review; preserve only lawful minimal non-identifying tombstones", "Description retirement or disposal does not cancel a service entitlement or delete separately mastered cases; audit history is not a reason for indefinite personal-data retention" ] }, "roles": [ { "name": "Service steward", "responsibilities": [ "Maintain description identity, review status and source continuity" ] }, { "name": "Competent authority reviewer", "responsibilities": [ "Verify mandate and approve service-level rule assertions within delegation" ] }, { "name": "Delivery and accessibility reviewer", "responsibilities": [ "Assess channel routes, inclusion evidence and declared availability" ] }, { "name": "Records and privacy officer", "responsibilities": [ "Authorize restricted scopes, release, retention and disposal" ] }, { "name": "Catalogue editor", "responsibilities": [ "Prepare evidence-backed revisions without determining individual rights" ] } ], "access": { "default_rule": "Public read applies only to approved service-description fields. Deny access to restricted notes and case references unless actor, purpose and scope are authorized.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory or supervisory access requires a recorded legal basis, responsible actor and bounded disclosure", "A public channel or catalogue listing never implies access to individual applications or personal evidence" ], "audit_requirements": [ "Record actor, purpose, revision, field scope and result for restricted reads, exports, revisions and disposal; minimize personal audit data and apply retention controls" ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and authority/access policies", "spec.yaml and all publication holds", "Pinned jurisdiction profile, source records and approved recipient view" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one identifiable public service offering, with service-level entitlement and delivery design and separately mastered transaction references. A separate frozen local no-tools self-audit found no critical contradiction. Selected European and UK sources do not establish universal duties or implemented conformance; source/version, jurisdiction-profile and independent-review holds remain.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Service, catalogue entry, channel and case identities are distinct." }, { "dimension": "lifecycle", "status": "covered", "notes": "Description revision and service activation, suspension and retirement are distinct." }, { "dimension": "relationships", "status": "covered", "notes": "Optional applications, cases and decisions; authority and mandate remain external masters." }, { "dimension": "temporal", "status": "covered", "notes": "Effective periods, estimates, limits and observation instants remain qualified." }, { "dimension": "provenance", "status": "covered", "notes": "Sources, review, derivation and revision history accompany assertions." }, { "dimension": "ownership", "status": "covered", "notes": "Competent public authority, steward and delivery roles are separate." }, { "dimension": "validation", "status": "gap", "notes": "Research schema validation is separate from nested instance schemas, legal review and conformance fixtures." }, { "dimension": "access", "status": "covered", "notes": "Approved public description fields and restricted operational/case data have different scopes." }, { "dimension": "interoperability", "status": "gap", "notes": "Candidate vocabulary mappings need pinned bindings and loss-aware tests." }, { "dimension": "direct properties", "status": "covered", "notes": "Purpose, territory, audience, status, channels, costs and durations are nonphysical service properties; physical measurements are inapplicable to the offering." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Official source evidence and dated channel observations distinguish claims from verified service state." }, { "dimension": "capabilities and hazards", "status": "covered", "notes": "Six proposed local functions; wrong guidance, exclusion, privacy leakage and false authority are explicit hazards." }, { "dimension": "context and evidence", "status": "covered", "notes": "Applicable legal and regional context and evidence limits are visible." }, { "dimension": "retention", "status": "covered", "notes": "Scoped schedules, holds and disposal keep personal records out of public catalogues." } ], "known_omissions": [ "Independent external review is waived; local self-audit is not independent review", "Live source status, current legal consolidation, translation, licensing and jurisdictional applicability remain unverified", "Nested field schemas, external master bindings, runnable entitlement rules and conformance fixtures are not implemented", "Sector-specific and non-European profiles, legal remedies, automated decisions and regulated-service exceptions need qualified review", "CPSV-AP and provenance mappings and complete-process accessibility tests remain proposed" ], "conflicts": [], "regional_assumptions": [ "CPSV-AP is a selected European interoperability profile, not a universal legal definition", "The service standard is UK guidance and the administrative code concerns EU institutions; neither establishes duties for every public authority", "GDPR and Single Digital Gateway excerpts are used only within their applicable scope; current versions and local applicability remain holds" ], "adversarial_checks": [ "Reject mandatory application, applicant identity or decision for every service", "Reject treating eligibility guidance, a processing estimate or a catalogue revision as an individual legal determination", "Reject automatic transfer of competent authority to an outsourced delivery provider", "Reject universal accessibility or conformance claims based on metadata alone", "Reject public case payloads and indefinite personal-data retention from service transparency claims" ] }, "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": "entity", "status": "accepted", "rationale": "The service offering retains identity across catalogue revisions, channels and use by multiple cases. It is neither a transaction event nor a registry of all services. The frozen standalone-mm value describes the record plane; the registry purpose is reconciled through service-level entitlement and delivery rules plus optional case references." }, "decisions": [ { "concept": "Offering versus case root", "disposition": "accepted", "rationale": "Every finding and question concerns service-level design, evidence or stewardship. Individual applications, entitlement assessments, decisions and outputs retain external identities and access controls." }, { "concept": "Generic service parent", "disposition": "qualified", "rationale": "The registry parent WM-ACT-004 is preserved as a candidate ALIGN relation, with no claim of validated inheritance or a pinned runtime dependency." }, { "concept": "Mandatory application or decision", "disposition": "rejected", "rationale": "Optional reference relations and route questions permit automatic, referral, informational and ongoing services. The unreviewed supplement cannot force an applicant or a terminal decision into every service instance." }, { "concept": "Authority and ownership", "disposition": "separated", "rationale": "Mandate, competent authority, operational participant and catalogue steward have separate roles and evidence. Optional composition required flags do not waive the mandate assessment needed by a verified operational profile." }, { "concept": "Entitlement and evidence", "disposition": "qualified", "rationale": "Requirement descriptions and candidate field groups do not determine a person's eligibility or authorize reuse of personal data. Exceptions, discretion and unresolved rule authority remain visible." }, { "concept": "Accessibility and channel inclusion", "disposition": "accepted with limits", "rationale": "Channels, assisted routes, user barriers and complete web-process assessment are addressed separately. WCAG scope is not generalized to offices or all user needs, and no operational conformance claim is made." }, { "concept": "Fees, time and redress", "disposition": "accepted with profile dependency", "rationale": "Questions distinguish fees, waivers, unknown values, estimated processing duration and legal time limits. Support and complaints are not equated with a legally effective appeal or suspended decision." }, { "concept": "Lifecycle and observations", "disposition": "separated", "rationale": "Service state, local revision, legal effectivity and channel observations have separate evidence and timestamps. Retirement proposals neither stop service nor extinguish entitlements or external cases." }, { "concept": "Local proposed operations", "disposition": "accepted as unimplemented", "rationale": "All six functions have inputs, outputs, authority and revision checks, and refusal paths. Their effects are read-only or local proposals; no operation files, pays, adjudicates or changes an external service." }, { "concept": "Privacy and record continuity", "disposition": "accepted with policy dependency", "rationale": "Public metadata excludes personal case payloads. Metric release has disclosure checks; retention schedules and lawful disposal qualify revision history, so integrity and traceability do not imply perpetual personal-data storage." }, { "concept": "Source coverage and status", "disposition": "limited", "rationale": "Six browser-readable documents and two partially indexed legal sources support a bounded proposal. Direct HTTP was not attempted in this run; zero measured successes cannot be recast as source failure, source verification or current-law assurance." }, { "concept": "Nested schema and standards conformance", "disposition": "deferred", "rationale": "Optional object field groups, unpinned neighbor bindings and conceptual mappings are research content rather than executable validation. Instance fixtures, mapping tests, licensing and operational profile assessment remain required." }, { "concept": "Independent provider agreement", "disposition": "waived and held", "rationale": "Claude and Grok were explicitly skipped. This phase is a separate local Codex semantic self-audit of frozen evidence, not independent external review or agreement between providers." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped; a separate local Codex no-tools self-audit is not independent second-provider review.", "Live source and version verification is incomplete. Direct HTTP checks were not run because the sandbox blocks them; zero HTTP 200 responses were measured. Browser evidence is separate. GDPR and Single Digital Gateway full text/current consolidation remain unverified; run check_sources.py outside the sandbox and complete claim review.", "Jurisdiction, sector, legal applicability, translation, licensing, mandate, privacy/records rules, automated-decision authority, fees, deadlines and remedies require qualified profile review before operational use.", "Nested instance schemas, pinned external master bindings, CPSV-AP and provenance mappings, accessibility conformance and adversarial fixtures remain incomplete. Research validation is not operational or legal-compliance certification.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify source status, current legal consolidations and applicability for every adopting jurisdiction and service sector.", "Implement and assess nested schemas and loss-aware mappings with fixtures covering shared authority, proactive provision, offline access, conditional fees, stale channels, restricted metrics and retirement.", "Restore independent external review before promotion toward canonical or publishable-draft assurance." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }