Attention Item
What It Models
An attention occurrence presents a condition that needs someone, such as unposted batches or a gap in accountability.
Identity and Attributes
Kinds describe the condition; occurrences retain facts and timing; personal responses remain separate from lifecycle status.
Relationships
Providers own the business records. Responsibilities and Security supply current audience membership.
Invariants
Occurrence uniqueness, generation retention and response concurrency have different guarantees and are stated separately.
How It Is Stored and Shared
Attention owns declarations, occurrences, audiences, settings, responses and follow-up records. Provider functions enforce transactional writes; no custom fields are declared.
Open Design Questions
Reminder audience checks, delivery deduplication, the Notifications boundary and response races remain unresolved. Portal attention stays held.