# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T03:01:43Z", "synthesisSha256": "eafc357d58f8c08bc9e14c388c4eb6de2a8341a648d0cd2004e5f314eed9985f", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-POL-004", "registryId": "vr.wm-pol-004", "name": "Permit / Authorization", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.POL.PRM" ], "tags": [ "permit", "authorization", "soc.pol.prm" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-pol-004-permit-authorization/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-pol-004", "model": { "registry_id": "vr.wm-pol-004", "model_id": "WM-POL-004", "name": "Permit / Authorization", "entry_kind": "aggregate", "purpose": "Represent the governed application, assessment and decision case for regulated authorization while keeping the permission-bearing grant in its authoritative external master.", "scope_statement": "Owns authorization-case identity, requested class and scope, submissions, evidence-use assertions, completeness, criterion assessments, consultations, decisions, reasons, notifications, appeal routes and follow-on administration cases. Applicants, authorities, legal instruments, public-service definitions, reusable criteria, evidence artifacts, payments, inspections, enforcement, appeals and granted rights remain external masters.", "in_scope": [ "Case identity, class, actors in procedural roles, service, legal basis and requested authorization scope", "Application revisions, evidence-use, completeness, assessment, consultation, decision, reasons and notification", "Follow-on renewal, variation, suspension or termination cases, access views, retention, interoperability and safe operations" ], "out_of_scope": [ "Permission-bearing permit, licence, authorization, credential or right master and its independently verified current status", "Applicant, authority, legal instrument, public service, criterion, evidence artifact, payment, inspection, enforcement and appeal-case masters", "Universal licensing law, legal advice or automated final decision without competent authority" ], "boundary_notes": [ { "neighbor": "Granted Right or Attestation", "distinction": "A favorable decision points to a separately mastered permission-bearing grant; case completion and grant validity are never interchangeable.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "neighbor": "Public Service", "distinction": "The reusable service definition supplies channels, requirements, outputs and legal resources; this model owns one execution case.", "source_refs": [ "SRC-001" ] }, { "neighbor": "Criterion and Evidence", "distinction": "Reusable requirements and evidence artifacts keep external masters; the case owns submissions, supported claims, verification and assessment findings.", "source_refs": [ "SRC-002", "SRC-004" ] }, { "neighbor": "Inspection and Enforcement", "distinction": "Inspections and enforcement actions may trigger or inform a case but retain their own authority, evidence and lifecycle.", "source_refs": [ "SRC-003", "SRC-008" ] }, { "neighbor": "Legal Instrument / Norm", "distinction": "Legal sources establish competence, requirements and effects; the authorization case applies them but does not own or reinterpret the law.", "source_refs": [ "SRC-005" ] } ] }, "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": "CPSV-AP 3.2.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Defines public services, competent agents, legal resources, requirements, evidence inputs, outputs, costs, channels, participation and related events for interoperable service descriptions." }, { "id": "SRC-002", "title": "Core Criterion and Core Evidence Vocabulary", "organization": "European Commission SEMIC", "url": "https://semiceu.github.io/CCCEV/releases/2.2.0/", "version_or_date": "CCCEV 2.2.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Defines requirements, criteria, constraints, information concepts, evidence, evidence types, supported values and reference frameworks for assessment and decision support." }, { "id": "SRC-003", "title": "Regulation (EU) 2018/1724 establishing a Single Digital Gateway", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=celex%3A32018R1724", "version_or_date": "Regulation (EU) 2018/1724", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Defines procedure, competent authority and evidence in a cross-border public-service context and requires access to information, procedures and assistance." }, { "id": "SRC-004", "title": "Commission Implementing Regulation (EU) 2022/1463", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32022R1463", "version_or_date": "Implementing Regulation (EU) 2022/1463", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Sets technical and operational specifications for cross-border automated evidence exchange, including user request, preview, delivery, logging and data-protection controls." }, { "id": "SRC-005", "title": "LegalRuleML Core Specification Version 1.0", "organization": "OASIS", "url": "https://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/os/legalruleml-core-spec-v1.0-os.html", "version_or_date": "OASIS Standard, 30 August 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Defines legal sources, authority, jurisdiction, temporal characteristics and deontic effects useful for expressing requirements and permission decisions without creating substantive law." }, { "id": "SRC-006", "title": "Streamlined presentation of UN/CEFACT standards", "organization": "United Nations Economic Commission for Europe", "url": "https://unece.org/trade/uncefact/mainstandards", "version_or_date": "Official standards catalogue accessed 6 September 2026", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Lists the Fishing Licence, Authorization and Permit process among UN/CEFACT standards and establishes it as a sector interoperability profile rather than a universal permit lifecycle." }, { "id": "SRC-007", "title": "Fishing Licence, Authorization and Permit Process Business Requirements Specification", "organization": "United Nations Centre for Trade Facilitation and Electronic Business", "url": "https://unece.org/fileadmin/DAM/cefact/Standards/Agriculture/FLUX/FLUX_P1000-9_FLAP_domain_v1_1_1.pdf", "version_or_date": "FLUX FLAP domain version 1.1.1", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Provides a sector example of licence, authorization and permit applications, responses, parties, conditions, validity and exchanges across a regulated activity." }, { "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, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Provides provenance for application revisions, assessments, evidence use, decisions, derivations, responsible agents and generated outputs." }, { "id": "SRC-009", "title": "Time Ontology in OWL", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/owl-time/", "version_or_date": "W3C Candidate Recommendation Draft, 15 November 2022", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Provides instants, intervals and temporal relations for submissions, deadlines, decisions, grant effects, reviews and knowledge time." }, { "id": "SRC-010", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T03:00:00Z", "relevance": "Defines timestamps with seconds and explicit UTC relation for application, assessment, decision, notification, legal-effect and audit events." } ], "structure": { "bundles": [ { "id": "case-identity-class-and-parties", "name": "Case identity, class and parties", "description": "Identifies one authorization case in the competent authority's system and classifies the requested procedure without absorbing party masters.", "rationale": "A case number, applicant, requested activity and resulting grant each have distinct identities and lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-008" ], "layers": [ { "id": "case-master-identity-and-classification", "name": "Case master identity and classification", "description": "Stable case identity, authority, service and jurisdiction-qualified permit class.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ], "findings": [ { "id": "authorization-case-identifier-register-and-competent-authority", "name": "Authorization case identifier, register and competent authority", "description": "Master case identifier, namespace, case register, competent authority, office, jurisdiction, resolver, aliases and collision state.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ], "questions": [ { "id": "authorization-case-identifier-register-and-competent-authority-q01", "text": "What exact identities, classes, values, links and explicit unknowns define authorization case identifier, register and competent authority for this authorization case?", "kind": "identity", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "authorization-case-identifier-register-and-competent-authority-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports authorization case identifier, register and competent authority?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "authorization-case-identifier-register-and-competent-authority-q03", "text": "How may authorization case identifier, register and competent authority be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "authorization-case-identifier-register-and-competent-authority-data", "name": "Authorization case identifier, register and competent authority data", "description": "Structured authority-qualified case data for authorization case identifier, register and competent authority.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "authorization-case-identifier-register-and-competent-authority-record", "name": "Authorization case identifier, register and competent authority record", "description": "Versioned evidence-bearing case record for authorization case identifier, register and competent authority with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus authorization-case-identifier-register-and-competent-authority assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "permit-licence-approval-registration-exemption-and-certificate-class", "name": "Permit, licence, approval, registration, exemption and certificate class", "description": "Jurisdiction-qualified case and requested-output class, class-definition version, regulated domain, synonyms, exclusions and uncertainty.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "questions": [ { "id": "permit-licence-approval-registration-exemption-and-certificate-class-q01", "text": "What exact identities, classes, values, links and explicit unknowns define permit, licence, approval, registration, exemption and certificate class for this authorization case?", "kind": "classification", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "permit-licence-approval-registration-exemption-and-certificate-class-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports permit, licence, approval, registration, exemption and certificate class?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "permit-licence-approval-registration-exemption-and-certificate-class-q03", "text": "How may permit, licence, approval, registration, exemption and certificate class be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "permit-licence-approval-registration-exemption-and-certificate-class-data", "name": "Permit, licence, approval, registration, exemption and certificate class data", "description": "Structured authority-qualified case data for permit, licence, approval, registration, exemption and certificate class.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "permit-licence-approval-registration-exemption-and-certificate-class-record", "name": "Permit, licence, approval, registration, exemption and certificate class record", "description": "Versioned evidence-bearing case record for permit, licence, approval, registration, exemption and certificate class with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus permit-licence-approval-registration-exemption-and-certificate-class assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "applicant-representative-authority-and-case-roles", "name": "Applicant, representative, authority and case roles", "description": "References external actors and records their procedural capacity and authority interval.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "findings": [ { "id": "applicant-holder-operator-owner-beneficiary-and-subject-reference", "name": "Applicant, holder, operator, owner, beneficiary and subject reference", "description": "External party or regulated-object references, role, representation, identity-assurance level, authority and valid interval.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ], "questions": [ { "id": "applicant-holder-operator-owner-beneficiary-and-subject-reference-q01", "text": "What exact identities, classes, values, links and explicit unknowns define applicant, holder, operator, owner, beneficiary and subject reference for this authorization case?", "kind": "relationship", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "applicant-holder-operator-owner-beneficiary-and-subject-reference-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports applicant, holder, operator, owner, beneficiary and subject reference?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "applicant-holder-operator-owner-beneficiary-and-subject-reference-q03", "text": "How may applicant, holder, operator, owner, beneficiary and subject reference be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "applicant-holder-operator-owner-beneficiary-and-subject-reference-data", "name": "Applicant, holder, operator, owner, beneficiary and subject reference data", "description": "Structured authority-qualified case data for applicant, holder, operator, owner, beneficiary and subject reference.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "applicant-holder-operator-owner-beneficiary-and-subject-reference-record", "name": "Applicant, holder, operator, owner, beneficiary and subject reference record", "description": "Versioned evidence-bearing case record for applicant, holder, operator, owner, beneficiary and subject reference with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus applicant-holder-operator-owner-beneficiary-and-subject-reference assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "caseworker-assessor-consultee-decider-and-delegation", "name": "Caseworker, assessor, consultee, decider and delegation", "description": "External actor, procedural role, competence, assignment, segregation of duties, delegation basis, interval and conflict disclosure.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "questions": [ { "id": "caseworker-assessor-consultee-decider-and-delegation-q01", "text": "What exact identities, classes, values, links and explicit unknowns define caseworker, assessor, consultee, decider and delegation for this authorization case?", "kind": "authority", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "caseworker-assessor-consultee-decider-and-delegation-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports caseworker, assessor, consultee, decider and delegation?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "caseworker-assessor-consultee-decider-and-delegation-q03", "text": "How may caseworker, assessor, consultee, decider and delegation be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "caseworker-assessor-consultee-decider-and-delegation-data", "name": "Caseworker, assessor, consultee, decider and delegation data", "description": "Structured authority-qualified case data for caseworker, assessor, consultee, decider and delegation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "caseworker-assessor-consultee-decider-and-delegation-record", "name": "Caseworker, assessor, consultee, decider and delegation record", "description": "Versioned evidence-bearing case record for caseworker, assessor, consultee, decider and delegation with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus caseworker-assessor-consultee-decider-and-delegation assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "service-legal-basis-and-requested-scope", "name": "Service, legal basis and requested scope", "description": "Pins the public-service profile, governing legal sources and the exact authorization requested.", "rationale": "A user may complete a service process without acquiring a right unless a competent decision and external grant record establish it.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007" ], "layers": [ { "id": "public-service-procedure-and-legal-framework", "name": "Public service, procedure and legal framework", "description": "Connects the case to the advertised service, procedure, legal basis and current requirements.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005" ], "findings": [ { "id": "service-procedure-channel-jurisdiction-and-competent-authority-profile", "name": "Service, procedure, channel, jurisdiction and competent-authority profile", "description": "External service and procedure identifiers, channel, language, jurisdiction, delivery rules, authority, profile version and availability.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "service-procedure-channel-jurisdiction-and-competent-authority-profile-q01", "text": "What exact identities, classes, values, links and explicit unknowns define service, procedure, channel, jurisdiction and competent-authority profile for this authorization case?", "kind": "classification", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "service-procedure-channel-jurisdiction-and-competent-authority-profile-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports service, procedure, channel, jurisdiction and competent-authority profile?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "service-procedure-channel-jurisdiction-and-competent-authority-profile-q03", "text": "How may service, procedure, channel, jurisdiction and competent-authority profile be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "service-procedure-channel-jurisdiction-and-competent-authority-profile-data", "name": "Service, procedure, channel, jurisdiction and competent-authority profile data", "description": "Structured authority-qualified case data for service, procedure, channel, jurisdiction and competent-authority profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "service-procedure-channel-jurisdiction-and-competent-authority-profile-record", "name": "Service, procedure, channel, jurisdiction and competent-authority profile record", "description": "Versioned evidence-bearing case record for service, procedure, channel, jurisdiction and competent-authority profile with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus service-procedure-channel-jurisdiction-and-competent-authority-profile assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "legal-resource-enabling-power-requirement-set-and-version", "name": "Legal resource, enabling power, requirement set and version", "description": "External legal instruments, delegated competence, applicable requirement and criterion-set versions, effect time and exceptions.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "legal-resource-enabling-power-requirement-set-and-version-q01", "text": "What exact identities, classes, values, links and explicit unknowns define legal resource, enabling power, requirement set and version for this authorization case?", "kind": "authority", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "legal-resource-enabling-power-requirement-set-and-version-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports legal resource, enabling power, requirement set and version?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "legal-resource-enabling-power-requirement-set-and-version-q03", "text": "How may legal resource, enabling power, requirement set and version be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "legal-resource-enabling-power-requirement-set-and-version-data", "name": "Legal resource, enabling power, requirement set and version data", "description": "Structured authority-qualified case data for legal resource, enabling power, requirement set and version.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "legal-resource-enabling-power-requirement-set-and-version-record", "name": "Legal resource, enabling power, requirement set and version record", "description": "Versioned evidence-bearing case record for legal resource, enabling power, requirement set and version with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus legal-resource-enabling-power-requirement-set-and-version assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "requested-activity-object-place-time-and-limits", "name": "Requested activity, object, place, time and limits", "description": "Defines the precise permission sought and exclusions from the request.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009" ], "findings": [ { "id": "regulated-activity-object-facility-resource-and-holder-capacity", "name": "Regulated activity, object, facility, resource and holder capacity", "description": "Requested acts, regulated subjects, facilities, resources, operator capacity, purpose, quantities and external object references.", "source_refs": [ "SRC-005", "SRC-007" ], "questions": [ { "id": "regulated-activity-object-facility-resource-and-holder-capacity-q01", "text": "What exact identities, classes, values, links and explicit unknowns define regulated activity, object, facility, resource and holder capacity for this authorization case?", "kind": "definition", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "regulated-activity-object-facility-resource-and-holder-capacity-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports regulated activity, object, facility, resource and holder capacity?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "regulated-activity-object-facility-resource-and-holder-capacity-q03", "text": "How may regulated activity, object, facility, resource and holder capacity be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "regulated-activity-object-facility-resource-and-holder-capacity-data", "name": "Regulated activity, object, facility, resource and holder capacity data", "description": "Structured authority-qualified case data for regulated activity, object, facility, resource and holder capacity.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "regulated-activity-object-facility-resource-and-holder-capacity-record", "name": "Regulated activity, object, facility, resource and holder capacity record", "description": "Versioned evidence-bearing case record for regulated activity, object, facility, resource and holder capacity with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus regulated-activity-object-facility-resource-and-holder-capacity assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "geographic-temporal-quantitative-operational-scope-and-exclusions", "name": "Geographic, temporal, quantitative, operational scope and exclusions", "description": "Requested territory, site, period, schedule, thresholds, quotas, methods, equipment, excluded acts and uncertainty.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009" ], "questions": [ { "id": "geographic-temporal-quantitative-operational-scope-and-exclusions-q01", "text": "What exact identities, classes, values, links and explicit unknowns define geographic, temporal, quantitative, operational scope and exclusions for this authorization case?", "kind": "requirement", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "geographic-temporal-quantitative-operational-scope-and-exclusions-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports geographic, temporal, quantitative, operational scope and exclusions?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "geographic-temporal-quantitative-operational-scope-and-exclusions-q03", "text": "How may geographic, temporal, quantitative, operational scope and exclusions be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "geographic-temporal-quantitative-operational-scope-and-exclusions-data", "name": "Geographic, temporal, quantitative, operational scope and exclusions data", "description": "Structured authority-qualified case data for geographic, temporal, quantitative, operational scope and exclusions.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "geographic-temporal-quantitative-operational-scope-and-exclusions-record", "name": "Geographic, temporal, quantitative, operational scope and exclusions record", "description": "Versioned evidence-bearing case record for geographic, temporal, quantitative, operational scope and exclusions with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus geographic-temporal-quantitative-operational-scope-and-exclusions assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-005", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "application-submissions-evidence-and-cost", "name": "Application, submissions, evidence and cost", "description": "Preserves submitted claims and evidence use while keeping source artifacts, payments and reusable criteria externally mastered.", "rationale": "A received document, payment or registry lookup does not by itself prove a criterion or authorize the activity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-008" ], "layers": [ { "id": "application-revisions-declarations-and-completeness", "name": "Application revisions, declarations and completeness", "description": "Tracks request revisions, signatures, declarations, required fields and procedural completeness.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-010" ], "findings": [ { "id": "application-submission-revision-signature-and-receipt", "name": "Application submission, revision, signature and receipt", "description": "Submission identifier, content revision, applicant declaration, representative authority, signature, channel, receipt, timestamps and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-010" ], "questions": [ { "id": "application-submission-revision-signature-and-receipt-q01", "text": "What exact identities, classes, values, links and explicit unknowns define application submission, revision, signature and receipt for this authorization case?", "kind": "event", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "application-submission-revision-signature-and-receipt-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports application submission, revision, signature and receipt?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "application-submission-revision-signature-and-receipt-q03", "text": "How may application submission, revision, signature and receipt be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "application-submission-revision-signature-and-receipt-data", "name": "Application submission, revision, signature and receipt data", "description": "Structured authority-qualified case data for application submission, revision, signature and receipt.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-010" ] } ], "artifacts": [ { "id": "application-submission-revision-signature-and-receipt-record", "name": "Application submission, revision, signature and receipt record", "description": "Versioned evidence-bearing case record for application submission, revision, signature and receipt with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus application-submission-revision-signature-and-receipt assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "completeness-validation-missing-information-and-cure-request", "name": "Completeness validation, missing information and cure request", "description": "Required fields, missing or invalid items, cure notice, deadline, response, waiver, lapse risk and validation result.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "completeness-validation-missing-information-and-cure-request-q01", "text": "What exact identities, classes, values, links and explicit unknowns define completeness validation, missing information and cure request for this authorization case?", "kind": "validation", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "completeness-validation-missing-information-and-cure-request-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports completeness validation, missing information and cure request?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "completeness-validation-missing-information-and-cure-request-q03", "text": "How may completeness validation, missing information and cure request be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "completeness-validation-missing-information-and-cure-request-data", "name": "Completeness validation, missing information and cure request data", "description": "Structured authority-qualified case data for completeness validation, missing information and cure request.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "completeness-validation-missing-information-and-cure-request-record", "name": "Completeness validation, missing information and cure request record", "description": "Versioned evidence-bearing case record for completeness validation, missing information and cure request with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus completeness-validation-missing-information-and-cure-request assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "evidence-claims-fees-and-data-exchange", "name": "Evidence, claims, fees and data exchange", "description": "Records what was offered, requested, verified or paid without importing the evidence or payment master.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-008" ], "findings": [ { "id": "criterion-evidence-submission-supported-value-and-verification", "name": "Criterion, evidence submission, supported value and verification", "description": "Criterion version, external evidence artifact or registry record, submitted claim, supported value, provider, validity, verification method and finding.", "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ], "questions": [ { "id": "criterion-evidence-submission-supported-value-and-verification-q01", "text": "What exact identities, classes, values, links and explicit unknowns define criterion, evidence submission, supported value and verification for this authorization case?", "kind": "evidence", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "criterion-evidence-submission-supported-value-and-verification-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports criterion, evidence submission, supported value and verification?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "criterion-evidence-submission-supported-value-and-verification-q03", "text": "How may criterion, evidence submission, supported value and verification be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "criterion-evidence-submission-supported-value-and-verification-data", "name": "Criterion, evidence submission, supported value and verification data", "description": "Structured authority-qualified case data for criterion, evidence submission, supported value and verification.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "criterion-evidence-submission-supported-value-and-verification-record", "name": "Criterion, evidence submission, supported value and verification record", "description": "Versioned evidence-bearing case record for criterion, evidence submission, supported value and verification with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus criterion-evidence-submission-supported-value-and-verification assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "fee-charge-payment-waiver-refund-and-cost-reference", "name": "Fee, charge, payment, waiver, refund and cost reference", "description": "External fee schedule and payment records, amount and currency, due state, waiver basis, refund trigger and non-inference rule.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "fee-charge-payment-waiver-refund-and-cost-reference-q01", "text": "What exact identities, classes, values, links and explicit unknowns define fee, charge, payment, waiver, refund and cost reference for this authorization case?", "kind": "relationship", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "fee-charge-payment-waiver-refund-and-cost-reference-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports fee, charge, payment, waiver, refund and cost reference?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "fee-charge-payment-waiver-refund-and-cost-reference-q03", "text": "How may fee, charge, payment, waiver, refund and cost reference be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "fee-charge-payment-waiver-refund-and-cost-reference-data", "name": "Fee, charge, payment, waiver, refund and cost reference data", "description": "Structured authority-qualified case data for fee, charge, payment, waiver, refund and cost reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "fee-charge-payment-waiver-refund-and-cost-reference-record", "name": "Fee, charge, payment, waiver, refund and cost reference record", "description": "Versioned evidence-bearing case record for fee, charge, payment, waiver, refund and cost reference with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus fee-charge-payment-waiver-refund-and-cost-reference assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "assessment-consultation-and-decision", "name": "Assessment, consultation and decision", "description": "Captures criterion-by-criterion findings, consultations and the competent authority's reasoned outcome.", "rationale": "Automated checks and recommendations may support a decision but do not replace the accountable decision or its legal-effect evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "assessment-plan-findings-and-consultations", "name": "Assessment plan, findings and consultations", "description": "Organizes review steps, criteria, evidence use, conflicts and external input.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ], "findings": [ { "id": "criterion-assessment-finding-score-uncertainty-and-reviewer", "name": "Criterion assessment, finding, score, uncertainty and reviewer", "description": "Criterion and version, evidence used, method, result, score, reasons, uncertainty, assessor, review time and override trail.", "source_refs": [ "SRC-002", "SRC-008" ], "questions": [ { "id": "criterion-assessment-finding-score-uncertainty-and-reviewer-q01", "text": "What exact identities, classes, values, links and explicit unknowns define criterion assessment, finding, score, uncertainty and reviewer for this authorization case?", "kind": "decision", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "criterion-assessment-finding-score-uncertainty-and-reviewer-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports criterion assessment, finding, score, uncertainty and reviewer?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "criterion-assessment-finding-score-uncertainty-and-reviewer-q03", "text": "How may criterion assessment, finding, score, uncertainty and reviewer be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "criterion-assessment-finding-score-uncertainty-and-reviewer-data", "name": "Criterion assessment, finding, score, uncertainty and reviewer data", "description": "Structured authority-qualified case data for criterion assessment, finding, score, uncertainty and reviewer.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "criterion-assessment-finding-score-uncertainty-and-reviewer-record", "name": "Criterion assessment, finding, score, uncertainty and reviewer record", "description": "Versioned evidence-bearing case record for criterion assessment, finding, score, uncertainty and reviewer with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus criterion-assessment-finding-score-uncertainty-and-reviewer assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "consultation-referral-inspection-opinion-and-conflict-of-interest", "name": "Consultation, referral, inspection, opinion and conflict of interest", "description": "External request and response, consulted body, inspection reference, opinion authority, deadline, confidentiality and conflict declaration.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ], "questions": [ { "id": "consultation-referral-inspection-opinion-and-conflict-of-interest-q01", "text": "What exact identities, classes, values, links and explicit unknowns define consultation, referral, inspection, opinion and conflict of interest for this authorization case?", "kind": "process", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "consultation-referral-inspection-opinion-and-conflict-of-interest-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports consultation, referral, inspection, opinion and conflict of interest?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "consultation-referral-inspection-opinion-and-conflict-of-interest-q03", "text": "How may consultation, referral, inspection, opinion and conflict of interest be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "consultation-referral-inspection-opinion-and-conflict-of-interest-data", "name": "Consultation, referral, inspection, opinion and conflict of interest data", "description": "Structured authority-qualified case data for consultation, referral, inspection, opinion and conflict of interest.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "consultation-referral-inspection-opinion-and-conflict-of-interest-record", "name": "Consultation, referral, inspection, opinion and conflict of interest record", "description": "Versioned evidence-bearing case record for consultation, referral, inspection, opinion and conflict of interest with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus consultation-referral-inspection-opinion-and-conflict-of-interest assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "decision-reasons-notification-and-output-reference", "name": "Decision, reasons, notification and output reference", "description": "Represents one authority-qualified conclusion and the link to any separately mastered grant.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-010" ], "findings": [ { "id": "grant-refuse-partial-defer-withdraw-lapse-and-closure-decision", "name": "Grant, refuse, partial, defer, withdraw, lapse and closure decision", "description": "Outcome, decider, competence, reasons, legal basis, affected requested scope, conditions summary, decision and effect time, confidence and signature.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-010" ], "questions": [ { "id": "grant-refuse-partial-defer-withdraw-lapse-and-closure-decision-q01", "text": "What exact identities, classes, values, links and explicit unknowns define grant, refuse, partial, defer, withdraw, lapse and closure decision for this authorization case?", "kind": "decision", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "grant-refuse-partial-defer-withdraw-lapse-and-closure-decision-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports grant, refuse, partial, defer, withdraw, lapse and closure decision?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "grant-refuse-partial-defer-withdraw-lapse-and-closure-decision-q03", "text": "How may grant, refuse, partial, defer, withdraw, lapse and closure decision be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "grant-refuse-partial-defer-withdraw-lapse-and-closure-decision-data", "name": "Grant, refuse, partial, defer, withdraw, lapse and closure decision data", "description": "Structured authority-qualified case data for grant, refuse, partial, defer, withdraw, lapse and closure decision.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "grant-refuse-partial-defer-withdraw-lapse-and-closure-decision-record", "name": "Grant, refuse, partial, defer, withdraw, lapse and closure decision record", "description": "Versioned evidence-bearing case record for grant, refuse, partial, defer, withdraw, lapse and closure decision with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus grant-refuse-partial-defer-withdraw-lapse-and-closure-decision assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "decision-notification-publication-appeal-path-and-grant-reference", "name": "Decision notification, publication, appeal path and grant reference", "description": "Recipients, delivery and deemed-service time, public notice, reasons access, review or appeal route, deadline and external grant identifier.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-010" ], "questions": [ { "id": "decision-notification-publication-appeal-path-and-grant-reference-q01", "text": "What exact identities, classes, values, links and explicit unknowns define decision notification, publication, appeal path and grant reference for this authorization case?", "kind": "lifecycle", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "decision-notification-publication-appeal-path-and-grant-reference-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports decision notification, publication, appeal path and grant reference?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "decision-notification-publication-appeal-path-and-grant-reference-q03", "text": "How may decision notification, publication, appeal path and grant reference be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "decision-notification-publication-appeal-path-and-grant-reference-data", "name": "Decision notification, publication, appeal path and grant reference data", "description": "Structured authority-qualified case data for decision notification, publication, appeal path and grant reference.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-010" ] } ], "artifacts": [ { "id": "decision-notification-publication-appeal-path-and-grant-reference-record", "name": "Decision notification, publication, appeal path and grant reference record", "description": "Versioned evidence-bearing case record for decision notification, publication, appeal path and grant reference with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus decision-notification-publication-appeal-path-and-grant-reference assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "post-decision-administration-review-and-lineage", "name": "Post-decision administration, review and lineage", "description": "Tracks later administrative cases and oversight references without mutating the external permission master by inference.", "rationale": "Renewal, variation, transfer, suspension, revocation, annulment and surrender have jurisdiction-specific identity and authority consequences.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "layers": [ { "id": "conditions-monitoring-and-follow-up-obligations", "name": "Conditions, monitoring and follow-up obligations", "description": "References grant conditions, reporting schedules, inspections and noncompliance signals.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ], "findings": [ { "id": "condition-prerequisite-continuing-duty-limit-exception-and-waiver", "name": "Condition, prerequisite, continuing duty, limit, exception and waiver", "description": "External grant condition or legal norm, category, source, responsible party, deadline, trigger, exception, waiver and breach consequence.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ], "questions": [ { "id": "condition-prerequisite-continuing-duty-limit-exception-and-waiver-q01", "text": "What exact identities, classes, values, links and explicit unknowns define condition, prerequisite, continuing duty, limit, exception and waiver for this authorization case?", "kind": "requirement", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "condition-prerequisite-continuing-duty-limit-exception-and-waiver-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports condition, prerequisite, continuing duty, limit, exception and waiver?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "condition-prerequisite-continuing-duty-limit-exception-and-waiver-q03", "text": "How may condition, prerequisite, continuing duty, limit, exception and waiver be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "condition-prerequisite-continuing-duty-limit-exception-and-waiver-data", "name": "Condition, prerequisite, continuing duty, limit, exception and waiver data", "description": "Structured authority-qualified case data for condition, prerequisite, continuing duty, limit, exception and waiver.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "condition-prerequisite-continuing-duty-limit-exception-and-waiver-record", "name": "Condition, prerequisite, continuing duty, limit, exception and waiver record", "description": "Versioned evidence-bearing case record for condition, prerequisite, continuing duty, limit, exception and waiver with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus condition-prerequisite-continuing-duty-limit-exception-and-waiver assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "report-monitoring-inspection-compliance-signal-and-enforcement-reference", "name": "Report, monitoring, inspection, compliance signal and enforcement reference", "description": "External report, inspection, observation or enforcement case, scope, source, finding, time and prohibited inference.", "source_refs": [ "SRC-002", "SRC-008", "SRC-009" ], "questions": [ { "id": "report-monitoring-inspection-compliance-signal-and-enforcement-reference-q01", "text": "What exact identities, classes, values, links and explicit unknowns define report, monitoring, inspection, compliance signal and enforcement reference for this authorization case?", "kind": "relationship", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "report-monitoring-inspection-compliance-signal-and-enforcement-reference-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports report, monitoring, inspection, compliance signal and enforcement reference?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "report-monitoring-inspection-compliance-signal-and-enforcement-reference-q03", "text": "How may report, monitoring, inspection, compliance signal and enforcement reference be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "report-monitoring-inspection-compliance-signal-and-enforcement-reference-data", "name": "Report, monitoring, inspection, compliance signal and enforcement reference data", "description": "Structured authority-qualified case data for report, monitoring, inspection, compliance signal and enforcement reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "report-monitoring-inspection-compliance-signal-and-enforcement-reference-record", "name": "Report, monitoring, inspection, compliance signal and enforcement reference record", "description": "Versioned evidence-bearing case record for report, monitoring, inspection, compliance signal and enforcement reference with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus report-monitoring-inspection-compliance-signal-and-enforcement-reference assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-002", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "renewal-variation-transfer-suspension-and-termination-cases", "name": "Renewal, variation, transfer, suspension and termination cases", "description": "Represents follow-on requests and authority decisions with explicit grant-version consequences.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007", "SRC-008" ], "findings": [ { "id": "renewal-variation-transfer-extension-and-replacement-case", "name": "Renewal, variation, transfer, extension and replacement case", "description": "Parent grant and case, requested change, affected scope, new evidence, decision, effective time, identity-continuity rule and successor reference.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "questions": [ { "id": "renewal-variation-transfer-extension-and-replacement-case-q01", "text": "What exact identities, classes, values, links and explicit unknowns define renewal, variation, transfer, extension and replacement case for this authorization case?", "kind": "lifecycle", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "renewal-variation-transfer-extension-and-replacement-case-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports renewal, variation, transfer, extension and replacement case?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "renewal-variation-transfer-extension-and-replacement-case-q03", "text": "How may renewal, variation, transfer, extension and replacement case be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "renewal-variation-transfer-extension-and-replacement-case-data", "name": "Renewal, variation, transfer, extension and replacement case data", "description": "Structured authority-qualified case data for renewal, variation, transfer, extension and replacement case.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "renewal-variation-transfer-extension-and-replacement-case-record", "name": "Renewal, variation, transfer, extension and replacement case record", "description": "Versioned evidence-bearing case record for renewal, variation, transfer, extension and replacement case with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus renewal-variation-transfer-extension-and-replacement-case assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "suspension-revocation-annulment-surrender-expiry-and-reinstatement-case", "name": "Suspension, revocation, annulment, surrender, expiry and reinstatement case", "description": "Trigger, initiator, grounds, due process, decision authority, affected scope, effect time, appeal, grant update reference and tombstone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ], "questions": [ { "id": "suspension-revocation-annulment-surrender-expiry-and-reinstatement-case-q01", "text": "What exact identities, classes, values, links and explicit unknowns define suspension, revocation, annulment, surrender, expiry and reinstatement case for this authorization case?", "kind": "lifecycle", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "suspension-revocation-annulment-surrender-expiry-and-reinstatement-case-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports suspension, revocation, annulment, surrender, expiry and reinstatement case?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "suspension-revocation-annulment-surrender-expiry-and-reinstatement-case-q03", "text": "How may suspension, revocation, annulment, surrender, expiry and reinstatement case be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "suspension-revocation-annulment-surrender-expiry-and-reinstatement-case-data", "name": "Suspension, revocation, annulment, surrender, expiry and reinstatement case data", "description": "Structured authority-qualified case data for suspension, revocation, annulment, surrender, expiry and reinstatement case.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "suspension-revocation-annulment-surrender-expiry-and-reinstatement-case-record", "name": "Suspension, revocation, annulment, surrender, expiry and reinstatement case record", "description": "Versioned evidence-bearing case record for suspension, revocation, annulment, surrender, expiry and reinstatement case with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus suspension-revocation-annulment-surrender-expiry-and-reinstatement-case assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interoperability-access-records-and-agent-control", "name": "Interoperability, access, records and agent control", "description": "Provides loss-aware sector exchange, purpose-bound case views and safe automated operations.", "rationale": "A public verification view, sector message or workflow status can omit parties, evidence, appeal rights, legal effect and current grant state.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-010" ], "layers": [ { "id": "cpsv-cccev-sector-exchange-and-verification-views", "name": "CPSV, CCCEV, sector exchange and verification views", "description": "Maps service, criterion, evidence and sector messages and defines disclosure-specific projections.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "cpsv-cccev-flap-and-legalruleml-projection", "name": "CPSV, CCCEV, FLAP and LegalRuleML projection", "description": "Source and target versions, service, requirement, evidence, response, legal-source and permission mappings, omissions and round-trip limits.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "cpsv-cccev-flap-and-legalruleml-projection-q01", "text": "What exact identities, classes, values, links and explicit unknowns define cpsv, cccev, flap and legalruleml projection for this authorization case?", "kind": "interoperability", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "cpsv-cccev-flap-and-legalruleml-projection-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports cpsv, cccev, flap and legalruleml projection?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "cpsv-cccev-flap-and-legalruleml-projection-q03", "text": "How may cpsv, cccev, flap and legalruleml projection be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "cpsv-cccev-flap-and-legalruleml-projection-data", "name": "CPSV, CCCEV, FLAP and LegalRuleML projection data", "description": "Structured authority-qualified case data for cpsv, cccev, flap and legalruleml projection.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "cpsv-cccev-flap-and-legalruleml-projection-record", "name": "CPSV, CCCEV, FLAP and LegalRuleML projection record", "description": "Versioned evidence-bearing case record for cpsv, cccev, flap and legalruleml projection with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus cpsv-cccev-flap-and-legalruleml-projection assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "applicant-casefile-regulator-public-statistical-and-verification-view", "name": "Applicant casefile, regulator, public, statistical and verification view", "description": "Audience, purpose, legal status, field policy, redaction, aggregation, freshness, scope warning, expiry and inference risk.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "applicant-casefile-regulator-public-statistical-and-verification-view-q01", "text": "What exact identities, classes, values, links and explicit unknowns define applicant casefile, regulator, public, statistical and verification view for this authorization case?", "kind": "access", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "applicant-casefile-regulator-public-statistical-and-verification-view-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports applicant casefile, regulator, public, statistical and verification view?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "applicant-casefile-regulator-public-statistical-and-verification-view-q03", "text": "How may applicant casefile, regulator, public, statistical and verification view be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "applicant-casefile-regulator-public-statistical-and-verification-view-data", "name": "Applicant casefile, regulator, public, statistical and verification view data", "description": "Structured authority-qualified case data for applicant casefile, regulator, public, statistical and verification view.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "applicant-casefile-regulator-public-statistical-and-verification-view-record", "name": "Applicant casefile, regulator, public, statistical and verification view record", "description": "Versioned evidence-bearing case record for applicant casefile, regulator, public, statistical and verification view with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus applicant-casefile-regulator-public-statistical-and-verification-view assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "agent-operations-validation-retention-and-recovery", "name": "Agent operations, validation, retention and recovery", "description": "Controls automated proposals, accountable decisions, audit, concurrency and disposition.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-010" ], "findings": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation", "name": "Agent operation, authority, purpose, preconditions and confirmation", "description": "Classifies open, submit, validate, assess, request, recommend, decide, notify, disclose and close operations as autonomous, propose, confirm or forbidden.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q01", "text": "What exact identities, classes, values, links and explicit unknowns define agent operation, authority, purpose, preconditions and confirmation for this authorization case?", "kind": "security", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports agent operation, authority, purpose, preconditions and confirmation?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q03", "text": "How may agent operation, authority, purpose, preconditions and confirmation be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-data", "name": "Agent operation, authority, purpose, preconditions and confirmation data", "description": "Structured authority-qualified case data for agent operation, authority, purpose, preconditions and confirmation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-record", "name": "Agent operation, authority, purpose, preconditions and confirmation record", "description": "Versioned evidence-bearing case record for agent operation, authority, purpose, preconditions and confirmation with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus agent-operation-authority-purpose-preconditions-and-confirmation assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery", "name": "Pre-write and post-write validation, concurrency, retention and recovery", "description": "Identity, competence, requirements, evidence, reasons, legal time, appeal, access and stale-head checks with immutable event history and rollback evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010" ], "questions": [ { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-q01", "text": "What exact identities, classes, values, links and explicit unknowns define pre-write and post-write validation, concurrency, retention and recovery for this authorization case?", "kind": "validation", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-q02", "text": "Which competent actor, legal source, submission, evidence, decision and event or knowledge time supports pre-write and post-write validation, concurrency, retention and recovery?", "kind": "evidence", "answer_data": [ "actor and competence", "legal source", "submission or evidence", "decision", "times" ] }, { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-q03", "text": "How may pre-write and post-write validation, concurrency, retention and recovery be validated, contested, corrected, superseded, retained or disclosed without implying an external grant or erasing history?", "kind": "validation", "answer_data": [ "validation", "contest route", "grant non-inference", "successor", "retention and access" ] } ], "data_elements": [ { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-data", "name": "Pre-write and post-write validation, concurrency, retention and recovery data", "description": "Structured authority-qualified case data for pre-write and post-write validation, concurrency, retention and recovery.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010" ] } ], "artifacts": [ { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-record", "name": "Pre-write and post-write validation, concurrency, retention and recovery record", "description": "Versioned evidence-bearing case record for pre-write and post-write validation, concurrency, retention and recovery with legal basis, event and knowledge time, provenance and access marking.", "media_or_form": [ "logical authorization-case record", "authoritative decision or evidence reference" ], "serial": true, "identity_strategy": "Authorization-case identifier plus prewrite-postwrite-validation-concurrency-retention-and-recovery assertion or event identifier; applicant, permit number, title, date and hash never identify the case alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-008", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "open-authorization-case", "name": "Open authorization case", "description": "Create case identity, class, authority, service, legal basis, applicant roles and requested scope.", "inputs": [ "case request", "service", "authority", "applicant", "scope" ], "outputs": [ "open case revision" ], "preconditions": [ "competence, identity and service version validate" ], "effects": [ "case becomes resolvable without creating a grant" ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "submit-application-revision", "name": "Submit application revision", "description": "Append signed declarations, requested scope, receipt and completeness context.", "inputs": [ "case", "application content", "signer", "channel" ], "outputs": [ "submission event and receipt" ], "preconditions": [ "representation and required fields validate" ], "effects": [ "immutable revision is recorded for review" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-010" ] }, { "id": "attach-and-verify-evidence", "name": "Attach and verify evidence", "description": "Link external evidence or registry data to requirements and record a verification assertion.", "inputs": [ "case", "criterion", "evidence reference", "provider" ], "outputs": [ "evidence-use and verification record" ], "preconditions": [ "purpose, provider and validity resolve" ], "effects": [ "evidence use stays attributable and privacy-scoped" ], "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] }, { "id": "assess-criterion", "name": "Assess criterion", "description": "Record method, evidence used, result, reasons, uncertainty and accountable reviewer for one criterion.", "inputs": [ "case", "criterion version", "evidence", "method" ], "outputs": [ "assessment finding" ], "preconditions": [ "criterion and reviewer authority resolve" ], "effects": [ "finding contributes to review without becoming the final decision" ], "source_refs": [ "SRC-002", "SRC-008" ] }, { "id": "request-information-or-consultation", "name": "Request information or consultation", "description": "Issue a cure, referral, consultation or inspection request and track the response deadline.", "inputs": [ "case", "request kind", "recipient", "scope", "deadline" ], "outputs": [ "request and response tracking record" ], "preconditions": [ "authority, necessity and disclosure validate" ], "effects": [ "review is paused or enriched with attributable input" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "issue-reasoned-decision", "name": "Issue reasoned decision", "description": "Record grant, refusal, partial, defer, withdrawal, lapse or closure with authority, reasons and effect time.", "inputs": [ "case", "assessment set", "decider", "outcome", "reasons" ], "outputs": [ "signed decision record" ], "preconditions": [ "competence, due process, reasons and affected scope validate" ], "effects": [ "case outcome is fixed without itself creating a grant master" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-010" ] }, { "id": "notify-and-bind-grant-reference", "name": "Notify and bind grant reference", "description": "Record decision delivery, publication, appeal route and any separately mastered authorization identifier.", "inputs": [ "case", "decision", "recipients", "grant reference" ], "outputs": [ "notification and output-link record" ], "preconditions": [ "decision, recipient policy and external grant resolve" ], "effects": [ "parties can verify outcome without conflating case and grant" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] }, { "id": "open-follow-on-administration-case", "name": "Open follow-on administration case", "description": "Create renewal, variation, transfer, suspension, revocation, annulment, surrender or reinstatement case.", "inputs": [ "grant reference", "case kind", "trigger", "authority" ], "outputs": [ "linked follow-on case" ], "preconditions": [ "grant and jurisdictional identity-continuity rule resolve" ], "effects": [ "later action stays auditable and cannot mutate grant by inference" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-007" ] }, { "id": "issue-purpose-bound-case-view", "name": "Issue purpose-bound case view", "description": "Create applicant, regulator, public, statistical or sector exchange projection with declared omissions.", "inputs": [ "case revision", "audience", "purpose", "profile" ], "outputs": [ "validated projection" ], "preconditions": [ "access, freshness and target version validate" ], "effects": [ "view links source digest, scope warning and omissions" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ] }, { "id": "close-and-retain-case", "name": "Close and retain case", "description": "Close, lapse, withdraw, archive or tombstone the case while preserving decisions, appeals and grant references.", "inputs": [ "case", "closure basis", "retention policy" ], "outputs": [ "closure event and retention schedule" ], "preconditions": [ "appeal, legal hold and disposition authority validate" ], "effects": [ "active processing ends while citable history remains" ], "source_refs": [ "SRC-003", "SRC-008", "SRC-010" ] } ], "composition": [ { "target": "Granted Right, Attestation or Credential model", "relation": "REFERENCE", "purpose": "Resolve the permission-bearing grant created, changed or terminated after an authority decision.", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "target": "Person, Organization, Public Authority, Public Service and Legal Instrument models", "relation": "REFERENCE", "purpose": "Resolve applicants, representatives, competent actors, reusable procedure definitions and governing law.", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "Criterion, Evidence, Payment, Inspection, Enforcement and Appeal Case models", "relation": "REFERENCE", "purpose": "Connect case-specific use and findings to external requirement, artifact, financial, oversight and review masters.", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] }, { "target": "CPSV-AP and CCCEV", "relation": "ALIGN", "purpose": "Project public-service, requirement, evidence, output and participation bindings.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "LegalRuleML and UN/CEFACT FLAP", "relation": "ALIGN", "purpose": "Project legal-source and permission semantics plus sector authorization messages with declared loss.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, authorization-case authority, rights-register authority and namespace", "Service, requirement, evidence, application, assessment, decision, grant-reference, appeal and lifecycle registries", "Master-system mappings for parties, authorities, legal instruments, grants, evidence, payments, inspections and enforcement", "Competence, identity, requirements, evidence, reasons, due process, access, retention and agent-operation policies" ], "namespace_guidance": "Mint authorization-case identifiers only when no competent authority identity exists; keep applicants, authorities, legal sources, public services, criteria, evidence artifacts, payments, inspections, appeals, enforcement and grants as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local authorization-case, submission, assessment, decision, notification and follow-on action registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by competent-authority case identifier and register, never by applicant, permit number, requested activity, decision date, document or hash.", "Keep authorization case, application revision, assessment, decision, notification and external permission-bearing grant separately identifiable." ], "patch_rules": [ "Extensions declare jurisdiction and sector profile, target finding, legal source, authority, criterion and exchange-profile versions and interoperability impact.", "Case identity, competence, requirement semantics, decision effect or grant-reference changes require a successor revision, migration map and retained cited history." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when identity, competence, requested scope, criteria, evidence links, reasons, legal times, appeal, access and provenance remain intact.", "Every CPSV, CCCEV, LegalRuleML or sector projection pins versions and states transformed fields, omissions and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Competent authority's master case identifier, qualified by register and jurisdiction.", "Governed globally resolvable authorization-case IRI with authority binding.", "Dimension UUID or ULID when no external identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and offset or Z; separate submission, receipt, assessment, decision, notification, legal-effect, observation, knowledge and ingestion times.", "serial_naming_rule": "Use {authorization-case-id}--{artifact-kind}--{assertion-or-event-id}; never use applicant, permit number, title, date or hash alone.", "integrity_rule": "Store digest, media type, issuer, legal-source and profile versions, authority, source anchors, valid and knowledge times, quality, confidentiality, licence and access marking." }, "policies": [ "Only a competent authority may issue a decision or establish its legal effect; automation may validate and recommend but cannot invent competence.", "A successful process, payment, submitted evidence, status page or decision copy never alone proves a current external grant.", "Criteria, evidence, inspections, enforcement and appeal records remain in their authoritative masters and are referenced with purpose and freshness.", "Agents may perform reversible clerical actions and propose findings; final decisions, adverse actions, sensitive disclosure and disposition require accountable authority." ], "crud": { "read": [ "Resolve Dimension, jurisdiction, case register, competent authority, service and requirement versions, current revision, legal time and access purpose." ], "create": [ "Create case identity, class, authority, legal basis, applicant roles, requested scope and explicit unknowns before assessment or decision." ], "update": [ "Append submission, evidence-use, finding, consultation, decision or event with actor, authority, reason, time and provenance; never overwrite cited history." ], "delete": [ "Apply appeal, legal hold and records policy; prefer withdrawal, closure or tombstone and never cascade to applicants, evidence, grants or enforcement records." ] }, "roles": [ { "name": "Authorization authority", "responsibilities": [ "Own case identity, competence, procedure and authority-qualified decisions." ] }, { "name": "Applicant or representative", "responsibilities": [ "Submit declarations and evidence and receive notices and reasons under applicable access rights." ] }, { "name": "Caseworker", "responsibilities": [ "Validate completeness, manage communications and preserve procedural history." ] }, { "name": "Assessor or consultee", "responsibilities": [ "Produce criterion findings or opinions with method, evidence and conflict disclosure." ] }, { "name": "Accountable decider", "responsibilities": [ "Issue signed reasoned decisions within delegated competence." ] }, { "name": "Rights-register steward", "responsibilities": [ "Own the permission-bearing grant and its authoritative current status outside this case model." ] }, { "name": "Access and records steward", "responsibilities": [ "Apply casefile disclosure, retention, legal hold and audit policy." ] } ], "access": { "default_rule": "Deny mutation and casefile disclosure unless authority, role, purpose and field policy grant it; public verification must use the external grant master and disclose minimum necessary data.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory disclosure, appeal, oversight or emergency access cites authority and remains purpose-bound, attributable and reviewable." ], "audit_requirements": [ "Log actor, agent, role, purpose, case, operation, policy, RFC 3339 time, authority, affected fields, external references and outcome." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension authorization, rights-register, legal-source, requirement, evidence, due-process, access and retention policies.", "Read this model and linked party, authority, service, legal instrument, grant, evidence, payment, inspection, enforcement and appeal models before mutation." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of a permit or authorization application and decision case across CPSV-AP, CCCEV, EU procedure and evidence rules, LegalRuleML and UN/CEFACT sector exchange, without universal licensing-law, automatic-decision, grant-validity or certified crosswalk claims.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Authority-qualified case identity is separated from application revisions, decisions and external grants." }, { "dimension": "classification and definition", "status": "covered", "notes": "Permit, licence, approval, registration, exemption and certificate classes are jurisdiction-qualified." }, { "dimension": "direct properties", "status": "covered", "notes": "Requested scope, submissions, criteria, findings, decisions, reasons, deadlines and case states are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Receipts, evidence-use, verification, assessment, signature and notification evidence are covered." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Open, submit, verify, assess, consult, decide, notify, review, project and close operations are governed." }, { "dimension": "composition", "status": "covered", "notes": "Parties, authorities, services, laws, criteria, evidence, payments, inspections, enforcement, appeals and grants retain external masters." }, { "dimension": "lifecycle", "status": "covered", "notes": "Submission, cure, review, decision, notification, follow-on action, closure and retention preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Actor roles, requirement-evidence links, consultations, decisions, appeals and grant references are typed." }, { "dimension": "temporal", "status": "covered", "notes": "Submission, receipt, assessment, decision, notification, effect, observation and knowledge times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Requested place and territorial jurisdiction are referenced without importing geographic masters." }, { "dimension": "provenance", "status": "covered", "notes": "Application derivation, evidence use, assessment method, decision authority and publication remain attributable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Authorization case, rights register, evidence, payment, inspection and enforcement masters remain separate." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, competence, completeness, criteria, evidence, reasons, legal time, appeal, access and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Applicant, regulator, public, statistical and sector views are purpose-bound." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Submissions, findings, decisions, appeals, external grant links and tombstones are preserved." }, { "dimension": "interoperability", "status": "covered", "notes": "CPSV-AP, CCCEV, LegalRuleML and UN/CEFACT sector projections are loss-aware." } ], "known_omissions": [ "No independent Claude or Grok result was available; later administrative-law and sector review is required before canonical promotion.", "Jurisdiction-specific licensing, due-process, appeal, automatic-decision, fee, inspection, sanction and grant-identity profiles require specialist review.", "The frozen relation ledger contains no approved WM-POL-004 rows; all composition targets remain draft.", "Certified CPSV-AP, CCCEV, LegalRuleML and sector-message crosswalks and conformance fixtures remain future work." ], "conflicts": [ "The legacy model owns the application-to-decision process, while the permission-bearing grant remains an external right or attestation master.", "Application status and current grant status can disagree and must not be inferred from one another.", "Permit, licence, approval, registration, exemption and certificate classifications vary by jurisdiction and sector." ], "regional_assumptions": [ "CPSV-AP, CCCEV and the Single Digital Gateway provide European interoperability patterns rather than universal administrative law.", "UN/CEFACT FLAP is a fishing-sector profile and cannot define every permit process.", "LegalRuleML represents legal and deontic semantics but does not create authority or a binding decision." ], "adversarial_checks": [ "Reject a case identified solely by applicant, permit number, requested activity, date or file hash.", "Reject a successful workflow, payment or evidence submission represented as a valid external grant.", "Reject an automated recommendation treated as a competent authority decision.", "Reject revocation, suspension, renewal or transfer inferred from monitoring without authoritative event and grant update.", "Reject public verification that exposes protected case data or omits jurisdiction, scope, freshness and grant-master source." ] }, "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 as an authorization process case, not the permission-bearing grant", "rationale": "The legacy specification and registry purpose define application-to-decision processing. The case owns submissions, assessments, consultations, decisions and follow-on administrative actions, while the actual grant, reusable service, law, criteria, evidence artifacts, payments, inspections, enforcement and appeals remain external masters." }, "decisions": [ { "concept": "Case versus grant", "disposition": "legacy case boundary retained", "rationale": "A favorable decision references a separately mastered right or attestation; process completion, a permit number and current grant validity cannot be inferred from one another." }, { "concept": "Permit class semantics", "disposition": "accepted as jurisdiction-qualified classification", "rationale": "Permit, licence, approval, registration, exemption and certificate may differ by sector and legal system and are not universal synonyms." }, { "concept": "Requirements and evidence", "disposition": "accepted as external masters with case-specific use", "rationale": "The case records submission, supported claim, verification and assessment, while reusable criteria and source evidence artifacts retain independent identity and privacy policy." }, { "concept": "Decision authority", "disposition": "accepted as accountable authority event", "rationale": "Automated checks and recommendations may inform a result but cannot invent competence, due process, reasons or legal effect." }, { "concept": "Post-decision administration", "disposition": "accepted as linked follow-on cases", "rationale": "Renewal, variation, transfer, suspension, revocation, annulment, surrender and reinstatement record authority and effect without mutating the external grant by inference." }, { "concept": "Status and time", "disposition": "accepted as separate case and grant axes", "rationale": "Submission, review, decision, notification and closure state is not external grant state; decision, effect, observation and knowledge times remain distinct." }, { "concept": "Public verification", "disposition": "external grant master required", "rationale": "A case projection may show a decision and reference, but current authorization validity must resolve the authoritative grant, scope, jurisdiction and freshness." }, { "concept": "Interoperability", "disposition": "accepted as loss-aware projections", "rationale": "CPSV-AP, CCCEV, LegalRuleML and UN/CEFACT FLAP address different service, evidence, legal and sector concerns, so mappings disclose version and loss." }, { "concept": "Approved registry composition", "disposition": "held pending relation governance", "rationale": "The approved relation ledger contains no WM-POL-004 rows, so all proposed links remain draft." } ], "publicationHolds": [ "Claude and Grok timed out during their bounded attempts, so independent external review is absent and explicitly waived for this published reviewable draft.", "The approved relationship ledger contains no WM-POL-004 rows, so all proposed sibling composition remains draft.", "Jurisdiction-specific licensing, due-process, appeal, automatic-decision, fee, inspection, sanction and grant-identity profiles require specialist review.", "Certified CPSV-AP, CCCEV, LegalRuleML and UN/CEFACT sector crosswalks and conformance fixtures remain unverified.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Approve identifiers and relation cardinalities for grants, attestations, parties, authorities, services, laws, evidence, payments, inspections, enforcement and appeals.", "Develop jurisdiction and sector profiles for licensing, registration, approval, exemption, certificate and renewal or termination processes.", "Create fixtures for partial grants, cure requests, reused evidence, automated recommendations, deemed notification, appeals, transfer, suspension and stale public verification.", "Validate certified service, criterion, evidence, legal-rule and sector-message projections with privacy, authority, legal-time, information-loss and round-trip tests." ] }, "statistics": { "sources": 10, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }