# Write known, unknown and assumed as different states

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Write known, unknown and assumed as different states

ID: MHC-D-RESEARCH-0610 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/write-known-unknown-and-assumed-as-different-states

Uncertainty becomes dangerous when formatting erases it.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A status update blends verified facts, guesses and missing information.

### Avoid when

- Do not use 'unknown' as an excuse to omit available evidence; name the next way to reduce uncertainty where it matters.

### Explanation

Use three explicit buckets when the distinction affects action: known facts with source or observation, unknowns that block confidence, and assumptions currently used to proceed. Add what would change the assumption.

### Template

Known: [verified]. Unknown: [missing]. Assumption for now: [assumption]. Revisit when: [evidence/trigger].

### Example

'Known: transport imported. Unknown: downstream job result. Assumption: no customer impact until AIF check completes.'

### Check

A reader can tell which statements may change without rereading the whole thread.

### Limits

- Do not use 'unknown' as an excuse to omit available evidence; name the next way to reduce uncertainty where it matters.

### Evidence and sources

- supports: CDC guidance explicitly recommends distinguishing what authoritative sources know and do not know rather than presenting uncertainty as settled. — RS-F1D9B8FF58D3742D. The exact evidence standard depends on domain; this supports uncertainty labeling, not scientific review of ordinary work messages. (State of the science item)
- RS-F1D9B8FF58D3742D: How to Use the CDC Clear Communication Index — https://www.cdc.gov/ccindex/tool/how-to-use.html

### Vedokrok editorial review

Keep unknown impact unknown

“The import was accepted” does not tell you what happened downstream. If customer impact is still being checked, say so; do not let “no impact” become the default.

#### Show what you know and what you suspect

For a technical update, you could write: “Known: the import was accepted; see job 42. Unknown: the downstream result and customer impact. Working explanation: a queue delay may explain the wait. Next check: Mira will inspect the job outcome and impact signals at the agreed checkpoint.” The queue explanation is a hypothesis. It does not establish success or absence of harm.

#### Give each important unknown a next check

Name the evidence to seek, who will check it and when the next update is due. Revise the statement as results arrive. If the observed situation meets the team’s escalation rules, act without waiting for a complete explanation. CDC guidance supports acknowledging uncertainty; this technical example is an editorial application, not a CDC-tested incident procedure.

**Editorial takeaway:** Use “impact not yet established” while that is the actual state. Keep assumptions open to revision and follow required verification and escalation rules.

#### Editorial evidence

- supports: CDC guidance asks communicators to acknowledge uncertainty in data, findings, recommendations, guidance and action steps. — EA-CDC-CCINDEX-ITEM11. Selected guidance inspected on 2026-10-05. Used for uncertainty labeling; public-health guidance does not independently validate this workplace workflow. (State of the Science, opening paragraphs)
- limits: Information currently treated as known may still be incomplete or insufficient to answer the audience’s questions. — EA-CDC-CCINDEX-ITEM11. Limits what a Known label establishes: neither a label nor a completed intermediate step proves the downstream outcome. (State of the Science, opening paragraph)
- contextualizes: Google’s incident guidance recommends predefined declaration conditions and early use of incident management rather than waiting for a worsening situation. — RS-A7FC21766320D048. Selected passage inspected on 2026-10-05. Its example thresholds are local practice, not universal timing rules; no incident was operated. (When to Declare an Incident)
- EA-CDC-CCINDEX-ITEM11: CDC Clear Communication Index, item 11: State of the Science — https://www.cdc.gov/ccindex/tool/page-11.html
- RS-A7FC21766320D048: Managing Incidents — https://sre.google/sre-book/managing-incidents/

Editorial version: 1.0.1 · evidence checked 2026-10-05 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/put-the-caveat-beside-the-decision-it-can-change
