Validate for credibility

Validation is where organizations quantify trust.

Through Validation Policies (VPs), they define how verified actions, proofs, or interactions contribute to a participant’s DISC Score and metric health.

Each VP is programmable, auditable, and cryptographically signed under the organization’s TRIS.org ID.

---

Key Capabilities

• Programmable Logic

  Define both positive and negative scoring logic for participant actions within your ecosystem.

• Metric Mapping

  Tag inputs to relevant DISC Metrics — Finance, Governance, Security, Compliance, and Sustainability.

• Criticality Weights Assign proportional impact multipliers (0.01 – 0.14) per event, with total policy weight constrained between 0.95 – 1.05.

• Version Control Maintain policy lineage (e.g., VP_FINANCE_V1 → VP_FINANCE_V2) for full traceability and audit consistency.

• Public or Private Visibility Select between open validation frameworks for transparency or internal scoring models for proprietary systems.

Each verified event — from loan repayment to validator uptime — becomes a standardized, measurable credibility signal within your ecosystem and beyond.

Validation Policies (VPs) are the programmable logic layer behind DISC. They determine how verified actions translate into trust data, forming the foundation of measurable, cross-platform credibility.

---

FAQs

How do Validation Policies differ from internal scoring models? VPs are verifiable, programmable frameworks recorded via hashed policy proofs. They enable transparent, reproducible credibility assessment instead of opaque, platform-specific scoring. Every VP is cryptographically signed under the organization’s TRIS.org ID, ensuring provenance, auditability, and tamper resistance.

Can an organization operate multiple VPs? Organizations can maintain one Validation Policy including both positive and negative trust logic. Validation Policies defines what actions earn users credibility on their platform versus actions that reduce it. This allows protocols to tailor trust dynamics precisely to their operational models while maintaining full interoperability with Tythe’s DISC framework.

How are VPs enforced and secured? All policy hashes are anchored in PolicyRegistry.sol on-chain, guaranteeing authenticity and version integrity. Computation occurs off-chain for scalability, while periodic Merkle root anchoring ensures proofs remain verifiable without exposing raw data.

Can organizations simulate policy outcomes before deployment? Yes. Developers can use the /v1/policies/vp/evaluate endpoint to simulate DISC Score and Metric Health Factor changes before activating a policy. This enables sandbox testing, validation of weight distribution (0.95–1.05 bounds), and prevention of scoring bias.

Can a VP be co-endorsed by other organizations? Yes. VPs can be submitted for community or DAO-based endorsement, enabling ecosystem-wide credibility interoperability.

---