# Leave work another person can use

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

Make results, failures, fixes and responsibilities inspectable.
Collection kind: collection
Source: https://vedokrok.com/collections/leave-work-another-person-can-use
Version: 1.0.0

---

## Build a checklist from real misses

ID: MHC-D-BRALI-0014 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/build-a-checklist-from-real-misses

'Check carefully' is a wish wearing a checkbox. A useful check names the action and the expected result. Build the list from errors that matter, then keep revising it when real work reveals a gap.

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

### Use when

- A recurring low-risk workflow has known, preventable misses.

### Avoid when

- Do not replace regulated or safety-critical procedures with a personal checklist. A completed box is not proof unless the check was actually performed.

### Explanation

'Check carefully' is a wish wearing a checkbox. A useful check names the action and the expected result. Build the list from errors that matter, then keep revising it when real work reveals a gap.

### Steps

1. List the failure modes worth catching.
2. For each necessary check, write what to inspect and what a pass looks like.
3. State what to capture or do when the result differs.
4. Try the list on a representative case and remove redundant checks.

### Example

Replace 'check the file' with 'confirm the expected columns, record count and date range against the source request.'

### Check

Another person can run the checks and distinguish pass, fail and not checked.

### Limits

- Do not replace regulated or safety-critical procedures with a personal checklist. A completed box is not proof unless the check was actually performed.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-e31b81f5ba0e2f64b7ce. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/qa-checklist-templates-runbook.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-c0110765f1034fef591d. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/document-review-checklist-template.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-bdea99e537474bfc4de0. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/attention-to-detail-trainer.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-d0eed253dd05d04bc0ea. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/qa-attention-to-detail-checks.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-5fecb783184e6c309973. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/double-check-precision-tracker.json)
- FP-BRALI-SRC-e31b81f5ba0e2f64b7ce: Build a QA Checklist from Real Failure Modes — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/qa-checklist-templates-runbook.json
- FP-BRALI-SRC-c0110765f1034fef591d: Create a Checklist of Common Errors to Review Each Time You Finish a Document — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/document-review-checklist-template.json
- FP-BRALI-SRC-bdea99e537474bfc4de0: Run a Detail Check Before You Ship — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/attention-to-detail-trainer.json
- FP-BRALI-SRC-d0eed253dd05d04bc0ea: QA Specialists Meticulously Check for Errors — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/qa-attention-to-detail-checks.json
- FP-BRALI-SRC-5fecb783184e6c309973: Pay Close Attention to Detail in Your Tasks — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/double-check-precision-tracker.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (useful_with): https://vedokrok.com/knowledge/write-a-bug-report-someone-can-use
Related (useful_with): https://vedokrok.com/knowledge/keep-a-work-evidence-log
Related (useful_with): https://vedokrok.com/knowledge/save-the-fix-with-its-conditions
Related (useful_with): https://vedokrok.com/knowledge/map-the-handoffs-not-just-the-boxes
Related (useful_with): https://vedokrok.com/knowledge/make-the-capacity-trade-off-visible

---

## Write a bug report someone can use

ID: MHC-D-BRALI-0015 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/write-a-bug-report-someone-can-use

A symptom is an observation. Its cause is still a hypothesis.

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

### Use when

- You need another person to investigate a reproducible work-system problem.

### Explanation

Give the investigator a path from the conditions to what you actually saw. Separate expected behaviour, observed behaviour and your suspected explanation. If the failure happened once, say so; do not invent reliable reproduction. The acceptance check describes the behaviour a fix must restore.

### Template

Context and version: ___.
Smallest reproduction steps: ___.
Expected result: ___.
Observed result and evidence: ___.
Suspected cause, if any: ___.
Acceptance check for the fix: ___.

### Example

A browser shows an old address after saving. You record the version and one failed attempt; caching remains a suspicion.

### Check

Can another person distinguish what happened, what should happen and what still needs testing?

