12 Day Officers · 执 (Hold)
执 — Hold Day: Enforce, Execute, and Make It Stick
Use 执 (Hold) to enforce decisions, run playbooks, and lock compliance. This is execution — not brainstorming, not demolition.
Clarity
What “Hold” favors
●Enforcement
Apply agreed rules, boundaries, and SOPs with calm precision.
●Execution
Run the work exactly as written. No scope drift; no improvisation.
●Certification
Sign-offs, acceptance tests, compliance checks. Avoid open exploration (平 / 建) or destructive resets (破).
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 执 | Why | Avoid on 执 | Better Day |
|---|---|---|---|
| Run SOPs, checklists, QA gates | Precision and consistency compound | Brainstorming / discovery sessions | 平 (Level) / 建 (Establish) |
| Collect sign-offs; enforce acceptance criteria | Closes loopholes; prevents rework | Public launches / PR spikes | 开 (Open) / 成 (Success) |
| Compliance & audit runs | Locks standards; reduces risk | Terminations / teardowns | 破 (Break) |
| Escalate non-compliance calmly | Signal consequence without drama | Price re-anchoring / renegotiation | 平 → 定 |
Execution
Business playbooks (enforcement without noise)
1) Acceptance test & sign-off
- Publish the Done Definition: scope, tests, evidence links.
- Run the checklist. If criteria pass, obtain written sign-off.
Per the acceptance criteria for {{deliverable}}, all checks passed (links above). Please reply “Approved” so we can proceed to {{next step}}.
2) SOP rollout
- One-page SOP. Inputs → Steps → Owner → SLA → Output. No essays.
- Spot-check 3 random cases; publish results.
3) Compliance nudge → consequence (ladder)
- Nudge: “Reminder: SOP-12 applies here. Please follow step 3 before handoff.”
- Warning: “Second miss. Next miss triggers manager review.”
- Consequence: remove privileges / gate merges until compliance.
Boundaries
Relationship plays (boundaries that hold)
1) Boundary enforcement (script)
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.
2) Routine compliance
- Check the basics: bedtime, spending caps, respect windows.
- Document the routine; defer renegotiation to 平 / 定.
3) Calm escalation
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.
Sequencing
Timing tactics (stacking & sequences)
- Settle → Hold: signatures yesterday, enforcement today.
- Hold → Success / Receive: after clean execution, ship or collect.
- Hold → Break (if needed): persistent non-compliance → teardown on 破.
- Hold ↔ Danger: if risk is unclear, run 危 checks before enforcing hard.
Patterns
Real examples
- Engineering: enforce branch protection; block merges without tests.
- Sales Ops: require CRM fields before opportunity stage change.
- Personal: keep quiet hours; if broken, suspend the chat until tomorrow.
Answers
Quick FAQ
Can I launch on 执?
You can, but it’s not the edge. 执 is for internal execution. Launch on 开 / 成.
Is 执 the same as 定?
No. 定 decides and locks; 执 enforces and executes what’s locked.
What if someone resists enforcement?
Use the ladder: nudge → warning → consequence. If structure is rotten, schedule 破.
