Intuition primary sources — 2026-05-10

What I reviewed

Key takeaways from primary sources

  • Intuition’s core reusable mechanism is the split between Atoms, Triples, and Signals: identifiers, claims, and economically weighted conviction are separate protocol objects rather than one merged attestation record.
  • The primitives docs show that the protocol is trying to build a recursively composable semantic graph, not just a list of credentials. Triples can themselves become referents for later Triples.
  • The economics docs matter as much as the semantic model. Intuition is not only asserting that knowledge should be structured; it is asserting that identifier creation, claim reuse, and schema adoption should be shaped by bonding curves and token incentives.
  • The strongest control-surface insight is canonicalization. If anyone can create an identifier for anything, the important question becomes what pushes participants toward shared identifiers and predicates instead of endless duplication.
  • The docs and repo positioning make clear that Intuition wants to sit beneath applications as a portable data layer, with SDK, GraphQL, and network components supporting reuse across apps, chains, and AI systems.
  • This puts Intuition adjacent to but distinct from EAS, Sign Protocol, OpenRank, and Human Passport: it is upstream of score computation and downstream of raw unstructured data, trying to make the graph itself economically legible.

Specific source signals worth retaining

  • Intro docs: best concise statement of the protocol thesis that Intuition decentralizes information, trust, ownership, discoverability, and monetization rather than just social identity.
  • Primitives docs: strongest explanation of Atoms, Triples, Signals, recursive composition, and why the system is more than a flat attestation table.
  • Economics docs: key evidence for the token-curated and convergence-seeking design, especially around bonding curves, early-mover rewards, and standards alignment.
  • Whitepapers portal: useful because it shows the team treats the protocol, token, and AgentRank as related but separable documents.
  • Docs repo: confirms the protocol is being developed as a reusable stack with dedicated docs for contracts, network, node operation, GraphQL, and SDK usage.

Why this entry belongs in the corpus

  • It adds a mechanism-rich identity / attestation / knowledge-graph project that is not reducible to a wallet-login spec or a credential issuance registry.
  • It sharpens comparisons across EAS, Sign Protocol, OpenRank, Human Passport, and Ethereum Follow Protocol by isolating a different layer: canonical identifier formation and economically weighted graph construction.
  • The reusable insight is that decentralized trust systems do not only compete on who can issue attestations or compute rankings. They also compete on how a shared graph gets named, merged, weighted, and made canonical enough for downstream reuse.