A.8 Control Plane, Data Plane, and Finality Artifacts
Control Plane / Data Plane
The control plane refers to on-chain commitments, PHK receipts, settlement/finality references, and parameter governance. The data plane refers to off-chain content, computation, encrypted storage, integrity artifacts, manifests, and delivery payloads. Lioth commits minimal control-plane artifacts on-chain while keeping sensitive data-plane content off-chain.
Finality Artifacts
The current protocol/runtime semantics distinguish several artifact classes:
- PHK receipts: canonical proofs of accepted/rejected finality.
- Service events: auditable orchestration, integrity, packaging, and delivery records.
- Delivery receipts: requester-facing delivery references for artifact/manifest versions.
- Safety-overlay events: operational records for payout freeze, settlement hold, quarantine, and TGE eligibility changes.
Only PHK receipts define canonical task truth. The others support execution, delivery, and operational safety without becoming truth authorities.