← Back to catalogue
Published

Assumption

vr.wm-knw-016 · wm-knw-016-assumption

Represent one governed premise accepted provisionally for a stated purpose, scope and reasoning context without asserting that it is a verified fact.

World Models Information and virtual systems INF.KNW.ASM

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Assumption identity, expression, kind and status Groups the governed Resource Consumption concern for assumption identity, expression, kind and status.

Identity, revision, proposition and record boundary

Groups Resource Consumption context for identity, revision, proposition and record boundary without importing neighboring master lifecycles.

Assumption identifier, namespace, version, revision, predecessor and successor

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish assumption identifier, namespace, version, revision, predecessor and successor? identity
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses assumption identifier, namespace, version, revision, predecessor and successor, and under which authority? ownership
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify assumption identifier, namespace, version, revision, predecessor and successor? validation

Proposition reference, statement, language, terms and formal expression

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish proposition reference, statement, language, terms and formal expression? definition
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses proposition reference, statement, language, terms and formal expression, and under which authority? authority
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify proposition reference, statement, language, terms and formal expression? security

Kind, epistemic status and recognition

Groups Resource Consumption context for kind, epistemic status and recognition without importing neighboring master lifecycles.

Planning, modeling, estimating, argument, safety and operational kind

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish planning, modeling, estimating, argument, safety and operational kind? classification
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses planning, modeling, estimating, argument, safety and operational kind, and under which authority? requirement
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify planning, modeling, estimating, argument, safety and operational kind? privacy

Proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status? state
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status, and under which authority? constraint
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify proposed, accepted, assumed, axiomatic, unsupported, unknown and contested status? retention
Purpose, actors, authority, scope and time Groups the governed Resource Consumption concern for purpose, actors, authority, scope and time.

Proposer, owner, approver, challenger and steward

Groups Resource Consumption context for proposer, owner, approver, challenger and steward without importing neighboring master lifecycles.

Proposer, owner, steward, approver, reviewer, challenger and affected role

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish proposer, owner, steward, approver, reviewer, challenger and affected role? ownership
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses proposer, owner, steward, approver, reviewer, challenger and affected role, and under which authority? process
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify proposer, owner, steward, approver, reviewer, challenger and affected role? access

Authority, sign-off, accountability, separation of duties and escalation

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish authority, sign-off, accountability, separation of duties and escalation? authority
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses authority, sign-off, accountability, separation of duties and escalation, and under which authority? event
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify authority, sign-off, accountability, separation of duties and escalation? exception

Purpose, reasoning context, scope, place and time

Groups Resource Consumption context for purpose, reasoning context, scope, place and time without importing neighboring master lifecycles.

Intended use, reasoning context, decision, plan, model and system boundary

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish intended use, reasoning context, decision, plan, model and system boundary? constraint
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses intended use, reasoning context, decision, plan, model and system boundary, and under which authority? measurement
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify intended use, reasoning context, decision, plan, model and system boundary? interoperability

Population, jurisdiction, environment, location, validity, review and observation time

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish population, jurisdiction, environment, location, validity, review and observation time? temporal
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses population, jurisdiction, environment, location, validity, review and observation time, and under which authority? evidence
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify population, jurisdiction, environment, location, validity, review and observation time? decision
Rationale, evidence, uncertainty and sensitivity Groups the governed Resource Consumption concern for rationale, evidence, uncertainty and sensitivity.

Rationale, source, support, challenge and gap

Groups Resource Consumption context for rationale, source, support, challenge and gap without importing neighboring master lifecycles.

Motivation, rationale, source, citation, support and justification

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish motivation, rationale, source, citation, support and justification? provenance
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses motivation, rationale, source, citation, support and justification, and under which authority? quality
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify motivation, rationale, source, citation, support and justification? identity

Contrary evidence, counterclaim, gap, conflict, bias and limitation

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish contrary evidence, counterclaim, gap, conflict, bias and limitation? evidence
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses contrary evidence, counterclaim, gap, conflict, bias and limitation, and under which authority? validation
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify contrary evidence, counterclaim, gap, conflict, bias and limitation? classification

Confidence, uncertainty, reliability and sensitivity

Groups Resource Consumption context for confidence, uncertainty, reliability and sensitivity without importing neighboring master lifecycles.

Confidence basis, probability, range, distribution, uncertainty and reliability

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish confidence basis, probability, range, distribution, uncertainty and reliability? measurement
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses confidence basis, probability, range, distribution, uncertainty and reliability, and under which authority? security
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify confidence basis, probability, range, distribution, uncertainty and reliability? composition

