Authenticate credibility

Validation Policies (VPs) let you define how trust is scored and enforced across your system.

Each VP is tied to your organization’s TRIS ID and describes what inputs matter, how much they matter, and under what context they should apply.

---

Create a Validation Policy (VP)

Note: Validation Policies (VPs) replace static scoring models with programmable rules that define how credibility is earned or lost. Each policy is recorded as a hashed proof in Tythe’s PolicyRegistry for auditability.

POST /v1/policies/vp
{
  "policy_id": "VP_LEND_V1",
  "tris_org": "tris:0xORG...",
  "inputs": [
    {"metric": "finance_loan_repayment_consistency", "criticality": "Critical", "weight": 0.14},
    {"metric": "finance_liquidity_provision_duration", "criticality": "High", "weight": 0.10},
    {"metric": "governance_vote_participation", "criticality": "Moderate", "weight": 0.07},
    {"metric": "security_multisig_participation", "criticality": "High", "weight": 0.10},
    {"metric": "compliance_kyc_verified", "criticality": "Critical", "weight": 0.14}
  ],
  "metadata": {
    "total_weight": 1.02,
    "visibility": "public",
    "version": "v1.0"
  }
}

---

Criticality Levels (Weights)

Level	Weight	Meaning
Minimal	0.01	Passive signal
Low	0.03	Common signal
Moderate	0.07	Meaningful signal
High	0.10	Significant signal
Critical	0.14	Definitive signal

Each VP must maintain a total weight between 0.95–1.05 to ensure interpretability and fairness.

Tip: Assign higher criticality levels to inputs that directly impact system integrity or core function reliability. For example, repayment consistency may weigh more than governance participation in a lending protocol.

---

FAQs

What is a Validation Policy (VP)? A VP defines how verified actions are scored and weighted to produce credibility outcomes. It replaces static, opaque scoring systems with programmable, auditable logic.

How are Validation Policies tied to organizations? Each VP is linked to the organization’s TRIS ID and versioned for accountability (e.g., VP_LEND_V1, VP_LEND_V2), ensuring every scoring policy remains traceable.

Can developers define multiple VPs? Yes. A single organization or developer can maintain multiple Validation Policies for distinct modules or systems (for example, separate policies for lending and staking).

What happens if the total VP weight exceeds the 1.05 limit? The VP fails validation. Tythe enforces a total weight requirement between 0.95 and 1.05 to preserve fairness and interpretability across the ecosystem.

Can I simulate a VP before deploying it? Yes. You can perform dry-run evaluations using the /v1/policies/vp/evaluate endpoint to preview DISC outcomes and metric adjustments before applying them.

Is VP evaluation automatic after each action? It depends on your integration model. You can call VP evaluation manually or integrate it directly into your protocol’s event listeners for real-time computation.

---