EA-MP-VERIFY-01 proposes machine-readable fields that distinguish deposit, authorship, affiliation, alias, heteronymic function, institutional confirmation, independent corroboration, profile merging, and functional performance. It argues that a DOI, ORCID, or repository record verifies the existence of metadata and deposit infrastructure but not every claim entered by the depositor. The schema defines claim status, identity relation, verification level, affiliation status, a function test, depth proof, and profile integrity. Worked examples contrast provenance-forward development with a totalizing, self-asserted identity claim. The body explicitly says the function test requires external evidence and cannot be automated from metadata alone. It is a specification draft, not a deployed vocabulary or neutral fraud-detection standard. The displayed JSON also contains a duplicated and misnested `functionTest` block that must be repaired before machine ingestion.
Full packet — deposit #703 (canonical record) Plain text
A Metadata Packet for AI Indexing catalogued at metadatapacket.dev. The specification is deposit #656; the catalog as data is catalog.json.