執 — Hold DayEnforce, execute, and make it stick.
Use 執 to apply agreed rules, run proven playbooks, collect sign-offs, and lock compliance. This is execution—not brainstorming, renegotiation, or demolition.
What Hold favours
Make yesterday’s decision operational.
Hold is the Officer of disciplined follow-through. It supports consistent execution, quality gates, compliance checks, acceptance testing, and boundaries applied exactly as agreed.
Enforcement
Apply agreed rules, boundaries, and SOPs with calm precision.
Execution
Run the work exactly as written—without scope drift or improvised exceptions.
Certification
Complete acceptance tests, compliance reviews, sign-offs, and evidence checks.
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 執 | Why | Avoid on 執 | Better day |
|---|---|---|---|
| Run SOPs, checklists, and QA gates | Precision and consistency compound. | Brainstorming or discovery sessions | 平 / 建 |
| Collect sign-offs and enforce acceptance criteria | Closes loopholes and prevents rework. | Public launches or PR spikes | 開 / 成 |
| Conduct compliance and audit runs | Locks standards and reduces operational risk. | Terminations or teardowns | 破 · Break |
| Escalate non-compliance calmly | Signals consequence without unnecessary drama. | Price re-anchoring or renegotiation | 平 → 定 |
Execution
Business playbooks for enforcement without noise
Acceptance Test and Sign-off
- Publish the Done Definition: scope, tests, and evidence links.
- Run the checklist and obtain written sign-off when every criterion passes.
SOP Rollout
- Keep the SOP to one page: inputs → steps → owner → SLA → output.
- Spot-check three random cases.
- Publish the result so the standard remains visible.
Compliance Ladder
- Nudge: point to the exact rule and missed step.
- Warning: state the next consequence clearly.
- Consequence: remove privileges or gate access until compliance returns.
Boundaries that hold
Keep the agreement steady in real life
Enforce what was agreed
“We agreed on {{boundary}}. I’m keeping it. If it’s crossed, I’ll pause and we’ll reschedule on terms we both can hold.”
Maintain the basics
Check bedtime, spending caps, respect windows, and other shared routines. Document the baseline and defer renegotiation to 平 or 定.
State the consequence calmly
“This is the second time we skipped the rule we set. Let’s keep it now. If it slips again, we’ll change access until we’re steady.”
Enforcement ladder
Escalate in stages, not in anger.
“Reminder: SOP-12 applies here. Please follow step 3 before handoff.”
“This is the second miss. The next miss triggers manager review.”
Gate merges, pause access, or remove privileges until the agreed standard is restored.
Stacking and sequences
Lock first. Enforce now. Ship or reset next.
Sign and confirm on Settle; enforce the agreed terms on Hold.
After clean execution, ship the result on Success or collect on Receive.
Persistent non-compliance or a failed structure may require a teardown on Break.
If risk is unclear, run a Danger Day review before enforcing hard.
Patterns
Real examples
Protect the Standard
Enforce branch protection and block merges until required tests pass.
Gate the Stage Change
Require every mandatory CRM field before an opportunity can move forward.
Keep Quiet Hours
If the boundary is broken, suspend the conversation and resume it tomorrow.
Quick answers
Hold Day FAQ
Can I launch on 執?
You can, but it is not the natural advantage of the day. Hold is for internal execution; use 開 (Open) or 成 (Success) for the launch.
Is 執 the same as 定?
No. 定 (Settle) decides and locks the arrangement; 執 (Hold) enforces and executes what has already been locked.
What if someone resists enforcement?
Use the ladder: nudge → warning → consequence. If the underlying structure is unsound rather than merely ignored, schedule 破 (Break).
Continue the cycle
Enforce cleanly. Know when to maintain or break.
定 — Settle
Decide, sign, and lock the agreement.
Explore Settle → Next破 — Break
End what no longer deserves to hold.
Explore Break → 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
Make the agreement visible in action.
Check today’s Officer, identify the rule or process that needs consistent follow-through, and enforce it with clear evidence, calm escalation, and no unnecessary noise.