Asterpath · Revision 4
Supporting evidence
Passing checks still need meaningful coverage.
202 illustrative checks pass; payment and AI recovery remain outside the enforced test set.
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
| Check family | Illustrative result | What remains open |
|---|---|---|
| Typecheck / lint / build | No configured error in the fictional example | Runtime behaviour, exclusions and business outcomes need separate evidence. |
| Unit / component | 164 checks pass in the invented scenario | Selected validation/state behaviour; provider boundaries are not fully exercised. |
| Integration | 34 checks pass in the invented scenario | Complete payment recovery is not covered. |
| End-to-end | 4 happy-path checks pass in the invented scenario | Timeout, interrupted-write and recovery paths are incomplete. |
| Total | 164 + 34 + 4 = 202 | A count is not a release-readiness verdict. |
What it means
F03 concerns the missing assurance. F01 and F05 are the existing product failures; they are not counted again as new defects here.
What would establish a fix
Show that controlled regressions in durable access and input preservation fail the relevant checks, then prove those checks gate the candidate that will be promoted.
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.