12 Day Officers · 危 (Danger)
危 — Danger Day: Risk Mapping, Stress Tests, Tripwire Checks
Use 危 (Danger) to expose weak points before they cost you. Today is for probes, audits, and contingency building—not big launches.
Clarity
What “Danger” favors
●Risk discovery
Red-team reviews, due diligence, scenario planning that pressures weak spots.
●Stress testing
Load tests, chaos drills, DR runbooks, pen-tests to validate resilience.
●Tripwires & monitoring
Alerts, SLOs, early-warning dashboards. Avoid irreversible commitments today.
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 危 | Why | Avoid on 危 | Better Day |
|---|---|---|---|
| Run red-team / premortems | Find failure modes while stakes are low | Big launches / PR spikes | 开 (Open) / 成 (Success) |
| Chaos/DR drills; load tests | Surface fragility; validate runbooks | Terminations / teardowns | 破 (Break) |
| Due diligence & compliance audits | Reduce legal/financial exposure | Final contract locking | 定 (Settle) |
| Set tripwires & monitoring | Early detection beats firefighting | Price re-anchoring & negotiations | 平 (Level) |
Execution
Business playbooks (probe first, act second)
1) Premortem workshop (45 min)
- Prompt: “It’s 90 days later and the project failed. What happened?”
- Collect top 5 failure modes; assign owner → mitigation → trigger.
2) Vendor / deal diligence
- Checklist: financial health, IP/assignment, security posture, data residency, exit terms.
- Flag reds; push final decision to 定.
3) Chaos/DR mini-drill
- Kill a non-critical dependency for 15 minutes. Measure MTTD/MTTR; fix runbook gaps.
- Record lessons; schedule enforcement on 执.
4) Risk-probe email (short)
Quick probe on {{project}}: list the top three risks you see and the earliest warning signals. I’ll consolidate and set owners by tomorrow.
Diagnostic
Relationship plays (calm, diagnostic)
1) Map the risks without blame
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.
2) Safety & money checks
- Review boundaries, backup plans, and emergency contacts.
- Audit shared accounts/subscriptions; set alerts for unusual activity.
3) Decision deferral
Today I’m mapping risks, not locking decisions. We’ll confirm terms on a 定 day.
Sequencing
Timing tactics (stacking & sequences)
- Danger → Settle: discover risks today; lock mitigations tomorrow.
- Danger → Hold: after findings, enforce SOPs and checks.
- Danger → Break: if you uncover rot, schedule teardown on 破.
- Danger → Success / Open: pass tests first; then ship or announce.
Patterns
Real examples
- Security: run a targeted pen-test on auth; fix high sev; re-test.
- Finance: stress-test cashflow; set burn tripwires; draft contingency.
- Personal: discuss trigger points; agree “pause & reset” protocol.
Answers
Quick FAQ
Is 危 only for negatives?
No. It’s for information. You’re buying clarity. What you do next depends on findings.
What if tests reveal nothing?
Document “no findings,” improve monitoring, and proceed. Confidence is also data.
Launch anyway?
If optics are critical, wait for 开 / 成 after you fix what 危 surfaced.
