Manage personal responses to attention items

Purpose

People need to manage how outstanding conditions appear to them. Personal responses preserve the condition while recording their own handling of it.

How It Works

The person chooses an action on an item addressed to them. Acknowledgement records that they have seen it. Snoozing postpones its normal display until the chosen time. Ending a snooze brings it back sooner. Dismissal is available only for the classes that permit it. Required items retain stricter postponement bounds. Responses belong to the person rather than every recipient. Successful actions update personal state and create audit evidence. Closed occurrences reject further actions.

Relationships

Deliver relevant attention with a reason provides the visible occurrence a recipient acts on.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Required attention remains until its underlying condition ends.Personal actions stay independent and create an audit trail.
Surfaces: consoleapi
Intent sources: services-platform:docs/proposals/responsibilities-and-attention/16-decisions.md#D-06services-platform:docs/milestones/plans/PLAT-M15-plan.md#A5services-platform:docs/milestones/plans/PLAT-M15-plan.md#PLAT-M15-S06

Controls

22 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-002 TC-LOG-003 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`platform.attention.use`	api	tenant

Business Rules

7 rules, 7 to be proved before approval. A rule's product intent is derived from its origin: 7 confirmed by a product decision, the rest inheriting this capability's confirmed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Personal actions require an open occurrence addressed to the caller, with every action rejected after the occurrence closes. proved by `ATS-PFM-ELG-018-01`, `TST-PFM-ELG-408`	validation	service	test services-platform:modules/attention/tests/unit/rules.spec.js#refuses every action on an item that is no longer open
`02`must prove Confirmed	Acknowledgement marks the item seen and removes its unread contribution while keeping it on the list. proved by `ATS-PFM-ELG-017-18`, `ATS-PFM-ELG-018-02`, `ATS-PFM-ELG-018-07`, `ATS-PFM-ELG-018-10`, `TST-PFM-ELG-388`, `TST-PFM-ELG-396`	lifecycle	service	test services-platform:modules/attention/tests/integration/services/persistence/states.integration.spec.js#acknowledges an item and records attention.acknowledged against its definition
`03`must prove Confirmed	Required attention cannot be dismissed. origin: services-platform:docs/proposals/responsibilities-and-attention/16-decisions.md#D-06 proved by `ATS-PFM-ELG-018-03`, `TST-PFM-ELG-370`, `TST-PFM-ELG-388`, `TST-PFM-ELG-396`	policy	service	test services-platform:modules/attention/tests/integration/services/persistence/states.integration.spec.js#refuses dismissing a required item as not_dismissable, writing no trail
`04`must prove Confirmed	Required snoozes obey the kind’s duration and count bounds, defaulting to seven days and three uses; other classes allow repeated snoozes up to 90 days, always ending in the future. origin: services-platform:docs/proposals/responsibilities-and-attention/16-decisions.md#D-06 proved by `ATS-PFM-ELG-018-04`, `ATS-PFM-ELG-018-08`, `ATS-PFM-ELG-019-08`, `TST-PFM-ELG-388`, `TST-PFM-ELG-408`	validation	service	test services-platform:modules/attention/tests/unit/rules.spec.js#refuses a required item’s snooze once it has been snoozed its allowed number of times
`05`must prove Confirmed	Dismissal removes an advisory or opportunity from that person’s list, with a recurring advisory appearing only as a fresh occurrence. proved by `ATS-PFM-ELG-018-05`, `TST-PFM-ELG-388`, `TST-PFM-ELG-396`	lifecycle	service	test services-platform:modules/attention/tests/e2e/attention.e2e.spec.js#dismisses an advisory, which then leaves the caller’s list
`06`must prove Confirmed	Snoozed attention reappears at its end time or when the person explicitly ends the snooze. proved by `ATS-PFM-ELG-018-09`, `ATS-PFM-ELG-018-10`, `TST-PFM-ELG-396`	lifecycle	service	test react-console:acceptance/platform-attention/playwright/journeys/attention/RA-ACC-0103.spec.ts#RA-ACC-0103
`07`must prove Confirmed	Actions lock an existing personal state, advance its version and audit kind, occurrence and generation; snoozes additionally audit their count, while rejected actions create no trail. proved by `ATS-PFM-ELG-018-06`, `ATS-PFM-ELG-018-09`, `ATS-PFM-ELG-018-11`, `TST-PFM-ELG-396`	invariant	service	observed services-platform:modules/attention/services/persistence/states.ts:applyStateAction

Scenarios

Id	Given	When	Then	Provenance
`01`	Pat receives a required batch and separate advisory occurrences.	Pat attempts required dismissal and uses dismissal and snooze on separate advisories.	Required dismissal fails, optional dismissal hides its occurrence and the snoozed advisory returns at its end.	test react-console:acceptance/platform-attention/playwright/journeys/attention/RA-ACC-0103.spec.ts#RA-ACC-0103

Planning

Implementation

Manage personal responses to attention items ​

Purpose ​

How It Works ​

Relationships ​