HERMETICUM - BLINDATA · COMPUTABILE · EVOLUTIVA
HERMETICUM B.C.E. S.r.l.
VERIFY · IPR · PASS / FAIL · HASH-ONLY · FAIL-CLOSED

Identity and proof verification gateway

Verify is the verification gateway of the HBCE system. It exposes two complementary surfaces:

Public verification checks the visible state of an IPR identity object.
Technical verification reproduces deterministic proof through exact byte hashing and strict PASS / FAIL logic.

Missing, invalid, or non-reproducible states are treated as failure by design.

Verify IPR ID Technical verify Open registry Enter runtime

Public IPR verification

This surface is designed for readable identity-state checks. Insert an IPR identifier and inspect the visible result. In the MVP, this page performs a strict local-format check and returns a visible state response.

INPUT

IPR identifier

Insert an IPR ID in canonical format. Example: IPR-USER-002341

RESULT

Visible identity state

Public verification returns a readable state. Missing or invalid identifiers are treated as failure.

Status
MISSING INPUT
In the current MVP, this surface validates canonical identifier structure and returns a public state response.

Position in the system

Verification is not a standalone utility. It is the reconstruction layer of the HBCE system: identity establishes attributable state, registry exposes public proof, and verification reproduces deterministic comparison or visible identity status. 

IPR ID / RELEASE
↓
VISIBLE STATE OR SHA-256(UTF8(as-is))
↓
PUBLIC PROOF / EXPECTED CONDITION
↓
VALID / FAIL

Technical deterministic verification

Paste the local release content exactly as stored and compare it against the expected public hash. No normalization is applied. Determinism requires byte-level equivalence.

INPUT 01

Local release text

Paste the full content of the release object under holder custody.

bytes0 lines0
INPUT 02

Expected proof hash

Paste the expected SHA-256 from the public registry state.

Lowercase hex only. Invalid format results in FAIL.
Reference
Public proof presence can be inspected through Registry.
INPUT 03

Run technical verification

Execute deterministic comparison between local release bytes and expected public proof.

Status
MISSING INPUT
computed_sha256: —
compare: —
RULE

No normalization

The technical verifier hashes the exact bytes provided by the user. Determinism requires byte-level equivalence.

SHA-256(UTF8(release_text_as-is))
FAIL-CLOSED

Missing means failure

Missing release text, invalid identifier format, invalid hash format, or mismatch always produce failure.

missing → FAIL
invalid → FAIL
mismatch → FAIL
NEXT

Use the result operationally

Valid proof means the visible or technical state can be trusted. Failure means the infrastructure state must not be trusted.