### Limits

- Remove credentials and unnecessary personal or customer data from screenshots, logs and examples.

### Evidence and sources

- contextualizes: This report template keeps expected behaviour, observed behaviour and suspected cause in separate fields. — FP-BRALI-0015. Editorial design and source provenance only. No causal benefit, percentage improvement or validated intervention is claimed. Access: full_structured_record; 2026-10-11. Registered first-party project text; template provenance, not an efficacy study. (Selected template fields)
- FP-BRALI-0015: Write a bug report someone can use — Brali source record — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/qa-clear-feedback-templates.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/separate-severity-from-priority
Related (use_before): https://vedokrok.com/knowledge/save-the-fix-with-its-conditions

---

## Save the fix with its conditions

ID: MHC-D-BRALI-0018 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/save-the-fix-with-its-conditions

A solution without its conditions is a future misunderstanding. Record what failed, where the fix applied and how you knew it worked. Leave enough context for someone to decide whether the same fix belongs in a different case.

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

### Use when

- You have solved a problem that is likely to recur.

### Avoid when

- Exclude secrets and personal data. Recheck version-sensitive instructions before applying them again.

### Explanation

Keep a workaround labelled as a workaround. Its usefulness does not make the underlying cause known.

### Template

Symptom and affected context: ___.
Confirmed cause, or remaining uncertainty: ___.
Change made: ___.
Verification performed: ___.
Do not reuse when: ___.

### Check

The fix can be found, understood and checked for fit before reuse.

### Limits

- Exclude secrets and personal data. Recheck version-sensitive instructions before applying them again.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-1160e21bcf4b137b08c4. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/document-learnings-knowledge-base.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-b967bd2353325cff4fc3. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/qa-documentation-tracker.json)
- FP-BRALI-SRC-1160e21bcf4b137b08c4: After Solving a Problem or Learning Something New, Document It in Your Knowledge Base — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/document-learnings-knowledge-base.json
- FP-BRALI-SRC-b967bd2353325cff4fc3: QA Specialists Document Testing Procedures — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/qa-documentation-tracker.json

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

---

## Keep a work evidence log

ID: MHC-D-BRALI-0017 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/keep-a-work-evidence-log

When review season arrives, 'I did a lot' is not much of a case. Capture a few facts after meaningful work while you can still locate the evidence. The point is a reusable record, not a collection of heroic adjectives.

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

### Use when

- A completed contribution may matter in a review, interview or project handover.

### Avoid when

- Do not publish confidential client details or turn a team's result into a solo achievement.

### Explanation

Before reusing an entry, verify the figures and distinguish completed results from expected benefits.

### Template

Situation: ___.
My contribution: ___.
Team or partner contributions: ___.
Result or current state: ___.
Evidence location and reuse restrictions: ___.

### Check

One contribution is recorded with proportionate attribution and traceable evidence.

### Limits

- Do not publish confidential client details or turn a team's result into a solo achievement.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-9632e1bcb5ee71a8b782. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/brag-doc-wins-hub.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-a788b89a528dde970b58. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/work-evidence-log.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-aeb046d40fedefa65f9a. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/leverage-past-wins.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-966d745c39c2e21a10d7. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/step-logging-reflection.json)
- FP-BRALI-SRC-9632e1bcb5ee71a8b782: Keep a Work Wins Log You Can Reuse — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/brag-doc-wins-hub.json
- FP-BRALI-SRC-a788b89a528dde970b58: Keep Detailed Records of Your Work, Projects, and Results to Track Progress and Identify — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/work-evidence-log.json
- FP-BRALI-SRC-aeb046d40fedefa65f9a: Use Your Previous Achievements to Open Doors — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/leverage-past-wins.json
- FP-BRALI-SRC-966d745c39c2e21a10d7: As You Work on a Task, Log Each Step You Take in Real-Time) — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/step-logging-reflection.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (use_before): https://vedokrok.com/knowledge/tell-an-interview-case-honestly

