Key Terms
- Campaign
- A batch of tasks with shared schema, cohort requirements, budget, delivery mode, and verification settings.
- Task
- A single structured unit of work (prompt/context + response schema + rubric).
- Contribution
- A participant's submission for a task.
- PHK (Proof of Human Knowledge)
- Lioth's canonical verification workflow for finalizing accepted/rejected outcomes and producing auditable receipts.
- PHK Receipt
- A verifiable record of which campaign rules were applied, what outcome was finalized, and whether audit/dispute/arbitration paths were involved.
- Human Verified Output (HVO)
- A finalized task result intended for direct requester consumption under PHK.
- Human Verified Data (HVD)
- Validated outputs packaged into reusable dataset artifacts with manifest, quality summary, and provenance reference.
- Account Trust
- A runtime operational access/readiness score used in bootstrap or testnet deployments for routing, caps, validator readiness, launch access, and settlement timing. It is distinct from canonical PHK truth.
- Admin Safety Overlay
- A distinct operational layer that can hold settlement, freeze payout, quarantine entities, and exclude TGE eligibility without rewriting canonical PHK outcomes.
- Quality Tier
- A predefined verification configuration (quorum, audits, dispute, privacy mode) defining strength vs cost.
- Distribution Layer
- Delivery of verified outputs and datasets via private delivery, public distribution, subscriptions, or integrations.
What Verified Means in Lioth (PHK)
This section operationalizes the terms used in the Technical Abstract and defines what PHK verification guarantees, and does not guarantee.
A verified output is:
- Rubric-compliant under a declared campaign specification, as determined by validator quorum rules, audits, and dispute/arbitration (if enabled).
- Auditable as a workflow event, because the campaign specification hash and outcome receipts are committed on-chain or anchored through committed finality artifacts.
- Bounded by the campaign's Assistance Policy, which defines whether AI assistance is allowed/disallowed/allowed-with-disclosure (see PHK specification).
Verified does not:
- Guarantee a "one human, one account" statement.
- Claim perfect detection of AI-assisted work. Where assistance is disallowed, Lioth targets bounded-risk outcomes via tier configuration, audits, integrity gating, and economic enforcement rather than claiming absolute proof.
- Claim outputs are "true" in subjective tasks; it claims they are produced and reviewed under the declared rubric and tier.
- Guarantee that payout release, settlement release, or TGE-sensitive eligibility has already been operationally released. Operational release policy can remain separate from canonical PHK truth.
PHK Design Goal
PHK is designed to make repeated low-effort, policy-violating, or synthetic submissions detectable, economically unattractive, and limited in impact, while enabling honest participants to build durable performance records.
Implementation note: Current live runtime access policy, validator readiness lanes, and bootstrap controls are documented in App Status. These controls affect operational access, not PHK truth authority.
Privacy and Cohort Targeting
Lioth is private by design: contributors are not required to reveal real-world identity. When tasks require specific attributes (e.g., region, expertise), Lioth supports zero-knowledge credentials to prove eligibility without exposing identity.
Use Cases
- Verified microtask and human evaluation workflows.
- Expert and group-restricted campaigns.
- Model evaluation datasets (judgment, preference, critique, safety).
- Forecasting datasets and probabilistic decision intelligence.
- Market research datasets and experiments (ranking, trade-offs, messaging tests).