Claims & Non-Claims
HBCE is an operational verification baseline. This page defines what HBCE does, and what it does not claim. Clear boundaries reduce ambiguity and increase auditability.
What HBCE provides (claims)
- Operational identity trajectory: origin + key reference + append-only evolution.
- Hash-only public evidence: GDPR-min posture, no public data custody.
- Deterministic verification: reproducible PASS/FAIL checks.
- Fail-closed enforcement: missing/inconsistent evidence blocks execution.
- Interoperable baseline: compatible with any implementation following the standard profiles.
What HBCE does NOT claim (non-claims)
Not a legal identity scheme
HBCE does not claim to replace eIDAS 2.0, the EUDI Wallet, national eID systems, or qualified trust services. HBCE is an operational identity layer for verifiable trajectories and proofs.
Not KYC / not a data vault
HBCE does not provide public custody of personal data. Public layer is hash-only evidence. Any personal data remains outside the public registry by design.
Not a replacement for cybersecurity
HBCE does not replace firewalls, SOC, IDS/IPS, endpoint security, or secure development. HBCE adds deterministic accountability and trajectory proofs to critical operations.
Not a “trust me” system
HBCE does not rely on institutional trust, brand trust or narrative trust. Verification is deterministic and can be performed independently.
Not reputation scoring
HBCE does not claim to rank entities by reputation. It provides evidence and identity continuity so that responsibility can be audited.
Not surveillance infrastructure
HBCE does not require continuous tracking of individuals. The public layer contains only cryptographic proofs, not personal telemetry.
Why boundaries matter
In high-accountability environments, ambiguity becomes risk. Boundaries make adoption easier because integration scope is explicit.
Status
Scope and posture statement. Applies to HBCE Baseline v1.0 and its standard profiles.