# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T22:05:10Z", "synthesisSha256": "b30339f1767af438b2c10b4486278851d49ca30a16fecb3073e62a0643f5598b", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-KNW-013", "registryId": "vr.wm-knw-013", "name": "Constraint / Requirement Rule", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.KNW.CNS" ], "tags": [ "constraint", "requirement", "rule", "inf.knw.cns" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-knw-013-constraint-requirement-rule/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-knw-013", "model": { "registry_id": "vr.wm-knw-013", "model_id": "WM-KNW-013", "name": "Constraint / Requirement Rule", "entry_kind": "entity", "purpose": "Represent one governed formal or formalizable rule that constrains, requires, permits or prohibits a subject under explicit applicability, authority and evaluation semantics.", "scope_statement": "Owns rule identity and immutable revision; source statement and normalized expression; rule kind, normative modality, severity, priority and criticality; issuer, owner, steward, subject, target, beneficiary and authority; rationale and evidence references; scope, jurisdiction, system boundary, applicability, trigger, preconditions and effective period; predicate, operands, variables, operators, datatypes, units, tolerance, cardinality, quantifiers and logical composition; dependencies and traceability; evaluation input, engine, profile, result and evidence; exceptions, waivers, conflicts and precedence; approval, effectivity, suspension, correction, retirement, access, retention and loss-aware projections. Requirement, policy, standard, control, system, object, actor, decision, test, observation, evidence, exception and enforcement masters remain external.", "in_scope": [ "Rule identity, source and normalized expression, kind, modality, revision and authority", "Applicability, predicate, operands, datatypes, units, logic, dependency, traceability, evaluation and outcomes", "Exceptions, conflicts, lifecycle, provenance, governance, access, retention and interoperability" ], "out_of_scope": [ "Owning stakeholder need, requirement record, policy, standard, control, system, object, actor, decision, test, observation, evidence, exception or enforcement lifecycles", "Equating syntax validity with satisfaction, satisfaction with conformance, conformance with compliance, rule-engine output with accountable decision, or normative keyword with authority absent an adopting context", "Executing approval, waiver, enforcement, protected disclosure, external system mutation, safety action or irreversible deletion" ], "boundary_notes": [ { "neighbor": "WM-REC-006 Requirement", "distinction": "Requirement owns the stakeholder need or governed requirement record. Constraint / Requirement Rule owns a separately reusable formal or formalizable normative expression; the candidate parent signal is held for review.", "source_refs": [ "SRC-001", "SRC-002", "SRC-020", "SRC-021" ] }, { "neighbor": "Policy, standard and control", "distinction": "These authoritative packages may issue or group rules. Their identity, governance and lifecycle remain external while each rule preserves source and authority.", "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ] }, { "neighbor": "Validation shape and schema", "distinction": "SHACL, JSON Schema and Schematron are executable projections. Schema syntax, engine conformance and validation reports do not replace rule identity or substantive intent.", "source_refs": [ "SRC-006", "SRC-015", "SRC-016" ] }, { "neighbor": "Decision and enforcement", "distinction": "A rule evaluation supplies a qualified result. Accountable decisions, remedies, sanctions and physical or digital enforcement remain external actions.", "source_refs": [ "SRC-005", "SRC-009", "SRC-013", "SRC-014", "SRC-024" ] }, { "neighbor": "Test, evidence and compliance assessment", "distinction": "Tests and evidence support verification or assessment. A passed test or satisfied predicate does not by itself prove system validation, compliance, safety or legal effect.", "source_refs": [ "SRC-001", "SRC-002", "SRC-012", "SRC-018", "SRC-019" ] }, { "neighbor": "Exception, deviation and waiver", "distinction": "The rule records bounded exception references and their effect on evaluation. The external authorization case and accountable approval remain independently mastered.", "source_refs": [ "SRC-013", "SRC-014", "SRC-018" ] }, { "neighbor": "Rule engine and executable code", "distinction": "Engines evaluate pinned projections against input snapshots. Runtime, deployment, code, security and operational lifecycles remain external.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-014", "SRC-015", "SRC-016", "SRC-024" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ISO/IEC/IEEE 29148 Requirements engineering", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/72089.html", "version_or_date": "ISO/IEC/IEEE 29148:2018, confirmed 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines requirements engineering processes and required information items." }, { "id": "SRC-002", "title": "Systems Modeling Language", "organization": "Object Management Group", "url": "https://www.omg.org/spec/SysML/2.0", "version_or_date": "OMG SysML 2.0, September 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines precise system and requirement modeling, relations and machine-readable syntax." }, { "id": "SRC-003", "title": "Object Constraint Language", "organization": "Object Management Group", "url": "https://www.omg.org/spec/OCL/2.4", "version_or_date": "OMG OCL 2.4, February 2014", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines declarative constraints, invariants, preconditions and postconditions over models." }, { "id": "SRC-004", "title": "Semantics of Business Vocabulary and Business Rules", "organization": "Object Management Group", "url": "https://www.omg.org/spec/SBVR/1.5", "version_or_date": "OMG SBVR 1.5", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines business vocabularies, fact types, rules, modalities and formulations." }, { "id": "SRC-005", "title": "Decision Model and Notation", "organization": "Object Management Group", "url": "https://www.omg.org/spec/DMN/1.5", "version_or_date": "OMG DMN 1.5", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines decision requirements, decision logic, inputs and FEEL expressions." }, { "id": "SRC-006", "title": "Shapes Constraint Language", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/shacl/", "version_or_date": "W3C Recommendation, 20 July 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines RDF graph constraints, targets, severity, validation and reports." }, { "id": "SRC-007", "title": "OWL 2 Web Ontology Language Structural Specification", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/owl2-syntax/", "version_or_date": "W3C Recommendation, 11 December 2012", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines ontology axioms, class expressions, restrictions and logical structure." }, { "id": "SRC-008", "title": "SPARQL 1.1 Query Language", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/sparql11-query/", "version_or_date": "W3C Recommendation, 21 March 2013", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines graph patterns, expressions, filters and query result semantics." }, { "id": "SRC-009", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation, 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines permissions, prohibitions, duties, constraints, operands and operators." }, { "id": "SRC-010", "title": "Constraints of the PROV Data Model", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-constraints/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines inference, uniqueness, ordering, impossibility, normalization and validity constraints." }, { "id": "SRC-011", "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-06T21:59:00Z", "relevance": "Defines entities, activities, agents, attribution, derivation, revision and invalidation." }, { "id": "SRC-012", "title": "Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note, 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines quality measurements, annotations, policies and provenance." }, { "id": "SRC-013", "title": "LegalRuleML Core Specification", "organization": "OASIS Open", "url": "https://www.oasis-open.org/standard/legalruleml-core-specification-version-1-0-oasis-standard/", "version_or_date": "LegalRuleML 1.0, 30 August 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines legal normative rules, temporal aspects, authority, defeasibility and metadata." }, { "id": "SRC-014", "title": "XACML Version 3.0", "organization": "OASIS Open", "url": "https://www.oasis-open.org/standard/xacmlv3-0/", "version_or_date": "XACML 3.0 plus Errata 01, July 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines policy sets, targets, rules, effects, combining algorithms, requests and decisions." }, { "id": "SRC-015", "title": "JSON Schema Draft 2020-12", "organization": "JSON Schema", "url": "https://json-schema.org/draft/2020-12", "version_or_date": "Draft 2020-12", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines JSON instance constraints, annotations, vocabularies and evaluation results." }, { "id": "SRC-016", "title": "Schematron", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/85625.html", "version_or_date": "ISO/IEC 19757-3:2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines rule-based XML validation using patterns, assertions and query languages." }, { "id": "SRC-017", "title": "OpenAPI Specification", "organization": "OpenAPI Initiative", "url": "https://spec.openapis.org/oas/v3.1.1.html", "version_or_date": "OpenAPI 3.1.1, 24 October 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines API contracts, schemas, parameters, responses and security requirements." }, { "id": "SRC-018", "title": "OSCAL", "organization": "National Institute of Standards and Technology", "url": "https://pages.nist.gov/OSCAL/", "version_or_date": "OSCAL 1.1.3, accessed 2026-09-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines machine-readable control catalogs, profiles, implementations and assessments." }, { "id": "SRC-019", "title": "Security and Privacy Controls", "organization": "National Institute of Standards and Technology", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final", "version_or_date": "NIST SP 800-53 Rev. 5 Update 1", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines control requirements, parameters, enhancements and assessment context." }, { "id": "SRC-020", "title": "Key words for use in RFCs", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc2119.html", "version_or_date": "RFC 2119, March 1997", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines MUST, SHOULD, MAY and related normative requirement levels." }, { "id": "SRC-021", "title": "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc8174.html", "version_or_date": "RFC 8174, May 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Clarifies that normative keyword interpretation applies only when explicitly invoked." }, { "id": "SRC-022", "title": "Date and Time on the Internet", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines timestamps with seconds and explicit numeric offsets or Z." }, { "id": "SRC-023", "title": "JSON Canonicalization Scheme", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc8785.html", "version_or_date": "RFC 8785, June 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines deterministic JSON canonicalization for hashing and signing." }, { "id": "SRC-024", "title": "Open Policy Agent Policy Language", "organization": "Cloud Native Computing Foundation", "url": "https://www.openpolicyagent.org/docs/policy-language", "version_or_date": "OPA Rego documentation accessed 2026-09-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T21:59:00Z", "relevance": "Defines a declarative policy language, rule evaluation, inputs, outputs and conflicts." } ], "structure": { "bundles": [ { "id": "rule-identity-expression-kind-and-force", "name": "Rule identity, expression, kind and force", "description": "Groups the governed Resource Consumption concern for rule identity, expression, kind and force.", "rationale": "Identify one governed rule and preserve source and normalized expressions.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023", "SRC-006", "SRC-009", "SRC-013", "SRC-014" ], "layers": [ { "id": "identity-revision-source-and-expression", "name": "Identity, revision, source and expression", "description": "Groups Resource Consumption context for identity, revision, source and expression without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023" ], "findings": [ { "id": "rule-identifier-namespace-version-revision-predecessor-and-successor", "name": "Rule identifier, namespace, version, revision, predecessor and successor", "description": "Records rule identifier, namespace, version, revision, predecessor and successor as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023" ], "questions": [ { "id": "rule-identifier-namespace-version-revision-predecessor-and-successor-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish rule identifier, namespace, version, revision, predecessor and successor?", "kind": "identity", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "rule-identifier-namespace-version-revision-predecessor-and-successor-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses rule identifier, namespace, version, revision, predecessor and successor, and under which authority?", "kind": "ownership", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "rule-identifier-namespace-version-revision-predecessor-and-successor-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify rule identifier, namespace, version, revision, predecessor and successor?", "kind": "validation", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "rule-identifier-namespace-version-revision-predecessor-and-successor-data", "name": "Rule identifier, namespace, version, revision, predecessor and successor data", "description": "Typed rule-scoped values and references required to answer the governed questions for rule identifier, namespace, version, revision, predecessor and successor.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023" ] } ], "artifacts": [ { "id": "rule-identifier-namespace-version-revision-predecessor-and-successor-artifact", "name": "Rule identifier, namespace, version, revision, predecessor and successor evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting rule identifier, namespace, version, revision, predecessor and successor.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023" ] } ], "inline_only_rationale": null }, { "id": "source-statement-normalized-natural-language-and-formal-expression", "name": "Source statement, normalized natural language and formal expression", "description": "Records source statement, normalized natural language and formal expression as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023" ], "questions": [ { "id": "source-statement-normalized-natural-language-and-formal-expression-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish source statement, normalized natural language and formal expression?", "kind": "definition", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "source-statement-normalized-natural-language-and-formal-expression-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses source statement, normalized natural language and formal expression, and under which authority?", "kind": "authority", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "source-statement-normalized-natural-language-and-formal-expression-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify source statement, normalized natural language and formal expression?", "kind": "security", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "source-statement-normalized-natural-language-and-formal-expression-data", "name": "Source statement, normalized natural language and formal expression data", "description": "Typed rule-scoped values and references required to answer the governed questions for source statement, normalized natural language and formal expression.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023" ] } ], "artifacts": [ { "id": "source-statement-normalized-natural-language-and-formal-expression-artifact", "name": "Source statement, normalized natural language and formal expression evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting source statement, normalized natural language and formal expression.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023" ] } ], "inline_only_rationale": null } ] }, { "id": "rule-kind-modality-and-criticality", "name": "Rule kind, modality and criticality", "description": "Groups Resource Consumption context for rule kind, modality and criticality without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-020", "SRC-021" ], "findings": [ { "id": "requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind", "name": "Requirement, constraint, invariant, business, validation, policy and legal rule kind", "description": "Records requirement, constraint, invariant, business, validation, policy and legal rule kind as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-020", "SRC-021" ], "questions": [ { "id": "requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish requirement, constraint, invariant, business, validation, policy and legal rule kind?", "kind": "classification", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses requirement, constraint, invariant, business, validation, policy and legal rule kind, and under which authority?", "kind": "requirement", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify requirement, constraint, invariant, business, validation, policy and legal rule kind?", "kind": "privacy", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind-data", "name": "Requirement, constraint, invariant, business, validation, policy and legal rule kind data", "description": "Typed rule-scoped values and references required to answer the governed questions for requirement, constraint, invariant, business, validation, policy and legal rule kind.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-020", "SRC-021" ] } ], "artifacts": [ { "id": "requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind-artifact", "name": "Requirement, constraint, invariant, business, validation, policy and legal rule kind evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting requirement, constraint, invariant, business, validation, policy and legal rule kind.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-020", "SRC-021" ] } ], "inline_only_rationale": null }, { "id": "obligation-prohibition-permission-must-should-may-severity-priority-and-criticality", "name": "Obligation, prohibition, permission, must, should, may, severity, priority and criticality", "description": "Records obligation, prohibition, permission, must, should, may, severity, priority and criticality as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-020", "SRC-021" ], "questions": [ { "id": "obligation-prohibition-permission-must-should-may-severity-priority-and-criticality-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish obligation, prohibition, permission, must, should, may, severity, priority and criticality?", "kind": "requirement", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "obligation-prohibition-permission-must-should-may-severity-priority-and-criticality-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses obligation, prohibition, permission, must, should, may, severity, priority and criticality, and under which authority?", "kind": "constraint", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "obligation-prohibition-permission-must-should-may-severity-priority-and-criticality-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify obligation, prohibition, permission, must, should, may, severity, priority and criticality?", "kind": "retention", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "obligation-prohibition-permission-must-should-may-severity-priority-and-criticality-data", "name": "Obligation, prohibition, permission, must, should, may, severity, priority and criticality data", "description": "Typed rule-scoped values and references required to answer the governed questions for obligation, prohibition, permission, must, should, may, severity, priority and criticality.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-020", "SRC-021" ] } ], "artifacts": [ { "id": "obligation-prohibition-permission-must-should-may-severity-priority-and-criticality-artifact", "name": "Obligation, prohibition, permission, must, should, may, severity, priority and criticality evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting obligation, prohibition, permission, must, should, may, severity, priority and criticality.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-020", "SRC-021" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "authority-subject-scope-and-applicability", "name": "Authority, subject, scope and applicability", "description": "Groups the governed Resource Consumption concern for authority, subject, scope and applicability.", "rationale": "Bind every rule to accountable authority, target and activation context.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019", "SRC-003", "SRC-006", "SRC-022" ], "layers": [ { "id": "issuer-owner-roles-and-authority", "name": "Issuer, owner, roles and authority", "description": "Groups Resource Consumption context for issuer, owner, roles and authority without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ], "findings": [ { "id": "issuer-owner-steward-subject-target-beneficiary-and-accountable-role", "name": "Issuer, owner, steward, subject, target, beneficiary and accountable role", "description": "Records issuer, owner, steward, subject, target, beneficiary and accountable role as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ], "questions": [ { "id": "issuer-owner-steward-subject-target-beneficiary-and-accountable-role-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish issuer, owner, steward, subject, target, beneficiary and accountable role?", "kind": "authority", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "issuer-owner-steward-subject-target-beneficiary-and-accountable-role-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses issuer, owner, steward, subject, target, beneficiary and accountable role, and under which authority?", "kind": "process", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "issuer-owner-steward-subject-target-beneficiary-and-accountable-role-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify issuer, owner, steward, subject, target, beneficiary and accountable role?", "kind": "access", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "issuer-owner-steward-subject-target-beneficiary-and-accountable-role-data", "name": "Issuer, owner, steward, subject, target, beneficiary and accountable role data", "description": "Typed rule-scoped values and references required to answer the governed questions for issuer, owner, steward, subject, target, beneficiary and accountable role.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ] } ], "artifacts": [ { "id": "issuer-owner-steward-subject-target-beneficiary-and-accountable-role-artifact", "name": "Issuer, owner, steward, subject, target, beneficiary and accountable role evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting issuer, owner, steward, subject, target, beneficiary and accountable role.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "mandate-source-rationale-evidence-jurisdiction-and-authority-scope", "name": "Mandate, source, rationale, evidence, jurisdiction and authority scope", "description": "Records mandate, source, rationale, evidence, jurisdiction and authority scope as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ], "questions": [ { "id": "mandate-source-rationale-evidence-jurisdiction-and-authority-scope-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish mandate, source, rationale, evidence, jurisdiction and authority scope?", "kind": "provenance", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "mandate-source-rationale-evidence-jurisdiction-and-authority-scope-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses mandate, source, rationale, evidence, jurisdiction and authority scope, and under which authority?", "kind": "event", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "mandate-source-rationale-evidence-jurisdiction-and-authority-scope-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify mandate, source, rationale, evidence, jurisdiction and authority scope?", "kind": "exception", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "mandate-source-rationale-evidence-jurisdiction-and-authority-scope-data", "name": "Mandate, source, rationale, evidence, jurisdiction and authority scope data", "description": "Typed rule-scoped values and references required to answer the governed questions for mandate, source, rationale, evidence, jurisdiction and authority scope.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ] } ], "artifacts": [ { "id": "mandate-source-rationale-evidence-jurisdiction-and-authority-scope-artifact", "name": "Mandate, source, rationale, evidence, jurisdiction and authority scope evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting mandate, source, rationale, evidence, jurisdiction and authority scope.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ] } ], "inline_only_rationale": null } ] }, { "id": "applicability-context-trigger-and-time", "name": "Applicability, context, trigger and time", "description": "Groups Resource Consumption context for applicability, context, trigger and time without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-022" ], "findings": [ { "id": "subject-class-object-scope-system-boundary-context-and-exclusion", "name": "Subject class, object scope, system boundary, context and exclusion", "description": "Records subject class, object scope, system boundary, context and exclusion as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-022" ], "questions": [ { "id": "subject-class-object-scope-system-boundary-context-and-exclusion-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish subject class, object scope, system boundary, context and exclusion?", "kind": "constraint", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "subject-class-object-scope-system-boundary-context-and-exclusion-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses subject class, object scope, system boundary, context and exclusion, and under which authority?", "kind": "measurement", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "subject-class-object-scope-system-boundary-context-and-exclusion-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify subject class, object scope, system boundary, context and exclusion?", "kind": "interoperability", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "subject-class-object-scope-system-boundary-context-and-exclusion-data", "name": "Subject class, object scope, system boundary, context and exclusion data", "description": "Typed rule-scoped values and references required to answer the governed questions for subject class, object scope, system boundary, context and exclusion.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-022" ] } ], "artifacts": [ { "id": "subject-class-object-scope-system-boundary-context-and-exclusion-artifact", "name": "Subject class, object scope, system boundary, context and exclusion evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting subject class, object scope, system boundary, context and exclusion.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-022" ] } ], "inline_only_rationale": null }, { "id": "precondition-activation-trigger-effective-period-suspension-and-expiry", "name": "Precondition, activation trigger, effective period, suspension and expiry", "description": "Records precondition, activation trigger, effective period, suspension and expiry as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-022" ], "questions": [ { "id": "precondition-activation-trigger-effective-period-suspension-and-expiry-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish precondition, activation trigger, effective period, suspension and expiry?", "kind": "temporal", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "precondition-activation-trigger-effective-period-suspension-and-expiry-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses precondition, activation trigger, effective period, suspension and expiry, and under which authority?", "kind": "evidence", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "precondition-activation-trigger-effective-period-suspension-and-expiry-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify precondition, activation trigger, effective period, suspension and expiry?", "kind": "decision", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "precondition-activation-trigger-effective-period-suspension-and-expiry-data", "name": "Precondition, activation trigger, effective period, suspension and expiry data", "description": "Typed rule-scoped values and references required to answer the governed questions for precondition, activation trigger, effective period, suspension and expiry.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-022" ] } ], "artifacts": [ { "id": "precondition-activation-trigger-effective-period-suspension-and-expiry-artifact", "name": "Precondition, activation trigger, effective period, suspension and expiry evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting precondition, activation trigger, effective period, suspension and expiry.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-022" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "predicate-operands-types-units-and-composition", "name": "Predicate, operands, types, units and composition", "description": "Groups the governed Resource Consumption concern for predicate, operands, types, units and composition.", "rationale": "Represent declarative logic precisely enough for reproducible evaluation.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-024", "SRC-004", "SRC-010", "SRC-013", "SRC-014" ], "layers": [ { "id": "predicate-variable-operand-and-datatype", "name": "Predicate, variable, operand and datatype", "description": "Groups Resource Consumption context for predicate, variable, operand and datatype without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-024" ], "findings": [ { "id": "predicate-left-and-right-operand-operator-variable-binding-and-function", "name": "Predicate, left and right operand, operator, variable binding and function", "description": "Records predicate, left and right operand, operator, variable binding and function as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-024" ], "questions": [ { "id": "predicate-left-and-right-operand-operator-variable-binding-and-function-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish predicate, left and right operand, operator, variable binding and function?", "kind": "constraint", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "predicate-left-and-right-operand-operator-variable-binding-and-function-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses predicate, left and right operand, operator, variable binding and function, and under which authority?", "kind": "quality", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "predicate-left-and-right-operand-operator-variable-binding-and-function-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify predicate, left and right operand, operator, variable binding and function?", "kind": "identity", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "predicate-left-and-right-operand-operator-variable-binding-and-function-data", "name": "Predicate, left and right operand, operator, variable binding and function data", "description": "Typed rule-scoped values and references required to answer the governed questions for predicate, left and right operand, operator, variable binding and function.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-024" ] } ], "artifacts": [ { "id": "predicate-left-and-right-operand-operator-variable-binding-and-function-artifact", "name": "Predicate, left and right operand, operator, variable binding and function evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting predicate, left and right operand, operator, variable binding and function.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default", "name": "Datatype, value set, unit, dimension, tolerance, pattern, cardinality and default", "description": "Records datatype, value set, unit, dimension, tolerance, pattern, cardinality and default as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-024" ], "questions": [ { "id": "datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish datatype, value set, unit, dimension, tolerance, pattern, cardinality and default?", "kind": "validation", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses datatype, value set, unit, dimension, tolerance, pattern, cardinality and default, and under which authority?", "kind": "validation", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify datatype, value set, unit, dimension, tolerance, pattern, cardinality and default?", "kind": "classification", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default-data", "name": "Datatype, value set, unit, dimension, tolerance, pattern, cardinality and default data", "description": "Typed rule-scoped values and references required to answer the governed questions for datatype, value set, unit, dimension, tolerance, pattern, cardinality and default.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-024" ] } ], "artifacts": [ { "id": "datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default-artifact", "name": "Datatype, value set, unit, dimension, tolerance, pattern, cardinality and default evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting datatype, value set, unit, dimension, tolerance, pattern, cardinality and default.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-015", "SRC-016", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "logic-quantification-composition-and-dependency", "name": "Logic, quantification, composition and dependency", "description": "Groups Resource Consumption context for logic, quantification, composition and dependency without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-014", "SRC-024" ], "findings": [ { "id": "and-or-not-xone-sequence-quantifier-implication-and-equivalence", "name": "And, or, not, xone, sequence, quantifier, implication and equivalence", "description": "Records and, or, not, xone, sequence, quantifier, implication and equivalence as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-014", "SRC-024" ], "questions": [ { "id": "and-or-not-xone-sequence-quantifier-implication-and-equivalence-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish and, or, not, xone, sequence, quantifier, implication and equivalence?", "kind": "composition", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "and-or-not-xone-sequence-quantifier-implication-and-equivalence-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses and, or, not, xone, sequence, quantifier, implication and equivalence, and under which authority?", "kind": "security", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "and-or-not-xone-sequence-quantifier-implication-and-equivalence-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify and, or, not, xone, sequence, quantifier, implication and equivalence?", "kind": "composition", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "and-or-not-xone-sequence-quantifier-implication-and-equivalence-data", "name": "And, or, not, xone, sequence, quantifier, implication and equivalence data", "description": "Typed rule-scoped values and references required to answer the governed questions for and, or, not, xone, sequence, quantifier, implication and equivalence.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-014", "SRC-024" ] } ], "artifacts": [ { "id": "and-or-not-xone-sequence-quantifier-implication-and-equivalence-artifact", "name": "And, or, not, xone, sequence, quantifier, implication and equivalence evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting and, or, not, xone, sequence, quantifier, implication and equivalence.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-014", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "dependency-import-parameter-reference-recursion-order-and-termination", "name": "Dependency, import, parameter reference, recursion, order and termination", "description": "Records dependency, import, parameter reference, recursion, order and termination as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-014", "SRC-024" ], "questions": [ { "id": "dependency-import-parameter-reference-recursion-order-and-termination-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish dependency, import, parameter reference, recursion, order and termination?", "kind": "relationship", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "dependency-import-parameter-reference-recursion-order-and-termination-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses dependency, import, parameter reference, recursion, order and termination, and under which authority?", "kind": "privacy", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "dependency-import-parameter-reference-recursion-order-and-termination-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify dependency, import, parameter reference, recursion, order and termination?", "kind": "relationship", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "dependency-import-parameter-reference-recursion-order-and-termination-data", "name": "Dependency, import, parameter reference, recursion, order and termination data", "description": "Typed rule-scoped values and references required to answer the governed questions for dependency, import, parameter reference, recursion, order and termination.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-014", "SRC-024" ] } ], "artifacts": [ { "id": "dependency-import-parameter-reference-recursion-order-and-termination-artifact", "name": "Dependency, import, parameter reference, recursion, order and termination evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting dependency, import, parameter reference, recursion, order and termination.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-014", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "traceability-exception-waiver-conflict-and-precedence", "name": "Traceability, exception, waiver, conflict and precedence", "description": "Groups the governed Resource Consumption concern for traceability, exception, waiver, conflict and precedence.", "rationale": "Keep requirement relations and bounded departures explicit and auditable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-018", "SRC-019", "SRC-009", "SRC-013", "SRC-014", "SRC-024" ], "layers": [ { "id": "requirement-trace-and-satisfaction-links", "name": "Requirement trace and satisfaction links", "description": "Groups Resource Consumption context for requirement trace and satisfaction links without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-018", "SRC-019" ], "findings": [ { "id": "need-requirement-rule-derivation-refinement-decomposition-and-allocation", "name": "Need, requirement, rule, derivation, refinement, decomposition and allocation", "description": "Records need, requirement, rule, derivation, refinement, decomposition and allocation as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-018", "SRC-019" ], "questions": [ { "id": "need-requirement-rule-derivation-refinement-decomposition-and-allocation-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish need, requirement, rule, derivation, refinement, decomposition and allocation?", "kind": "relationship", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "need-requirement-rule-derivation-refinement-decomposition-and-allocation-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses need, requirement, rule, derivation, refinement, decomposition and allocation, and under which authority?", "kind": "retention", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "need-requirement-rule-derivation-refinement-decomposition-and-allocation-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify need, requirement, rule, derivation, refinement, decomposition and allocation?", "kind": "state", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "need-requirement-rule-derivation-refinement-decomposition-and-allocation-data", "name": "Need, requirement, rule, derivation, refinement, decomposition and allocation data", "description": "Typed rule-scoped values and references required to answer the governed questions for need, requirement, rule, derivation, refinement, decomposition and allocation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-018", "SRC-019" ] } ], "artifacts": [ { "id": "need-requirement-rule-derivation-refinement-decomposition-and-allocation-artifact", "name": "Need, requirement, rule, derivation, refinement, decomposition and allocation evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting need, requirement, rule, derivation, refinement, decomposition and allocation.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-018", "SRC-019" ] } ], "inline_only_rationale": null }, { "id": "satisfaction-verification-validation-test-control-and-evidence-reference", "name": "Satisfaction, verification, validation, test, control and evidence reference", "description": "Records satisfaction, verification, validation, test, control and evidence reference as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-018", "SRC-019" ], "questions": [ { "id": "satisfaction-verification-validation-test-control-and-evidence-reference-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish satisfaction, verification, validation, test, control and evidence reference?", "kind": "evidence", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "satisfaction-verification-validation-test-control-and-evidence-reference-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses satisfaction, verification, validation, test, control and evidence reference, and under which authority?", "kind": "access", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "satisfaction-verification-validation-test-control-and-evidence-reference-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify satisfaction, verification, validation, test, control and evidence reference?", "kind": "lifecycle", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "satisfaction-verification-validation-test-control-and-evidence-reference-data", "name": "Satisfaction, verification, validation, test, control and evidence reference data", "description": "Typed rule-scoped values and references required to answer the governed questions for satisfaction, verification, validation, test, control and evidence reference.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-018", "SRC-019" ] } ], "artifacts": [ { "id": "satisfaction-verification-validation-test-control-and-evidence-reference-artifact", "name": "Satisfaction, verification, validation, test, control and evidence reference evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting satisfaction, verification, validation, test, control and evidence reference.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-011", "SRC-018", "SRC-019" ] } ], "inline_only_rationale": null } ] }, { "id": "exception-waiver-conflict-and-resolution", "name": "Exception, waiver, conflict and resolution", "description": "Groups Resource Consumption context for exception, waiver, conflict and resolution without importing neighboring master lifecycles.", "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019", "SRC-024" ], "findings": [ { "id": "exception-deviation-waiver-scope-request-approver-condition-and-expiry", "name": "Exception, deviation, waiver, scope, request, approver, condition and expiry", "description": "Records exception, deviation, waiver, scope, request, approver, condition and expiry as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019", "SRC-024" ], "questions": [ { "id": "exception-deviation-waiver-scope-request-approver-condition-and-expiry-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish exception, deviation, waiver, scope, request, approver, condition and expiry?", "kind": "exception", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "exception-deviation-waiver-scope-request-approver-condition-and-expiry-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses exception, deviation, waiver, scope, request, approver, condition and expiry, and under which authority?", "kind": "exception", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "exception-deviation-waiver-scope-request-approver-condition-and-expiry-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify exception, deviation, waiver, scope, request, approver, condition and expiry?", "kind": "temporal", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "exception-deviation-waiver-scope-request-approver-condition-and-expiry-data", "name": "Exception, deviation, waiver, scope, request, approver, condition and expiry data", "description": "Typed rule-scoped values and references required to answer the governed questions for exception, deviation, waiver, scope, request, approver, condition and expiry.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019", "SRC-024" ] } ], "artifacts": [ { "id": "exception-deviation-waiver-scope-request-approver-condition-and-expiry-artifact", "name": "Exception, deviation, waiver, scope, request, approver, condition and expiry evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting exception, deviation, waiver, scope, request, approver, condition and expiry.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "conflict-overlap-priority-specificity-precedence-combining-and-resolution", "name": "Conflict, overlap, priority, specificity, precedence, combining and resolution", "description": "Records conflict, overlap, priority, specificity, precedence, combining and resolution as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019", "SRC-024" ], "questions": [ { "id": "conflict-overlap-priority-specificity-precedence-combining-and-resolution-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish conflict, overlap, priority, specificity, precedence, combining and resolution?", "kind": "decision", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "conflict-overlap-priority-specificity-precedence-combining-and-resolution-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses conflict, overlap, priority, specificity, precedence, combining and resolution, and under which authority?", "kind": "interoperability", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "conflict-overlap-priority-specificity-precedence-combining-and-resolution-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify conflict, overlap, priority, specificity, precedence, combining and resolution?", "kind": "spatial", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "conflict-overlap-priority-specificity-precedence-combining-and-resolution-data", "name": "Conflict, overlap, priority, specificity, precedence, combining and resolution data", "description": "Typed rule-scoped values and references required to answer the governed questions for conflict, overlap, priority, specificity, precedence, combining and resolution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019", "SRC-024" ] } ], "artifacts": [ { "id": "conflict-overlap-priority-specificity-precedence-combining-and-resolution-artifact", "name": "Conflict, overlap, priority, specificity, precedence, combining and resolution evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting conflict, overlap, priority, specificity, precedence, combining and resolution.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "evaluation-outcome-evidence-and-lifecycle", "name": "Evaluation, outcome, evidence and lifecycle", "description": "Groups the governed Resource Consumption concern for evaluation, outcome, evidence and lifecycle.", "rationale": "Separate rule evaluation from conformance, compliance and accountable decision.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-024", "SRC-001", "SRC-002", "SRC-011", "SRC-013", "SRC-018", "SRC-019", "SRC-022", "SRC-023" ], "layers": [ { "id": "evaluation-input-engine-result-and-evidence", "name": "Evaluation input, engine, result and evidence", "description": "Groups Resource Consumption context for evaluation input, engine, result and evidence without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-024" ], "findings": [ { "id": "input-snapshot-engine-profile-version-evaluation-time-and-trace", "name": "Input snapshot, engine, profile version, evaluation time and trace", "description": "Records input snapshot, engine, profile version, evaluation time and trace as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-024" ], "questions": [ { "id": "input-snapshot-engine-profile-version-evaluation-time-and-trace-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish input snapshot, engine, profile version, evaluation time and trace?", "kind": "process", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "input-snapshot-engine-profile-version-evaluation-time-and-trace-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses input snapshot, engine, profile version, evaluation time and trace, and under which authority?", "kind": "decision", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "input-snapshot-engine-profile-version-evaluation-time-and-trace-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify input snapshot, engine, profile version, evaluation time and trace?", "kind": "provenance", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "input-snapshot-engine-profile-version-evaluation-time-and-trace-data", "name": "Input snapshot, engine, profile version, evaluation time and trace data", "description": "Typed rule-scoped values and references required to answer the governed questions for input snapshot, engine, profile version, evaluation time and trace.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-024" ] } ], "artifacts": [ { "id": "input-snapshot-engine-profile-version-evaluation-time-and-trace-artifact", "name": "Input snapshot, engine, profile version, evaluation time and trace evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting input snapshot, engine, profile version, evaluation time and trace.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome", "name": "Satisfied, violated, indeterminate, not applicable, unknown and waived outcome", "description": "Records satisfied, violated, indeterminate, not applicable, unknown and waived outcome as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-024" ], "questions": [ { "id": "satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish satisfied, violated, indeterminate, not applicable, unknown and waived outcome?", "kind": "state", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses satisfied, violated, indeterminate, not applicable, unknown and waived outcome, and under which authority?", "kind": "identity", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify satisfied, violated, indeterminate, not applicable, unknown and waived outcome?", "kind": "ownership", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome-data", "name": "Satisfied, violated, indeterminate, not applicable, unknown and waived outcome data", "description": "Typed rule-scoped values and references required to answer the governed questions for satisfied, violated, indeterminate, not applicable, unknown and waived outcome.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-024" ] } ], "artifacts": [ { "id": "satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome-artifact", "name": "Satisfied, violated, indeterminate, not applicable, unknown and waived outcome evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting satisfied, violated, indeterminate, not applicable, unknown and waived outcome.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "approval-effectivity-revision-and-retirement", "name": "Approval, effectivity, revision and retirement", "description": "Groups Resource Consumption context for approval, effectivity, revision and retirement without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-013", "SRC-018", "SRC-019", "SRC-022", "SRC-023" ], "findings": [ { "id": "draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state", "name": "Draft, proposed, reviewed, approved, effective, suspended, superseded and retired state", "description": "Records draft, proposed, reviewed, approved, effective, suspended, superseded and retired state as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-013", "SRC-018", "SRC-019", "SRC-022", "SRC-023" ], "questions": [ { "id": "draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish draft, proposed, reviewed, approved, effective, suspended, superseded and retired state?", "kind": "lifecycle", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses draft, proposed, reviewed, approved, effective, suspended, superseded and retired state, and under which authority?", "kind": "classification", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify draft, proposed, reviewed, approved, effective, suspended, superseded and retired state?", "kind": "authority", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state-data", "name": "Draft, proposed, reviewed, approved, effective, suspended, superseded and retired state data", "description": "Typed rule-scoped values and references required to answer the governed questions for draft, proposed, reviewed, approved, effective, suspended, superseded and retired state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-013", "SRC-018", "SRC-019", "SRC-022", "SRC-023" ] } ], "artifacts": [ { "id": "draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state-artifact", "name": "Draft, proposed, reviewed, approved, effective, suspended, superseded and retired state evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting draft, proposed, reviewed, approved, effective, suspended, superseded and retired state.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-013", "SRC-018", "SRC-019", "SRC-022", "SRC-023" ] } ], "inline_only_rationale": null }, { "id": "correction-amendment-replacement-retraction-migration-and-audit-lineage", "name": "Correction, amendment, replacement, retraction, migration and audit lineage", "description": "Records correction, amendment, replacement, retraction, migration and audit lineage as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-013", "SRC-018", "SRC-019", "SRC-022", "SRC-023" ], "questions": [ { "id": "correction-amendment-replacement-retraction-migration-and-audit-lineage-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish correction, amendment, replacement, retraction, migration and audit lineage?", "kind": "lifecycle", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "correction-amendment-replacement-retraction-migration-and-audit-lineage-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses correction, amendment, replacement, retraction, migration and audit lineage, and under which authority?", "kind": "composition", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "correction-amendment-replacement-retraction-migration-and-audit-lineage-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify correction, amendment, replacement, retraction, migration and audit lineage?", "kind": "requirement", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "correction-amendment-replacement-retraction-migration-and-audit-lineage-data", "name": "Correction, amendment, replacement, retraction, migration and audit lineage data", "description": "Typed rule-scoped values and references required to answer the governed questions for correction, amendment, replacement, retraction, migration and audit lineage.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-013", "SRC-018", "SRC-019", "SRC-022", "SRC-023" ] } ], "artifacts": [ { "id": "correction-amendment-replacement-retraction-migration-and-audit-lineage-artifact", "name": "Correction, amendment, replacement, retraction, migration and audit lineage evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting correction, amendment, replacement, retraction, migration and audit lineage.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-013", "SRC-018", "SRC-019", "SRC-022", "SRC-023" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-access-retention-and-interoperability", "name": "Governance, access, retention and interoperability", "description": "Groups the governed Resource Consumption concern for governance, access, retention and interoperability.", "rationale": "Govern rule use and project multiple executable formats without hiding semantic loss.", "source_refs": [ "SRC-011", "SRC-012", "SRC-014", "SRC-018", "SRC-019", "SRC-023", "SRC-024", "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-013", "SRC-015", "SRC-016", "SRC-017", "SRC-020", "SRC-021", "SRC-022" ], "layers": [ { "id": "quality-security-access-and-retention", "name": "Quality, security, access and retention", "description": "Groups Resource Consumption context for quality, security, access and retention without importing neighboring master lifecycles.", "source_refs": [ "SRC-011", "SRC-012", "SRC-014", "SRC-018", "SRC-019", "SRC-023", "SRC-024" ], "findings": [ { "id": "completeness-consistency-decidability-testability-quality-and-assurance", "name": "Completeness, consistency, decidability, testability, quality and assurance", "description": "Records completeness, consistency, decidability, testability, quality and assurance as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-011", "SRC-012", "SRC-014", "SRC-018", "SRC-019", "SRC-023", "SRC-024" ], "questions": [ { "id": "completeness-consistency-decidability-testability-quality-and-assurance-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish completeness, consistency, decidability, testability, quality and assurance?", "kind": "quality", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "completeness-consistency-decidability-testability-quality-and-assurance-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses completeness, consistency, decidability, testability, quality and assurance, and under which authority?", "kind": "relationship", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "completeness-consistency-decidability-testability-quality-and-assurance-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify completeness, consistency, decidability, testability, quality and assurance?", "kind": "constraint", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "completeness-consistency-decidability-testability-quality-and-assurance-data", "name": "Completeness, consistency, decidability, testability, quality and assurance data", "description": "Typed rule-scoped values and references required to answer the governed questions for completeness, consistency, decidability, testability, quality and assurance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-011", "SRC-012", "SRC-014", "SRC-018", "SRC-019", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "completeness-consistency-decidability-testability-quality-and-assurance-artifact", "name": "Completeness, consistency, decidability, testability, quality and assurance evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting completeness, consistency, decidability, testability, quality and assurance.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-011", "SRC-012", "SRC-014", "SRC-018", "SRC-019", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold", "name": "Purpose, role, confidentiality, minimum disclosure, retention and legal hold", "description": "Records purpose, role, confidentiality, minimum disclosure, retention and legal hold as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-011", "SRC-012", "SRC-014", "SRC-018", "SRC-019", "SRC-023", "SRC-024" ], "questions": [ { "id": "purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish purpose, role, confidentiality, minimum disclosure, retention and legal hold?", "kind": "access", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses purpose, role, confidentiality, minimum disclosure, retention and legal hold, and under which authority?", "kind": "state", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify purpose, role, confidentiality, minimum disclosure, retention and legal hold?", "kind": "process", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold-data", "name": "Purpose, role, confidentiality, minimum disclosure, retention and legal hold data", "description": "Typed rule-scoped values and references required to answer the governed questions for purpose, role, confidentiality, minimum disclosure, retention and legal hold.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-011", "SRC-012", "SRC-014", "SRC-018", "SRC-019", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold-artifact", "name": "Purpose, role, confidentiality, minimum disclosure, retention and legal hold evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting purpose, role, confidentiality, minimum disclosure, retention and legal hold.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-011", "SRC-012", "SRC-014", "SRC-018", "SRC-019", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "standards-crosswalk-conformance-and-loss", "name": "Standards crosswalk, conformance and loss", "description": "Groups Resource Consumption context for standards crosswalk, conformance and loss without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "findings": [ { "id": "requirements-model-rule-shape-schema-policy-control-and-api-crosswalk", "name": "Requirements, model, rule, shape, schema, policy, control and API crosswalk", "description": "Records requirements, model, rule, shape, schema, policy, control and api crosswalk as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "requirements-model-rule-shape-schema-policy-control-and-api-crosswalk-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish requirements, model, rule, shape, schema, policy, control and api crosswalk?", "kind": "interoperability", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "requirements-model-rule-shape-schema-policy-control-and-api-crosswalk-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses requirements, model, rule, shape, schema, policy, control and api crosswalk, and under which authority?", "kind": "lifecycle", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "requirements-model-rule-shape-schema-policy-control-and-api-crosswalk-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify requirements, model, rule, shape, schema, policy, control and api crosswalk?", "kind": "event", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "requirements-model-rule-shape-schema-policy-control-and-api-crosswalk-data", "name": "Requirements, model, rule, shape, schema, policy, control and API crosswalk data", "description": "Typed rule-scoped values and references required to answer the governed questions for requirements, model, rule, shape, schema, policy, control and api crosswalk.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "requirements-model-rule-shape-schema-policy-control-and-api-crosswalk-artifact", "name": "Requirements, model, rule, shape, schema, policy, control and API crosswalk evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting requirements, model, rule, shape, schema, policy, control and api crosswalk.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "profile-version-license-engine-conformance-transformation-and-semantic-loss", "name": "Profile, version, license, engine conformance, transformation and semantic loss", "description": "Records profile, version, license, engine conformance, transformation and semantic loss as a source-qualified Constraint / Requirement Rule assertion while requirements, policies, standards, systems, tests, decisions, evidence and enforcement retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "profile-version-license-engine-conformance-transformation-and-semantic-loss-q01", "text": "Which identity, source expression, rule kind, normative force, subject, scope and revision establish profile, version, license, engine conformance, transformation and semantic loss?", "kind": "validation", "answer_data": [ "rule identifier, namespace, version, predecessor, source statement and normalized expression", "rule kind, modality, severity, priority, subject, target and authority", "scope, applicability, context, jurisdiction, effective period and exclusions" ] }, { "id": "profile-version-license-engine-conformance-transformation-and-semantic-loss-q02", "text": "Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses profile, version, license, engine conformance, transformation and semantic loss, and under which authority?", "kind": "temporal", "answer_data": [ "issuer, owner, steward, subject, evaluator, approver and disclosure roles", "mandate, rationale, evidence, approval, exception, conflict-resolution and revision authority", "source system, policy, jurisdiction, purpose, access, retention and audit basis" ] }, { "id": "profile-version-license-engine-conformance-transformation-and-semantic-loss-q03", "text": "Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify profile, version, license, engine conformance, transformation and semantic loss?", "kind": "measurement", "answer_data": [ "predicate, variables, operators, values, datatypes, units, tolerances and logic", "input snapshot, engine and profile versions, result state, evidence and uncertainty", "waiver, conflict, precedence, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "profile-version-license-engine-conformance-transformation-and-semantic-loss-data", "name": "Profile, version, license, engine conformance, transformation and semantic loss data", "description": "Typed rule-scoped values and references required to answer the governed questions for profile, version, license, engine conformance, transformation and semantic loss.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "profile-version-license-engine-conformance-transformation-and-semantic-loss-artifact", "name": "Profile, version, license, engine conformance, transformation and semantic loss evidence manifest", "description": "Digest-addressed manifest of expressions, applicability, predicates, inputs, evaluations, exceptions, conflicts and revisions supporting profile, version, license, engine conformance, transformation and semantic loss.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative rule, requirement or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-rule", "name": "Register rule", "description": "Create one stable rule identity, source statement and initial revision.", "inputs": [ "source statement", "issuer", "owner" ], "outputs": [ "rule identifier", "initial revision" ], "preconditions": [ "active Dimension", "create authority" ], "effects": [ "identity and unknowns are appended" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-011", "SRC-020", "SRC-021", "SRC-023" ] }, { "id": "formalize-rule", "name": "Formalize rule", "description": "Append a normalized natural-language or formal expression linked to the source statement.", "inputs": [ "rule revision", "expression", "language profile" ], "outputs": [ "versioned formalization" ], "preconditions": [ "terms and source resolvable" ], "effects": [ "source and normalized meanings remain distinct" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-009", "SRC-013", "SRC-015" ] }, { "id": "classify-rule", "name": "Classify rule", "description": "Record rule kind, normative force, severity, priority and criticality.", "inputs": [ "rule revision", "kind", "modality" ], "outputs": [ "classification assertion" ], "preconditions": [ "profile pinned" ], "effects": [ "classification is source-qualified" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009", "SRC-020", "SRC-021" ] }, { "id": "bind-applicability", "name": "Bind applicability", "description": "Record target, authority, scope, context, preconditions, trigger and effective period.", "inputs": [ "rule revision", "scope", "authority" ], "outputs": [ "applicability profile" ], "preconditions": [ "identities resolvable" ], "effects": [ "activation and exclusions are explicit" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-009", "SRC-013", "SRC-014", "SRC-022" ] }, { "id": "compose-and-trace", "name": "Compose and trace rules", "description": "Bind operands, logical composition, dependencies, requirements, controls and tests.", "inputs": [ "rule revision", "components", "relations" ], "outputs": [ "composition graph" ], "preconditions": [ "component versions pinned" ], "effects": [ "derivation and dependency lineage is appended" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-018" ] }, { "id": "approve-activate", "name": "Approve or activate", "description": "Append review, approval, effectivity, suspension or retirement state under authority.", "inputs": [ "rule revision", "decision reference", "effective time" ], "outputs": [ "lifecycle assertion" ], "preconditions": [ "approval authority", "conflicts reviewed" ], "effects": [ "prior states remain immutable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-013", "SRC-018", "SRC-019" ] }, { "id": "evaluate-rule", "name": "Evaluate rule", "description": "Evaluate a pinned rule against a source-qualified input snapshot and retain the trace.", "inputs": [ "rule revision", "input snapshot", "engine profile" ], "outputs": [ "qualified outcome", "evaluation trace" ], "preconditions": [ "rule active", "engine supports profile" ], "effects": [ "result remains distinct from compliance or decision" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-010", "SRC-014", "SRC-015", "SRC-016", "SRC-024" ] }, { "id": "record-exception-conflict", "name": "Record exception or conflict", "description": "Append a bounded waiver, deviation, overlap or precedence resolution without altering source rules.", "inputs": [ "rules", "exception or conflict", "authority" ], "outputs": [ "qualified resolution" ], "preconditions": [ "scope and expiry known" ], "effects": [ "competing rules and rationale remain visible" ], "source_refs": [ "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-024" ] }, { "id": "revise-supersede", "name": "Revise or supersede", "description": "Create a corrected, amended or replacement rule without overwriting history.", "inputs": [ "current revision", "reason", "replacement" ], "outputs": [ "successor revision", "difference trace" ], "preconditions": [ "revision authority" ], "effects": [ "prior rule and evaluations remain resolvable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-023" ] }, { "id": "project-rule", "name": "Project rule view", "description": "Produce minimum-necessary standards-aligned or executable views with declared loss.", "inputs": [ "rule revision", "target profile", "purpose" ], "outputs": [ "versioned projection", "semantic-loss declaration" ], "preconditions": [ "authorized recipient", "pinned target" ], "effects": [ "projection is logged and source identity preserved" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "composition": [ { "target": "WM-REC-006 Requirement", "relation": "REFERENCE", "purpose": "Resolve the owning need or requirement record while the candidate parent relation remains under joint boundary review.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-020", "SRC-021" ] }, { "target": "Policy, standard, control, system, object, test, decision, evidence, exception and enforcement masters", "relation": "REFERENCE", "purpose": "Resolve source, subject, evaluation and operational context without importing neighboring lifecycles.", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-013", "SRC-014", "SRC-018", "SRC-019" ] }, { "target": "ISO/IEC/IEEE 29148 and OMG SysML 2.0", "relation": "ALIGN", "purpose": "Project requirements engineering, traceability, derivation, satisfaction and system-model semantics.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "OMG OCL, SBVR and DMN", "relation": "ALIGN", "purpose": "Project model constraints, business vocabulary, normative rules, decision requirements and expressions.", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "target": "W3C SHACL, OWL, SPARQL, ODRL and PROV constraints", "relation": "ALIGN", "purpose": "Project graph validation, axioms, query expressions, policy constraints, normalization and validity.", "required": false, "source_refs": [ "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010" ] }, { "target": "PROV-O and DQV", "relation": "ALIGN", "purpose": "Project revision, attribution, invalidation, quality and validation provenance.", "required": false, "source_refs": [ "SRC-011", "SRC-012" ] }, { "target": "OASIS LegalRuleML and XACML", "relation": "ALIGN", "purpose": "Project legal normative and authorization-policy rule profiles with explicit limits.", "required": false, "source_refs": [ "SRC-013", "SRC-014" ] }, { "target": "JSON Schema 2020-12 and ISO Schematron 2025", "relation": "ALIGN", "purpose": "Project JSON and XML constraint expressions and evaluation outputs.", "required": false, "source_refs": [ "SRC-015", "SRC-016" ] }, { "target": "OpenAPI 3.1.1, NIST OSCAL and SP 800-53", "relation": "ALIGN", "purpose": "Project API, control-catalog, implementation and assessment requirement views.", "required": false, "source_refs": [ "SRC-017", "SRC-018", "SRC-019" ] }, { "target": "RFC 2119, RFC 8174, RFC 3339 and RFC 8785", "relation": "ALIGN", "purpose": "Project normative keyword, temporal and deterministic serialization semantics.", "required": false, "source_refs": [ "SRC-020", "SRC-021", "SRC-022", "SRC-023" ] }, { "target": "CNCF Open Policy Agent Rego", "relation": "ALIGN", "purpose": "Project one declarative policy-engine profile without making Rego the logical master.", "required": false, "source_refs": [ "SRC-024" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, rule steward, requirement and policy owners, issuing authorities, evaluators, approvers and disclosure roles.", "Register authoritative requirement, policy, standard, control, system, object, test, decision, exception, evidence and enforcement masters.", "Publish rule-kind, modality, operator, datatype, unit, outcome, precedence, access, retention and interoperability registries.", "Pin domain, model, schema, policy, legal, safety, security, jurisdiction, engine and exchange profiles." ], "namespace_guidance": "Mint rule, expression, revision, evaluation, exception, resolution and projection identifiers only in the adopting Dimension namespace; preserve requirement, policy, standard, system, test, decision, evidence and enforcement identities as typed external references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local rule, operator, outcome, authority, exception, access, retention and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, authoritative rule identity, rule kind, source statement, immutable revision, applicability profile, issuer and source; never use title, text hash, filename or expression alone as identity.", "Keep need, requirement record, constraint rule, policy, control, standard, test, validation result, compliance assessment, decision, exception, waiver and enforcement action distinct." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, domain profile, authority, source, rationale, access, time, engine and interoperability impact.", "Breaking changes require a new version, migration and crosswalk maps, compatibility declaration and continued resolution of prior rule revisions, evaluations and exceptions." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when identity, kind, modality, predicate, applicability, authority, lifecycle, evaluation and access meaning remain intact.", "SysML, OCL, SBVR, DMN, SHACL, OWL, SPARQL, ODRL, LegalRuleML, XACML, JSON Schema, Schematron, OSCAL, OpenAPI and Rego mappings pin source and target versions and declare transformed, omitted or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for the rule and immutable expression revision.", "Governed globally resolvable rule, requirement or policy IRI.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record event timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep issue, approval, effective, evaluation, exception, suspension, correction and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {rule-id}--{artifact-kind}--{revision-or-evaluation-id}; never use a date, title, expression, result, filename or hash alone as identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and vocabulary versions, rule and applicability scope, clocks, provenance, assurance, license, engine and access marking for each retained serial artifact." }, "policies": [ "The adopting Dimension declares who may issue, formalize, classify, approve, activate, evaluate, waive, resolve, revise, disclose, retain and tombstone rules.", "Every assertion requires rule identity and revision, kind, modality, subject, applicability, source, authority, state, evidence and lineage as applicable.", "Agents never infer substantive correctness, legal force, conformance, compliance, safety or accountable approval from syntactic validity, a rule-engine outcome or one source alone.", "Requirements, policies, standards, controls, systems, tests, decisions, evidence, exceptions and enforcement remain external masters.", "Automated agents may append low-risk formalizations, validations and projections under delegation, but approval, waiver, enforcement, protected disclosure and irreversible deletion require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, requested revision, rule kind, applicability, effective horizon, assurance, engine, license and access policy; return the minimum permitted projection." ], "create": [ "Create stable identity, source statement, rule kind, issuer, authority, subject, applicability and explicit unknowns before adding formal execution semantics." ], "update": [ "Append an immutable expression, applicability, approval, evaluation, exception, resolution or correction revision with actor, authority, reason, RFC 3339 effective time and predecessor." ], "delete": [ "Apply safety, legal, policy, dispute, audit, retention and legal-hold rules; tombstone eligible Rule-owned records or withdraw projections while preserving identity, material provenance and non-cascading external references." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Rule steward", "responsibilities": [ "Own rule identity, kinds, operators, lifecycle, version and crosswalk policy." ] }, { "name": "Issuer or requirement owner", "responsibilities": [ "Own source intent, authority, applicability, rationale and approval request." ] }, { "name": "Domain or vocabulary steward", "responsibilities": [ "Own referenced terms, datatypes, units, value sets and profiles." ] }, { "name": "Rule author or formalizer", "responsibilities": [ "Own normalized expression, mappings, test fixtures and declared semantic limits." ] }, { "name": "Evaluator or engine authority", "responsibilities": [ "Own input snapshot, engine, profile, evaluation trace and result assertion." ] }, { "name": "Approver or exception authority", "responsibilities": [ "Own effectivity, waiver, deviation, conflict resolution and accountable decisions." ] }, { "name": "Reviewer or auditor", "responsibilities": [ "Review authority, consistency, results, conflicts, corrections, access and retention without rewriting originals." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless active Dimension, role, purpose, rule sensitivity, jurisdiction, license and field policy grant the action; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency or legally compelled access must be grounded, time-limited, purpose-bound, attributable, independently reviewed and unable to erase immutable rule, evaluation, exception or legal-hold evidence." ], "audit_requirements": [ "Log actor, role, purpose, rule and revision identity, action, decision, policy, engine and vocabulary versions, RFC 3339 timestamp with offset, affected fields, source evidence and outcome for privileged mutation or disclosure." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, issuing and exception authorities, active domain, policy, jurisdiction, time, access, retention and licensing rules.", "Read this model AGENTS.md, pinned spec.yaml and required requirement, policy, standard, control, system, test, decision, evidence and enforcement instructions before mutation." ] } }, "coverage": { "claim": "WM-KNW-013 covers a versioned formal or formalizable Constraint / Requirement Rule with identity, expression, kind, normative force, authority, applicability, predicate, composition, traceability, evaluation, exceptions, conflict handling, lifecycle, governance and loss-aware interoperability. Domain, legal, safety, policy, engine and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Rule, expression revision, evaluation, exception, resolution and successor identities remain distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Requirement, constraint, invariant, business, validation, policy and legal rule profiles are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Expression, modality, subject, scope, predicate, operands, logic, severity, state and outcome are covered." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Input snapshots, engine traces, tests, evidence and evaluations remain independently identified." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, proposed, approved, effective, suspended, superseded and retired states preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Requirements, policies, standards, controls, systems, tests, decisions, exceptions and evidence use typed references." }, { "dimension": "temporal", "status": "covered", "notes": "Issue, approval, effective, evaluation, waiver, suspension, correction and ingestion clocks remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Jurisdiction, system boundary, environment and location scope are represented where relevant." }, { "dimension": "provenance", "status": "covered", "notes": "Issuer, source, rationale, formalization, approval, evaluation, exception, conflict resolution and revision are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Rule ownership, requirement ownership, system responsibility, evaluation authority and enforcement authority are not conflated." }, { "dimension": "validation", "status": "covered", "notes": "Identity, expression, applicability, type, unit, logic, engine, outcome, exception and crosswalk checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, policy sensitivity, minimum projection and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Corrections, disputes, exceptions, audit or legal hold, withdrawal and tombstones are non-cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "Requirements, modeling, rule, schema, policy, control and API mappings disclose loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Registration, formalization, classification, applicability, composition, activation, evaluation, exception, revision and projection declare controlled effects." } ], "known_omissions": [ "Domain, safety, legal, policy, security, privacy, jurisdiction, engine, licensing and retention profiles require expert review.", "Requirements, policies, standards, controls, systems, objects, tests, decisions, evidence, exceptions and enforcement lifecycles remain neighboring masters.", "Universal satisfiability, conflict resolution, theorem proving, optimization, code generation, autonomous enforcement and legal-effect determination remain future work." ], "conflicts": [ "Requirement, constraint, invariant, business rule, validation shape, policy rule and legal norm use different authority and evaluation semantics and require a profile.", "Closed-world validation, open-world inference, three-valued logic, defeasible legal reasoning and policy combining cannot share one universal outcome model.", "Syntactic validity, rule satisfaction, verification, validation, conformance, compliance, safety and legal effect are distinct governed claims." ], "regional_assumptions": [ "ISO and OMG engineering sources do not define every legal, business, data-quality or access-policy rule.", "LegalRuleML and XACML are legal-norm and authorization-policy profiles rather than universal constraint languages.", "Authority, waiver, enforcement, compliance, retention and legal consequences depend on organization, domain and jurisdiction." ], "adversarial_checks": [ "Reject a rule without stable identity, revision, source expression, kind, modality, subject, applicability, issuer, authority and lineage.", "Reject a requirement record, policy artifact, standard, control, test, validation result, decision, exception or enforcement action represented as the rule itself.", "Reject executable evaluation without pinned rule revision, input snapshot, engine, profile, clock, outcome vocabulary and trace.", "Reject passed syntax or validation as proof of conformance, compliance, safety, legal force or substantive correctness.", "Reject exception or precedence without scope, authority, rationale, conditions, effective time and expiry.", "Reject silent last-write-wins when rules or evaluations conflict; preserve both sources and the qualified resolution.", "Reject approval, waiver, enforcement, protected disclosure or record destruction outside delegated authority." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The root is a persistent versioned rule expression with its own identity, authority, applicability and evaluation contract. Evaluations, decisions and enforcement occur around it but do not turn the rule itself into an event." }, "decisions": [ { "concept": "Constraint / Requirement Rule entity boundary", "disposition": "accepted", "rationale": "The model owns one reusable rule and its immutable revisions rather than requirement-record authorship, validation execution or accountable enforcement." }, { "concept": "WM-REC-006 parent signal", "disposition": "held-as-reference", "rationale": "A requirement may source or own the rule, but canonical inheritance requires joint boundary review because rules also originate in policies, standards and other authorities." }, { "concept": "Rule kinds and normative force", "disposition": "accepted-with-explicit-profile", "rationale": "Requirement, constraint, invariant, business rule, validation shape, policy rule and legal norm use distinct modality and authority semantics." }, { "concept": "Expression and evaluation semantics", "disposition": "accepted-with-version-pins", "rationale": "Operands, operators, datatypes, units, logic, input snapshot, engine and profile must be source-qualified and versioned." }, { "concept": "Truth, conformance and compliance boundary", "disposition": "kept-distinct", "rationale": "Syntax validity, satisfaction, verification, validation, conformance, compliance, safety, legal effect and accountable decision are separate claims." }, { "concept": "Exception, waiver and conflict", "disposition": "accepted-with-authority-and-time", "rationale": "Departures and precedence resolutions require explicit scope, authority, rationale, conditions, effective time and expiry while source rules remain visible." }, { "concept": "Executable formats", "disposition": "accepted-as-loss-aware-projections", "rationale": "OCL, DMN, SHACL, OWL, SPARQL, ODRL, LegalRuleML, XACML, JSON Schema, Schematron, OSCAL, OpenAPI and Rego views do not replace canonical rule identity." }, { "concept": "Automated operation boundary", "disposition": "accepted-with-delegation", "rationale": "Agents may append low-risk formalizations and evaluations but not approve, waive, enforce, disclose protected data or destroy records without authority." }, { "concept": "Provider waiver and local no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet attempt timed out and one bounded Grok attempt failed with stderr suppressed and hashed. Codex separately audits the frozen validated result and comparison without acquiring new facts, so assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet attempt timed out and one Grok attempt failed before producing an admissible result; no external result was admitted.", "Relation hold: WM-REC-006 remains a reference rather than an approved parent until joint boundary review.", "Boundary hold: requirements, policies, standards, controls, systems, objects, tests, evidence, decisions, exceptions and enforcement actions remain external masters.", "Profile hold: engineering, business, validation, legal, access-control, safety and compliance rules require domain-specific semantics.", "Evaluation hold: syntax validity, rule satisfaction, verification, validation, conformance, compliance, safety and legal effect remain distinct.", "Exception hold: waivers, deviations, conflicts and precedence require accountable authority, bounded scope, rationale and time.", "Engine hold: executable evaluation requires pinned rule revision, input snapshot, engine, built-ins, profile, clock and outcome vocabulary.", "Interoperability hold: every standards projection requires exact release pins, conformance tests and semantic-loss declarations.", "Completeness hold: the 24-source draft is broad but does not claim universal domain, legal, logical, safety or operational coverage.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [] }, "statistics": { "sources": 24, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }