破 — Break DayEnd decisively. Control the damage.
Use 破 to terminate failing arrangements, dismantle unsafe structures, revoke access, or trigger legal escalation. This is controlled destruction—precise, documented, and complete.
What Break favours
Remove the structure that keeps producing damage.
Break is the Officer of decisive separation. It supports shutdowns, terminations, access revocation, evidence preservation, and the removal of components that cannot be repaired safely.
Teardown
Remove failing components, sunset products, and pull the plug completely.
Termination
End contracts, revoke access, and decommission assets with documented rationale.
Litigation readiness
Preserve evidence, send precise notices, and enforce rights without editorialising.
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 破 | Why | Avoid on 破 | Better day |
|---|---|---|---|
| Terminate a vendor or employee cleanly | Decisive closure reduces continued loss. | Public launches or PR spikes | 開 / 成 |
| Sunset a product or decommission infrastructure | Stops ongoing risk and cost. | Price anchoring or contract tweaks | 平 / 定 |
| Issue notice and preserve evidence | Positions you for legal leverage. | “Win-win” diplomacy | 平 · Level |
| Reorganise to remove a rotten layer | Removes a bottleneck and the fear around it. | Collections and reconciliations | 收 · Receive |
Execution
Business playbooks for clean cuts with low noise
Vendor Termination
- Collect breach or underperformance evidence.
- Export data and prepare the handover.
- Disable risky access before sending notice through the contractual channel.
Product Sunset
- Announce internally and freeze new users.
- Set the final date and migrate the data.
- Kill billing hooks, archive repositories, and document the rationale to prevent backsliding.
Litigation Readiness
- Place a legal hold on email, chat, logs, and code history.
- Send a narrow demand or notice.
- Separate facts from emotion and preserve the original records.
Hard boundary, minimal drama
End the arrangement without feeding the conflict.
Name what ends
“This pattern breaks trust. I’m ending {{specific behaviour / arrangement}} now. If conditions change and we both agree later, we can reassess.”
Close the chapter
“I’m closing this chapter. No further messages on this topic. Wishing you steadiness.”
Separate and document
Separate physically or financially where needed, preserve records, and keep statements short. Move remaining logistics to 定 (Settle).
Control the blast radius
A hard cut still needs careful containment.
Secure emails, logs, files, agreements, and other evidence before access changes.
Disable risky credentials, permissions, payment paths, and shared systems.
Move critical data, customers, ownership, and operations to a safe baseline.
State the decision, effective date, transition path, and nothing unnecessary.
Stacking and sequences
Assess first. Break cleanly. Seal and rebuild.
Assess the exposure on Danger, then execute the necessary cut on Break.
After teardown, seal, archive, and close the remaining pathways.
Normalise the new baseline and lock replacement terms after the cut.
Stay factual now; build the public narrative later on Open or Success.
Patterns
Real examples
Remove the Unsafe Vendor
Terminate a non-compliant supplier and migrate operations to a safe baseline.
Cut the Toxic Layer
Remove a damaging management layer, redistribute owners, and publish the new structure.
Complete the Separation
Block contact, return property, and close shared accounts or access paths.
Quick answers
Break Day FAQ
Is 破 always negative?
No. It is pruning with force. When something is structurally wrong, Break Day can prevent greater cost and future damage.
What about collateral damage?
Control the blast radius: revoke access, preserve evidence, stage migrations, and communicate only what is necessary.
Can I launch after a teardown?
Yes—once the dust settles and the new baseline is stable. Use 開 (Open) or 成 (Success) for the later launch.
Continue the cycle
Execute the cut. Know what follows.
執 — Hold
Enforce and execute what was agreed.
Explore Hold → Next危 — Danger
Expose risk and test the weak points.
Explore Danger → 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
End what keeps producing damage.
Check today’s Officer, identify the failing structure that needs a decisive end, and prepare the evidence, access controls, migration, and communication before making the cut.