Every unit has an identity
Application run, durable step, generation attempt, provider operation, and Genblaze run IDs are stored separately instead of being conflated.
Product / Provenance
A campaign should be explainable.
Beavous preserves the path from approved source to delivered asset, including failed checks and corrective work—not just the polished final.
Corrections keep their parent
A corrective run reconstructs the prior verified Genblaze result and persists the resulting parent run identifier.
B2 is authoritative media storage
Sources, normalized references, intermediates, outputs, manifests, evaluations, private prompts, verification records, and exports live in B2.
Two integrity checks
Beavous verifies the canonical Genblaze manifest, then fetches the stored asset through authenticated B2 access and checks the bytes again.
Private prompts stay private
The database and user interface expose a hash and safe summary. Full sensitive prompts are stored as private B2 sidecars.
The claim stays honest
Current trust mode supports integrity verification. Beavous does not claim that a hash proves creative authorship or signer identity.