危 — Danger DayProbe first. Act with evidence.
Use 危 to expose weak points before they cost you. Run premortems, audits, diligence, stress tests, and contingency drills—then decide what to lock, enforce, break, or launch on the appropriate day.
What Danger favours
Find the failure mode while the stakes are still low.
Danger is the Officer of diagnostic pressure. It supports red-team reviews, scenario planning, due diligence, load tests, monitoring, and the early-warning systems that make later decisions safer.
Risk discovery
Run red-team reviews and premortems that pressure the weak points.
Stress testing
Use load tests, chaos drills, disaster-recovery rehearsals, and penetration tests.
Tripwires and monitoring
Install alerts, SLOs, thresholds, and early-warning dashboards.
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 危 | Why | Avoid on 危 | Better day |
|---|---|---|---|
| Run red-team reviews and premortems | Find failure modes while the stakes are low. | Big launches or PR spikes | 開 / 成 |
| Conduct chaos, DR, and load tests | Surface fragility and validate the runbook. | Terminations or teardowns | 破 · Break |
| Perform due diligence and compliance audits | Reduce legal and financial exposure. | Final contract locking | 定 · Settle |
| Set tripwires and monitoring | Early detection beats firefighting. | Price re-anchoring and negotiation | 平 · Level |
Execution
Business playbooks that probe before acting
45-Minute Premortem
- Prompt: “It is 90 days later and the project failed. What happened?”
- Collect the five most plausible failure modes.
- Assign an owner, mitigation, and trigger to each.
Vendor and Deal Diligence
- Check financial health, IP assignment, security posture, data residency, and exit terms.
- Flag every red item.
- Push the final decision to 定 (Settle).
Chaos / DR Mini-Drill
- Disable one non-critical dependency for 15 minutes.
- Measure detection and recovery time.
- Fix runbook gaps, then schedule enforcement on 執 (Hold).
Risk-Probe Email
Calm and diagnostic
Name the risks without assigning blame.
Identify failure points
“Let’s list the top three points where this tends to go wrong and what early signs we’ll watch for. Then we’ll agree what we do at each signal.”
Review safety and money
Check boundaries, backup plans, emergency contacts, shared accounts, subscriptions, and alerts for unusual activity.
Do not lock prematurely
“Today I’m mapping risks, not locking decisions. We’ll confirm terms on a 定 day.”
Risk map
Every material risk needs four fields.
What could realistically go wrong—not a vague fear, but a specific breakdown.
The observable metric, event, or behaviour that appears before the failure.
The preventive step that reduces likelihood, exposure, or recovery time.
Who acts, and exactly when the contingency becomes active.
Stacking and sequences
Let the finding determine the next Officer.
Discover the risks today, then lock the mitigations and final terms on Settle.
Translate findings into mandatory SOPs, gates, and checks on Hold.
If the probe exposes structural rot, schedule the teardown on Break.
Pass the tests first, then ship or announce on Success or Open.
Patterns
Real examples
Probe Authentication
Run a targeted penetration test, fix high-severity issues, and retest.
Stress-Test Cash Flow
Model downside conditions, set burn tripwires, and draft the contingency plan.
Agree on a Reset Protocol
Identify trigger points and decide what “pause and reset” means before conflict escalates.
Quick answers
Danger Day FAQ
Is 危 only for negatives?
No. Danger Day is for information. You are buying clarity; what you do next depends on what the probe reveals.
What if tests reveal nothing?
Document “no findings,” improve the monitoring, and proceed. Confidence earned through a credible test is valuable data.
Should I launch anyway?
If optics matter, wait for 開 (Open) or 成 (Success) after fixing what Danger Day surfaced.
Continue the cycle
Run one probe that actually matters.
破 — Break
Terminate and dismantle decisively.
Explore Break → Next成 — Success
Complete, deliver, and make the win visible.
Explore Success → All TwelveOfficers Hub
Browse the complete timing cycle.
Return to the Hub → Deep LearningDefinitive Guide
Study the rules, sequence, and practical method.
Read the Guide →Your next move
Expose the weak point before committing.
Check today’s Officer, choose one meaningful risk probe, and record the failure mode, early signal, mitigation, trigger, and owner before deciding what follows.