閉 — Close DaySeal, archive, and contain.
Use 閉 to shut doors properly: publish closure statements, revoke access, collect final receipts, archive evidence, and stop old issues from reopening informally.
What Close favours
Create finality that can be proved.
Close supports completion records, offboarding, custody updates, restricted access, archive indexes, retention schedules, and formal acknowledgement that nothing remains open.
Publish closure statements, mark complete, and obtain receipts.
Revoke access, collect assets, and update custody records.
Index artefacts, record decisions, and set retention dates.
Fast decisions
Do / Avoid — 30-second cheat sheet
| Do on 閉 | Why | Avoid on 閉 | Better day |
|---|---|---|---|
| Issue closure memos and receipts | Creates finality and evidence. | Open new projects or pilots | 開 / 建 |
| Revoke access and collect devices or keys | Eliminates residual risk. | Renegotiation | 平 → 定 |
| Archive repositories and publish decision logs | Stops dead issues being re-litigated. | Public celebration or PR | 成 |
| Finalise reconciliation and handovers | Nothing remains dangling. | Terminations or teardown | 破 |
Execution
Business playbooks that seal and contain
- Summary and final asset links.
- Acceptance, metrics, and invoice status.
- Access owners, archive index, and retention period.
- Disable SSO, repositories, production consoles, and shared credentials.
- Collect hardware and IDs; record chain of custody.
- Close cards and settle final payroll or invoices.
- Use consistent filenames and searchable indexes.
- Store immutable PDF receipts.
- Apply retention by finance, legal, and operations class.
Quiet endings, firm boundaries
End the loop without performance.
“We’re closing this loop today. Items returned, access ended, and notes filed. If something is outstanding, state it plainly and we’ll resolve it—then we’re done.”
“Received {{items / payments}}. Marked complete. Thank you—wishing you steadiness.”
“I’m not reopening this topic. Future requests go through the agreed channel with context. Otherwise, no response.”
Stacking and sequences
Collect or break first. Seal now. Begin again later.
Collect funds and assets, then seal and archive.
Complete the teardown, then contain and document it.
After the public win, archive the proof and decision log.
Once the old cycle is sealed, frame or open the next one.
Patterns
Real examples
Archive the repository, lock the branch, disable CI tokens, and export the audit trail.
Issue the paid-in-full receipt, close the purchase order, and move records to storage.
Return keys, remove shared accounts, and box and label keepsakes.
Quick answers
Close Day FAQ
Is 閉 the same as 破?
No. 破 breaks the structure; 閉 seals and contains it. They are different tools.
Should I do PR on 閉?
Keep it minimal or private. Save amplification and celebration for 成 (Success).
What if new information appears?
Log it in the archive and schedule 平 or 定 to reopen the issue with structure. Do not derail Close Day.
Complete the cycle
Close something properly.
Your next move
Seal the loop before beginning another.
Check today’s Officer, choose one completed matter, and make its receipt, access state, archive index, custody, and retention unmistakably clear.