Post-Protocol Logic

Once Tythe is live, all credibility scoring is governed by the DISC Engine — a decentralized system that processes verified behavior in real time. Unlike pre-launch logic, which depends on proof-based contribution seeding, Post-Protocol Logic evaluates every action, contribution, or validation as it happens.

This phase of scoring supports two primary input types:

1. Third-Party Attested — platform-submitted decision relays

2. Self-Attested — user-submitted contributions verified through Trovebook or Reclaim

Together, they form the post-launch backbone of DISC Score enforcement.

Reputation Flow (Post-Protocol)

1. A behavior or contribution occurs

2. The input is submitted to Tythe (by a platform or the user)

3. It is mapped to one or more metric categories (e.g. Creative, Financial)

4. TCT is issued, automatically split between the user’s two vaults

5. Their DISC Score is updated using Credibility Vault holdings

6. The score becomes visible across the network

All scoring is:

• Modular – Platforms choose metrics; users submit proofs

• Weighted – Criticality defines the TCT impact

• ZK-Compliant – No personal data is stored or exposed

• Permanent – Every issuance is cryptographically logged

Input Type 1: Third-Party Attested (Decision Relays)

• Submitted by integrated platforms via Tythe’s API

• Mapped to a pre-approved metric (e.g. creative_code_contribution, behavioral_peer_feedback_score)

• Carries a platform-assigned criticality weight

• Automatically triggers TCT issuance

This method ensures:

• Verifiable behavioral events can be scored immediately

• Platform incentives align with ecosystem credibility

• No fake claims — only recorded platform activity counts

Input Type 2: Self-Attested (User-Submitted Contributions)

• Users may submit new off-chain or on-chain contributions after onboarding

• Contributions must be proven through:

 – Trovebook ZK Proofs (locally hashed contribution metadata)

 – Reclaim Protocol (for verifying ownership of off-chain profiles like GitHub or X)

• Tythe’s review mechanism ensures off-chain inputs are:

 – Unrepeated across TRIS IDs

 – Impact-weighted

 – Tied to the correct user identity

Score Calculation

Your DISC Score = total TCT in your Credibility Vault

• Validation Vault TCT does not affect the score

• Every valid input (relay or proof) increases the score permanently

• TCT issuance is tamper-proof, non-transferable, and capped by impact

Score Behavior Rules

• Scores can only increase with verified input

• TCT cannot be bought, traded, or reallocated

• TRIS IDs with BAD Status may have scores frozen, capped, or reset

• Credonations amplify perceived trust, but never inflate the raw TCT base

Snapshot Format

The DISC Score endpoint returns real-time scoring data for any TRIS ID, including category weightings and rating metadata:

Example output from GET /api/DISC-score/{tris_id} (json):

{ "tris_id": "tris@satoshi", "DISC_score": 19877.4, "Rating": "Excellent", "category_breakdown": { "financial": 0.16, "creative": 0.22, "educational": 0.15, "behavioral": 0.12, "social": 0.09, "security": 0.15, "compliance": 0.11 } }

---

“Whoever walks in uprightness fears the Lord, but he who is devious in his ways despises Him.”

— Proverbs 14:2