Cognitive Biases · Growth Library
Check the Operating Context Before Reusing a Decision
Make changed conditions, constraints and unknowns visible before applying an old answer.
Try this
State the decision, note what changed since the comparable case, list the concrete constraints and stakeholders that affect execution, mark assumptions separately from verified facts, and choose a reversible next step or clarification when a missing condition could change the choice.
Check-in: What changed, which constraint matters now, what am I assuming rather than verifying, and what is the smallest next step that fits the current context?
Evidence: Practical guidance; no evidence-like claim is detected in the current source record.
Review note: The inherited article contained fabricated project outcomes, unsupported psychological framing, arbitrary timing and sample rules, health-adjacent examples and assumptions about other people's motives. The effective public record is narrowed to checking changed conditions, concrete constraints, stakeholders, verified facts and unknowns before choosing a reversible next step.
A solution that worked before can fail when the surrounding conditions change. Instead of treating context as background, make the conditions that affect execution explicit: what changed, who or what is constrained, which facts are known, and which assumption could still reverse the decision.
1. State what changed
Compare the current situation with the case you are using as a reference. Note changed timing, ownership, system state, customer need, workload, permissions, environment or other condition that could affect the decision.
2. Identify concrete constraints
List the constraints that limit what can actually be done. Use observable facts such as available access, required approval, device or system capability, deadline, dependency, language, format or staffing rather than guessing about character or motivation.
3. Separate facts from assumptions
Mark each important unknown that you are currently filling with an assumption. Ask which unknown could materially change the decision and whether it can be clarified before committing.
4. Choose a context-fit next step
When the context is sufficiently clear, choose the action that fits it. When an important condition is unresolved, prefer a reversible step, clarification or small probe rather than a large commitment built on an unverified assumption.
Questions to consider
Do I need to analyze another person's motives?
No. Prefer observable constraints, stated needs, permissions, deadlines, capabilities and system conditions. When motive matters but is unknown, ask or leave it marked as an assumption rather than inventing an explanation.
When is the old solution safe to reuse?
Reuse it when the conditions that made it work are still relevant and no changed constraint materially alters the choice. If a key condition is unknown, make the next step reversible or gather that information first.
What if the decision is high stakes?
Use the required domain process and qualified review. This context check can help expose assumptions, but it does not replace safety, legal, financial, medical or compliance procedures.
Maintenance record
Review history
Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.
2026-09-10 · reviewed · Brali claim cleanup agent Source: protocol-content-overrides-claim-cleanup-batch-9.json
Replace fabricated project outcomes, psychological mechanism claims, universal timing and sample rules, health and emotional examples and assumptions about other people's motives with a bounded operating-context check.
Browse the review ledger · Challenge or update this hack
Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.
Continue from here
Choose the next useful path.
Article versions
Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.
- Version 2025-10-06: first recorded publication in the migrated Brali corpus.
- Evidence review 2026-09-10: reviewed by Brali claim cleanup agent; evidence state is
practical.
Canonical source record · Evidence state: practical.