12 Day Officers · 闭 (Close)
闭 — Close Day: Seal, Archive, Audit
Use 闭 (Close) to shut doors properly: seal decisions, revoke access, archive evidence, finalize receipts. No new starts. No drama.
Clarity
What “Close” favors
●Sealing
Publish closure statements, mark complete, obtain receipts and acknowledgements.
●Offboarding
Revoke access, collect assets, confirm returns, and update custody records.
●Archiving
Organize artifacts, index decisions, set retention. Avoid launches or teardowns today.
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 闭 | Why | Avoid on 闭 | Better Day |
|---|---|---|---|
| Issue closure memos & receipts | Creates finality and evidence | Open new projects / pilots | 开 (Open) / 建 (Establish) |
| Revoke access, collect devices/keys | Eliminates residual risk/leakage | Renegotiations | 平 (Level) → 定 (Settle) |
| Archive repos; publish decision log | Prevents re-litigating dead issues | Public celebrations/PR spikes | 成 (Success) |
| Finalize reconciliation & handovers | Nothing dangles; clean books | Terminations/teardowns | 破 (Break) |
Execution
Business playbooks (seal and contain)
1) Closure packet (one page)
- Summary: what was delivered; links to final assets.
- Evidence: acceptance/sign-offs, metrics snapshot, invoice status.
- Access: who retains what; revocations complete.
- Archive: index link; retention period; owner.
Closing {{project}} today. Assets & acceptance attached; access now limited to {{names}}. Archive index: {{link}}. If anything’s missing, reply by {{date}}.
2) Offboarding protocol (vendor/employee)
- Disable SSO, repo, prod consoles; rotate shared creds.
- Collect hardware/IDs; wipe devices; record chain of custody.
- Close expense cards; settle final payroll/invoices.
3) Audit & archive
- Name patterns:
YYYY-MM-Project-DecisionLog.pdf,Closure-Receipt-{{counter}}.pdf. - Retention: set policy per class (finance, legal, ops). Put dates on calendar.
Tip: store immutable receipts (PDF) + searchable index (CSV/MD). Keep access scoped by least privilege.
Boundaries
Relationship plays (quiet endings, firm boundaries)
1) Clean closure (script)
We’re closing this loop today. Items returned, access ended, and notes filed. If something’s outstanding, state it plainly and we’ll resolve it—then we’re done.
2) Receipt + thanks (non-performative)
Received {{items/payments}}. Marked complete. Thank you—wishing you steadiness.
3) Boundary seal
I’m not reopening this topic. Future requests go through the agreed channel with context. Otherwise, no response.
Sequencing
Timing tactics (stacking & sequences)
- Receive → Close: collect funds/assets, then seal and archive.
- Break → Close: teardown yesterday; containment and receipts today.
- Success → Close: after public wins, archive and record the decision log.
- Close → Establish/Open: once sealed, start the next cycle tomorrow.
Patterns
Real examples
- Ops: archive repo; lock branch; disable CI tokens; export audit trail.
- Finance: send “paid in full” receipt; close PO; move to storage class.
- Personal: return keys; remove shared accounts; box and label keepsakes.
Answers
Quick FAQ
Is 闭 the same as 破?
No. 破 breaks structure; 闭 seals and contains. Different blades.
PR on 闭?
Keep it minimal or private. Save amplification for 成.
What if new info appears?
Log it in the archive; schedule 平 / 定 to reopen with structure. Don’t derail 闭.
