Enterprise & Procurement
Overview
ImmutableProof is infrastructure, not a platform.
It provides a minimal cryptographic proof-of-existence and finalization primitive intended for auditability and long-term verification.
Procurement-relevant facts
- Verification does not require proprietary services
- No subscription required to verify proofs
- Deterministic verification behavior for a given proof and protocol version
- Explicit failure behavior
- Protocol semantics for INP v1.0 are frozen
Assumptions and non-assumptions
What is assumed
- Standard cryptographic primitives as defined by the protocol
- Deterministic verification rules as defined by the protocol
- Frozen protocol semantics for INP v1.0
What is not relied upon
- Mutable servers for proof meaning
- Runtime configuration for proof meaning
- Future software updates to reinterpret existing proofs
- Continued company operation for verification
Data handling
- ImmutableProof does not interpret content.
- Proofs contain hashes, signatures, and metadata only.
- Verification is specified to be possible without reliance on ImmutableProof services.
Compliance and audit
- Verification is deterministic and repeatable for a given proof and protocol version.
- Results are derived from the proof and the published specification.
- Proofs can be independently verified.
Failure and continuity
- Payment failures affect only creation of new proofs.
- Service unavailability does not modify existing proofs.
- Verification does not require ImmutableProof services.
See: How ImmutableProof fails.
Commercial model
- Payment is required only to create new finalized proofs.
- Verification is free.
- Payment does not affect proof semantics or verification outcomes.
Suitability
ImmutableProof is appropriate where:
- Evidence must survive organizational change
- Long-term auditability is required
- Trust assumptions must be minimized
Contact
For procurement, compliance, or security review:
- Documentation review
- Failure semantics discussion
- Long-term verification assessment
Status
- Protocol: INP v1.0 (frozen semantics)
- Verification: deterministic behavior (public)
- Release: public-ready