# Analysis Scope

Define project-specific heuristics for the inventory & analysis step.

**Default (absent/empty):** Use standard heuristics. Every count is
read ROLLED UP for an area — its own actions plus the actions of the
projects filed under it — because carving work into a child project
must not make the area look emptier or quieter than it is:
- Stale: 14+ days since last completion with open actions (weigh by
  kind — a quiet area is a weaker signal than a stalled project; an
  area whose child project closed work this week is not stale at all)
- Mega-container: 10+ open actions
- Duplicate: >70% text overlap between actions in the same container
- Finishable project: `kind='project'` with 0 open actions (an area
  never completes, so it is never a completion candidate; and a project
  holds no child containers, so its direct count is the whole picture)

## Customization examples

```markdown
# Exclude someday containers from staleness detection
exclude_from_stale: status = 'someday'

# Lower the mega-container threshold for this team
mega_container_threshold: 7

# These areas are intentionally long-running — don't flag as stale
always_skip:
  - prj:abc12345  # ongoing maintenance
  - prj:def67890  # quarterly review
```