What BitGraph is Not
Precise distinctions matter for a protocol that makes specific cryptographic claims. Here is what BitGraph does not claim and does not do.
BitGraph is not a blockchain
BitGraph does not use distributed consensus, a global ledger, or tokens. It constrains a single execution boundary. There is no mining, no gas, no network of validators. Proof chaining (prevB64) creates a local hash chain within one boundary, not a distributed data structure.
BitGraph is not a watermark
BitGraph does not embed anything in the artifact bytes. The artifact is hashed, not modified. The proof is a separate JSON object that travels alongside the artifact. Removing the proof does not change the artifact; it only removes the evidence of the commit event.
BitGraph is not DRM
BitGraph does not prevent copying, sharing, or redistribution of artifact bytes. It prevents the authoritative proof lineage from being duplicated within a policy domain. The artifact itself is freely copyable, but only the original proof will verify against it.
BitGraph is not proof of truth
BitGraph proves that specific bytes were committed through an authorized boundary. The content of those bytes may be factually wrong, misleading, or fabricated. An LLM committed through BitGraph is still an LLM. It can hallucinate. BitGraph proves the commit event, not the content semantics.
BitGraph is not proof of authorship
A base proof attests which boundary committed an artifact, not who created the underlying content. Actor-bound proofs can additionally attest that a specific person or device authorized the commitment, but this is actor-binding, not authorship attribution.
BitGraph is not proof of first creation
BitGraph does not prove that these bytes never existed before this commit. The same content could have been created elsewhere earlier. BitGraph proves that this specific boundary committed these bytes at this point in its counter sequence. Nothing more.
BitGraph is not attestation
Attestation is evidence that BitGraph carries, not what BitGraph is. A TEE attestation report (e.g., AWS Nitro) proves that specific code is running inside a specific hardware boundary. BitGraph is the proof architecture that attestation fits into, the framework for atomic commit events where attestation provides environmental evidence.
BitGraph is not notarization
Traditional notarization involves a trusted third party witnessing a signing event. BitGraph is a self-contained proof system. The proof is verifiable offline using only the public key and the original bytes. No trusted third party is required for core verification.