Free local tool · Self-declaration
Show what your build has checked.
Share exact versions, actual test records and clear limits. You do not need an account, a paid badge or a receipt to use the personal tools.
Three simple steps
- Keep your actual test evidence files in a private folder. Read the template and enter your implementation, revision and known limits.
- Use the local statement command to bind the evidence files’ fingerprints. No files are sent to us.
- Review the statement before sharing. Keep the original files so a reviewer can compare the evidence you choose to provide.
Say exactly what is known
The statement distinguishes passed, failed and untested checks. File hashes establish which evidence you selected; they do not establish that your results are true. Test results remain self-declared.
Passing engineering checks does not grant certification, mark permission or independent accuracy validation. There is no operating certification programme.
Find a passage in your references
The optional local retrieval tool compares the claim lines you supply with your own references and reports similarity and exact locations. It sends nothing to us.
Similar words can still mean different things. This tool does not validate facts or issue NF or FI.
Give clear credit
Identify the source revision and your own publisher. Say if you modified the source. Describe your checks without implying AI Trust ID endorsed or certified your build.
Keep required licenses and notices. Source-code licensing does not grant general permission to adopt a project’s branding.
You can decline a receipt
Write, check, reset and leave without creating or sharing a receipt. Receipt issuance and endorsement are separate choices. Our reference policy rejects compulsory or automatic receipts.
These software controls cannot detect pressure outside the tool or prove freely given consent.