Sensitivity driver, threshold, scenario, robustness and materiality

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish sensitivity driver, threshold, scenario, robustness and materiality? quality
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses sensitivity driver, threshold, scenario, robustness and materiality, and under which authority? privacy
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify sensitivity driver, threshold, scenario, robustness and materiality? relationship
Dependencies, consequences, risk and contingency Groups the governed Resource Consumption concern for dependencies, consequences, risk and contingency.

Dependency, derivation, conflict and affected output

Groups Resource Consumption context for dependency, derivation, conflict and affected output without importing neighboring master lifecycles.

Parent, child, derived, prerequisite, equivalent, conflicting and circular relation

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish parent, child, derived, prerequisite, equivalent, conflicting and circular relation? relationship
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses parent, child, derived, prerequisite, equivalent, conflicting and circular relation, and under which authority? retention
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify parent, child, derived, prerequisite, equivalent, conflicting and circular relation? state

Dependent requirement, model, estimate, plan, decision, control and action

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish dependent requirement, model, estimate, plan, decision, control and action? composition
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses dependent requirement, model, estimate, plan, decision, control and action, and under which authority? access
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify dependent requirement, model, estimate, plan, decision, control and action? lifecycle

False consequence, exposure, risk, mitigation and contingency

Groups Resource Consumption context for false consequence, exposure, risk, mitigation and contingency without importing neighboring master lifecycles.

False or invalid consequence, impact, likelihood, exposure, priority and criticality

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish false or invalid consequence, impact, likelihood, exposure, priority and criticality? measurement
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses false or invalid consequence, impact, likelihood, exposure, priority and criticality, and under which authority? exception
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify false or invalid consequence, impact, likelihood, exposure, priority and criticality? temporal

Monitor, indicator, trigger, mitigation, contingency, fallback and safe state

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish monitor, indicator, trigger, mitigation, contingency, fallback and safe state? process
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses monitor, indicator, trigger, mitigation, contingency, fallback and safe state, and under which authority? interoperability
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify monitor, indicator, trigger, mitigation, contingency, fallback and safe state? spatial
Challenge, validation, review, lifecycle and change Groups the governed Resource Consumption concern for challenge, validation, review, lifecycle and change.

Validation method, criterion, result and evidence

Groups Resource Consumption context for validation method, criterion, result and evidence without importing neighboring master lifecycles.

Validation question, method, input, criterion, threshold, reviewer and schedule

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish validation question, method, input, criterion, threshold, reviewer and schedule? validation
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses validation question, method, input, criterion, threshold, reviewer and schedule, and under which authority? decision
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify validation question, method, input, criterion, threshold, reviewer and schedule? provenance

Supported, challenged, confirmed, invalidated, inconclusive and not-tested result

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish supported, challenged, confirmed, invalidated, inconclusive and not-tested result? state
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses supported, challenged, confirmed, invalidated, inconclusive and not-tested result, and under which authority? identity
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify supported, challenged, confirmed, invalidated, inconclusive and not-tested result? ownership

Lifecycle, review, correction and supersession

Groups Resource Consumption context for lifecycle, review, correction and supersession without importing neighboring master lifecycles.

Draft, proposed, accepted, active, challenged, invalidated, expired and retired state

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish draft, proposed, accepted, active, challenged, invalidated, expired and retired state? lifecycle
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses draft, proposed, accepted, active, challenged, invalidated, expired and retired state, and under which authority? classification
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify draft, proposed, accepted, active, challenged, invalidated, expired and retired state? authority

Review trigger, correction, revision, split, merge, replacement and supersession

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish review trigger, correction, revision, split, merge, replacement and supersession? lifecycle
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses review trigger, correction, revision, split, merge, replacement and supersession, and under which authority? composition
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify review trigger, correction, revision, split, merge, replacement and supersession? requirement
Governance, access, retention and interoperability Groups the governed Resource Consumption concern for governance, access, retention and interoperability.

Policy, quality, security, access and retention

Groups Resource Consumption context for policy, quality, security, access and retention without importing neighboring master lifecycles.

Completeness, consistency, freshness, traceability, quality and assurance

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish completeness, consistency, freshness, traceability, quality and assurance? quality
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses completeness, consistency, freshness, traceability, quality and assurance, and under which authority? relationship
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify completeness, consistency, freshness, traceability, quality and assurance? constraint

Purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone? access
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone, and under which authority? state
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify purpose, role, sensitivity, minimum disclosure, retention, legal hold and tombstone? process

Standards crosswalk, conformance and loss

Groups Resource Consumption context for standards crosswalk, conformance and loss without importing neighboring master lifecycles.

