# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-07T09:08:19Z", "synthesisSha256": "cc7eaffa9275ff6efbbe253f73e33059dc0ef870cd0ded0be9f928b7fdc0f26b", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-KNW-016", "registryId": "vr.wm-knw-016", "name": "Assumption", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.KNW.ASM" ], "tags": [ "assumption", "inf.knw.asm" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-knw-016-assumption/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-knw-016", "model": { "registry_id": "vr.wm-knw-016", "model_id": "WM-KNW-016", "name": "Assumption", "entry_kind": "entity", "purpose": "Represent one governed premise accepted provisionally for a stated purpose, scope and reasoning context without asserting that it is a verified fact.", "scope_statement": "Owns assumption identity and immutable revision; proposition reference or marked statement; kind and epistemic status; proposer, owner, steward, approver, reviewer, challenger and affected roles; purpose, reasoning context, scope, jurisdiction, environment, validity interval and review date; rationale, sources, supporting and contrary evidence; confidence, uncertainty, reliability and sensitivity; typed dependencies and affected outputs; consequences if false, impact, exposure, risk, mitigation and contingency; challenge, validation and review; acceptance, activation, invalidation, expiry, correction, supersession, access, retention and loss-aware projections. Proposition, fact, evidence, hypothesis, requirement, rule, risk, issue, decision, plan, test, measurement and source-document masters remain external.", "in_scope": [ "Assumption identity, proposition role, statement, kind, status, revision and authority", "Purpose, context, scope, rationale, evidence, uncertainty, dependency, consequence, review and lifecycle", "Provenance, governance, access, retention and interoperability" ], "out_of_scope": [ "Owning proposition, fact, evidence, hypothesis, requirement, rule, risk, issue, decision, plan, test, measurement or source-document lifecycles", "Equating acceptance with truth, confidence with probability, contextual validation with universal proof, or missing evidence with support", "Executing approval, risk acceptance, protected disclosure, external system mutation, safety action or irreversible deletion" ], "boundary_notes": [ { "neighbor": "WM-KNW-007 Claim / Proposition", "distinction": "Claim owns truth-apt proposition identity and content. Assumption owns the premise role, acceptance state and reliance context; the registry parent signal remains under joint boundary review.", "source_refs": [ "SRC-001", "SRC-014", "SRC-019" ] }, { "neighbor": "Fact and observation", "distinction": "A fact or observation is asserted as established under its evidence rules. An assumption is explicitly accepted despite unresolved verification and never becomes a fact through use alone.", "source_refs": [ "SRC-007", "SRC-009", "SRC-010", "SRC-012", "SRC-013" ] }, { "neighbor": "WM-KNW-009 Hypothesis", "distinction": "A hypothesis is framed for evaluation or testing. An assumption is a premise used by another reasoning or action context and may be testable, untestable or awaiting validation.", "source_refs": [ "SRC-001", "SRC-007", "SRC-010" ] }, { "neighbor": "WM-KNW-008 Evidence / Citation", "distinction": "Evidence and citations remain external records. The assumption owns qualified support, challenge and gap bindings, not the evidence content.", "source_refs": [ "SRC-001", "SRC-012", "SRC-013", "SRC-014" ] }, { "neighbor": "Requirement, rule, risk and issue", "distinction": "These records may depend on or challenge an assumption. Their normative force, assessment, treatment and resolution lifecycles remain external.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-008" ] }, { "neighbor": "Decision, plan, model and estimate", "distinction": "These contexts rely on assumptions and own accountable choices, execution, algorithms or calculated outputs. The assumption records typed reliance and impact links only.", "source_refs": [ "SRC-002", "SRC-004", "SRC-010", "SRC-011", "SRC-024" ] }, { "neighbor": "Validation and review", "distinction": "A validation activity and its evidence remain external. The assumption owns source-qualified assessment links and contextual status, never a global truth flag.", "source_refs": [ "SRC-003", "SRC-006", "SRC-009", "SRC-010", "SRC-016" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Structured Assurance Case Metamodel", "organization": "Object Management Group", "url": "https://www.omg.org/spec/SACM/", "version_or_date": "OMG SACM 2.3, May 2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines claims whose declaration may be assumed, asserted, axiomatic, defeated or in need of support, plus argument context and evidence links." }, { "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-07T09:08:00Z", "relevance": "Defines machine-readable system models, viewpoints, requirements, constraints, analysis and traceable model relations." }, { "id": "SRC-003", "title": "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 and revision initiated 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines requirements engineering information items, characteristics, traceability and lifecycle processes." }, { "id": "SRC-004", "title": "System life cycle processes", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/81702.html", "version_or_date": "ISO/IEC/IEEE 15288:2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines system life-cycle processes, stakeholder involvement, decisions, risk, information management and retirement." }, { "id": "SRC-005", "title": "Risk management guidelines", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/65694.html", "version_or_date": "ISO 31000:2018, confirmed 2023 and under revision", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines contextual, iterative risk identification, analysis, evaluation, treatment, monitoring and communication." }, { "id": "SRC-006", "title": "Risk assessment techniques", "organization": "International Electrotechnical Commission", "url": "https://www.iso.org/standard/72140.html", "version_or_date": "IEC 31010:2019, under review", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines selection and use of risk assessment techniques for decisions under uncertainty." }, { "id": "SRC-007", "title": "Artificial Intelligence Risk Management Framework", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-ai-rmf-10", "version_or_date": "NIST AI 100-1, January 2023; revision in progress", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Requires documented context, assumptions, limitations, risks, measurements and ongoing monitoring for AI systems." }, { "id": "SRC-008", "title": "Guide for Conducting Risk Assessments", "organization": "National Institute of Standards and Technology", "url": "https://csrc.nist.gov/pubs/sp/800/30/r1/final", "version_or_date": "NIST SP 800-30 Rev. 1, September 2012", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines risk models, assumptions, inputs, likelihood, impact, uncertainty and maintenance of assessments." }, { "id": "SRC-009", "title": "Systems Engineering Handbook Appendix", "organization": "National Aeronautics and Space Administration", "url": "https://www.nasa.gov/reference/system-engineering-handbook-appendix/", "version_or_date": "NASA/SP-2016-6105 Rev. 2 appendix, page accessed 2026-09-07", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Requires assumptions and constraints in concepts of operation and reviews whether stated assumptions are correct." }, { "id": "SRC-010", "title": "The AQuA Book", "organization": "United Kingdom Government Analysis Function", "url": "https://www.gov.uk/guidance/the-aqua-book", "version_or_date": "Updated edition published 30 July 2025", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines assumption logs with description, quantified effect and reliability, time, rationale, author and sign-off." }, { "id": "SRC-011", "title": "Cost Estimating and Assessment Guide", "organization": "United States Government Accountability Office", "url": "https://www.gao.gov/products/gao-20-195g", "version_or_date": "GAO-20-195G, March 2020", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines documented ground rules and assumptions, sources, sensitivity, risk analysis, validation and estimate updates." }, { "id": "SRC-012", "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-07T09:08:00Z", "relevance": "Defines entities, activities, agents, attribution, derivation, revision and invalidation." }, { "id": "SRC-013", "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-07T09:08:00Z", "relevance": "Defines quality measurements, annotations, policies, standards and provenance." }, { "id": "SRC-014", "title": "Web Annotation Data Model", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/annotation-model/", "version_or_date": "W3C Recommendation, 23 February 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines attributable body-target annotations, motivations, selectors, states and provenance." }, { "id": "SRC-015", "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-07T09:08:00Z", "relevance": "Defines permissions, prohibitions, duties, constraints and policy parties for governed use." }, { "id": "SRC-016", "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-07T09:08:00Z", "relevance": "Defines declarative graph validation, severity, results and validation reports." }, { "id": "SRC-017", "title": "DataCite Metadata Schema", "organization": "DataCite", "url": "https://schema.datacite.org/", "version_or_date": "DataCite Metadata Schema 4.7, 3 March 2026", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines persistent resource identity, versions, relations, contributors, rights and descriptions." }, { "id": "SRC-018", "title": "RO-Crate Specification", "organization": "RO-Crate Community", "url": "https://www.researchobject.org/ro-crate/specification.html", "version_or_date": "RO-Crate 1.3, current long-term release", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines portable research-object packaging, contextual entities, actions, provenance and profiles." }, { "id": "SRC-019", "title": "Schema.org Claim", "organization": "Schema.org Community Group", "url": "https://schema.org/Claim", "version_or_date": "Schema.org vocabulary accessed 2026-09-07", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines a fact-oriented claim that can be reviewed or referenced and separates claim content from review." }, { "id": "SRC-020", "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-07T09:08:00Z", "relevance": "Defines timestamps with seconds and explicit numeric offsets or Z." }, { "id": "SRC-021", "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-07T09:08:00Z", "relevance": "Defines normative requirement keywords and their intended interpretation." }, { "id": "SRC-022", "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-07T09:08:00Z", "relevance": "Limits normative keyword interpretation to explicitly adopting documents." }, { "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-07T09:08:00Z", "relevance": "Defines deterministic JSON canonicalization for hashing and signing." }, { "id": "SRC-024", "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, August 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:08:00Z", "relevance": "Defines decision requirements, inputs, knowledge sources, decisions, logic and execution profiles." } ], "structure": { "bundles": [ { "id": "assumption-identity-expression-kind-and-status", "name": "Assumption identity, expression, kind and status", "description": "Groups the governed Resource Consumption concern for assumption identity, expression, kind and status.", "rationale": "Identify one premise and distinguish acceptance for use from established truth.", "source_refs": [ "SRC-001", "SRC-012", "SRC-014", "SRC-017", "SRC-019", "SRC-020", "SRC-023", "SRC-002", "SRC-003", "SRC-007", "SRC-010", "SRC-024" ], "layers": [ { "id": "identity-revision-proposition-and-record-boundary", "name": "Identity, revision, proposition and record boundary", "description": "Groups Resource Consumption context for identity, revision, proposition and record boundary without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-012", "SRC-014", "SRC-017", "SRC-019", "SRC-020", "SRC-023" ], "findings": [ { "id": "assumption-identifier-namespace-version-revision-predecessor-and-successor", "name": "Assumption identifier, namespace, version, revision, predecessor and successor", "description": "Records assumption identifier, namespace, version, revision, predecessor and successor as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-012", "SRC-014", "SRC-017", "SRC-019", "SRC-020", "SRC-023" ], "questions": [ { "id": "assumption-identifier-namespace-version-revision-predecessor-and-successor-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish assumption identifier, namespace, version, revision, predecessor and successor?", "kind": "identity", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "assumption-identifier-namespace-version-revision-predecessor-and-successor-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses assumption identifier, namespace, version, revision, predecessor and successor, and under which authority?", "kind": "ownership", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "assumption-identifier-namespace-version-revision-predecessor-and-successor-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify assumption identifier, namespace, version, revision, predecessor and successor?", "kind": "validation", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "assumption-identifier-namespace-version-revision-predecessor-and-successor-data", "name": "Assumption identifier, namespace, version, revision, predecessor and successor data", "description": "Typed assumption-scoped values and references required to answer the governed questions for assumption identifier, namespace, version, revision, predecessor and successor.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-012", "SRC-014", "SRC-017", "SRC-019", "SRC-020", "SRC-023" ] } ], "artifacts": [ { "id": "assumption-identifier-namespace-version-revision-predecessor-and-successor-artifact", "name": "Assumption identifier, namespace, version, revision, predecessor and successor evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting assumption identifier, namespace, version, revision, predecessor and successor.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-012", "SRC-014", "SRC-017", "SRC-019", "SRC-020", "SRC-023" ] } ], "inline_only_rationale": null }, { "id": "proposition-reference-statement-language-terms-and-formal-expression", "name": "Proposition reference, statement, language, terms and formal expression", "description": "Records proposition reference, statement, language, terms and formal expression as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-012", "SRC-014", "SRC-017", "SRC-019", "SRC-020", "SRC-023" ], "questions": [ { "id": "proposition-reference-statement-language-terms-and-formal-expression-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish proposition reference, statement, language, terms and formal expression?", "kind": "definition", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "proposition-reference-statement-language-terms-and-formal-expression-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses proposition reference, statement, language, terms and formal expression, and under which authority?", "kind": "authority", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "proposition-reference-statement-language-terms-and-formal-expression-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify proposition reference, statement, language, terms and formal expression?", "kind": "security", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "proposition-reference-statement-language-terms-and-formal-expression-data", "name": "Proposition reference, statement, language, terms and formal expression data", "description": "Typed assumption-scoped values and references required to answer the governed questions for proposition reference, statement, language, terms and formal expression.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-012", "SRC-014", "SRC-017", "SRC-019", "SRC-020", "SRC-023" ] } ], "artifacts": [ { "id": "proposition-reference-statement-language-terms-and-formal-expression-artifact", "name": "Proposition reference, statement, language, terms and formal expression evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting proposition reference, statement, language, terms and formal expression.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-012", "SRC-014", "SRC-017", "SRC-019", "SRC-020", "SRC-023" ] } ], "inline_only_rationale": null } ] }, { "id": "kind-epistemic-status-and-recognition", "name": "Kind, epistemic status and recognition", "description": "Groups Resource Consumption context for kind, epistemic status and recognition without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-010", "SRC-019", "SRC-024" ], "findings": [ { "id": "planning-modeling-estimating-argument-safety-and-operational-kind", "name": "Planning, modeling, estimating, argument, safety and operational kind", "description": "Records planning, modeling, estimating, argument, safety and operational kind as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-010", "SRC-019", "SRC-024" ], "questions": [ { "id": "planning-modeling-estimating-argument-safety-and-operational-kind-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish planning, modeling, estimating, argument, safety and operational kind?", "kind": "classification", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "planning-modeling-estimating-argument-safety-and-operational-kind-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses planning, modeling, estimating, argument, safety and operational kind, and under which authority?", "kind": "requirement", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "planning-modeling-estimating-argument-safety-and-operational-kind-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify planning, modeling, estimating, argument, safety and operational kind?", "kind": "privacy", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "planning-modeling-estimating-argument-safety-and-operational-kind-data", "name": "Planning, modeling, estimating, argument, safety and operational kind data", "description": "Typed assumption-scoped values and references required to answer the governed questions for planning, modeling, estimating, argument, safety and operational kind.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-010", "SRC-019", "SRC-024" ] } ], "artifacts": [ { "id": "planning-modeling-estimating-argument-safety-and-operational-kind-artifact", "name": "Planning, modeling, estimating, argument, safety and operational kind evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting planning, modeling, estimating, argument, safety and operational kind.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log 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-007", "SRC-010", "SRC-019", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "proposed-accepted-assumed-axiomatic-unsupported-unknown-and-contested-status", "name": "Proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status", "description": "Records proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-010", "SRC-019", "SRC-024" ], "questions": [ { "id": "proposed-accepted-assumed-axiomatic-unsupported-unknown-and-contested-status-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status?", "kind": "state", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "proposed-accepted-assumed-axiomatic-unsupported-unknown-and-contested-status-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status, and under which authority?", "kind": "constraint", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "proposed-accepted-assumed-axiomatic-unsupported-unknown-and-contested-status-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status?", "kind": "retention", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "proposed-accepted-assumed-axiomatic-unsupported-unknown-and-contested-status-data", "name": "Proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status data", "description": "Typed assumption-scoped values and references required to answer the governed questions for proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-010", "SRC-019", "SRC-024" ] } ], "artifacts": [ { "id": "proposed-accepted-assumed-axiomatic-unsupported-unknown-and-contested-status-artifact", "name": "Proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log 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-007", "SRC-010", "SRC-019", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "purpose-actors-authority-scope-and-time", "name": "Purpose, actors, authority, scope and time", "description": "Groups the governed Resource Consumption concern for purpose, actors, authority, scope and time.", "rationale": "Bind the premise to the exact context and authority under which it may be used.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012", "SRC-014", "SRC-017", "SRC-002", "SRC-007", "SRC-009", "SRC-020", "SRC-024" ], "layers": [ { "id": "proposer-owner-approver-challenger-and-steward", "name": "Proposer, owner, approver, challenger and steward", "description": "Groups Resource Consumption context for proposer, owner, approver, challenger and steward without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012", "SRC-014", "SRC-017" ], "findings": [ { "id": "proposer-owner-steward-approver-reviewer-challenger-and-affected-role", "name": "Proposer, owner, steward, approver, reviewer, challenger and affected role", "description": "Records proposer, owner, steward, approver, reviewer, challenger and affected role as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012", "SRC-014", "SRC-017" ], "questions": [ { "id": "proposer-owner-steward-approver-reviewer-challenger-and-affected-role-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish proposer, owner, steward, approver, reviewer, challenger and affected role?", "kind": "ownership", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "proposer-owner-steward-approver-reviewer-challenger-and-affected-role-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses proposer, owner, steward, approver, reviewer, challenger and affected role, and under which authority?", "kind": "process", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "proposer-owner-steward-approver-reviewer-challenger-and-affected-role-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify proposer, owner, steward, approver, reviewer, challenger and affected role?", "kind": "access", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "proposer-owner-steward-approver-reviewer-challenger-and-affected-role-data", "name": "Proposer, owner, steward, approver, reviewer, challenger and affected role data", "description": "Typed assumption-scoped values and references required to answer the governed questions for proposer, owner, steward, approver, reviewer, challenger and affected role.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012", "SRC-014", "SRC-017" ] } ], "artifacts": [ { "id": "proposer-owner-steward-approver-reviewer-challenger-and-affected-role-artifact", "name": "Proposer, owner, steward, approver, reviewer, challenger and affected role evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting proposer, owner, steward, approver, reviewer, challenger and affected role.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012", "SRC-014", "SRC-017" ] } ], "inline_only_rationale": null }, { "id": "authority-signoff-accountability-separation-of-duties-and-escalation", "name": "Authority, sign-off, accountability, separation of duties and escalation", "description": "Records authority, sign-off, accountability, separation of duties and escalation as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012", "SRC-014", "SRC-017" ], "questions": [ { "id": "authority-signoff-accountability-separation-of-duties-and-escalation-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish authority, sign-off, accountability, separation of duties and escalation?", "kind": "authority", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "authority-signoff-accountability-separation-of-duties-and-escalation-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses authority, sign-off, accountability, separation of duties and escalation, and under which authority?", "kind": "event", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "authority-signoff-accountability-separation-of-duties-and-escalation-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify authority, sign-off, accountability, separation of duties and escalation?", "kind": "exception", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "authority-signoff-accountability-separation-of-duties-and-escalation-data", "name": "Authority, sign-off, accountability, separation of duties and escalation data", "description": "Typed assumption-scoped values and references required to answer the governed questions for authority, sign-off, accountability, separation of duties and escalation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012", "SRC-014", "SRC-017" ] } ], "artifacts": [ { "id": "authority-signoff-accountability-separation-of-duties-and-escalation-artifact", "name": "Authority, sign-off, accountability, separation of duties and escalation evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting authority, sign-off, accountability, separation of duties and escalation.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-010", "SRC-012", "SRC-014", "SRC-017" ] } ], "inline_only_rationale": null } ] }, { "id": "purpose-reasoning-context-scope-place-and-time", "name": "Purpose, reasoning context, scope, place and time", "description": "Groups Resource Consumption context for purpose, reasoning context, scope, place and time without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-020", "SRC-024" ], "findings": [ { "id": "intended-use-reasoning-context-decision-plan-model-and-system-boundary", "name": "Intended use, reasoning context, decision, plan, model and system boundary", "description": "Records intended use, reasoning context, decision, plan, model and system boundary as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-020", "SRC-024" ], "questions": [ { "id": "intended-use-reasoning-context-decision-plan-model-and-system-boundary-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish intended use, reasoning context, decision, plan, model and system boundary?", "kind": "constraint", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "intended-use-reasoning-context-decision-plan-model-and-system-boundary-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses intended use, reasoning context, decision, plan, model and system boundary, and under which authority?", "kind": "measurement", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "intended-use-reasoning-context-decision-plan-model-and-system-boundary-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify intended use, reasoning context, decision, plan, model and system boundary?", "kind": "interoperability", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "intended-use-reasoning-context-decision-plan-model-and-system-boundary-data", "name": "Intended use, reasoning context, decision, plan, model and system boundary data", "description": "Typed assumption-scoped values and references required to answer the governed questions for intended use, reasoning context, decision, plan, model and system boundary.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-020", "SRC-024" ] } ], "artifacts": [ { "id": "intended-use-reasoning-context-decision-plan-model-and-system-boundary-artifact", "name": "Intended use, reasoning context, decision, plan, model and system boundary evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting intended use, reasoning context, decision, plan, model and system boundary.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log 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-007", "SRC-009", "SRC-010", "SRC-020", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "population-jurisdiction-environment-location-validity-review-and-observation-time", "name": "Population, jurisdiction, environment, location, validity, review and observation time", "description": "Records population, jurisdiction, environment, location, validity, review and observation time as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-020", "SRC-024" ], "questions": [ { "id": "population-jurisdiction-environment-location-validity-review-and-observation-time-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish population, jurisdiction, environment, location, validity, review and observation time?", "kind": "temporal", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "population-jurisdiction-environment-location-validity-review-and-observation-time-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses population, jurisdiction, environment, location, validity, review and observation time, and under which authority?", "kind": "evidence", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "population-jurisdiction-environment-location-validity-review-and-observation-time-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify population, jurisdiction, environment, location, validity, review and observation time?", "kind": "decision", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "population-jurisdiction-environment-location-validity-review-and-observation-time-data", "name": "Population, jurisdiction, environment, location, validity, review and observation time data", "description": "Typed assumption-scoped values and references required to answer the governed questions for population, jurisdiction, environment, location, validity, review and observation time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-020", "SRC-024" ] } ], "artifacts": [ { "id": "population-jurisdiction-environment-location-validity-review-and-observation-time-artifact", "name": "Population, jurisdiction, environment, location, validity, review and observation time evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting population, jurisdiction, environment, location, validity, review and observation time.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log 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-007", "SRC-009", "SRC-010", "SRC-020", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "rationale-evidence-uncertainty-and-sensitivity", "name": "Rationale, evidence, uncertainty and sensitivity", "description": "Groups the governed Resource Consumption concern for rationale, evidence, uncertainty and sensitivity.", "rationale": "Explain why the premise is used and how weak support or uncertainty changes reliance.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-005", "SRC-006", "SRC-008" ], "layers": [ { "id": "rationale-source-support-challenge-and-gap", "name": "Rationale, source, support, challenge and gap", "description": "Groups Resource Consumption context for rationale, source, support, challenge and gap without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ], "findings": [ { "id": "motivation-rationale-source-citation-support-and-justification", "name": "Motivation, rationale, source, citation, support and justification", "description": "Records motivation, rationale, source, citation, support and justification as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ], "questions": [ { "id": "motivation-rationale-source-citation-support-and-justification-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish motivation, rationale, source, citation, support and justification?", "kind": "provenance", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "motivation-rationale-source-citation-support-and-justification-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses motivation, rationale, source, citation, support and justification, and under which authority?", "kind": "quality", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "motivation-rationale-source-citation-support-and-justification-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify motivation, rationale, source, citation, support and justification?", "kind": "identity", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "motivation-rationale-source-citation-support-and-justification-data", "name": "Motivation, rationale, source, citation, support and justification data", "description": "Typed assumption-scoped values and references required to answer the governed questions for motivation, rationale, source, citation, support and justification.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "motivation-rationale-source-citation-support-and-justification-artifact", "name": "Motivation, rationale, source, citation, support and justification evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting motivation, rationale, source, citation, support and justification.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null }, { "id": "contrary-evidence-counterclaim-gap-conflict-bias-and-limitation", "name": "Contrary evidence, counterclaim, gap, conflict, bias and limitation", "description": "Records contrary evidence, counterclaim, gap, conflict, bias and limitation as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ], "questions": [ { "id": "contrary-evidence-counterclaim-gap-conflict-bias-and-limitation-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish contrary evidence, counterclaim, gap, conflict, bias and limitation?", "kind": "evidence", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "contrary-evidence-counterclaim-gap-conflict-bias-and-limitation-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses contrary evidence, counterclaim, gap, conflict, bias and limitation, and under which authority?", "kind": "validation", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "contrary-evidence-counterclaim-gap-conflict-bias-and-limitation-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify contrary evidence, counterclaim, gap, conflict, bias and limitation?", "kind": "classification", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "contrary-evidence-counterclaim-gap-conflict-bias-and-limitation-data", "name": "Contrary evidence, counterclaim, gap, conflict, bias and limitation data", "description": "Typed assumption-scoped values and references required to answer the governed questions for contrary evidence, counterclaim, gap, conflict, bias and limitation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ] } ], "artifacts": [ { "id": "contrary-evidence-counterclaim-gap-conflict-bias-and-limitation-artifact", "name": "Contrary evidence, counterclaim, gap, conflict, bias and limitation evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting contrary evidence, counterclaim, gap, conflict, bias and limitation.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014" ] } ], "inline_only_rationale": null } ] }, { "id": "confidence-uncertainty-reliability-and-sensitivity", "name": "Confidence, uncertainty, reliability and sensitivity", "description": "Groups Resource Consumption context for confidence, uncertainty, reliability and sensitivity without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013" ], "findings": [ { "id": "confidence-basis-probability-range-distribution-uncertainty-and-reliability", "name": "Confidence basis, probability, range, distribution, uncertainty and reliability", "description": "Records confidence basis, probability, range, distribution, uncertainty and reliability as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013" ], "questions": [ { "id": "confidence-basis-probability-range-distribution-uncertainty-and-reliability-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish confidence basis, probability, range, distribution, uncertainty and reliability?", "kind": "measurement", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "confidence-basis-probability-range-distribution-uncertainty-and-reliability-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses confidence basis, probability, range, distribution, uncertainty and reliability, and under which authority?", "kind": "security", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "confidence-basis-probability-range-distribution-uncertainty-and-reliability-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify confidence basis, probability, range, distribution, uncertainty and reliability?", "kind": "composition", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "confidence-basis-probability-range-distribution-uncertainty-and-reliability-data", "name": "Confidence basis, probability, range, distribution, uncertainty and reliability data", "description": "Typed assumption-scoped values and references required to answer the governed questions for confidence basis, probability, range, distribution, uncertainty and reliability.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "confidence-basis-probability-range-distribution-uncertainty-and-reliability-artifact", "name": "Confidence basis, probability, range, distribution, uncertainty and reliability evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting confidence basis, probability, range, distribution, uncertainty and reliability.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null }, { "id": "sensitivity-driver-threshold-scenario-robustness-and-materiality", "name": "Sensitivity driver, threshold, scenario, robustness and materiality", "description": "Records sensitivity driver, threshold, scenario, robustness and materiality as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013" ], "questions": [ { "id": "sensitivity-driver-threshold-scenario-robustness-and-materiality-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish sensitivity driver, threshold, scenario, robustness and materiality?", "kind": "quality", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "sensitivity-driver-threshold-scenario-robustness-and-materiality-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses sensitivity driver, threshold, scenario, robustness and materiality, and under which authority?", "kind": "privacy", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "sensitivity-driver-threshold-scenario-robustness-and-materiality-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify sensitivity driver, threshold, scenario, robustness and materiality?", "kind": "relationship", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "sensitivity-driver-threshold-scenario-robustness-and-materiality-data", "name": "Sensitivity driver, threshold, scenario, robustness and materiality data", "description": "Typed assumption-scoped values and references required to answer the governed questions for sensitivity driver, threshold, scenario, robustness and materiality.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013" ] } ], "artifacts": [ { "id": "sensitivity-driver-threshold-scenario-robustness-and-materiality-artifact", "name": "Sensitivity driver, threshold, scenario, robustness and materiality evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting sensitivity driver, threshold, scenario, robustness and materiality.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "dependencies-consequences-risk-and-contingency", "name": "Dependencies, consequences, risk and contingency", "description": "Groups the governed Resource Consumption concern for dependencies, consequences, risk and contingency.", "rationale": "Make downstream reliance and consequences of falsity visible before action.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-012", "SRC-024", "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "layers": [ { "id": "dependency-derivation-conflict-and-affected-output", "name": "Dependency, derivation, conflict and affected output", "description": "Groups Resource Consumption context for dependency, derivation, conflict and affected output without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-012", "SRC-024" ], "findings": [ { "id": "parent-child-derived-prerequisite-equivalent-conflicting-and-circular-relation", "name": "Parent, child, derived, prerequisite, equivalent, conflicting and circular relation", "description": "Records parent, child, derived, prerequisite, equivalent, conflicting and circular relation as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-012", "SRC-024" ], "questions": [ { "id": "parent-child-derived-prerequisite-equivalent-conflicting-and-circular-relation-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish parent, child, derived, prerequisite, equivalent, conflicting and circular relation?", "kind": "relationship", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "parent-child-derived-prerequisite-equivalent-conflicting-and-circular-relation-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses parent, child, derived, prerequisite, equivalent, conflicting and circular relation, and under which authority?", "kind": "retention", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "parent-child-derived-prerequisite-equivalent-conflicting-and-circular-relation-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify parent, child, derived, prerequisite, equivalent, conflicting and circular relation?", "kind": "state", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "parent-child-derived-prerequisite-equivalent-conflicting-and-circular-relation-data", "name": "Parent, child, derived, prerequisite, equivalent, conflicting and circular relation data", "description": "Typed assumption-scoped values and references required to answer the governed questions for parent, child, derived, prerequisite, equivalent, conflicting and circular relation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-012", "SRC-024" ] } ], "artifacts": [ { "id": "parent-child-derived-prerequisite-equivalent-conflicting-and-circular-relation-artifact", "name": "Parent, child, derived, prerequisite, equivalent, conflicting and circular relation evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting parent, child, derived, prerequisite, equivalent, conflicting and circular relation.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log 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-007", "SRC-012", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "dependent-requirement-model-estimate-plan-decision-control-and-action", "name": "Dependent requirement, model, estimate, plan, decision, control and action", "description": "Records dependent requirement, model, estimate, plan, decision, control and action as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-012", "SRC-024" ], "questions": [ { "id": "dependent-requirement-model-estimate-plan-decision-control-and-action-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish dependent requirement, model, estimate, plan, decision, control and action?", "kind": "composition", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "dependent-requirement-model-estimate-plan-decision-control-and-action-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses dependent requirement, model, estimate, plan, decision, control and action, and under which authority?", "kind": "access", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "dependent-requirement-model-estimate-plan-decision-control-and-action-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify dependent requirement, model, estimate, plan, decision, control and action?", "kind": "lifecycle", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "dependent-requirement-model-estimate-plan-decision-control-and-action-data", "name": "Dependent requirement, model, estimate, plan, decision, control and action data", "description": "Typed assumption-scoped values and references required to answer the governed questions for dependent requirement, model, estimate, plan, decision, control and action.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-007", "SRC-012", "SRC-024" ] } ], "artifacts": [ { "id": "dependent-requirement-model-estimate-plan-decision-control-and-action-artifact", "name": "Dependent requirement, model, estimate, plan, decision, control and action evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting dependent requirement, model, estimate, plan, decision, control and action.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log 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-007", "SRC-012", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "false-consequence-exposure-risk-mitigation-and-contingency", "name": "False consequence, exposure, risk, mitigation and contingency", "description": "Groups Resource Consumption context for false consequence, exposure, risk, mitigation and contingency without importing neighboring master lifecycles.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "findings": [ { "id": "false-or-invalid-consequence-impact-likelihood-exposure-priority-and-criticality", "name": "False or invalid consequence, impact, likelihood, exposure, priority and criticality", "description": "Records false or invalid consequence, impact, likelihood, exposure, priority and criticality as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "false-or-invalid-consequence-impact-likelihood-exposure-priority-and-criticality-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish false or invalid consequence, impact, likelihood, exposure, priority and criticality?", "kind": "measurement", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "false-or-invalid-consequence-impact-likelihood-exposure-priority-and-criticality-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses false or invalid consequence, impact, likelihood, exposure, priority and criticality, and under which authority?", "kind": "exception", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "false-or-invalid-consequence-impact-likelihood-exposure-priority-and-criticality-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify false or invalid consequence, impact, likelihood, exposure, priority and criticality?", "kind": "temporal", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "false-or-invalid-consequence-impact-likelihood-exposure-priority-and-criticality-data", "name": "False or invalid consequence, impact, likelihood, exposure, priority and criticality data", "description": "Typed assumption-scoped values and references required to answer the governed questions for false or invalid consequence, impact, likelihood, exposure, priority and criticality.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "false-or-invalid-consequence-impact-likelihood-exposure-priority-and-criticality-artifact", "name": "False or invalid consequence, impact, likelihood, exposure, priority and criticality evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting false or invalid consequence, impact, likelihood, exposure, priority and criticality.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null }, { "id": "monitor-indicator-trigger-mitigation-contingency-fallback-and-safe-state", "name": "Monitor, indicator, trigger, mitigation, contingency, fallback and safe state", "description": "Records monitor, indicator, trigger, mitigation, contingency, fallback and safe state as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ], "questions": [ { "id": "monitor-indicator-trigger-mitigation-contingency-fallback-and-safe-state-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish monitor, indicator, trigger, mitigation, contingency, fallback and safe state?", "kind": "process", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "monitor-indicator-trigger-mitigation-contingency-fallback-and-safe-state-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses monitor, indicator, trigger, mitigation, contingency, fallback and safe state, and under which authority?", "kind": "interoperability", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "monitor-indicator-trigger-mitigation-contingency-fallback-and-safe-state-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify monitor, indicator, trigger, mitigation, contingency, fallback and safe state?", "kind": "spatial", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "monitor-indicator-trigger-mitigation-contingency-fallback-and-safe-state-data", "name": "Monitor, indicator, trigger, mitigation, contingency, fallback and safe state data", "description": "Typed assumption-scoped values and references required to answer the governed questions for monitor, indicator, trigger, mitigation, contingency, fallback and safe state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "artifacts": [ { "id": "monitor-indicator-trigger-mitigation-contingency-fallback-and-safe-state-artifact", "name": "Monitor, indicator, trigger, mitigation, contingency, fallback and safe state evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting monitor, indicator, trigger, mitigation, contingency, fallback and safe state.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "challenge-validation-review-lifecycle-and-change", "name": "Challenge, validation, review, lifecycle and change", "description": "Groups the governed Resource Consumption concern for challenge, validation, review, lifecycle and change.", "rationale": "Test assumptions contextually and preserve every assessment and revision.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-016", "SRC-004", "SRC-012", "SRC-014", "SRC-017", "SRC-018", "SRC-020", "SRC-023" ], "layers": [ { "id": "validation-method-criterion-result-and-evidence", "name": "Validation method, criterion, result and evidence", "description": "Groups Resource Consumption context for validation method, criterion, result and evidence without importing neighboring master lifecycles.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ], "findings": [ { "id": "validation-question-method-input-criterion-threshold-reviewer-and-schedule", "name": "Validation question, method, input, criterion, threshold, reviewer and schedule", "description": "Records validation question, method, input, criterion, threshold, reviewer and schedule as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ], "questions": [ { "id": "validation-question-method-input-criterion-threshold-reviewer-and-schedule-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish validation question, method, input, criterion, threshold, reviewer and schedule?", "kind": "validation", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "validation-question-method-input-criterion-threshold-reviewer-and-schedule-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses validation question, method, input, criterion, threshold, reviewer and schedule, and under which authority?", "kind": "decision", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "validation-question-method-input-criterion-threshold-reviewer-and-schedule-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify validation question, method, input, criterion, threshold, reviewer and schedule?", "kind": "provenance", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "validation-question-method-input-criterion-threshold-reviewer-and-schedule-data", "name": "Validation question, method, input, criterion, threshold, reviewer and schedule data", "description": "Typed assumption-scoped values and references required to answer the governed questions for validation question, method, input, criterion, threshold, reviewer and schedule.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "validation-question-method-input-criterion-threshold-reviewer-and-schedule-artifact", "name": "Validation question, method, input, criterion, threshold, reviewer and schedule evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting validation question, method, input, criterion, threshold, reviewer and schedule.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "supported-challenged-confirmed-invalidated-inconclusive-and-not-tested-result", "name": "Supported, challenged, confirmed, invalidated, inconclusive and not-tested result", "description": "Records supported, challenged, confirmed, invalidated, inconclusive and not-tested result as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ], "questions": [ { "id": "supported-challenged-confirmed-invalidated-inconclusive-and-not-tested-result-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish supported, challenged, confirmed, invalidated, inconclusive and not-tested result?", "kind": "state", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "supported-challenged-confirmed-invalidated-inconclusive-and-not-tested-result-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses supported, challenged, confirmed, invalidated, inconclusive and not-tested result, and under which authority?", "kind": "identity", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "supported-challenged-confirmed-invalidated-inconclusive-and-not-tested-result-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify supported, challenged, confirmed, invalidated, inconclusive and not-tested result?", "kind": "ownership", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "supported-challenged-confirmed-invalidated-inconclusive-and-not-tested-result-data", "name": "Supported, challenged, confirmed, invalidated, inconclusive and not-tested result data", "description": "Typed assumption-scoped values and references required to answer the governed questions for supported, challenged, confirmed, invalidated, inconclusive and not-tested result.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ] } ], "artifacts": [ { "id": "supported-challenged-confirmed-invalidated-inconclusive-and-not-tested-result-artifact", "name": "Supported, challenged, confirmed, invalidated, inconclusive and not-tested result evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting supported, challenged, confirmed, invalidated, inconclusive and not-tested result.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-013", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "lifecycle-review-correction-and-supersession", "name": "Lifecycle, review, correction and supersession", "description": "Groups Resource Consumption context for lifecycle, review, correction and supersession without importing neighboring master lifecycles.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-014", "SRC-017", "SRC-018", "SRC-020", "SRC-023" ], "findings": [ { "id": "draft-proposed-accepted-active-challenged-invalidated-expired-and-retired-state", "name": "Draft, proposed, accepted, active, challenged, invalidated, expired and retired state", "description": "Records draft, proposed, accepted, active, challenged, invalidated, expired and retired state as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-014", "SRC-017", "SRC-018", "SRC-020", "SRC-023" ], "questions": [ { "id": "draft-proposed-accepted-active-challenged-invalidated-expired-and-retired-state-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish draft, proposed, accepted, active, challenged, invalidated, expired and retired state?", "kind": "lifecycle", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "draft-proposed-accepted-active-challenged-invalidated-expired-and-retired-state-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses draft, proposed, accepted, active, challenged, invalidated, expired and retired state, and under which authority?", "kind": "classification", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "draft-proposed-accepted-active-challenged-invalidated-expired-and-retired-state-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify draft, proposed, accepted, active, challenged, invalidated, expired and retired state?", "kind": "authority", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "draft-proposed-accepted-active-challenged-invalidated-expired-and-retired-state-data", "name": "Draft, proposed, accepted, active, challenged, invalidated, expired and retired state data", "description": "Typed assumption-scoped values and references required to answer the governed questions for draft, proposed, accepted, active, challenged, invalidated, expired and retired state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-014", "SRC-017", "SRC-018", "SRC-020", "SRC-023" ] } ], "artifacts": [ { "id": "draft-proposed-accepted-active-challenged-invalidated-expired-and-retired-state-artifact", "name": "Draft, proposed, accepted, active, challenged, invalidated, expired and retired state evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting draft, proposed, accepted, active, challenged, invalidated, expired and retired state.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-014", "SRC-017", "SRC-018", "SRC-020", "SRC-023" ] } ], "inline_only_rationale": null }, { "id": "review-trigger-correction-revision-split-merge-replacement-and-supersession", "name": "Review trigger, correction, revision, split, merge, replacement and supersession", "description": "Records review trigger, correction, revision, split, merge, replacement and supersession as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-014", "SRC-017", "SRC-018", "SRC-020", "SRC-023" ], "questions": [ { "id": "review-trigger-correction-revision-split-merge-replacement-and-supersession-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish review trigger, correction, revision, split, merge, replacement and supersession?", "kind": "lifecycle", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "review-trigger-correction-revision-split-merge-replacement-and-supersession-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses review trigger, correction, revision, split, merge, replacement and supersession, and under which authority?", "kind": "composition", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "review-trigger-correction-revision-split-merge-replacement-and-supersession-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify review trigger, correction, revision, split, merge, replacement and supersession?", "kind": "requirement", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "review-trigger-correction-revision-split-merge-replacement-and-supersession-data", "name": "Review trigger, correction, revision, split, merge, replacement and supersession data", "description": "Typed assumption-scoped values and references required to answer the governed questions for review trigger, correction, revision, split, merge, replacement and supersession.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-014", "SRC-017", "SRC-018", "SRC-020", "SRC-023" ] } ], "artifacts": [ { "id": "review-trigger-correction-revision-split-merge-replacement-and-supersession-artifact", "name": "Review trigger, correction, revision, split, merge, replacement and supersession evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting review trigger, correction, revision, split, merge, replacement and supersession.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-014", "SRC-017", "SRC-018", "SRC-020", "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 premise use and project it without hiding context or semantic loss.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-018", "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-008", "SRC-009", "SRC-011", "SRC-014", "SRC-016", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "layers": [ { "id": "policy-quality-security-access-and-retention", "name": "Policy, quality, security, access and retention", "description": "Groups Resource Consumption context for policy, quality, security, access and retention without importing neighboring master lifecycles.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-018" ], "findings": [ { "id": "completeness-consistency-freshness-traceability-quality-and-assurance", "name": "Completeness, consistency, freshness, traceability, quality and assurance", "description": "Records completeness, consistency, freshness, traceability, quality and assurance as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-018" ], "questions": [ { "id": "completeness-consistency-freshness-traceability-quality-and-assurance-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish completeness, consistency, freshness, traceability, quality and assurance?", "kind": "quality", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "completeness-consistency-freshness-traceability-quality-and-assurance-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses completeness, consistency, freshness, traceability, quality and assurance, and under which authority?", "kind": "relationship", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "completeness-consistency-freshness-traceability-quality-and-assurance-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify completeness, consistency, freshness, traceability, quality and assurance?", "kind": "constraint", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "completeness-consistency-freshness-traceability-quality-and-assurance-data", "name": "Completeness, consistency, freshness, traceability, quality and assurance data", "description": "Typed assumption-scoped values and references required to answer the governed questions for completeness, consistency, freshness, traceability, quality and assurance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "completeness-consistency-freshness-traceability-quality-and-assurance-artifact", "name": "Completeness, consistency, freshness, traceability, quality and assurance evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting completeness, consistency, freshness, traceability, quality and assurance.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "purpose-role-sensitivity-minimum-disclosure-retention-legal-hold-and-tombstone", "name": "Purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone", "description": "Records purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents retain external mastership.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-018" ], "questions": [ { "id": "purpose-role-sensitivity-minimum-disclosure-retention-legal-hold-and-tombstone-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone?", "kind": "access", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "purpose-role-sensitivity-minimum-disclosure-retention-legal-hold-and-tombstone-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone, and under which authority?", "kind": "state", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "purpose-role-sensitivity-minimum-disclosure-retention-legal-hold-and-tombstone-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone?", "kind": "process", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "purpose-role-sensitivity-minimum-disclosure-retention-legal-hold-and-tombstone-data", "name": "Purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone data", "description": "Typed assumption-scoped values and references required to answer the governed questions for purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "purpose-role-sensitivity-minimum-disclosure-retention-legal-hold-and-tombstone-artifact", "name": "Purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log or source-system record identifier first, otherwise governed IRI, then Dimension UUID or ULID; include immutable revision and digest.", "source_refs": [ "SRC-004", "SRC-007", "SRC-010", "SRC-012", "SRC-013", "SRC-015", "SRC-017", "SRC-018" ] } ], "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": "assurance-system-risk-analysis-provenance-quality-and-decision-crosswalk", "name": "Assurance, system, risk, analysis, provenance, quality and decision crosswalk", "description": "Records assurance, system, risk, analysis, provenance, quality and decision crosswalk as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents 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": "assurance-system-risk-analysis-provenance-quality-and-decision-crosswalk-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish assurance, system, risk, analysis, provenance, quality and decision crosswalk?", "kind": "interoperability", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "assurance-system-risk-analysis-provenance-quality-and-decision-crosswalk-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses assurance, system, risk, analysis, provenance, quality and decision crosswalk, and under which authority?", "kind": "lifecycle", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "assurance-system-risk-analysis-provenance-quality-and-decision-crosswalk-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify assurance, system, risk, analysis, provenance, quality and decision crosswalk?", "kind": "event", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "assurance-system-risk-analysis-provenance-quality-and-decision-crosswalk-data", "name": "Assurance, system, risk, analysis, provenance, quality and decision crosswalk data", "description": "Typed assumption-scoped values and references required to answer the governed questions for assurance, system, risk, analysis, provenance, quality and decision 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": "assurance-system-risk-analysis-provenance-quality-and-decision-crosswalk-artifact", "name": "Assurance, system, risk, analysis, provenance, quality and decision crosswalk evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting assurance, system, risk, analysis, provenance, quality and decision crosswalk.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log 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-conformance-transformation-and-semantic-loss", "name": "Profile, version, license, conformance, transformation and semantic loss", "description": "Records profile, version, license, conformance, transformation and semantic loss as a source-qualified Assumption assertion while propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents 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-conformance-transformation-and-semantic-loss-q01", "text": "Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish profile, version, license, conformance, transformation and semantic loss?", "kind": "validation", "answer_data": [ "assumption identifier, proposition reference, statement, version, predecessor and lifecycle state", "assumption kind, epistemic status, intended use, reasoning context and dependent output", "scope, population, system boundary, jurisdiction, validity interval, review date and exclusions" ] }, { "id": "profile-version-license-conformance-transformation-and-semantic-loss-q02", "text": "Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses profile, version, license, conformance, transformation and semantic loss, and under which authority?", "kind": "temporal", "answer_data": [ "proposer, owner, steward, approver, reviewer, challenger and affected roles", "acceptance, sign-off, challenge, validation, escalation and revision authority", "source system, policy, purpose, access, retention and audit basis" ] }, { "id": "profile-version-license-conformance-transformation-and-semantic-loss-q03", "text": "Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify profile, version, license, conformance, transformation and semantic loss?", "kind": "measurement", "answer_data": [ "rationale, source, supporting and contrary evidence, gap, confidence and uncertainty", "dependency graph, affected output, sensitivity, false consequence, risk, mitigation and contingency", "validation method, outcome, competing assessment, correction, successor, crosswalk and semantic-loss declaration" ] } ], "data_elements": [ { "id": "profile-version-license-conformance-transformation-and-semantic-loss-data", "name": "Profile, version, license, conformance, transformation and semantic loss data", "description": "Typed assumption-scoped values and references required to answer the governed questions for profile, version, license, 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-conformance-transformation-and-semantic-loss-artifact", "name": "Profile, version, license, conformance, transformation and semantic loss evidence manifest", "description": "Digest-addressed manifest of statements, context, rationale, evidence, dependencies, assessments, consequences and revisions supporting profile, version, license, conformance, transformation and semantic loss.", "media_or_form": [ "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative assumption-log 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-assumption", "name": "Register assumption", "description": "Create one stable assumption identity linked to a proposition and initial revision.", "inputs": [ "statement or proposition reference", "proposer", "owner" ], "outputs": [ "assumption identifier", "initial revision" ], "preconditions": [ "active Dimension", "create authority" ], "effects": [ "identity and explicit unknowns are appended" ], "source_refs": [ "SRC-001", "SRC-010", "SRC-012", "SRC-017", "SRC-019", "SRC-020", "SRC-023" ] }, { "id": "express-classify", "name": "Express and classify assumption", "description": "Record the statement, optional formal expression, assumption kind and epistemic status.", "inputs": [ "assumption revision", "expression", "kind" ], "outputs": [ "versioned expression", "classification assertion" ], "preconditions": [ "terms and context resolvable" ], "effects": [ "acceptance remains distinct from truth" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-019" ] }, { "id": "bind-context-authority", "name": "Bind context and authority", "description": "Record purpose, scope, actors, authority, location, validity interval and review date.", "inputs": [ "assumption revision", "reasoning context", "roles" ], "outputs": [ "context profile" ], "preconditions": [ "identities and authority resolvable" ], "effects": [ "applicability and exclusions become explicit" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-007", "SRC-009", "SRC-010", "SRC-020" ] }, { "id": "accept-signoff", "name": "Accept or sign off assumption", "description": "Append accountable acceptance for a bounded purpose without asserting universal truth.", "inputs": [ "assumption revision", "acceptance rationale", "approver" ], "outputs": [ "acceptance assertion" ], "preconditions": [ "sign-off authority", "scope known" ], "effects": [ "prior state and dissent remain visible" ], "source_refs": [ "SRC-001", "SRC-010", "SRC-011", "SRC-024" ] }, { "id": "link-dependencies", "name": "Link dependencies", "description": "Bind parent, derived, conflicting and affected requirements, models, estimates, plans and decisions.", "inputs": [ "assumption revision", "typed links", "dependent outputs" ], "outputs": [ "dependency graph" ], "preconditions": [ "endpoint versions resolvable" ], "effects": [ "circularity and conflicts are reported" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-012", "SRC-024" ] }, { "id": "assess-uncertainty-impact", "name": "Assess uncertainty and impact", "description": "Record confidence basis, sensitivity, false consequences, risk, mitigation and contingency.", "inputs": [ "assumption revision", "uncertainty inputs", "scenarios" ], "outputs": [ "qualified assessment" ], "preconditions": [ "method and units declared" ], "effects": [ "confidence, probability and risk remain distinct" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013" ] }, { "id": "challenge-assumption", "name": "Challenge assumption", "description": "Append contrary evidence, counterclaim, gap or dispute and notify affected contexts.", "inputs": [ "assumption revision", "challenge", "challenger" ], "outputs": [ "challenge assertion", "affected-context notice" ], "preconditions": [ "source and authority recorded" ], "effects": [ "the challenged premise is not overwritten" ], "source_refs": [ "SRC-001", "SRC-007", "SRC-010", "SRC-012", "SRC-014" ] }, { "id": "validate-review", "name": "Validate or review assumption", "description": "Apply a declared method and criteria, record contextual outcome and schedule follow-up.", "inputs": [ "assumption revision", "method", "evidence" ], "outputs": [ "review record", "qualified outcome" ], "preconditions": [ "criteria and reviewer authority declared" ], "effects": [ "outcome never becomes a context-free truth flag" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-016" ] }, { "id": "revise-supersede", "name": "Revise or supersede", "description": "Create a correction, replacement, split or merge without overwriting prior reliance history.", "inputs": [ "current revision", "reason", "successor" ], "outputs": [ "successor revision", "difference trace" ], "preconditions": [ "revision authority" ], "effects": [ "prior states and dependent uses remain resolvable" ], "source_refs": [ "SRC-004", "SRC-010", "SRC-012", "SRC-017", "SRC-023" ] }, { "id": "project-assumption", "name": "Project assumption view", "description": "Produce a minimum-necessary standards-aligned view with declared transformation loss.", "inputs": [ "assumption 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-KNW-007 Claim / Proposition", "relation": "REFERENCE", "purpose": "Resolve proposition identity while the registry parent signal remains under joint boundary review.", "required": true, "source_refs": [ "SRC-001", "SRC-014", "SRC-019" ] }, { "target": "WM-KNW-008 Evidence / Citation and fact, observation and source-document masters", "relation": "REFERENCE", "purpose": "Resolve supporting, contrary and missing evidence without importing evidence lifecycle or content.", "required": false, "source_refs": [ "SRC-007", "SRC-009", "SRC-010", "SRC-012", "SRC-013", "SRC-014" ] }, { "target": "WM-KNW-009 Hypothesis, WM-KNW-013 Constraint / Requirement Rule, risk, issue, decision, plan, model, estimate and test masters", "relation": "REFERENCE", "purpose": "Resolve neighboring epistemic, normative, risk and reliance contexts without copying their state machines.", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008", "SRC-011", "SRC-024" ] }, { "target": "OMG SACM 2.3 and SysML 2.0", "relation": "ALIGN", "purpose": "Project assumed-claim, argument-context and system-model assumption views.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "ISO/IEC/IEEE 29148:2018 and 15288:2023", "relation": "ALIGN", "purpose": "Project requirements and system-life-cycle contexts, traceability and review semantics.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "ISO 31000:2018, IEC 31010:2019 and NIST SP 800-30 Rev. 1", "relation": "ALIGN", "purpose": "Project uncertainty, risk, consequence, likelihood, impact and assessment-method views.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-008" ] }, { "target": "NIST AI RMF 1.0", "relation": "ALIGN", "purpose": "Project AI context assumptions, limitations, risk, validation and monitoring views while revision remains pending.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "NASA Systems Engineering Handbook, UK AQuA Book and GAO-20-195G", "relation": "ALIGN", "purpose": "Project engineering, analytical and estimating assumption-log profiles with explicit sign-off and sensitivity.", "required": false, "source_refs": [ "SRC-009", "SRC-010", "SRC-011" ] }, { "target": "PROV-O, DQV, Web Annotation, ODRL and SHACL", "relation": "ALIGN", "purpose": "Project provenance, quality, annotation, access-policy and validation-report semantics.", "required": false, "source_refs": [ "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016" ] }, { "target": "DataCite 4.7, RO-Crate 1.3 and Schema.org Claim", "relation": "ALIGN", "purpose": "Project persistent identity, packaging, contextual entities and claim discovery metadata.", "required": false, "source_refs": [ "SRC-017", "SRC-018", "SRC-019" ] }, { "target": "RFC 3339, RFC 2119, RFC 8174 and RFC 8785", "relation": "ALIGN", "purpose": "Project unambiguous clocks, declared normative language and deterministic serialization.", "required": false, "source_refs": [ "SRC-020", "SRC-021", "SRC-022", "SRC-023" ] }, { "target": "OMG DMN 1.5", "relation": "ALIGN", "purpose": "Project assumption-to-input, knowledge-source and decision dependency views without making DMN the master.", "required": false, "source_refs": [ "SRC-024" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, assumption steward, proposition, evidence, risk, decision, plan and policy masters, plus proposer, approver, reviewer and challenger roles.", "Publish assumption-kind, epistemic-state, confidence, uncertainty, impact, validation-outcome, access, retention and interoperability registries.", "Pin domain, assurance, risk, legal, safety, security, jurisdiction, analytical-method and exchange profiles." ], "namespace_guidance": "Mint assumption, revision, assessment, challenge, acceptance and projection identifiers only in the adopting Dimension namespace; preserve proposition, fact, evidence, requirement, risk, decision, plan, test and source-document identities as typed external references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local assumption, authority, uncertainty, validation, access, retention and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, authoritative assumption identity, proposition reference, immutable revision, intended-use context, owner and source; never use title, statement, date, filename or hash alone as identity.", "Keep proposition content, assumption role, acceptance, evidence assessment, hypothesis, requirement, risk, decision, plan and validation outcome distinct." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, profile, authority, source, rationale, access, time, dependency and interoperability impact.", "Breaking changes require a new version, migration and crosswalk maps, compatibility declaration and continued resolution of prior revisions and dependent uses." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when identity, proposition, status, purpose, scope, authority, dependency, validation and access meaning remain intact.", "SACM, SysML, ISO, NIST, NASA, Aqua Book, GAO, PROV, DQV, RO-Crate and DMN 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 assumption and immutable revision, including an assumption-log identifier where that log is authoritative.", "Governed globally resolvable assumption or proposition 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 proposal, acceptance, effective, observation, challenge, review, invalidation, expiry, correction and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {assumption-id}--{artifact-kind}--{revision-or-assessment-id}; never use a date, title, statement, result, filename or hash alone as identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and vocabulary versions, purpose and scope, clocks, provenance, confidence, license and access marking for each retained serial artifact." }, "policies": [ "The adopting Dimension declares who may propose, own, accept, challenge, validate, revise, disclose, retain and tombstone assumptions.", "Every accepted assumption requires identity and revision, proposition, kind, purpose, scope, owner, authority, rationale, status, review trigger and false-consequence assessment as applicable.", "Agents never infer truth, certainty, probability, safety, compliance or accountable approval from acceptance, confidence or one validation result.", "Facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source documents remain external masters.", "Automated agents may append low-risk classifications, links, freshness checks and projections under delegation, but acceptance, risk acceptance, protected disclosure and irreversible deletion require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, requested revision, intended-use context, status, validity horizon, dependency depth, assurance, license and access policy; return the minimum permitted projection." ], "create": [ "Create stable identity, proposition reference or marked statement, kind, proposer, owner, purpose, scope, rationale, review trigger and explicit unknowns before acceptance." ], "update": [ "Append an immutable acceptance, context, evidence, challenge, assessment, consequence, dependency 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 Assumption-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": "Assumption steward", "responsibilities": [ "Own assumption identity, kinds, states, review cadence, version and crosswalk policy." ] }, { "name": "Proposer or analyst", "responsibilities": [ "Own statement, purpose, scope, rationale, uncertainty and dependency proposal." ] }, { "name": "Owner or accountable user", "responsibilities": [ "Own operational reliance, monitoring, consequences, mitigation and escalation." ] }, { "name": "Approver", "responsibilities": [ "Own bounded acceptance or rejection and sign-off rationale." ] }, { "name": "Validator or reviewer", "responsibilities": [ "Own method, criteria, evidence, assessment and follow-up recommendation." ] }, { "name": "Challenger or affected party", "responsibilities": [ "Append contrary evidence, impacts, disputes and correction requests without rewriting originals." ] }, { "name": "Records and access steward", "responsibilities": [ "Own disclosure, retention, legal hold, tombstone and audit policy." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless active Dimension, role, purpose, assumption sensitivity, dependent-output impact, 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 assumption, challenge, assessment, reliance or legal-hold evidence." ], "audit_requirements": [ "Log actor, role, purpose, assumption and revision identity, action, decision, policy and vocabulary versions, RFC 3339 timestamp with offset, affected contexts, 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, active purpose, relying contexts, authorities, policy, jurisdiction, time, access, retention and licensing rules.", "Read this model AGENTS.md, pinned spec.yaml and required claim, evidence, risk, decision, plan and validation instructions before mutation." ] } }, "coverage": { "claim": "WM-KNW-016 covers a governed Assumption as a versioned premise accepted for a declared purpose and context, with identity, proposition role, epistemic status, actors, authority, scope, rationale, evidence, uncertainty, dependencies, consequences, validation, lifecycle, governance and loss-aware interoperability. Domain, legal, safety, analytical-method and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Assumption, proposition, revision, acceptance, challenge, assessment and successor identities remain distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Planning, modeling, estimating, argument, safety and operational assumption profiles are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Statement, kind, status, purpose, scope, rationale, uncertainty, impact and review properties are covered." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Agents recognize assumptions by explicit premise role, declared reliance context and non-factual status rather than wording alone." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, accepted, active, challenged, invalidated, expired, superseded and retired states preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Claims, evidence, requirements, risks, decisions, plans, tests and dependent outputs use typed references." }, { "dimension": "temporal", "status": "covered", "notes": "Proposal, acceptance, validity, observation, review, challenge, invalidation, expiry and correction clocks remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Jurisdiction, environment, deployment setting, population and location scope are represented where relevant." }, { "dimension": "provenance", "status": "covered", "notes": "Proposer, source, rationale, evidence, acceptance, challenge, validation, reliance and revision are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Proposition authorship, assumption ownership, acceptance authority, validation authority and decision accountability are not conflated." }, { "dimension": "validation", "status": "covered", "notes": "Identity, context, authority, evidence, uncertainty, sensitivity, consequence, dependency, freshness and crosswalk checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, sensitivity, affected-output impact, minimum projection and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Challenges, assessments, reliance, corrections, audit or legal hold, withdrawal and tombstones are non-cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "Assurance, systems, risk, analysis, provenance, quality, packaging and decision mappings disclose loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Registration, classification, contextualization, acceptance, linking, assessment, challenge, validation, revision and projection declare controlled effects." } ], "known_omissions": [ "Discipline, safety, legal, policy, security, privacy, jurisdiction, analytical-method, licensing and retention profiles require expert review.", "Propositions, facts, evidence, hypotheses, requirements, risks, decisions, plans, tests and source-document lifecycles remain neighboring masters.", "Universal truth determination, automated risk acceptance, autonomous decision replacement and irreversible enforcement remain future work." ], "conflicts": [ "SACM models an assumption as a claim declaration, while engineering and analytical logs often treat it as a separately governed register entry; the draft preserves both proposition and premise-role identities.", "Accepted, supported, validated, confirmed and true are not interchangeable and require purpose-qualified semantics.", "Confidence, probability, uncertainty, reliability, sensitivity, materiality and risk use different scales and cannot share one universal value." ], "regional_assumptions": [ "ISO, OMG, NIST, NASA, UK and US government sources are profiles rather than universal organizational or legal rules.", "Authority, sign-off, retention, disclosure, safety and consequences depend on organization, domain and jurisdiction.", "Aqua Book and GAO guidance are strong analytical profiles but do not govern all scientific, engineering, legal or operational assumptions." ], "adversarial_checks": [ "Reject an assumption without stable identity, proposition or marked statement, revision, kind, purpose, scope, owner, source and status.", "Reject acceptance, confidence or one validation outcome represented as universal truth.", "Reject missing or contrary evidence silently converted into support.", "Reject downstream decisions, plans, risks, requirements or tests copied into the assumption instead of typed references.", "Reject false-consequence or sensitivity claims without method, units, context, source and uncertainty.", "Reject expired, invalidated or superseded assumptions silently deleted while dependent uses remain.", "Reject acceptance, risk acceptance, protected disclosure or 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 governed premise record with stable identity, acceptance state, reliance context and revision lineage. Challenges, validations and dependent decisions occur around it but do not turn the assumption itself into an event." }, "decisions": [ { "concept": "Assumption entity boundary", "disposition": "accepted", "rationale": "The model owns one attributable premise role and its immutable revisions rather than proposition truth, evidence content or dependent decision execution." }, { "concept": "WM-KNW-007 parent signal", "disposition": "held-as-reference", "rationale": "SACM supports viewing an assumption as a claim declaration, but analytical registers give the premise role separate governance; canonical inheritance requires joint boundary review." }, { "concept": "Acceptance versus truth", "disposition": "kept-distinct", "rationale": "Accepted, supported, validated, confirmed and true are not interchangeable; every status remains source, purpose, scope and time qualified." }, { "concept": "Proposition content versus premise role", "disposition": "accepted-with-dual-identity", "rationale": "The external claim or proposition retains its identity while the assumption record owns how that proposition is used as a premise in one context." }, { "concept": "Confidence, probability, uncertainty and risk", "disposition": "kept-distinct", "rationale": "These values use different scales, methods and interpretations and require explicit basis, unit, profile, time and source." }, { "concept": "Downstream reliance and consequences if false", "disposition": "accepted-as-typed-references", "rationale": "The assumption must expose dependent requirements, models, estimates, plans and decisions plus impacts and contingencies without importing their lifecycles." }, { "concept": "Challenge, validation and lifecycle", "disposition": "accepted-with-contextual-results", "rationale": "Challenges and validation results are appended with methods and evidence; invalidation, expiry and supersession preserve prior reliance history." }, { "concept": "Automated operation boundary", "disposition": "accepted-with-delegation", "rationale": "Agents may append low-risk links, classifications and freshness checks but not accept risk, sign off protected assumptions 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 returned provider error 402. 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 returned provider error 402 before producing an admissible result; no external result was admitted.", "Relation hold: WM-KNW-007 remains a required proposition reference rather than an approved parent until joint boundary review.", "Boundary hold: propositions, facts, evidence, hypotheses, requirements, rules, risks, issues, decisions, plans, tests, measurements and source documents remain external masters.", "Semantic hold: accepted, supported, validated, confirmed and true remain distinct source-qualified statuses.", "Measurement hold: confidence, probability, uncertainty, reliability, sensitivity, materiality and risk require separate methods, scales and profiles.", "Authority hold: assumption acceptance, risk acceptance, protected disclosure and irreversible deletion require accountable delegated authority.", "Profile hold: engineering, analytical, AI, safety, legal and operational assumptions require domain and jurisdiction profiles.", "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 epistemic, domain, legal, safety or operational coverage.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Reconcile the WM-KNW-007 registry parent signal with the separate identity needed for an assumption role in engineering and analytical logs.", "Develop domain-specific assumption kinds, uncertainty methods, validation criteria, risk links, review cadences and authority profiles.", "Pin every production crosswalk to exact licensed or open releases and run bidirectional conformance and semantic-loss tests.", "Obtain independent epistemology, systems engineering, risk, safety, legal, records, privacy and security review." ] }, "statistics": { "sources": 24, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }