Asterpath · Revision 4
Supporting evidence
Follow the customer through interruption and recovery.
Normal journeys work in the fiction; interrupted payment, AI timeout and dialog-close paths reveal different gaps.
Fictional, not a scanner result. FICTIONAL ILLUSTRATIVE SAMPLE. Asterpath, its product, evidence, findings and measurements are invented. No Asterpath application was inspected and no scanner was executed. These are original GadirLabs illustrations, not native vendor exports.
What the fictional evidence shows
| Journey | Illustrative observation | Link to the report |
|---|---|---|
| J01 · Sign in / session | Selected sign-in, expiry and sign-out paths work; broad session recovery remains partial. | No material finding raised for this sample. |
| J02 · Subscribe / unlock | A provider success precedes a failed entitlement write; the paid account remains free. | F01 · sole launch blocker. |
| J03 · Generate an AI plan | A timeout clears the entered brief; retry requires reconstructing the input. | F05 · preserve work and make retry safe. |
| J04 · Export a plan | A PDF is produced, but closing the dialog returns keyboard focus to the page body. | F08 · restore focus to the initiating control. |
What it means
A successful response is only one step in the customer outcome. Each underlying failure has one finding identifier across journeys, code, testing and the action plan.
What would establish a fix
Verify successful and failed paths, duplicate/delayed/out-of-order payment events, preserved input after timeout, and predictable focus after closing the dialog.
This page and its JSON are two views of the same original illustration. They are not separate findings or independent corroboration. A real client record would identify actual versions, inputs, outputs and evidence limits.