SITEMAP · CANONICAL STRUCTURE · FAIL-CLOSED

Canonical infrastructure map

This sitemap defines the official operational structure of the HBCE platform. Canonical pages are stable entrypoints. Non-canonical pages must route users back to the spine.

Rule: if a path is not reachable from the canonical spine, it is not operational.

Activate Registry Verify Home

1) Canonical spine (operative core)

These are the five operational entrypoints that define the platform’s minimum viable infrastructure. Anything outside this spine is either governance/support documentation or non-operational surface.

ENTRY

Activate

Canonical onboarding and discipline. Defines the sequence and the fail-closed rule.

Open Activate

GENERATION

Create

Generates the local Release file (holder custody). Public surface remains hash-only.

Open Create (IPR Base)

PUBLIC PROOF

Registry

Public, append-only, hash-only ledger. If unreachable or invalid → non-operational.

Open Registry

DETERMINISTIC

Verify

PASS/FAIL validation: SHA-256(Release bytes) must match a registry proof.

Open Verify

ECONOMIC ACCESS

Pricing

Internal economic structure: four strata, three tiers each. Not “usage-based”.

Open Pricing

DEFINITION

What is IPR

Standard-grade definition of Identity Primary Record and operational identity.

Open IPR definition

Operational rule: VALID = hash present in Registry + Verify match
Else = INVALID (fail-closed)

2) Governance, security and standards

These pages define posture and constraints: EU-first, GDPR-min, audit-first, hash-only.

SECURITY

Threat model, disclosure policy and fail-closed enforcement posture.

Open Security

GOVERNANCE

Policy constraints and operational boundaries.

Open Governance

COMPLIANCE

EU-first compliance posture (hash-only, no custody, GDPR-min).

Open Compliance

Standards: IPR Standard · Terms · Privacy

3) Institutional and business surface

Non-executive pages for institutional review and adoption context.

Brussels track · Enterprise / B2G · B2G gateway · OEM integration · Press · Partners · Contact

4) Operator and network

Operator workflows and network deployment documentation. These require a valid IPR in operational usage.

Operator · Join operator · Training · Network map · Federated network spec · Root node

5) Non-canonical / labs / demos

These sections are experimental, archival or demonstrative. They are not operational entrypoints and must never replace the canonical spine.

Labs · Demos · Phase-1 (archival) · Evidence · Documents

HERMETICUM - BLINDATA · COMPUTABILE · EVOLUTIVA

HERMETICUM B.C.E. S.r.l.

EU-first · audit-first · fail-closed · hash-only · append-only · GDPR-min