The stored report still matches its locked fingerprint.
What is DAEDALUS?
Like a home inspection for software.
A builder can say a website or app is finished. DAEDALUS checks that claim independently, records observable results, and locks the inspection into a report that others can verify.
The inspection
What happens from claim to certificate
- 01
Define the claim
The customer identifies the software, expected behavior, and access DAEDALUS is authorized to use.
- 02
Test observable behavior
The inspection checks the agreed scope in a real browser and records evidence for what holds up and what does not.
- 03
Review the result
Findings are tied to evidence and boundaries. The report does not turn an untested assumption into a pass.
- 04
Lock the report
A fingerprint binds the report contents. The public certificate recomputes that fingerprint so later changes are detectable.
Why independence matters
The builder does not grade its own work.
DAEDALUS sits between a software claim and the decision to accept, release, or pay for it. The report shows the tested scope and observable evidence; it is not a score invented from the builder's confidence.
The contents and stored fingerprint do not match.
A public certificate confirms report integrity. Full evidence needs an intentional customer share link.
Report language
What the result badges mean
The tested expectation survived the recorded checks in that inspection scope.
The expectation failed, was checked again under the report's method, and became an evidence-backed finding.
A later re-check confirmed the named problem no longer reproduces in the retested scope.
Your next step