Trovebook

The Trovebook is Tythe’s protocol-native memory system. It records, verifies, and anchors credibility signals under each TRIS ID using a structured metadata schema. Though only individuals can submit entries, all actors (Individuals, AI Agents, and Organizations) have Trovebook memory capabilities.

Individuals

For individuals, the Trovebook stores:

  • Validated Trovebook submissions

  • External verifications (via systems like Reclaim, Kaito, and credit or academic data providers)

  • Decision Relays received from integrated validators

All entries are wallet-specific but unified under the individual’s TRIS identity. This ensures traceability by both action and actor.

Organizations

Organizations do not receive DISC Scores and cannot submit entries. Their Trovebooks instead log:

  • All validations they have issued

  • Each validation’s recipient, action, metric, criticality, and timestamp

  • Cryptographic signature metadata for auditability

This serves as a reverse ledger of organizational credibility enforcement.

AI Agents

AI Agents cannot submit inputs, but their Trovebook records:

  • Their registrant’s TRIS ID

  • All Decision Relays received

  • Sponsor information, including the date, sponsor TRIS, and trust weight

This allows traceable agent accountability without compromising their pseudonymity.

Metadata Structure

All Trovebook entries include:

  • TRIS ID

  • Wallet address (if applicable)

  • Actor class

  • Input type

  • Metric classification

  • Criticality level

  • Source entity

  • zk-hash of submission

  • Timestamp

Each entry is zk-anchored and immutably stored. Invalidated or disqualified entries are flagged and moved to a quarantine ledger for audit and potential reinclusion.

Querying & Disclosure

Trovebook data can be selectively disclosed for:

  • Access control

  • Attestation issuance

  • Protocol integrations

  • Trust or compliance verifications

All querying respects cryptographic access control, ensuring privacy-preserving exposure of only the requested data scope.

Last updated