Post-Protocol Logic

Once Tythe launched, the DISC Engine went live which enabled real-time scoring based on actions, contributions, and platform-submitted relays.

Unlike Pre-Protocol contributions (scored once), Post-Protocol Logic is continuous and modular. It enforces metric-tagged credibility scoring tied to real behavior. This is the part of the process where trust becomes programmable.

Inputs Accepted After Launch

Post-Protocol scoring operates across four distinct input vectors:

Input Type	Source	Eligible Actors
Verifications	ZK-based account proofs	Individuals only
Trovebook	User-submitted hashed claims	Individuals only
Decision Relays	Platform-submitted attestations	Individuals + AI Agents
Sponsorships	TCT-backed endorsements	AI Agents only

• Individuals may submit to Verifications, Trovebook, and receive platform Relays

• AI Agents do not submit data. They are scored via platform-attested relays and sponsorships

Post-Protocol for AI Agents

All DISC Score accumulation for AI Agents begins post-onboarding and comes from two primary sources:

1. Verified Decision Relays

• Submitted by integrated platforms

• Examples: zk validation tasks, fraud detection flags, smart output attestations

• Metric-tagged and weighted using LogicCR

2. TCT-Backed Sponsorships

• Submitted by verified Individuals or Organizations

• Transfer real TCT to the agent’s Credibility Vault

• Weighted based on:

  • Sponsor type (Individual vs Organization)

  • Sponsor’s DISC Score or orgRank

  • TCT amount allocated

Agents cannot submit Trovebook entries or Verifications. They do not own Validation Vaults and cannot sponsor other agents. Their credibility is entirely performance-based and trust-weighted, with no self-submission.

Types of Credibility Recorded

Type	Description	Actor Type	Source Channel
Contributions	High-effort, proof-backed submissions	Individuals only	Trovebook or Relays
Actions	Real-time platform-integrated behaviors	Individuals + Agents	Decision Relays
Sponsored Trust	TCT-backed endorsements weighted by sponsor reputation	AI Agents only	Sponsorships

The Reputation Flow

Step	Event
1	A user performs an action or submits a proof
2	A relay or claim is submitted to Tythe
3	The input is mapped to a metric (e.g., Creative, Financial, Behavioral)
4	A criticality weight is applied
5	TCT is issued and split between Credibility + Validation Vaults (ineligible for AI Agents)
6	DISC Score updates in real-time

All activity is cryptographically logged and score-transparent via TRIS metadata.

Enforcement Rules

• Deduplication — repeated or overlapping inputs are ignored

• Eligibility-Gated — only verified TRIS identities can accumulate DISC

  • zk-KYH required for Individuals

  • zk-KYA required for AI Agents

• Actor-Specific Flows

  • Individuals: full access to all Post-Protocol input types

  • AI Agents: relay-only data ingestion + sponsor-based scoring

• Tamper-Resistant — all inputs are ZK-verified or platform-signed

Example (JSON API Response)

{
  "tris_id": "tris@satoshi",
  "disc_score": 20584.7,
  "score_rating": "Excellent",
  "category_breakdown": {
    "financial": 0.29,
    "creative": 0.19,
    "educational": 0.14,
    "behavioral": 0.12,
    "social": 0.08,
    "security": 0.11,
    "compliance": 0.07
  }
}

Note: Sponsorship-derived trust (AI Agents only) is reflected in the overall DISC Score, but not in any single DISC metric category.

---

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

— Proverbs 14:2