Definitions and Glossary
This appendix includes both required primitives and optional modules. A minimal Lioth implementation requires only: Tasks, Campaigns, Contributions, Validators, PHK, PHK Receipts, and Delivery via the Distribution Layer. Optional components are explicitly labeled.
- Account Trust
- A runtime operational access/readiness score used in some bootstrap or testnet deployments for routing, caps, validator readiness, settlement timing, reward shaping, and requester launch access. It is distinct from canonical PHK truth.
- Admin Safety Overlay
- A distinct operational release-control layer that can hold settlement, freeze payout release, quarantine entities, mark suspected exploit posture, and exclude TGE-sensitive eligibility without rewriting PHK outcomes.
- Bootstrap-Approved Validator
- A validator explicitly enabled by audited bootstrap or testnet operator control. Bootstrap approval expands availability but does not grant truth authority.
- Policy-Eligible Validator
- A validator whose active policy state allows validator participation under the current network-phase rules.
- Effective Validator Readiness
- The currently usable validator state after policy eligibility, bootstrap approval where applicable, account status, safety restrictions, and integrity restrictions are all considered.
- Cluster Confidence
- An integrity posture score derived from account-overlap signals. It can drive operational restrictions, but it is not by itself proof of fraud or collusion.
- Restriction Level
- The operational category derived from cluster confidence, such as scrutiny, restricted, or hard block. It affects routing/readiness rather than PHK truth.
- Force Assignment (Testnet)
- An audited bootstrap/testnet operator action that explicitly assigns a validator to review a task even when automatic routing would block that validator. It changes assignment only, not canonical PHK truth.
- TGE Eligibility Overlay
- An operational release state indicating whether an output/account remains eligible for token-generation-event-sensitive accounting. It does not alter PHK finality.
- Delivery Artifact
- The off-chain requester-facing bundle produced after campaign completion, containing finalized outputs in the requested format.
- Manifest
- An off-chain structured record that summarizes a dataset/delivery artifact, including counts, provenance references, and integrity hashes.
- Delivery Receipt
- A delivery-layer record linking a completed requester-facing artifact to its version, integrity hashes, and delivery timestamp without exposing the underlying payload.
- PHK Receipt
- The canonical finality artifact describing what rules were applied, what outcome was finalized, and whether audit/dispute/arbitration paths were involved.