Verification Architecture
System architecture and component topology for the FH Protocol verification infrastructure.
System Overview
FH Protocol implements a layered verification pipeline: structured input is normalized to a canonical form, evaluated against governance rules, then hashed to a deterministic state root. Verification Records bind canonical payload, governance outcome, and state for audit and reproduction.
Processing Pipeline
- Structured input
Applications supply structured payloads through defined interfaces. Inputs are validated before canonicalization.
- Schema validation
- Field normalization
- Deterministic ordering
- Canonicalization
Payloads are serialized to a canonical byte-stable representation suitable for hashing and reproduction.
- Deterministic key ordering
- UTF-8 encoding
- Stable numeric and boolean forms
- Governance evaluation
The governance engine applies configured rules to the canonical payload. Rejection is explicit and deterministic.
- Rule evaluation ordering
- Structured decision records
- No state computation on rejection
- Deterministic state and records
Approved payloads yield a deterministic state root and Verification Record. The same canonical input and rules produce the same state across compliant implementations.
- SHA-256 state root computation
- Verification Record assembly
- Server-authoritative verification API
Deployment Topology
Deployments integrate the verification service into institutional environments: cloud, on-premises, or hybrid. Scaling and availability follow each organization's operational standards.
Integration: REST API (see API reference)
State: Deterministic per canonical payload and rule set
Authority: Server-side verification