{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-knw-013","code":"wm-knw-013-constraint-requirement-rule","url":"https://ver.cy/models/wm-knw-013-constraint-requirement-rule/","name":"Constraint / Requirement Rule","alternateNames":[],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"entity","plane":"","domain":["INF.KNW.CNS"],"industry":["Cross-industry"],"navPath":"NAV.INF.KNW.CNS","tags":["constraint","requirement","rule","inf.knw.cns"],"facets":{}},"whatItIs":"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.","purpose":"Represent one governed formal or formalizable rule that constrains, requires, permits or prohibits a subject under explicit applicability, authority and evaluation semantics.","scope":{"in":["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":["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"],"boundaries":[{"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."},{"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."},{"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."},{"neighbor":"Decision and enforcement","distinction":"A rule evaluation supplies a qualified result. Accountable decisions, remedies, sanctions and physical or digital enforcement remain external actions."},{"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."},{"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."},{"neighbor":"Rule engine and executable code","distinction":"Engines evaluate pinned projections against input snapshots. Runtime, deployment, code, security and operational lifecycles remain external."}]},"distinguishingFeatures":["A normative statement with an explicit modality such as must, should or may, separate from the requirement record that tracks a stakeholder need.","Differs from a policy or standard document, which is a source that contains many rules, and from a control, which implements a rule.","Differs from a validation shape or schema, which checks data structure but does not carry authority or rationale.","Satisfaction, conformance and compliance are separate judgements, and a rule-engine output is not an accountable decision."],"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.","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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish rule identifier, namespace, version, revision, predecessor and successor?","id":"rule-identifier-namespace-version-revision-predecessor-and-successor-q01","kind":"identity"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses rule identifier, namespace, version, revision, predecessor and successor, and under which authority?","id":"rule-identifier-namespace-version-revision-predecessor-and-successor-q02","kind":"ownership"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify rule identifier, namespace, version, revision, predecessor and successor?","id":"rule-identifier-namespace-version-revision-predecessor-and-successor-q03","kind":"validation"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish source statement, normalized natural language and formal expression?","id":"source-statement-normalized-natural-language-and-formal-expression-q01","kind":"definition"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses source statement, normalized natural language and formal expression, and under which authority?","id":"source-statement-normalized-natural-language-and-formal-expression-q02","kind":"authority"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify source statement, normalized natural language and formal expression?","id":"source-statement-normalized-natural-language-and-formal-expression-q03","kind":"security"}]}]},{"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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish requirement, constraint, invariant, business, validation, policy and legal rule kind?","id":"requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind-q01","kind":"classification"},{"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?","id":"requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind-q02","kind":"requirement"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify requirement, constraint, invariant, business, validation, policy and legal rule kind?","id":"requirement-constraint-invariant-business-validation-policy-and-legal-rule-kind-q03","kind":"privacy"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish obligation, prohibition, permission, must, should, may, severity, priority and criticality?","id":"obligation-prohibition-permission-must-should-may-severity-priority-and-criticality-q01","kind":"requirement"},{"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?","id":"obligation-prohibition-permission-must-should-may-severity-priority-and-criticality-q02","kind":"constraint"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify obligation, prohibition, permission, must, should, may, severity, priority and criticality?","id":"obligation-prohibition-permission-must-should-may-severity-priority-and-criticality-q03","kind":"retention"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish issuer, owner, steward, subject, target, beneficiary and accountable role?","id":"issuer-owner-steward-subject-target-beneficiary-and-accountable-role-q01","kind":"authority"},{"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?","id":"issuer-owner-steward-subject-target-beneficiary-and-accountable-role-q02","kind":"process"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify issuer, owner, steward, subject, target, beneficiary and accountable role?","id":"issuer-owner-steward-subject-target-beneficiary-and-accountable-role-q03","kind":"access"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish mandate, source, rationale, evidence, jurisdiction and authority scope?","id":"mandate-source-rationale-evidence-jurisdiction-and-authority-scope-q01","kind":"provenance"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses mandate, source, rationale, evidence, jurisdiction and authority scope, and under which authority?","id":"mandate-source-rationale-evidence-jurisdiction-and-authority-scope-q02","kind":"event"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify mandate, source, rationale, evidence, jurisdiction and authority scope?","id":"mandate-source-rationale-evidence-jurisdiction-and-authority-scope-q03","kind":"exception"}]}]},{"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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish subject class, object scope, system boundary, context and exclusion?","id":"subject-class-object-scope-system-boundary-context-and-exclusion-q01","kind":"constraint"},{"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?","id":"subject-class-object-scope-system-boundary-context-and-exclusion-q02","kind":"measurement"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify subject class, object scope, system boundary, context and exclusion?","id":"subject-class-object-scope-system-boundary-context-and-exclusion-q03","kind":"interoperability"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish precondition, activation trigger, effective period, suspension and expiry?","id":"precondition-activation-trigger-effective-period-suspension-and-expiry-q01","kind":"temporal"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses precondition, activation trigger, effective period, suspension and expiry, and under which authority?","id":"precondition-activation-trigger-effective-period-suspension-and-expiry-q02","kind":"evidence"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify precondition, activation trigger, effective period, suspension and expiry?","id":"precondition-activation-trigger-effective-period-suspension-and-expiry-q03","kind":"decision"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish predicate, left and right operand, operator, variable binding and function?","id":"predicate-left-and-right-operand-operator-variable-binding-and-function-q01","kind":"constraint"},{"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?","id":"predicate-left-and-right-operand-operator-variable-binding-and-function-q02","kind":"quality"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify predicate, left and right operand, operator, variable binding and function?","id":"predicate-left-and-right-operand-operator-variable-binding-and-function-q03","kind":"identity"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish datatype, value set, unit, dimension, tolerance, pattern, cardinality and default?","id":"datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default-q01","kind":"validation"},{"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?","id":"datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default-q02","kind":"validation"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify datatype, value set, unit, dimension, tolerance, pattern, cardinality and default?","id":"datatype-value-set-unit-dimension-tolerance-pattern-cardinality-and-default-q03","kind":"classification"}]}]},{"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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish and, or, not, xone, sequence, quantifier, implication and equivalence?","id":"and-or-not-xone-sequence-quantifier-implication-and-equivalence-q01","kind":"composition"},{"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?","id":"and-or-not-xone-sequence-quantifier-implication-and-equivalence-q02","kind":"security"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify and, or, not, xone, sequence, quantifier, implication and equivalence?","id":"and-or-not-xone-sequence-quantifier-implication-and-equivalence-q03","kind":"composition"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish dependency, import, parameter reference, recursion, order and termination?","id":"dependency-import-parameter-reference-recursion-order-and-termination-q01","kind":"relationship"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses dependency, import, parameter reference, recursion, order and termination, and under which authority?","id":"dependency-import-parameter-reference-recursion-order-and-termination-q02","kind":"privacy"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify dependency, import, parameter reference, recursion, order and termination?","id":"dependency-import-parameter-reference-recursion-order-and-termination-q03","kind":"relationship"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish need, requirement, rule, derivation, refinement, decomposition and allocation?","id":"need-requirement-rule-derivation-refinement-decomposition-and-allocation-q01","kind":"relationship"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses need, requirement, rule, derivation, refinement, decomposition and allocation, and under which authority?","id":"need-requirement-rule-derivation-refinement-decomposition-and-allocation-q02","kind":"retention"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify need, requirement, rule, derivation, refinement, decomposition and allocation?","id":"need-requirement-rule-derivation-refinement-decomposition-and-allocation-q03","kind":"state"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish satisfaction, verification, validation, test, control and evidence reference?","id":"satisfaction-verification-validation-test-control-and-evidence-reference-q01","kind":"evidence"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses satisfaction, verification, validation, test, control and evidence reference, and under which authority?","id":"satisfaction-verification-validation-test-control-and-evidence-reference-q02","kind":"access"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify satisfaction, verification, validation, test, control and evidence reference?","id":"satisfaction-verification-validation-test-control-and-evidence-reference-q03","kind":"lifecycle"}]}]},{"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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish exception, deviation, waiver, scope, request, approver, condition and expiry?","id":"exception-deviation-waiver-scope-request-approver-condition-and-expiry-q01","kind":"exception"},{"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?","id":"exception-deviation-waiver-scope-request-approver-condition-and-expiry-q02","kind":"exception"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify exception, deviation, waiver, scope, request, approver, condition and expiry?","id":"exception-deviation-waiver-scope-request-approver-condition-and-expiry-q03","kind":"temporal"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish conflict, overlap, priority, specificity, precedence, combining and resolution?","id":"conflict-overlap-priority-specificity-precedence-combining-and-resolution-q01","kind":"decision"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses conflict, overlap, priority, specificity, precedence, combining and resolution, and under which authority?","id":"conflict-overlap-priority-specificity-precedence-combining-and-resolution-q02","kind":"interoperability"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify conflict, overlap, priority, specificity, precedence, combining and resolution?","id":"conflict-overlap-priority-specificity-precedence-combining-and-resolution-q03","kind":"spatial"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish input snapshot, engine, profile version, evaluation time and trace?","id":"input-snapshot-engine-profile-version-evaluation-time-and-trace-q01","kind":"process"},{"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?","id":"input-snapshot-engine-profile-version-evaluation-time-and-trace-q02","kind":"decision"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify input snapshot, engine, profile version, evaluation time and trace?","id":"input-snapshot-engine-profile-version-evaluation-time-and-trace-q03","kind":"provenance"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish satisfied, violated, indeterminate, not applicable, unknown and waived outcome?","id":"satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome-q01","kind":"state"},{"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?","id":"satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome-q02","kind":"identity"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify satisfied, violated, indeterminate, not applicable, unknown and waived outcome?","id":"satisfied-violated-indeterminate-not-applicable-unknown-and-waived-outcome-q03","kind":"ownership"}]}]},{"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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish draft, proposed, reviewed, approved, effective, suspended, superseded and retired state?","id":"draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state-q01","kind":"lifecycle"},{"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?","id":"draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state-q02","kind":"classification"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify draft, proposed, reviewed, approved, effective, suspended, superseded and retired state?","id":"draft-proposed-reviewed-approved-effective-suspended-superseded-and-retired-state-q03","kind":"authority"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish correction, amendment, replacement, retraction, migration and audit lineage?","id":"correction-amendment-replacement-retraction-migration-and-audit-lineage-q01","kind":"lifecycle"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses correction, amendment, replacement, retraction, migration and audit lineage, and under which authority?","id":"correction-amendment-replacement-retraction-migration-and-audit-lineage-q02","kind":"composition"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify correction, amendment, replacement, retraction, migration and audit lineage?","id":"correction-amendment-replacement-retraction-migration-and-audit-lineage-q03","kind":"requirement"}]}]}]},{"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.","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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish completeness, consistency, decidability, testability, quality and assurance?","id":"completeness-consistency-decidability-testability-quality-and-assurance-q01","kind":"quality"},{"text":"Who issues, owns, formalizes, approves, evaluates, waives, resolves, revises or discloses completeness, consistency, decidability, testability, quality and assurance, and under which authority?","id":"completeness-consistency-decidability-testability-quality-and-assurance-q02","kind":"relationship"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify completeness, consistency, decidability, testability, quality and assurance?","id":"completeness-consistency-decidability-testability-quality-and-assurance-q03","kind":"constraint"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish purpose, role, confidentiality, minimum disclosure, retention and legal hold?","id":"purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold-q01","kind":"access"},{"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?","id":"purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold-q02","kind":"state"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify purpose, role, confidentiality, minimum disclosure, retention and legal hold?","id":"purpose-role-confidentiality-minimum-disclosure-retention-and-legal-hold-q03","kind":"process"}]}]},{"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.","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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish requirements, model, rule, shape, schema, policy, control and api crosswalk?","id":"requirements-model-rule-shape-schema-policy-control-and-api-crosswalk-q01","kind":"interoperability"},{"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?","id":"requirements-model-rule-shape-schema-policy-control-and-api-crosswalk-q02","kind":"lifecycle"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify requirements, model, rule, shape, schema, policy, control and api crosswalk?","id":"requirements-model-rule-shape-schema-policy-control-and-api-crosswalk-q03","kind":"event"}]},{"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.","questions":[{"text":"Which identity, source expression, rule kind, normative force, subject, scope and revision establish profile, version, license, engine conformance, transformation and semantic loss?","id":"profile-version-license-engine-conformance-transformation-and-semantic-loss-q01","kind":"validation"},{"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?","id":"profile-version-license-engine-conformance-transformation-and-semantic-loss-q02","kind":"temporal"},{"text":"Which predicate, operands, dependencies, outcome, exceptions, conflicts, evidence and interoperability limits qualify profile, version, license, engine conformance, transformation and semantic loss?","id":"profile-version-license-engine-conformance-transformation-and-semantic-loss-q03","kind":"measurement"}]}]}]}]},"agentConduct":{"may":["Record a rule with its source statement, normalised expression, modality, subject and scope.","Formalise a rule into a machine-checkable expression linked to the source text.","Evaluate rules against data and record results with the rule revision used.","Detect and report conflicts, overlaps and gaps between rules."],"mustNot":["Treat a successful syntax check as proof that the rule is satisfied or correct.","Approve, activate, waive or retire a rule.","Enforce a rule against a person or system as if engine output were a decision.","Change the meaning of an active rule without a new revision.","Resolve a conflict between rules by silently choosing one."],"requiresHuman":["Approving, activating or retiring a rule.","Granting a waiver or exception.","Enforcement actions against people based on rule evaluation."]},"ethics":{"considerations":["Rules applied automatically to people must be explainable and open to challenge.","A badly formalised rule can deny people services or rights they are entitled to.","Safety and legal rules protect people, so waivers need clear accountability."],"affectedParties":["People and organisations subject to the rule","Rule owners and issuing authorities","Operators of systems that apply the rule","Auditors and regulators"]},"owners":{"steward":"Declare the Dimension owner, rule steward, requirement and policy owners, issuing authorities, evaluators, approvers and disclosure roles.","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."]}],"masterSystems":[]},"relations":[{"target":"WM-REC-006 Requirement","type":"references","note":"Resolve the owning need or requirement record while the candidate parent relation remains under joint boundary review."},{"target":"Policy, standard, control, system, object, test, decision, evidence, exception and enforcement masters","type":"references","note":"Resolve source, subject, evaluation and operational context without importing neighboring lifecycles."},{"target":"ISO/IEC/IEEE 29148 and OMG SysML 2.0","type":"aligned","note":"Project requirements engineering, traceability, derivation, satisfaction and system-model semantics."},{"target":"OMG OCL, SBVR and DMN","type":"aligned","note":"Project model constraints, business vocabulary, normative rules, decision requirements and expressions."},{"target":"W3C SHACL, OWL, SPARQL, ODRL and PROV constraints","type":"aligned","note":"Project graph validation, axioms, query expressions, policy constraints, normalization and validity."},{"target":"PROV-O and DQV","type":"aligned","note":"Project revision, attribution, invalidation, quality and validation provenance."},{"target":"OASIS LegalRuleML and XACML","type":"aligned","note":"Project legal normative and authorization-policy rule profiles with explicit limits."},{"target":"JSON Schema 2020-12 and ISO Schematron 2025","type":"aligned","note":"Project JSON and XML constraint expressions and evaluation outputs."},{"target":"OpenAPI 3.1.1, NIST OSCAL and SP 800-53","type":"aligned","note":"Project API, control-catalog, implementation and assessment requirement views."},{"target":"RFC 2119, RFC 8174, RFC 3339 and RFC 8785","type":"aligned","note":"Project normative keyword, temporal and deterministic serialization semantics."},{"target":"CNCF Open Policy Agent Rego","type":"aligned","note":"Project one declarative policy-engine profile without making Rego the logical master."},{"target":"WM-REC-006 Requirement","type":"neighbor","note":"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."},{"target":"Policy, standard and control","type":"neighbor","note":"These authoritative packages may issue or group rules. Their identity, governance and lifecycle remain external while each rule preserves source and authority."},{"target":"Validation shape and schema","type":"neighbor","note":"SHACL, JSON Schema and Schematron are executable projections. Schema syntax, engine conformance and validation reports do not replace rule identity or substantive intent."},{"target":"Decision and enforcement","type":"neighbor","note":"A rule evaluation supplies a qualified result. Accountable decisions, remedies, sanctions and physical or digital enforcement remain external actions."},{"target":"Test, evidence and compliance assessment","type":"neighbor","note":"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."},{"target":"Exception, deviation and waiver","type":"neighbor","note":"The rule records bounded exception references and their effect on evaluation. The external authorization case and accountable approval remain independently mastered."},{"target":"Rule engine and executable code","type":"neighbor","note":"Engines evaluate pinned projections against input snapshots. Runtime, deployment, code, security and operational lifecycles remain external."}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":["A rule record has a source statement, modality, subject, applicability scope, issuing authority and revision.","Often confused with a requirement record, a policy document, a control and a data validation shape."]},"capabilities":{"applicability":"required","items":["Register rule: Create one stable rule identity, source statement and initial revision.","Formalize rule: Append a normalized natural-language or formal expression linked to the source statement.","Classify rule: Record rule kind, normative force, severity, priority and criticality.","Bind applicability: Record target, authority, scope, context, preconditions, trigger and effective period.","Compose and trace rules: Bind operands, logical composition, dependencies, requirements, controls and tests.","Approve or activate: Append review, approval, effectivity, suspension or retirement state under authority.","Evaluate rule: Evaluate a pinned rule against a source-qualified input snapshot and retain the trace.","Record exception or conflict: Append a bounded waiver, deviation, overlap or precedence resolution without altering source rules.","Revise or supersede: Create a corrected, amended or replacement rule without overwriting history.","Project rule view: Produce minimum-necessary standards-aligned or executable views with declared loss."]},"hazards":{"applicability":"required","items":["Wrongful denial or approval when a formal expression differs from the source text.","Conflicting rules leading to inconsistent outcomes.","Unnoticed change of meaning between revisions.","Unaccountable enforcement through automated rule engines."]},"interfaces":{"applicability":"required","items":["ISO/IEC/IEEE 29148 requirements engineering.","OMG SBVR for business vocabulary and rules.","OASIS LegalRuleML.","OASIS XACML for authorisation policies.","W3C SHACL for data constraints."]},"context":{"applicability":"required","items":["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."]}},"sources":[{"title":"ISO/IEC/IEEE 29148 Requirements engineering","url":"https://www.iso.org/standard/72089.html","note":"International Organization for Standardization"},{"title":"Systems Modeling Language","url":"https://www.omg.org/spec/SysML/2.0","note":"Object Management Group"},{"title":"Object Constraint Language","url":"https://www.omg.org/spec/OCL/2.4","note":"Object Management Group"},{"title":"Semantics of Business Vocabulary and Business Rules","url":"https://www.omg.org/spec/SBVR/1.5","note":"Object Management Group"},{"title":"Decision Model and Notation","url":"https://www.omg.org/spec/DMN/1.5","note":"Object Management Group"},{"title":"Shapes Constraint Language","url":"https://www.w3.org/TR/shacl/","note":"World Wide Web Consortium"},{"title":"OWL 2 Web Ontology Language Structural Specification","url":"https://www.w3.org/TR/owl2-syntax/","note":"World Wide Web Consortium"},{"title":"SPARQL 1.1 Query Language","url":"https://www.w3.org/TR/sparql11-query/","note":"World Wide Web Consortium"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"World Wide Web Consortium"},{"title":"Constraints of the PROV Data Model","url":"https://www.w3.org/TR/prov-constraints/","note":"World Wide Web Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"World Wide Web Consortium"},{"title":"LegalRuleML Core Specification","url":"https://www.oasis-open.org/standard/legalruleml-core-specification-version-1-0-oasis-standard/","note":"OASIS Open"},{"title":"XACML Version 3.0","url":"https://www.oasis-open.org/standard/xacmlv3-0/","note":"OASIS Open"},{"title":"JSON Schema Draft 2020-12","url":"https://json-schema.org/draft/2020-12","note":"JSON Schema"},{"title":"Schematron","url":"https://www.iso.org/standard/85625.html","note":"International Organization for Standardization"},{"title":"OpenAPI Specification","url":"https://spec.openapis.org/oas/v3.1.1.html","note":"OpenAPI Initiative"},{"title":"OSCAL","url":"https://pages.nist.gov/OSCAL/","note":"National Institute of Standards and Technology"},{"title":"Security and Privacy Controls","url":"https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final","note":"National Institute of Standards and Technology"},{"title":"Key words for use in RFCs","url":"https://www.rfc-editor.org/rfc/rfc2119.html","note":"Internet Engineering Task Force"},{"title":"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words","url":"https://www.rfc-editor.org/rfc/rfc8174.html","note":"Internet Engineering Task Force"},{"title":"Date and Time on the Internet","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"Internet Engineering Task Force"},{"title":"JSON Canonicalization Scheme","url":"https://www.rfc-editor.org/rfc/rfc8785.html","note":"Internet Engineering Task Force"},{"title":"Open Policy Agent Policy Language","url":"https://www.openpolicyagent.org/docs/policy-language","note":"Cloud Native Computing Foundation"}],"openQuestions":["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."],"resources":{"spec":"/models/wm-knw-013-constraint-requirement-rule/spec.yaml","agents":"/models/wm-knw-013-constraint-requirement-rule/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-knw-013"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-knw-013-constraint-requirement-rule/spec.yaml","ver-cy/world-models/card-supplements/wm-knw-013-constraint-requirement-rule.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T22:05:10Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"interaction.properties":"Institutional or informational subject: no invented physical properties.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}