What you have to do
Nothing. This page exists so you can check us the way we’d check you.
Our own report.
2seen.com · no verification data — This build could not identify which version of the code it is, so no verification result can be tied to it.
Every site we deliver comes with the run that measured it. It would be strange to withhold ours.
The artifact
There’s no run to show you, and here’s why.
This build could not identify which version of the code it is, so no verification result can be tied to it.
no run has ever completed
Nothing is shown in its place. A run that doesn’t answer for the code you’re reading isn’t a result for it, and a green line that has quietly stopped being about this page is worse than an empty one — it reassures you with a date.
This fills itself in. The next build whose verification covers this exact version publishes its table here, gate by gate, green or red, with no step in between where a person decides what to show.
Why a green here wouldn’t be the proof either
A green line would prove the checks ran. It wouldn’t prove they can fail — and that’s the only question worth asking about a measuring instrument.
For that, look at the run against the file we keep permanently broken. Eighteen readings, forty-two findings, and it has never been repaired.
What happens when we go red
Certificates expire. Links rot. A dependency changes underneath you. When a check on this site fails after launch, the finding appears on this page with the date it appeared and the date it was fixed.
Nothing here is watching anything
This report is generated by the build, not by a live monitor. Nothing on this page is watching anything right now, and we’re not going to imply otherwise with a green dot.
The line at the bottom of every page carries the date of that run and the version it measured. What decides whether it still counts isn’t its age: it’s whether the version it measured is the version you’re reading. When it isn’t, this site shows you no result at all rather than a green one that has stopped being about this code.
That is the state you are looking at right now. The gap is a fault on our side — the run that produces this page didn’t cover this build — and it’s exactly the kind of thing we’d flag on your site.
The page the engine is measured against
The page the build system is measured against. It isn’t a client project and it isn’t a portfolio piece: it’s the reference the engine is checked against, and it’s here whether or not a run is being shown above.