What problem does it solve? In a monorepo with multiple workstreams, planning entities (epics, ADRs, gaps, decisions, contracts) need a consistent grouping tag, and that tag must match where the actual code work landed. Without enforcement, area labels drift from reality and filtered status or roadmap views become unreliable. ## Core Features & Use Cases - Area assignment at creation: Tag entities explicitly with --area, or let aiwf derive the area from a --path-hint matched against declared paths: globs; ambiguous or unmatched hints never guess. - Closed member set with enforcement: Only declared areas.members plus the reserved global sentinel are valid; areas.required: true makes tagging mandatory and aiwf check raises blocking findings for untagged entities. - Lifecycle management: Fix tags with aiwf set-area, rename members repo-wide with aiwf rename-area, and acknowledge legitimate cross-cutting work with aiwf acknowledge mistag. - Use Case: You are about to fix a login bug in projects/app-a/auth/login.go but do not know the area name — pass the file path as --path-hint to aiwf add gap and the kernel derives area: app-a automatically. ## Quick Start Ask the AI to create an aiwf gap for a bug in a specific file using a path hint so the correct area is derived automatically.