Permanent Notification and Communication Identifiers

Allocation precedes authoring. Reserved identifiers remain assigned when an artifact is superseded, and imported acceptance identities appear only as predecessor references. Platform actor allocation belongs to the shared product-area registry.

Series Reservations

Series	Allocated	Next free
MOD-PFM-NOT	Module charter	—
FEAT-PFM-NOT-	01 through 07	08
CON-PFM-NOT-	001 through 006, including three superseded facet records	007
ACT-PFM-	001 through 005, shared across Platform	006
CAP-PFM-NOT-	001 through 020	021
JNY-PFM-NOT-	001 through 006	007
ATS-PFM-NOT-	001 through 020	021
FND-PFM-NOT-	001 through 052; 053 to 061 (control gaps)	062
OQ-PFM-NOT-	001 through 009	010
DOM-PFM-NOT-	003, 004 and 005 (001, 002 and 006 are not allocated: their concepts are superseded facet records)	—
STATE-PFM-NOT-	001 through 015	016
WF-PFM-NOT-	001 through 016	017
SVC-PFM-NOT-	notifications, communications	—
SCR-PFM-NOT-	001 through 006	007
ADR-PFM-NOT-	001 through 020	021
IOP-PFM-NOT-	none: the module asks no model a question	001

Artifact Reservations

Id	Allocated subject
CAP-PFM-NOT-001	Declare application notification types
CAP-PFM-NOT-002	Publish a notification with its business change
CAP-PFM-NOT-003	Select eligible notification recipients
CAP-PFM-NOT-004	Render recipient-specific notification content
CAP-PFM-NOT-005	Combine repeated events into one notice
CAP-PFM-NOT-006	Remove notices that have become stale
CAP-PFM-NOT-007	Route and send notification deliveries
CAP-PFM-NOT-008	Recover notification processing and retain its history
CAP-PFM-NOT-009	Manage a personal notification inbox
CAP-PFM-NOT-010	Explain notification selection and delivery
CAP-PFM-NOT-011	Review workspace notification activity
CAP-PFM-NOT-012	Investigate and retry notifications from HQ
CAP-PFM-NOT-013	Send operational alerts to Rhythm HQ
CAP-PFM-NOT-014	Announce explicit responsibility changes
CAP-PFM-NOT-015	Store notification preferences and channel configuration
CAP-PFM-NOT-016	Author and publish association e-mail content
CAP-PFM-NOT-017	Submit association communication requests
CAP-PFM-NOT-018	Send association e-mail with retry and capacity control
CAP-PFM-NOT-019	Inspect communication outcomes and provider feedback
CAP-PFM-NOT-020	Apply recipient protection and sender verification
CON-PFM-NOT-001	Notification Type
CON-PFM-NOT-002	Notification Submission
CON-PFM-NOT-003	Staff Notification
CON-PFM-NOT-004	Association E-mail Template
CON-PFM-NOT-005	Association Communication
CON-PFM-NOT-006	Communication Protection
FEAT-PFM-NOT-01	Application Notification Catalog
FEAT-PFM-NOT-02	Staff Notification Processing
FEAT-PFM-NOT-03	Personal Notification Workspace
FEAT-PFM-NOT-04	Notification Review and Operator Support
FEAT-PFM-NOT-05	Rhythm Operational Notifications
FEAT-PFM-NOT-06	Notification Delivery Configuration
FEAT-PFM-NOT-07	Association Communication Delivery
JNY-PFM-NOT-001	Receive and organize a responsibility notice
JNY-PFM-NOT-002	Withdraw an assignment notice before or after delivery
JNY-PFM-NOT-003	Investigate recipient and empty-request history
JNY-PFM-NOT-004	Receive a provisioning alert and review granted customer History
JNY-PFM-NOT-005	Register a notification type and publish a collapsing burst
JNY-PFM-NOT-006	Publish compliance content and inspect protected delivery
ACT-PFM-027	Staff Notification Recipient
ACT-PFM-028	Association Communication Administrator
ACT-PFM-029	Rhythm Notification Operator
ACT-PFM-030	Notification and Communication Producer
ACT-PFM-031	Platform Message Processor

Nested Rule and Scenario Reservations

