Asterpath · Revision 4
Supporting evidence
Distinguish sending an alert from delivering it.
The fictional relay reports local success even when the destination rejects the notification.
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
| Step | Illustrative observation | Consequence |
|---|---|---|
| Relay invoked | The local operation finishes successfully. | Invocation status alone does not establish delivery. |
| Destination rejects | The receiving channel does not accept the notification. | No retry or independent failed-delivery signal is represented. |
| Operator outcome | An important notification may be assumed delivered. | F07; detection depends on manual inspection or user reports. |
What it means
A successful process exit and a delivered message answer different questions. F07 is an operations finding linked to the existing observability chapter.
What would establish a fix
Use an approved controlled rejection to show visible failure, bounded retry, recovery and delivery to the intended responder or fallback.
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.