---

## Map the handoffs, not just the boxes

ID: MHC-D-BRALI-0025 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/map-the-handoffs-not-just-the-boxes

A process diagram can look orderly while hiding the place where work actually gets stuck: the handoff. Follow one real case through the system. Record what changes hands, who accepts it and what happens when the input is incomplete.

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

### Use when

- A workflow is hard to explain, diagnose or hand over.

### Avoid when

- Distinguish the observed process from the desired one. Do not publish names or operational details that should remain private.

### Explanation

A process diagram can look orderly while hiding the place where work actually gets stuck: the handoff. Follow one real case through the system. Record what changes hands, who accepts it and what happens when the input is incomplete.

### Steps

1. Start with one real input and its intended output.
2. Draw the steps and decisions it actually passes through.
3. At each handoff, name the owner, required input and acceptance condition.
4. Add the main waiting, failure and return paths.
5. Walk a second case through the map and repair the missing branch.

### Check

The map explains a representative case, including a meaningful exception.

### Limits

- Distinguish the observed process from the desired one. Do not publish names or operational details that should remain private.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-624ccfdf3a4274422223. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/flowchart-process-mapping-guide.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-97ca781b05cbfc48ba3e. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/practice-systems-thinking.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-6c70921f805a7e616ffd. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/systems-forecast-mapper.json)
- FP-BRALI-SRC-624ccfdf3a4274422223: Create Flowcharts to Visualize the Steps and Decision Points in a Process — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/flowchart-process-mapping-guide.json
- FP-BRALI-SRC-97ca781b05cbfc48ba3e: Look at the Big Picture — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/practice-systems-thinking.json
- FP-BRALI-SRC-6c70921f805a7e616ffd: When Analyzing a Situation, Consider How Each Part Fits into the Whole System — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/systems-forecast-mapper.json

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

---

## Make the capacity trade-off visible

ID: MHC-D-BRALI-0026 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/make-the-capacity-trade-off-visible

A new request does not create new hours. You can be helpful without pretending that every commitment fits. State what you can do, what would have to move and whose decision is needed. Keep the boundary clear enough that nobody hears a reluctant yes.

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

### Use when

- A request conflicts with existing commitments or available capacity.

### Avoid when

- Use the escalation and prioritization process your role requires. A personal preference does not erase a contractual or safety obligation.

### Explanation

A new request does not create new hours. You can be helpful without pretending that every commitment fits. State what you can do, what would have to move and whose decision is needed. Keep the boundary clear enough that nobody hears a reluctant yes.

### Template

I can deliver ___ by ___.
Taking on ___ as well would move ___.
Which should take priority, or should we reduce the scope?

### Example

I cannot take ownership of this task this week. I can share the existing notes, but I cannot promise a review.

### Check

The accepted, declined or renegotiated commitment is unambiguous.

### Limits

- Use the escalation and prioritization process your role requires. A personal preference does not erase a contractual or safety obligation.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-8989fce58fa2f5aa658c. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/when-to-say-no-at-work.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-ecb2eb339db6ce007700. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/say-no-politely-coach.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-7b5ff4fcca0b640217fb. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/burnout-boundary-tracker.json)
- FP-BRALI-SRC-8989fce58fa2f5aa658c: Learn to Say No to Tasks That Don’t Align with Your Goals, Values, or — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/when-to-say-no-at-work.json
- FP-BRALI-SRC-ecb2eb339db6ce007700: When You Need to Say No, Be Polite and Direct — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/say-no-politely-coach.json
- FP-BRALI-SRC-7b5ff4fcca0b640217fb: Establish Boundaries for Work and Rest to Maintain a Healthy Balance and Avoid Burnout — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/burnout-boundary-tracker.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (useful_with): https://vedokrok.com/knowledge/separate-urgency-from-importance-with-real-constraints