Capability	Rules allocated	Next rule	Capability scenarios allocated	Acceptance scenarios allocated	Next acceptance scenario
CAP-PFM-NOT-001	01 through 14	15	01 through 02	01 through 15	16
CAP-PFM-NOT-002	01 through 10	11	01 through 02	01 through 09	10
CAP-PFM-NOT-003	01 through 08	09	01 through 02	01 through 09	10
CAP-PFM-NOT-004	01 through 08	09	01 through 01	01 through 05	06
CAP-PFM-NOT-005	01 through 08	09	01 through 01	01 through 10	11
CAP-PFM-NOT-006	01 through 08	09	01 through 02	01 through 10	11
CAP-PFM-NOT-007	01 through 11	12	01 through 01	01 through 10	11
CAP-PFM-NOT-008	01 through 11	12	01 through 01	01 through 11	12
CAP-PFM-NOT-009	01 through 10	11	01 through 02	01 through 10	11
CAP-PFM-NOT-010	01 through 07	08	01 through 01	01 through 07	08
CAP-PFM-NOT-011	01 through 08	09	01 through 01	01 through 07	08
CAP-PFM-NOT-012	01 through 07	08	01 through 01	01 through 06	07
CAP-PFM-NOT-013	01 through 11	12	01 through 01	01 through 11	12
CAP-PFM-NOT-014	01 through 10	11	01 through 01	01 through 07	08
CAP-PFM-NOT-015	01 through 13	14	01 through 01	01 through 13	14
CAP-PFM-NOT-016	01 through 15	16	01 through 01	01 through 18	19
CAP-PFM-NOT-017	01 through 16	17	01 through 01	01 through 15	16
CAP-PFM-NOT-018	01 through 14	15	01 through 01	01 through 15	16
CAP-PFM-NOT-019	01 through 12	13	01 through 01	01 through 09	10
CAP-PFM-NOT-020	01 through 15	16	01 through 01	01 through 15	16

Journey Assertion Reservations

Journey	Assertions allocated	Next assertion
JNY-PFM-NOT-001	01 through 04	05
JNY-PFM-NOT-002	01 through 02	03
JNY-PFM-NOT-003	01 through 03	04
JNY-PFM-NOT-004	01 through 02	03
JNY-PFM-NOT-005	01 through 03	04
JNY-PFM-NOT-006	01 through 03	04

Examination Additions

Permanent allocation	Purpose
FND-PFM-NOT-025	The requested planning brief is missing from the supplied specification checkout.
FND-PFM-NOT-026	Some acceptance scenarios combine checks beyond their bound assertions.
FND-PFM-NOT-027	Definition retirement commits before workspace cancellation attempts.
FND-PFM-NOT-028	Unexpected adapter exceptions are logged using their raw message.
FND-PFM-NOT-029	Collapsed-item withdrawal cannot refresh wording when declared links have been redacted or the recipient is no longer eligible.
FND-PFM-NOT-030	Communication recovery can resubmit after the ambiguity interval.
FND-PFM-NOT-031	Sender provisioning adopts existing provider identities, and purge deletes adopted identities too.
FND-PFM-NOT-032	Allowed notification paths prove their own screens and behavior only.
FND-PFM-NOT-033	Caller-rendered purposes, Marketing-version content and changed-message behavior have code evidence without corresponding Andrew approval in the examined records.
FND-PFM-NOT-034	Deployment defines a text-message queue but no text-message consumer.
FND-PFM-NOT-035	The changed-message operation accepts a service filter from its invocation and does not independently authenticate that service name.
FND-PFM-NOT-036	HQ dead-letter and retry responses include retained channel content without checking the active customer access grant required for History.
BR-CAP-PFM-NOT-001-14; ATS-PFM-NOT-001-13	Additional observed behavior and its proposed acceptance check
BR-CAP-PFM-NOT-005-08; ATS-PFM-NOT-005-09	Additional observed behavior and its proposed acceptance check
BR-CAP-PFM-NOT-017-15; ATS-PFM-NOT-017-13	Additional observed behavior and its proposed acceptance check
BR-CAP-PFM-NOT-020-14; ATS-PFM-NOT-020-13	Additional observed behavior and its proposed acceptance check
BR-CAP-PFM-NOT-020-15; ATS-PFM-NOT-020-14	Additional observed behavior and its proposed acceptance check
ATS-PFM-NOT-007-08, ATS-PFM-NOT-007-09, ATS-PFM-NOT-013-09	Added proof checks for existing adapter, event and system-workspace rules

