---
id: ADR-MBR-MEM-017
title: Resolve Enabled Attention With Its Source Write
product_area: membership
module: memberships
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Expiry sweeps publish when enabled, and source writes resolve enabled
  attention transactionally so a resolution refusal aborts the write.
constrains:
  - SVC-MBR-MEM-memberships
  - STATE-MBR-MEM-011
  - WF-MBR-MEM-020
origin: >-
  Platform's responsibilities and attention proposal (approved 2026-10-18) and
  the attention provider contract, as Membership's attention account records
  them
alternatives:
  - option: Resolve alerts asynchronously after the write
    why_not: >-
      Post-commit resolution could leave staff acting on an alert after its
      condition ended.
  - option: Publishing on by default
    why_not: >-
      Default-on publication would require every deployment to provide working
      attention storage.
consequences:
  - Enabled source resolution shares the business commit boundary.
  - The default-off switch suppresses publication and resolution.
  - >-
    Automated proof of an attention refusal aborting the business write remains
    missing.
supersedes: []
evidence:
  - >-
    services-membership at 5994c270:
    modules/memberships/services/attention/expiring-memberships.ts;
    aws/membership.names.ts (attention publishing context); lib/attention.ts;
    docs/attention.md
---

# Resolve Enabled Attention With Its Source Write

## Context

Renewal attention becomes true through time and becomes obsolete when coverage changes. The current integration guards publication behind an environment switch.

## Decision

Expiry sweeps publish when enabled, and source writes resolve enabled attention transactionally so a resolution refusal aborts the write.

## Alternatives Considered

Resolve alerts asynchronously after the write: Post-commit resolution could leave staff acting on an alert after its condition ended.

Publishing on by default: Default-on publication would require every deployment to provide working attention storage.

## Consequences

Enabled source resolution shares the business commit boundary. The default-off switch suppresses publication and resolution. Automated proof of an attention refusal aborting the business write remains missing.