CUSTOMER-FACING APP
Customer Portal
Daywell marketplace · product browsing
THE EVERYDAY EDIT
Useful, lovely things for the everyday rituals that make a life. Picked with care, made to be lived with.
Find your everydayEveryday, with a little extra care.
THE GOOD STUFF
The pieces you reach for,
and feel good about.
Try a different search or browse all the good stuff.
BASTION / INCIDENT BRIEF
A synthetic billing-service credential failed twice, then signed in successfully. See how two different responses affect the Daywell marketplace.
01 / SERVICE MODEL
Three modeled services show where customer browsing, checkout, and order records depend on each other.
CUSTOMER-FACING APP
Daywell marketplace · product browsing
CHECKOUT SERVICE
Supports demo checkout · no payment processing
HOST · pay-api-01ORDER RECORDS
Stores marketplace order records · modeled
DATA · order-ledger-01CONTROLLED DEMO / LOCAL EVENT GENERATOR
Start with checkout healthy. Generate a short, deterministic credential-abuse scenario against a mock identity; a synthetic billing operation then disrupts checkout. Bastion detects it so you can contain the event and recover.
Controlled local simulation — no external systems or real credentials used.
Bastion detection is waiting for simulated events.
02 / EVIDENCE TRAIL
Addresses use documentation-only ranges; all identities and events are fictional.
04 / RESPONSE COMPARISON
Choose a simulated response to see its modeled impact on Daywell. Neither choice changes the storefront.
Disconnect the modeled payment host to stop all traffic to it, including legitimate checkout requests.
Block this identity’s requests, clear the simulated service degradation, and restore the customer-facing checkout path.
SIMULATED RESPONSE
This is a fictional, local-only demonstration. No backend, external requests, payment processing, credential changes, or security actions occur.