MachineIntelligences.org currently provides documentary provenance: versioned repository files, curated-source hashes, implementation history, validation reports, and a release-file integrity manifest. It does not claim cryptographic proof of every editorial or intellectual action.
The report manifest can show that a curated report corresponds to a particular supplied source hash and that the stored curated edition has a known hash. The release manifest can show package-file byte identity. A hash proves content identity within its stated scope, not truth or authorship.
Validation reports show which local checks were run against a release package. They do not prove the behavior of a live server that has not been inspected.
Signed workflow attestations, independent witnesses, and stronger identity systems remain research options that would require separate architecture and dependency decisions.