Training Path
Pricing is designed as a role ladder: user → pro → operator → governance.
This page defines the operational training required to use IPR correctly and (optionally) become a
HBCE Certified Operator.
Rule: VALID IPR = FILE INTEGRITY OK + PRESENT IN REGISTRY (fail-closed).
Public proof is hash-only (GDPR-min). Private proof is your local Release file.
Why training exists
IPR is not “just a file”. It is an operational identity gate used to prevent unverified execution. To operate safely, users and operators must follow strict procedures: issuance discipline, local file custody, append-only registry proofs, deterministic verification, and audit-first evidence packs.
If verification cannot be proven, the system must BLOCK. No silent execution.
What you need to operate (minimum kit)
Minimum technical kit
- Device: laptop / Chromebook / desktop
- Connection: stable internet
- Accounts: GitHub + email (PEC recommended for formal channels)
- Storage discipline: secure folder structure + backup plan for Release files
Operator kit (recommended)
- Dedicated workstation profile (separate user)
- Password manager
- Encrypted backup (offline copy)
- Operational checklist (intake → issuance → receipts → append → verify → evidence pack)
Course stack (IPR → Operator → Governance)
Citizen Onboarding (IPR Basics)
Goal: become VALID and understand the rule-set.
- CREATE → RECEIPT → APPEND → VERIFY
- Hash-only registry (GDPR-min)
- Fail-closed invalidation causes
- Release file custody (local proof)
Outcome: you can activate and maintain a VALID IPR.
Digital Operations (Proof Packs)
Goal: use IPR as a daily operational tool.
- Receipts and evidence packs
- Exportable audit traces
- Binding workflows to verification checks
Outcome: you can operate in “certified mode” with repeatable proofs.
Operator Foundation (Candidate)
Goal: learn operator discipline (without issuing yet).
- Registry logic (append-only) and deterministic verify
- Customer onboarding procedures and required fields
- Receipt discipline and audit-first documentation
- Fail-closed handling and escalation
Outcome: you can support customers and prepare registry-ready entries under supervision.
HBCE Operator License (Certified Issuer)
Goal: become a certified operator who can issue IPR and append registry entries.
- Issuance procedure: intake → release → receipt → registry append → verify
- Audit-first playbook
- Operational security and custody rules
- Service model (territorial hub, certified operations)
Eligibility: Business Scale level unlocks Operator application eligibility.
Node Operations (City / Region / Nation)
Goal: operate nodes, monitoring, and governance corridors.
What you learn
- Node roles and responsibilities
- Registry integrity monitoring and uptime discipline
- Incident handling and traceability
- Interoperability corridors (cross-entity / cross-jurisdiction)
Prerequisites
- HBCE Operator License
- Verified operational checklist accepted
- Secure storage + backup policy
Outcome: capability to assist or run node deployments and governance workflows.
Start now
- Activate: bank-like onboarding
- Create: release + receipt + registry entry
- Append: hash-only entry to registry
- Verify: VALID/INVALID (fail-closed)
- Scale: choose track + level, then training → operator path
Formal contact
Procurement / institutional channels.
- Company PEC: hermeticum@pec.it
- Operational PEC: manuelcoletta@domiciliodigitale.com
Policy: hash-only · append-only · GDPR-min · fail-closed
HERMETICUM - BLINDATA · COMPUTABILE · EVOLUTIVA
HERMETICUM B.C.E. S.r.l.
EU-first · audit-first · fail-closed · hash-only · append-only · GDPR-min