# Keep one inbox for unassigned work

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Keep one inbox for unassigned work

ID: MHC-D-BRALI-0185 · Version: 0.1.0 · Kind: pattern
Source: https://vedokrok.com/knowledge/keep-one-inbox-for-unassigned-work

Loose tasks become expensive when each one invents its own storage place. Keep one small inbox for work that has no project yet, then review it often enough that the inbox remains a capture point rather than a second backlog nobody trusts.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- A useful task or idea appears before you know which project, owner or schedule it belongs to.

### Avoid when

- The inbox is temporary routing, not a reward system, priority engine or permanent project category. Do not store secrets or sensitive personal material merely for convenience.

### Explanation

Loose tasks become expensive when each one invents its own storage place. Keep one small inbox for work that has no project yet, then review it often enough that the inbox remains a capture point rather than a second backlog nobody trusts.

### Steps

1. Capture the item in one agreed inbox with enough context to recognize it later.
2. During review, either assign it to a real project or owner, schedule it, do it, or delete it.
3. If the inbox keeps growing, fix the review or ownership problem instead of adding more labels.

### Recognition

Loose tasks become expensive when each one invents its own storage place. Keep one small inbox for work that has no project yet, then review it often enough that the inbox remains a capture point rather than a second backlog nobody trusts.

### Example

A note such as ‘check export failures from Tuesday run’ belongs in the inbox until it is assigned. ‘Improve everything’ does not become useful merely because it has a checkbox.

### Check

Every reviewed inbox item has a clearer home, owner, next action or explicit deletion decision.

### Limits

- The inbox is temporary routing, not a reward system, priority engine or permanent project category. Do not store secrets or sensitive personal material merely for convenience.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-f7ab5d0d70918ae38c61. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/unassigned-task-inbox.json)
- FP-BRALI-SRC-f7ab5d0d70918ae38c61: This Container Is Your Personal Hub for Tasks That Don’t Belong to Any Specific) — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/unassigned-task-inbox.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
