Publish and resolve attention at source
What It Does
A provider’s business transaction publishes, refreshes or resolves its own attention condition; its sweep repairs unconfirmed occurrences.
The Flow
Publish the declared kind, key, about record, provider scope chain, audiences, typed facts, timing and destination under the owning service. Lock the key, refresh the existing occurrence or create a new one, preserve escalation audiences and compute rank and effective surfaces. Resolve the key with a short outcome when its condition clears. Republish conditions that still hold, resolve older unconfirmed items within the sweep scope and record completion.
When Something Fails
Foreign ownership, missing or retired kinds and invalid facts or audiences raise. The failed attention write rolls back with the provider change. A database error aborts the caller transaction. No partial item update commits. A refused resolve aborts its transaction. No inconsistent source commit is introduced by a successful transactional resolve. Provider sweep failure handling determines retry. Conditions cleared without a source write can remain open until a successful sweep.
Open Design Questions
Provider integrations can be gated off by their own approved release switches; this contract does not establish a deployment state outside its source boundary.