12 Day Officers · 破 (Break)
破 — Break Day: Terminations, Hard Resets, Litigation
Use 破 (Break) when you need to end something decisively: terminate vendors, dismantle failed structures, or trigger legal escalation. This is controlled destruction.
Clarity
What “Break” favors
●Teardown
Remove failing components, sunset products, pull the plug calmly and completely.
●Termination
End contracts, revoke access, decommission assets with documented rationale.
●Litigation readiness
Preserve evidence, send notices, enforce rights. Avoid launches and fragile talks.
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 破 | Why | Avoid on 破 | Better Day |
|---|---|---|---|
| Terminate vendor/employee cleanly | Decisive closure reduces bleed | Public launches / PR spikes | 开 (Open) / 成 (Success) |
| Sunset product / decommission infra | Stops ongoing risk and cost | Price anchoring / contract tweaks | 平 (Level) / 定 (Settle) |
| Issue notice / preserve evidence | Positions you for legal leverage | “Win-win” diplomacy | 平 (Level) |
| Reorg to remove a rotten layer | Removes bottleneck and fear | Collections / reconciliations | 收 (Receive) |
Execution
Business playbooks (clean cuts, low noise)
1) Termination protocol (vendor)
- Pre-work: collect breach/underperformance evidence; export data; ready handover.
- Disable risky access first; then send notice through the contractual channel.
Per Section {{clause}}, we’re terminating effective {{date}} due to {{cause}}. Access is revoked; deliverables and transition steps are listed in the attached schedule.
2) Product sunset / infra teardown
- Announce internally; freeze new users; set final date; migrate data.
- Kill billing hooks; archive repos; document rationale to prevent backslide.
3) Litigation readiness (if required)
- Legal hold: preserve emails, chats, logs, code history.
- Send a precise demand/notice; avoid editorializing.
Boundaries
Relationship plays (hard boundary, minimal drama)
1) Controlled confrontation (script)
This pattern breaks trust. I’m ending {{specific behavior/arrangement}} now. If conditions change and we both agree later, we can reassess.
2) Exit script (clean)
I’m closing this chapter. No further messages on this topic. Wishing you steadiness.
3) Safety first
- Separate physically/financially where needed. Document everything. Keep statements short.
- Do not negotiate in the heat; move any logistics to 定.
Sequencing
Timing tactics (stacking & sequences)
- Danger → Break: assess risk on 危, then act on 破.
- Break → Close: after teardown, seal and archive on 闭.
- Break → Level / Settle: normalize and lock new terms the next days.
- PR containment: if optics matter, keep statements factual; push narrative building to 开 / 成.
Patterns
Real examples
- Ops: remove a non-compliant vendor; migrate to a safe baseline.
- Org: cut a toxic middle layer; redistribute owners; publish the new chart.
- Personal: block contact, return items, close shared accounts.
Answers
Quick FAQ
Is 破 always negative?
No. It’s pruning with force. If something is structurally wrong, 破 saves time and future damage.
What about collateral damage?
Control the blast radius: revoke access, preserve evidence, stage migrations, communicate minimally.
Can I launch after a teardown?
Yes—when the dust settles. Use 开 / 成 once the new baseline is stable.