Assurance, system, risk, analysis, provenance, quality and decision crosswalk

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish assurance, system, risk, analysis, provenance, quality and decision crosswalk? interoperability
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses assurance, system, risk, analysis, provenance, quality and decision crosswalk, and under which authority? lifecycle
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify assurance, system, risk, analysis, provenance, quality and decision crosswalk? event

Profile, version, license, conformance, transformation and semantic loss

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.

  1. Which identity, statement, assumption kind, epistemic status, purpose, scope and revision establish profile, version, license, conformance, transformation and semantic loss? validation
  2. Who proposes, owns, accepts, challenges, validates, reviews, revises or discloses profile, version, license, conformance, transformation and semantic loss, and under which authority? temporal
  3. Which rationale, evidence, uncertainty, dependencies, false consequences, assessments and interoperability limits qualify profile, version, license, conformance, transformation and semantic loss? measurement

Classifiers Filled

Family
World Models
Category
Information and virtual systems
Entry kind
entity
Navigation path
NAV.INF.KNW.ASM
Domain
INF.KNW.ASM
Industry
Cross-industry
Tags
assumptioninf.knw.asm

What it is Filled

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

Why it exists Filled

Represent one governed premise accepted provisionally for a stated purpose, scope and reasoning context without asserting that it is a verified fact.

Distinguishing features Filled

  • A proposition taken as true for a stated purpose and scope, without being established as fact.
  • Differs from a hypothesis, which is put to test, and from a requirement, which states what must hold.
  • Accepting an assumption does not make it true, and confidence in it is not a probability.
  • Carries a review trigger and the consequence of being wrong, which a plain fact record does not.

What robots and AI may and may not do Filled

Must not

  • Present an assumption as an established fact in reports or decisions.
  • Accept or sign off an assumption on behalf of its owner.
  • Accept the risk of an assumption being false.
  • Drop the recorded consequence of the assumption being false.
  • Silently extend an assumption beyond its stated scope or validity period.

Only with a human decision

  • Accepting or signing off an assumption.
  • Accepting the risk that a critical assumption is false.
  • Retiring an assumption that decisions still depend on.

May

  • Record an assumption with its statement, owner, purpose, scope and review date.
  • Link the plans, estimates, models and decisions that depend on it.
  • Check review dates and flag stale or expired assumptions.
  • Report evidence that contradicts an accepted assumption.

Moral aspects Filled

  • Unstated assumptions about people, for example their needs or behaviour, can carry bias into decisions.
  • Safety cases and analyses depend on assumptions, so hiding them puts people at risk.
  • Transparency about assumptions lets those affected challenge a decision.

Who is affected

  • People affected by decisions built on the assumption
  • Decision makers and analysts
  • Engineers and safety reviewers
  • Auditors

Owners Filled

Steward

Declare the Dimension owner, assumption steward, proposition, evidence, risk, decision, plan and policy masters, plus proposer, approver, reviewer and challenger roles.

Roles

Dimension owner
Own namespace, mastership, delegation, access, retention and federation rules.
Assumption steward
Own assumption identity, kinds, states, review cadence, version and crosswalk policy.
Proposer or analyst
Own statement, purpose, scope, rationale, uncertainty and dependency proposal.
Owner or accountable user
Own operational reliance, monitoring, consequences, mitigation and escalation.
Approver
Own bounded acceptance or rejection and sign-off rationale.
Validator or reviewer
Own method, criteria, evidence, assessment and follow-up recommendation.
Challenger or affected party
Append contrary evidence, impacts, disputes and correction requests without rewriting originals.
Records and access steward
Own disclosure, retention, legal hold, tombstone and audit policy.

Links to other meta-models Filled

references

  • WM-KNW-007 Claim / Proposition - Resolve proposition identity while the registry parent signal remains under joint boundary review.
  • WM-KNW-008 Evidence / Citation and fact, observation and source-document masters - Resolve supporting, contrary and missing evidence without importing evidence lifecycle or content.
  • WM-KNW-009 Hypothesis, WM-KNW-013 Constraint / Requirement Rule, risk, issue, decision, plan, model, estimate and test masters - Resolve neighboring epistemic, normative, risk and reliance contexts without copying their state machines.

aligned

  • OMG SACM 2.3 and SysML 2.0 - Project assumed-claim, argument-context and system-model assumption views.
  • ISO/IEC/IEEE 29148:2018 and 15288:2023 - Project requirements and system-life-cycle contexts, traceability and review semantics.
  • ISO 31000:2018, IEC 31010:2019 and NIST SP 800-30 Rev. 1 - Project uncertainty, risk, consequence, likelihood, impact and assessment-method views.
  • NIST AI RMF 1.0 - Project AI context assumptions, limitations, risk, validation and monitoring views while revision remains pending.
  • NASA Systems Engineering Handbook, UK AQuA Book and GAO-20-195G - Project engineering, analytical and estimating assumption-log profiles with explicit sign-off and sensitivity.
  • PROV-O, DQV, Web Annotation, ODRL and SHACL - Project provenance, quality, annotation, access-policy and validation-report semantics.
  • DataCite 4.7, RO-Crate 1.3 and Schema.org Claim - Project persistent identity, packaging, contextual entities and claim discovery metadata.
  • RFC 3339, RFC 2119, RFC 8174 and RFC 8785 - Project unambiguous clocks, declared normative language and deterministic serialization.
  • OMG DMN 1.5 - Project assumption-to-input, knowledge-source and decision dependency views without making DMN the master.