Permanent allocation	Examination purpose
BR-CAP-PFM-NOT-008-10, BR-CAP-PFM-NOT-008-11; ATS-PFM-NOT-008-09, ATS-PFM-NOT-008-10	Dispatcher and nightly reconciliation silence alarms
BR-CAP-PFM-NOT-012-07; ATS-PFM-NOT-012-05; OQ-PFM-NOT-007	Operator content outside the customer access-grant boundary
BR-CAP-PFM-NOT-017-16; ATS-PFM-NOT-017-14	Database rendering-mode and template-version constraints
ATS-PFM-NOT-015-11	Supported-channel, mandatory e-mail and digest preference validation

Design Allocations

Allocated by the design draft platform-notifications-desi-draft-1 (2026-10-23) before any design file was written.

Id	Allocated subject
DOM-PFM-NOT-003	Staff Notification
DOM-PFM-NOT-004	Association E-mail Template
DOM-PFM-NOT-005	Association Communication
STATE-PFM-NOT-001	Notification definition registration
STATE-PFM-NOT-002	Notification request processing and settlement
STATE-PFM-NOT-003	Notice delivery progress
STATE-PFM-NOT-004	Personal read and archive state
STATE-PFM-NOT-005	Notification delivery
STATE-PFM-NOT-006	Chat and text channel identity
STATE-PFM-NOT-007	Workspace wording override
STATE-PFM-NOT-008	Notification digest
STATE-PFM-NOT-009	Association template and its published versions
STATE-PFM-NOT-010	Communication request acceptance
STATE-PFM-NOT-011	Communication message dispatch
STATE-PFM-NOT-012	Communication message delivery as the provider reports it
STATE-PFM-NOT-013	Address suppression
STATE-PFM-NOT-014	Association sender verification
STATE-PFM-NOT-015	Marketing sending lane
WF-PFM-NOT-001	Register an application's notification definitions
WF-PFM-NOT-002	Publish a staff notification with its business change
WF-PFM-NOT-003	Turn one request into recipient notices
WF-PFM-NOT-004	Withdraw or replace a notice
WF-PFM-NOT-005	Deliver queued chat and text deliveries
WF-PFM-NOT-006	Alert Rhythm HQ in Slack
WF-PFM-NOT-007	Reconcile and trim notification records nightly
WF-PFM-NOT-008	Retry an exhausted delivery from Rhythm HQ
WF-PFM-NOT-009	Announce responsibility changes
WF-PFM-NOT-010	Submit an association communication request
WF-PFM-NOT-011	Accept and send association e-mail
WF-PFM-NOT-012	Pace association sending across lanes
WF-PFM-NOT-013	Record provider feedback
WF-PFM-NOT-014	Compose a record-owned template across services
WF-PFM-NOT-015	Provision, verify and remove the association sender
WF-PFM-NOT-016	Purge or reset a workspace's notifications and communications
SVC-PFM-NOT-notifications	Notifications service module
SVC-PFM-NOT-communications	Communications service module
SCR-PFM-NOT-001	Notifications inbox
SCR-PFM-NOT-002	Why Did I Get This sheet
SCR-PFM-NOT-003	Workspace notification History
SCR-PFM-NOT-004	Notification chain sheet
SCR-PFM-NOT-005	Rhythm HQ notification History
SCR-PFM-NOT-006	Header bell Notifications section
ADR-PFM-NOT-001	Notifications is a Platform module beside communications
ADR-PFM-NOT-002	Staff notices and association e-mail are separate models
ADR-PFM-NOT-003	Producers publish inside their own transaction through an insert-only role
ADR-PFM-NOT-004	The queue holds only work and SQS owns every retry
ADR-PFM-NOT-005	A submission is validated whole and travels complete
ADR-PFM-NOT-006	The request object is written inside the caller's transaction
ADR-PFM-NOT-007	Definitions are registered at deploy and retired, never deleted
ADR-PFM-NOT-008	Audiences resolve at processing, inside the workspace, capped at two hundred
ADR-PFM-NOT-009	Withdrawal ends unsent work and never recalls what left
ADR-PFM-NOT-010	An uncertain hand-off waits out a fifteen-minute window
ADR-PFM-NOT-011	Rhythm HQ alerts are hard-coded Slack deliveries in a system scope
ADR-PFM-NOT-012	Console, e-mail and text are native; customer chat goes through integrations
ADR-PFM-NOT-013	Preferences and workspace settings are stored but not applied yet
ADR-PFM-NOT-014	The person is always the signed caller; support reads need a grant
ADR-PFM-NOT-015	Notification and communication records carry no custom fields
ADR-PFM-NOT-016	No notification or communication operation is published to Submissions
ADR-PFM-NOT-017	Dispatch, provider delivery and engagement are separate facts
ADR-PFM-NOT-018	A record owns its template and composes it through its own API
ADR-PFM-NOT-019	Three rendering modes decide who supplies the content
ADR-PFM-NOT-020	Purpose-classified lanes keep transactional mail ahead of bulk mail
FND-PFM-NOT-037	Retiring a definition cancels requests without withdrawing their notices or queued deliveries
FND-PFM-NOT-038	The charter does not yet say the module performs no inference
FND-PFM-NOT-039	Reading the association sender in HQ refreshes and writes its verification state, from another module's route
FND-PFM-NOT-040	Notice cancellation and delivery deferral are declared states that nothing writes
FND-PFM-NOT-041	The two pipelines apply opposite policies after an uncertain hand-off
FND-PFM-NOT-042	A request item that exhausts its receives leaves no request record in History
FND-PFM-NOT-043	Template draft edits and archiving record no actor or audit entry
OQ-PFM-NOT-008	Should retiring a definition withdraw its open notices as a cancel does?

