Bound the question.
Choose permitted code and an exact revision. Test a declared rule in isolation and preserve the reproduction.
Evidence with its limits attached
Work with real consequences needs evidence people can inspect. We plan to audit open-source workflows and publish each as a case study, alongside its own scoped certificate for the exact version. No certificate is issued yet. Agent payment workflows are our starting point.
New to certificates? How to read a Geometer certificate, or practise on the illustrative example.
The open verifier shows a certificate is unchanged, not that everything was observed.
Self-issued certificates Free, opt-in links
Check one with the verifierEach case will identify the existing controls, the interaction tested and what any fix and recheck establish. Scope and missing coverage stay explicit. A reproducible problem does not establish customer savings; failed and incomplete certificates remain useful evidence.
Choose permitted code and an exact revision. Test a declared rule in isolation and preserve the reproduction.
Coordinate disclosure with maintainers. Explain problems, fixes where available and the recheck without concealing unresolved limits.
Publish a separate certificate for that audit when issuance and verification are ready. Link corrections and later certificates to the original record.
No completed open-source audit or issued certificate is published here yet. Start with the synthetic refund experiment and its illustrative certificate.
Inspect an illustrative exampleWhat did the certificate establish? What can be verified about integrity and issuer? Does it still apply?
How to read a Geometer certificate →The browser verifier checks supported evidence packs locally against separately retained anchors. It does not issue certificates.
Verify on this device →