# Analyze data for a decision

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

Define trustworthy inputs, a decision-linked metric and the right comparison before choosing a chart or declaring a trend.
Collection kind: collection
Source: https://vedokrok.com/collections/analyze-data-for-a-decision
Version: 1.0.0

---

## Give a KPI a decision

ID: MHC-D-BRALI-0176 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/give-a-kpi-a-decision

What would you do differently if this number changed?

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

### Use when

- A team is choosing a small set of headline metrics.

### Explanation

A KPI is a selected indicator of performance. Write what it represents, who interprets it and which decision it informs. Include a guardrail for something the main number can miss. Treat the template as a contract for interpreting a measure, not proof that measuring it improves the outcome.

### Template

KPI: ___.
Outcome/driver represented: ___.
Owner: ___.
Decision it informs: ___.
Guardrail metric: ___.
Known failure mode or gaming risk: ___.

### Example

A support team pairs resolution time with reopened cases. Faster closure alone cannot show whether a problem stayed solved.

### Check

Name a plausible change in the number and the decision it would inform. Is that decision still sensible if the guardrail worsens?

### Limits

- Not every important outcome is measurable as one KPI, and targets can distort behavior.

### Evidence and sources

- contextualizes: This KPI template separates the indicator, its intended meaning, its decision owner and a guardrail. — FP-BRALI-0176. Editorial design and source provenance only. No causal benefit, percentage improvement or validated intervention is claimed. Access: selected_source_sections; 2026-10-11. Registered first-party project text; template provenance, not an efficacy study. (Selected template fields)
- FP-BRALI-0176: Make a KPI answer a decision — Brali source record — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/kpi-coach.json

Review: agent · Agent editorial and scoped evidence review · 2026-10-11T19:01:14Z
Published: 2026-10-11T19:10:00Z
Related (use_before): https://vedokrok.com/knowledge/choose-the-chart-from-the-question

---

## Call a trend only after defining the window

ID: MHC-D-BRALI-0177 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/call-a-trend-only-after-defining-the-window

A line can look like a trend because the chart starts at the convenient point. Define the time window, baseline, seasonality and meaningful comparison before interpreting movement.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- A metric appears to be rising, falling or changing direction.

### Avoid when

- Visual movement does not establish causality. Use statistical methods when inference or forecast accuracy matters.

### Explanation

A line can look like a trend because the chart starts at the convenient point. Define the time window, baseline, seasonality and meaningful comparison before interpreting movement.

### Steps

1. Define the time window relevant to the decision.
2. Compare with an appropriate baseline or prior period.
3. Check seasonality, one-off events and changes in measurement.
4. Inspect whether a few observations dominate the pattern.
5. State the trend together with the uncertainty or caveat that matters.

### Check

The trend claim names its window, baseline and material caveat.

### Limits

- Visual movement does not establish causality. Use statistical methods when inference or forecast accuracy matters.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-6cb9c4d239648bd9a7a1. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/spot-and-track-data-trends.json)
- FP-BRALI-SRC-6cb9c4d239648bd9a7a1: Data Analysts Identify Patterns and Trends in Data — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/spot-and-track-data-trends.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z

---

## Choose the chart from the question

ID: MHC-D-BRALI-0178 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/choose-the-chart-from-the-question

A chart is a visual query. Choose the form from what the reader must compare: magnitude, trend, distribution, composition or relationship—not from what looks impressive.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- You need to present quantitative data visually.

### Avoid when

- A chart cannot rescue ambiguous definitions or bad data. Accessibility and truthful axes still matter.

### Explanation

A chart is a visual query. Choose the form from what the reader must compare: magnitude, trend, distribution, composition or relationship—not from what looks impressive.

### Checklist

- Write the question the chart should answer.
- Use position and length for precise comparisons when practical.
- Use a line for ordered change over time when continuity matters.
- Use distributions when averages would hide spread or outliers.
- Label units, denominators and important context.
- Remove decorative encodings that do not help answer the question.

### Check

The chart type and annotations make the intended quantitative comparison easy to inspect.

### Limits

- A chart cannot rescue ambiguous definitions or bad data. Accessibility and truthful axes still matter.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-28a7076a56681c43a388. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/visualize-data-with-charts.json)
- FP-BRALI-SRC-28a7076a56681c43a388: Data Analysts Use Charts and Graphs to Make Data Understandable — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/visualize-data-with-charts.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z

---

## Test the assumption, not only the flow

ID: MHC-D-BRALI-0181 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/test-the-assumption-not-only-the-flow

A system can pass every happy-path step and still be wrong because an underlying assumption fails. Add tests around data, permissions, timing, dependencies and user behavior—not only around buttons and responses.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- You are reviewing a feature or process whose correctness depends on assumptions outside the main path.

### Avoid when

- Risk-based coverage is more useful than trying to enumerate every imaginable case.

### Explanation

A system can pass every happy-path step and still be wrong because an underlying assumption fails. Add tests around data, permissions, timing, dependencies and user behavior—not only around buttons and responses.

### Checklist

- List the assumptions that must be true for the feature to work.
- Turn important assumptions into test conditions or monitoring.
- Test missing, stale, duplicate and contradictory data where relevant.
- Test permissions, concurrency, timeouts and dependency failure.
- Keep a visible unknown state instead of silently treating missing evidence as success.

### Check

At least the important failure-producing assumptions have explicit tests or monitoring.

### Limits

- Risk-based coverage is more useful than trying to enumerate every imaginable case.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-3df422c228f08abca472. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/qa-assumption-testing-habit.json)
- FP-BRALI-SRC-3df422c228f08abca472: QA Specialists Test Software to Find Flaws — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/qa-assumption-testing-habit.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z

---

## Separate severity from priority

ID: MHC-D-BRALI-0182 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/separate-severity-from-priority

Describe the damage before deciding the queue.

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

### Use when

- Bugs or incidents compete for limited remediation capacity.

### Explanation

Severity describes the observed impact of a defect. Priority records how urgently the organisation plans to address it, considering exposure, workarounds, dependencies and deadlines. Keeping them separate makes the scheduling decision visible without changing the impact record to justify it. Use the organisation’s definitions for each label.

### Template

Observed impact / severity: ___.
Who or what is affected: ___.
Workaround: ___.
Exposure/frequency: ___.
Deadline, dependency or business reason affecting priority: ___.
Current priority and owner: ___.

### Example

An export fails for a small group with a workaround. A contractual deadline can raise its priority without changing the observed failure.

### Check

Does the record explain both the impact and the reason for its place in the queue?

### Limits

- Priority can change with releases, regulation, customer exposure or available workaround; severity should not be rewritten merely to win scheduling. Follow the formal escalation policy for safety, security or regulatory incidents; this template does not set their urgency.

### Evidence and sources

- contextualizes: This triage template records observed impact separately from the organisation’s scheduling priority. — FP-BRALI-0182. Editorial design and source provenance only. No causal benefit, percentage improvement or validated intervention is claimed. Access: selected_source_sections; 2026-10-11. Registered first-party project text; template provenance, not an efficacy study. (Selected template fields)
- FP-BRALI-0182: Separate severity from priority — Brali source record — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/qa-severity-priority-coach.json

Review: agent · Agent editorial and scoped evidence review · 2026-10-11T19:01:14Z
Published: 2026-10-11T19:10:00Z