Independent Design Examination Allocations

Id	Subject
FND-PFM-NOT-044	Delivery outcomes and notice summaries commit separately
FND-PFM-NOT-045	Feedback duplicates can skip an unfinished suppression
FND-PFM-NOT-046	Dormant identity and digest guards are weaker than the draft claims
FND-PFM-NOT-047	Diagnostic sheet operations differ from the draft
FND-PFM-NOT-048	The requested design brief is unavailable
FND-PFM-NOT-049	Producer internals and enabling registrations remain outside verified scope
FND-PFM-NOT-050	Owned saves merge stored draft and commit publication separately
FND-PFM-NOT-051	Template checks precede locks and can race editing or archive
FND-PFM-NOT-052	Final receive can leave unattempted drafts in dead-lettered requests
OQ-PFM-NOT-009	Which recovery gaps must close before implementation preparation

Control Gap Allocations

Id	Controls	Existing Evidence
FND-PFM-NOT-053	TC-DAT-003	FND-PFM-NOT-024
FND-PFM-NOT-054	TC-PI-004, TC-AVL-004	FND-PFM-NOT-027
FND-PFM-NOT-055	TC-PI-002	FND-PFM-NOT-030
FND-PFM-NOT-056	TC-AZ-002, TC-TEN-004, TC-IAM-006	FND-PFM-NOT-035
FND-PFM-NOT-057	TC-AZ-005, TC-TEN-002, TC-DAT-002	FND-PFM-NOT-036
FND-PFM-NOT-058	TC-PI-005	FND-PFM-NOT-043
FND-PFM-NOT-059	TC-PI-004, TC-AVL-004	FND-PFM-NOT-044
FND-PFM-NOT-060	TC-PI-002, TC-PI-004, TC-PRV-004	FND-PFM-NOT-045
FND-PFM-NOT-061	TC-PI-003, TC-PI-005	FND-PFM-NOT-051

Testing Back-fill Allocations

Series	Allocated	Next free
FAS-PFM-NOT-	01 through 07, matching their features	08
TST-PFM-NOT-	001 through 123	124

