# Record the outcome and your contribution while the evidence is fresh

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

---

## Record the outcome and your contribution while the evidence is fresh

ID: MHC-D-RESEARCH-0647 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/record-the-outcome-and-your-contribution-while-the-evidence-is-fresh

Career evidence decays faster than the work did.

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

### Use when

- Months later, you remember the project but not what changed or which part was yours.

### Avoid when

- Do not claim confidential metrics, causal effects or sole ownership you cannot support.

### Explanation

At meaningful milestones, record the starting problem, your specific action, outcome, scale and safe verification source. Distinguish team result from personal contribution. Preserve numbers only when you can explain what they measure.

### Steps

1. A future case description can distinguish your contribution from the team's overall success.

### Example

'Reduced reconciliation from two manual passes to one by redesigning the validation step' is captured before the project artifacts disappear.

### Check

A future case description can distinguish your contribution from the team's overall success.

### Limits

- Do not claim confidential metrics, causal effects or sole ownership you cannot support.

### Evidence and sources

- supports: OECD's 2026 brief on skill use emphasizes examining how skills are actually used at work, not only whether workers possess them. — RS-01E7EE7F8CEAE807. Skill-use frequency is not the same as proficiency or labour-market value. (Abstract)
- RS-01E7EE7F8CEAE807: Putting skills to work — https://www.oecd.org/en/publications/putting-skills-to-work_84449b02-en.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/attach-evidence-to-every-skill-you-want-others-to-believe