neighbor

  • WM-KNW-007 Claim / Proposition - 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.
  • Fact and observation - 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.
  • WM-KNW-009 Hypothesis - 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.
  • WM-KNW-008 Evidence / Citation - Evidence and citations remain external records. The assumption owns qualified support, challenge and gap bindings, not the evidence content.
  • Requirement, rule, risk and issue - These records may depend on or challenge an assumption. Their normative force, assessment, treatment and resolution lifecycles remain external.
  • Decision, plan, model and estimate - These contexts rely on assumptions and own accountable choices, execution, algorithms or calculated outputs. The assumption records typed reliance and impact links only.
  • Validation and review - A validation activity and its evidence remain external. The assumption owns source-qualified assessment links and contextual status, never a global truth flag.

parent

  • WM-KNW-007

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • 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.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • An assumption record has a statement, owner, purpose, scope, status, review date and the consequence if false.
  • Often confused with a fact, a hypothesis, a requirement and a risk.

Capabilities and actions required Filled

  • Register assumption: Create one stable assumption identity linked to a proposition and initial revision.
  • Express and classify assumption: Record the statement, optional formal expression, assumption kind and epistemic status.
  • Bind context and authority: Record purpose, scope, actors, authority, location, validity interval and review date.
  • Accept or sign off assumption: Append accountable acceptance for a bounded purpose without asserting universal truth.
  • Link dependencies: Bind parent, derived, conflicting and affected requirements, models, estimates, plans and decisions.
  • Assess uncertainty and impact: Record confidence basis, sensitivity, false consequences, risk, mitigation and contingency.
  • Challenge assumption: Append contrary evidence, counterclaim, gap or dispute and notify affected contexts.
  • Validate or review assumption: Apply a declared method and criteria, record contextual outcome and schedule follow-up.
  • Revise or supersede: Create a correction, replacement, split or merge without overwriting prior reliance history.
  • Project assumption view: Produce a minimum-necessary standards-aligned view with declared transformation loss.

Hazards and failure modes required Filled

  • Decisions resting on stale or false assumptions.
  • Unsafe designs when a safety assumption fails unnoticed.
  • Hidden dependencies that spread an error across many analyses.

Standards and interfaces required Filled

  • W3C PROV-O for provenance.
  • IETF RFC 2119 and RFC 8174 requirement keywords.
  • ISO/IEC/IEEE 15288 system life cycle processes.

Context of use required Filled

  • 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.

Sources Filled

  1. Structured Assurance Case Metamodel - Object Management Group
  2. Systems Modeling Language - Object Management Group
  3. Requirements engineering - International Organization for Standardization
  4. System life cycle processes - International Organization for Standardization
  5. Risk management guidelines - International Organization for Standardization
  6. Risk assessment techniques - International Electrotechnical Commission
  7. Artificial Intelligence Risk Management Framework - National Institute of Standards and Technology
  8. Guide for Conducting Risk Assessments - National Institute of Standards and Technology
  9. Systems Engineering Handbook Appendix - National Aeronautics and Space Administration
  10. The AQuA Book - United Kingdom Government Analysis Function
  11. Cost Estimating and Assessment Guide - United States Government Accountability Office
  12. PROV-O: The PROV Ontology - World Wide Web Consortium
  13. Data Quality Vocabulary - World Wide Web Consortium
  14. Web Annotation Data Model - World Wide Web Consortium
  15. ODRL Information Model 2.2 - World Wide Web Consortium
  16. Shapes Constraint Language - World Wide Web Consortium
  17. DataCite Metadata Schema - DataCite
  18. RO-Crate Specification - RO-Crate Community
  19. Schema.org Claim - Schema.org Community Group
  20. Date and Time on the Internet - Internet Engineering Task Force
  21. Key words for use in RFCs - Internet Engineering Task Force
  22. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words - Internet Engineering Task Force
  23. JSON Canonicalization Scheme - Internet Engineering Task Force
  24. Decision Model and Notation - Object Management Group

Open questions

  • 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.
  • 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.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-knw-016-assumption/spec.yaml, ver-cy/world-models/card-supplements/wm-knw-016-assumption.json