Permanent allocation	Subject
ATS-PFM-NOT-001-14	Registration reaches both personal and operational processing
ATS-PFM-NOT-002-09	Committed publication survives dispatch recovery and withdrawal
ATS-PFM-NOT-003-09	Current audience selection is explained in both personal and workspace views
ATS-PFM-NOT-004-05	Rendered destinations remain usable across channel and inbox views
ATS-PFM-NOT-005-10	Read and withdrawal actions change subsequent folding
ATS-PFM-NOT-006-10	Withdrawal closes pending delivery while preserving remaining history
ATS-PFM-NOT-007-10	Channel failure and operator retry preserve routing explanations
ATS-PFM-NOT-008-11	Recovery does not restore withdrawn work or duplicate delivery
ATS-PFM-NOT-009-10	Inbox organization and explanation follow responsibility withdrawal
ATS-PFM-NOT-010-07	Personal and administrator explanations agree without expanding access
ATS-PFM-NOT-011-07	Workspace investigation carries the same chain into granted support
ATS-PFM-NOT-012-06	HQ retry affects operational progress within its authority boundary
ATS-PFM-NOT-013-10	HQ routing stays separate from personal selection and operator recovery
ATS-PFM-NOT-014-07	Responsibility announcements stay distinct across folding and withdrawal
ATS-PFM-NOT-015-12	Stored configuration does not change current rendered delivery
ATS-PFM-NOT-016-15	Publication controls acceptance and later message history
ATS-PFM-NOT-017-15	Accepted content, safeguards and feedback remain connected
ATS-PFM-NOT-018-14	Late protection and feedback constrain retry outcomes
ATS-PFM-NOT-019-09	Copy feedback protects the copy without rewriting primary delivery
ATS-PFM-NOT-020-15	Sender and recipient safeguards remain visible through the mail lifecycle
ATS-PFM-NOT-016-16	Preview record-owned content and retain the saved version
ATS-PFM-NOT-016-17	Select published scheduled-report content during schedule setup
FAS-PFM-NOT-01	Application Notification Catalog
FAS-PFM-NOT-01-01	A declared event becomes a usable catalog entry
FAS-PFM-NOT-01-02	An unmapped operational declaration cannot enter processing
FAS-PFM-NOT-01-03	Release changes preserve declaration history
FAS-PFM-NOT-01-04	Customer authority does not expose the global catalog
FAS-PFM-NOT-01-05	Manifest refusal leaves installed definitions available
FAS-PFM-NOT-02	Staff Notification Processing
FAS-PFM-NOT-02-01	A committed event reaches its eligible recipient
FAS-PFM-NOT-02-02	Reading and withdrawal change folding eligibility
FAS-PFM-NOT-02-03	Withdrawal and expiry stop pending work across the pipeline
FAS-PFM-NOT-02-04	Publication and audience selection enforce distinct boundaries
FAS-PFM-NOT-02-05	Lost acknowledgement does not duplicate recipient work
FAS-PFM-NOT-03	Personal Notification Workspace
FAS-PFM-NOT-03-01	An assignment is actionable and understandable
FAS-PFM-NOT-03-02	Ending one scope leaves another scope available
FAS-PFM-NOT-03-03	Assignment ending preserves delivered history
FAS-PFM-NOT-03-04	A colleague cannot organize or investigate a personal item
FAS-PFM-NOT-03-05	Responsibility screens and attention totals keep working
FAS-PFM-NOT-04	Notification Review and Operator Support
FAS-PFM-NOT-04-01	An administrator follows a notice through its processing chain
FAS-PFM-NOT-04-02	Workspace and support history share results under separate authority
FAS-PFM-NOT-04-03	Retry reopens only exhausted delivery work
FAS-PFM-NOT-04-04	Read-only personal access cannot become administrative review
FAS-PFM-NOT-04-05	Failed support access returns no customer records
FAS-PFM-NOT-05	Rhythm Operational Notifications
FAS-PFM-NOT-05-01	Operational events reach the mapped operations channel
FAS-PFM-NOT-05-02	Operational failure can be recovered from HQ
FAS-PFM-NOT-05-03	Repeated operational publication retains one occurrence
FAS-PFM-NOT-05-04	Operational audiences cannot enter customer processing
FAS-PFM-NOT-05-05	Operational Slack does not enable personal Slack
FAS-PFM-NOT-06	Notification Delivery Configuration
FAS-PFM-NOT-06-01	Stored delivery choices remain inspectable
FAS-PFM-NOT-06-02	Dormant wording and channels do not alter current inbox output
FAS-PFM-NOT-06-03	Digest settlement retains collected history
FAS-PFM-NOT-06-04	Storage stays within workspace and recipient boundaries
FAS-PFM-NOT-06-05	Rejected configuration does not add audit history
FAS-PFM-NOT-07	Association Communication Delivery
FAS-PFM-NOT-07-01	Published compliance content yields protected recipient outcomes
FAS-PFM-NOT-07-02	Bounce feedback changes the next request outcome
FAS-PFM-NOT-07-03	Publication, acceptance and provider history retain distinct facts
FAS-PFM-NOT-07-04	Submission, message history and body access remain separate
FAS-PFM-NOT-07-05	Replayed queue work and feedback add no second send
TST-PFM-NOT-001	Notification acceptance journey cross-application 0300
TST-PFM-NOT-002	Notification acceptance journey history 0100
TST-PFM-NOT-003	Notification acceptance journey history 0101
TST-PFM-NOT-004	Notification acceptance journey hq 0150
TST-PFM-NOT-005	Notification acceptance journey inbox 0001
TST-PFM-NOT-006	Notification acceptance journey inbox 0002
TST-PFM-NOT-007	Notification acceptance journey inbox 0003
TST-PFM-NOT-008	Notification acceptance journey inbox 0004
TST-PFM-NOT-009	Notification acceptance journey inbox 0005
TST-PFM-NOT-010	Notification acceptance journey inbox 0006
TST-PFM-NOT-011	Notification acceptance journey pipeline 0200
TST-PFM-NOT-012	Notification acceptance journey pipeline 0201
TST-PFM-NOT-013	Notification acceptance journey pipeline 0202
TST-PFM-NOT-014	Notification acceptance journey pipeline 0203
TST-PFM-NOT-015	Notification acceptance journey pipeline 0204
TST-PFM-NOT-016	Notification acceptance journey pipeline 0205
TST-PFM-NOT-017	Notification acceptance journey pipeline 0206
TST-PFM-NOT-018	Notification acceptance journey pipeline 0207
TST-PFM-NOT-019	Notification acceptance journey pipeline 0208
TST-PFM-NOT-020	destination
TST-PFM-NOT-021	notifications
TST-PFM-NOT-022	model
TST-PFM-NOT-023	messages
TST-PFM-NOT-024	requests
TST-PFM-NOT-025	suppressions
TST-PFM-NOT-026	templates
TST-PFM-NOT-027	communication messages table
TST-PFM-NOT-028	communication request submissions table
TST-PFM-NOT-029	communication sender identities table
TST-PFM-NOT-030	contact role compliance communication
TST-PFM-NOT-031	communication reads
TST-PFM-NOT-032	caller rendered
TST-PFM-NOT-033	dispatch communications
TST-PFM-NOT-034	marketing lane
TST-PFM-NOT-035	owned template
TST-PFM-NOT-036	process communication request
TST-PFM-NOT-037	reserved domain suppression
TST-PFM-NOT-038	send handler
TST-PFM-NOT-039	template copies
TST-PFM-NOT-040	lane budgets
TST-PFM-NOT-041	messages changes queries
TST-PFM-NOT-042	messages
TST-PFM-NOT-043	messages queries
TST-PFM-NOT-044	request submissions
TST-PFM-NOT-045	request submissions queries
TST-PFM-NOT-046	requests
TST-PFM-NOT-047	requests queries
TST-PFM-NOT-048	sender identities
TST-PFM-NOT-049	sender identities queries
TST-PFM-NOT-050	suppressions
TST-PFM-NOT-051	suppressions queries
TST-PFM-NOT-052	templates
TST-PFM-NOT-053	templates queries
TST-PFM-NOT-054	changed messages
TST-PFM-NOT-055	handle invocation
TST-PFM-NOT-056	record merge fields
TST-PFM-NOT-057	submit request
TST-PFM-NOT-058	provision sender identity
TST-PFM-NOT-059	workspace sender address
TST-PFM-NOT-060	communication objects
TST-PFM-NOT-061	workspace objects
TST-PFM-NOT-062	caller rendered purposes
TST-PFM-NOT-063	message version templates
TST-PFM-NOT-064	owned templates
TST-PFM-NOT-065	render preview
TST-PFM-NOT-066	communications schemas
TST-PFM-NOT-067	lane bucket
TST-PFM-NOT-068	lanes
TST-PFM-NOT-069	notifications
TST-PFM-NOT-070	notification instances table
TST-PFM-NOT-071	notification submissions table
TST-PFM-NOT-072	hq notifications
TST-PFM-NOT-073	notification centre
TST-PFM-NOT-074	deliver delivery
TST-PFM-NOT-075	dispatch notifications
TST-PFM-NOT-076	process request batch
TST-PFM-NOT-077	cancel and supersede
TST-PFM-NOT-078	logging
TST-PFM-NOT-079	orchestrate request
TST-PFM-NOT-080	resolve audience
TST-PFM-NOT-081	channel settings
TST-PFM-NOT-082	definition settings
TST-PFM-NOT-083	definitions
TST-PFM-NOT-084	definitions queries
TST-PFM-NOT-085	deliveries
TST-PFM-NOT-086	delivery works
TST-PFM-NOT-087	digests
TST-PFM-NOT-088	identities
TST-PFM-NOT-089	instances
TST-PFM-NOT-090	instances queries
TST-PFM-NOT-091	preferences
TST-PFM-NOT-092	reconcile jobs
TST-PFM-NOT-093	requests
TST-PFM-NOT-094	requests queries
TST-PFM-NOT-095	sms usages
TST-PFM-NOT-096	submissions
TST-PFM-NOT-097	template overrides
TST-PFM-NOT-098	workspace purges
TST-PFM-NOT-099	user settings
TST-PFM-NOT-100	reconcile workspace
TST-PFM-NOT-101	register service notifications
TST-PFM-NOT-102	submit notification request
TST-PFM-NOT-103	system audience
TST-PFM-NOT-104	audience planner
TST-PFM-NOT-105	channel resolution
TST-PFM-NOT-106	collapsing
TST-PFM-NOT-107	hq channels
TST-PFM-NOT-108	instance status
TST-PFM-NOT-109	permissions
TST-PFM-NOT-110	queue items
TST-PFM-NOT-111	registration manifest
TST-PFM-NOT-112	registry tables
TST-PFM-NOT-113	render message
TST-PFM-NOT-114	slack system adapter
TST-PFM-NOT-115	slack system render
TST-PFM-NOT-116	templates
TST-PFM-NOT-117	organization types dev
TST-PFM-NOT-118	query schedules dev
FND-PFM-NOT-062	The test specification for application notification declarations has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-063	The test specification for transactional publication has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-064	The test specification for recipient selection has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-065	The test specification for recipient-specific rendering has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-066	The test specification for repeated-event collapse has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-067	The test specification for withdrawal and expiry has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-068	The test specification for notification routing and delivery has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-069	The test specification for notification recovery and retention has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-070	The test specification for the personal inbox has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-071	The test specification for selection and delivery explanations has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-072	The test specification for workspace activity review has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-073	The test specification for HQ investigation and retry has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-074	The test specification for operational alerts has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-075	The test specification for responsibility announcements has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-076	The test specification for stored delivery configuration has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-077	The test specification for association content publication has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-078	The test specification for communication submission has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-079	The test specification for communication sending has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-080	The test specification for communication outcomes has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-081	The test specification for recipient and sender safeguards has incomplete detailed proof. Missing category cases and lifecycle rows require independent fixtures and assertions; existing composite cases supply only their named test assertions.
FND-PFM-NOT-082	Many retained capability scenarios combine assertions from several executable files. Suite bindings identify contributing assertions rather than complete execution of every composite precondition and step; an assertion-by-assertion qualification run remains required.
FND-PFM-NOT-083	Several feature-level chains have specification coverage but no executable file that performs the complete chain. Component capability tests do not supply an executable feature binding by themselves.
FND-PFM-NOT-084	The added related-capability chains have no inspected executable suite performing their complete sequence. They remain proposed until a cumulative workflow suite supplies the missing assertions.

| ATS-PFM-NOT-015-13 | Settle a collected digest window once |

| FND-PFM-NOT-085 | Domain guarantees with incomplete assertion coverage |

| TST-PFM-NOT-119 | Operational Slack provider delivery | | ATS-PFM-NOT-013-11 | Post an operational payload to the configured provider | | TST-PFM-NOT-120 | Platform notification declaration contracts | | ATS-PFM-NOT-001-15 | Validate the complete Platform declaration set | | TST-PFM-NOT-121 | Empty preview merge fields | | ATS-PFM-NOT-016-18 | Distinguish empty preview values from zero and false | | TST-PFM-NOT-122 | Communication queue item contracts | | ATS-PFM-NOT-018-15 | Read supported communication queue items and reject malformed versions | | TST-PFM-NOT-123 | Communication content in the organization type editor |