para-reviewlisted

# PARA Review > "Your system stays useful only if you tend it. Review converts a pile into a garden — > completed projects move to the archive, and attention returns to what is alive." — adapted from > Tiago Forte, fortelabs.com/blog/para ## Core Philosophy A PARA system degrades without maintenance: finished projects linger in Projects, the inbox fills, Resources accumulate that no longer match any living interest, and items drift into the wrong category. This skill is the counterweight. It runs in three composable modes — **audit** (find drift), **ritual** (the weekly review), and **summarize** (digest new/changed material) — and ends with **safe archiving** of what is demonstrably done or inactive. Review is read-mostly and proposal-first. It surfaces findings and a proposed move-list, then acts only on what the user (or the ritual's rules) confirms. The bias is the inverse of `para-file`: filing is fast and forgiving; review is careful, because archiving and bulk moves touch many items at once and must never lose data. **Non-Negotiable Constraints:** 1. PROPOSE BEFORE MOVING — every audit/archive action is presented as a reviewable list first; bulk moves require confirmation. No silent reorganization. 2. ARCHIVE, NEVER DELETE — completed/inactive items move to Archive (preserving original category); deletion is never performed by this skill. 3. ACTIONABILITY IS THE RULER — judge placement by the same P→A→R→Archive actionability order `para-file` uses; flag m