This commit is contained in:
@@ -0,0 +1,22 @@
|
||||
# GEN2-CAPABILITY-001 notification receiver classification
|
||||
|
||||
## Evidence
|
||||
|
||||
The notification target is implemented by this repository's
|
||||
`cmd/notification-receiver` runtime. It exposes the bounded delivery and
|
||||
receipt protocol used by `adapters/notificationexecutor`; it is therefore an
|
||||
Assistant ReleaseComponent, not a shared external service.
|
||||
|
||||
The current stable receiver persists idempotent receipts and is configured
|
||||
with separate read/write secrets. Candidate acceptance must not reuse its
|
||||
runtime instance, secret mount, or stable Capability ACTIVE binding.
|
||||
|
||||
## Candidate decision
|
||||
|
||||
The candidate ReleaseSet requires its own `notification-receiver-candidate`
|
||||
instance in explicit shadow mode. That instance accepts only synthetic,
|
||||
task-scoped delivery traffic and returns a shadow receipt. It has no
|
||||
production delivery credential or production destination route.
|
||||
|
||||
`SHADOW_CAPTURED` proves only receipt capture. It is not delivery, a sent
|
||||
notification, or a verified World outcome.
|
||||
Reference in New Issue
Block a user