Evidence index
Evidence
Every claim this site makes, with the artifact behind it. Not everything here is verified — that is the point of publishing the index rather than a summary.
All evidence records
28 records · 18 verified
| Project | Type | Claim supported | Status | Evidence |
|---|---|---|---|---|
FieldProof Mobile | TESTS | Offline capture, sync, reporting and search behave as specified Flutter unit and widget suite — 279 tests passed | VERIFIED | Open ↗ |
FieldProof Mobile | CI | Every push is gated on format, static analysis and the test suite dart format --set-exit-if-changed, flutter analyze --fatal-infos, flutter test | VERIFIED | Open ↗ |
FieldProof Database | SECURITY | One inspector cannot read or mutate another's work at any level of the chain pgTAP suite — 183 assertions across 9 files, run three times per CI pass. Covers silent denials, not only raised errors | VERIFIED | Open ↗ |
FieldProof Database | DATABASE | Migrations apply from an empty database to head 5 migrations applied unseeded, then re-applied seeded, against a real Postgres engine | VERIFIED | Open ↗ |
FieldProof Backend | DEMO | The security boundary holds against the real hosted project Hosted Supabase smoke — 38 tests through real Auth, real RLS and real Storage, not fakes | VERIFIED | Open ↗ |
FieldProof Admin | TESTS | The review console is read-only and scoped to submitted work Vitest — 41 tests across 6 files, plus lint and tsc --noEmit | VERIFIED | Open ↗ |
FieldProof Admin | DEMO | The review console is deployed and publicly reachable Live deployment with demo credentials published deliberately, so the security model can be pushed against | VERIFIED | Open ↗ |
FieldProof Mobile | RELEASE | An installable Android build exists and is downloadable v0.1.0-demo — fieldproof-f12d71d.apk, sha256 published alongside the tag | VERIFIED | Open ↗ |
FieldProof Mobile | DEVICE QA | The offline workflow was walked end to end on real hardware Two Android devices (SDK 30 and SDK 36) against the hosted project. The pass found a real defect — the app had no submit action at all | VERIFIED | Open ↗ |
FieldProof Mobile | DESIGN | Sixteen screens were rendered from the real widget trees 390×844 @2x goldens with the platform fonts registered. Not a CI gate, and explicitly not a substitute for device QA | VERIFIED | Open ↗ |
FieldProof Admin | DESIGN | Console screens captured against live demo data Headless Chrome, signed in as the published demo reviewer. A point-in-time snapshot, not a reproducible fixture | VERIFIED | Open ↗ |
FieldProof Repository | SOURCE | The whole system is public and inspectable Mobile, admin, migrations, RLS suite, CI and the acceptance record | VERIFIED | Open ↗ |
FieldProof Mobile | CI | iOS build verification Passed once on a macOS runner at c796b6f. Moved to manual dispatch and not re-verified at HEAD, so iOS is not claimed | PARTIAL | Open ↗ |
FieldProof Mobile | TESTS | Offline photo capture Not implemented. Drafts and punch items work offline; attaching a photo does not. Deferred as its own slice rather than quietly dropped | UNAVAILABLE | Open ↗ |
One Frame Mobile | TESTS | The local-first data and backup paths hold flutter test — 220 tests passed. The source repository is private, so the unedited output is committed here: readable, not re-runnable | PARTIAL | Open ↗ |
One Frame Mobile | RELEASE | A release build refuses to produce an unsigned artifact flutter build apk --release fails by design when the signing key is absent. A green build here would mean signing had regressed to the debug key | PARTIAL | Open ↗ |
One Frame Mobile | CI | Quality workflow green on the default branch Format, analyze, test and Android build. The repository is private, so the run itself is not publicly inspectable | PARTIAL | — |
One Frame Mobile | DEVICE QA | The app was run and photographed on an Android device Three screens captured on hardware. Screenshots are the artifact; there is no public run to accompany them | PARTIAL | Open ↗ |
One Frame Product | REPORTS | The privacy position is published and checkable Public repository holding the privacy policy | VERIFIED | Open ↗ |
One Frame Repository | SOURCE | Source code Private repository. Access for review on request | UNAVAILABLE | — |
One Frame Distribution | RELEASE | Play Store or App Store publication Not published to any store, and no store listing is claimed. No GitHub release exists either | UNAVAILABLE | — |
First Week Repository | SOURCE | The whole application is public and clonable Flutter app, contract, fixtures, tooling and device evidence | VERIFIED | Open ↗ |
First Week App | TESTS | The offline suite passes at the current head of the repository flutter test --exclude-tags live at 3cba674 — 79 of 80 declared tests. The excluded one is tagged live and hits a real endpoint. Public, so it reproduces | VERIFIED | Open ↗ |
First Week App | DEVICE QA | Rendered and driven by hand on an Android device Redmi Note 10, release build, 14 captured screens. The pass caught a defect the green test suite had missed | VERIFIED | Open ↗ |
First Week App | DESIGN | The screen behaviour is written down as a contract first openapi.yaml — 9 operations, each answering one thing a screen does. The in-process mock implements it | VERIFIED | Open ↗ |
First Week Data | REPORTS | Data provenance is recorded rather than asserted 271 schools seeded from a public API; 160 have no region and the screen says so instead of guessing | VERIFIED | Open ↗ |
First Week App | CI | Continuous integration There is none. The repository has no GitHub Actions workflow — the gates run locally through tool/check.sh, and no hosted run backs them | UNAVAILABLE | Open ↗ |
Skillr — | SOURCE | Nothing is claimed No repository, deployment, build or written artifact for this project could be located. Rather than describe work that cannot be shown, the entry stands empty | UNAVAILABLE | — |
VERIFIED — a linked artifact anyone can open · PARTIAL — evidence exists but cannot be independently re-run · DEPENDENCY — blocked by something outside this work · HISTORICAL — happened, no artifact of mine to publish · UNAVAILABLE — nothing to show, and nothing claimed
A test count is not the accomplishment. The claim is the accomplishment; the count is how far it was pushed before it was believed.