Personal, workspace and support access boundaries

Verification Boundary

This browser suite exercises its configured console and service environment. Fixture availability and deployed routes can cause a skip; a present suite is not evidence of a successful run.

What This Suite Proves

Its cases exercise confine personal operations to the signed-in user; require notification management for History; investigate delivered and recipient-less activity; require an active customer access grant; read HQ History only while access is granted; a colleague cannot organize or investigate a personal item.

The registered scenario bindings identify the assertions this executable file contributes. They retain individual test references so that a composite scenario does not become a claim of complete execution by one file.

What It Does Not Prove

A browser assertion about a retained status does not prove external provider delivery or every guard in the capability specification. Conditional setup checks prove only the branch that executes. No fresh execution or conformance result is claimed.

Real Dependencies and Test Doubles

The suite uses the configured dev console, signed accounts and service endpoints. Notification acceptance journeys can also invoke local Platform assertion cases; those embedded cases retain their own database and adapter boundary.

Must Not Be Doubled

The console action, service response and assertions for the tested workflow must remain real. Embedded Platform cases must retain the lifecycle logic and database constraints that their assertions inspect.