All learning paths
Complete pathNo coding required

New to Intuition

Understand Intuition

Build the complete mental model, inspect the live graph, and decide where your skills fit before writing code.

Beginner 3h 25m 15 steps

You will leave able to

Explain Intuition clearly, evaluate a graph-shaped use case, and choose the right specialist path.

One complete course

All 12 Intuition Foundations lessons, kept in their original theory-first curriculum.

Three field activities

Observe the live graph, interpret signal, and test a product idea without writing code.

Responsible by design

Every exercise separates protocol evidence, application inference, and unresolved uncertainty.

Your path progress

Lessons sync with the Foundations course. Activities and progress stay in this browser—no account required.

0 / 15 steps

1

Orient

See the problem clearly

Understand the information problem, Intuition’s thesis, and the boundaries of each system layer.

  1. 1
    Course lesson 12 min

    The internet's information problem

    Why abundant information can still be difficult to identify, verify, reuse, and trust across applications.

  2. 2
    Course lesson 12 min

    What Intuition changes

    The protocol thesis: make claims structured, attributable, composable, and economically signalable.

  3. 3
    Course lesson 13 min

    The Intuition system at a glance

    A high-level map of the network, protocol, indexing, and application layers—and the boundaries between them.

2

Model

Learn the graph’s language

Move from identifiers to explicit claims, then inspect how those ideas appear in a live interface.

  1. 4
    Course lesson 12 min

    Atoms: identity for anything

    How Intuition gives people, concepts, files, and claims reusable identifiers—and why canonical identity is a design problem.

  2. 5
    Course lesson 13 min

    Triples: claims as relationships

    How subject-predicate-object structure turns human assertions into explicit, reusable graph relationships.

  3. 6
    Course lesson 13 min

    Context, composition, and provenance

    How graph relationships become more expressive without losing who asserted what and under which conditions.

  4. 7
    No-code field activity 15 min

    Inspect one real claim in the Portal

    Translate a live graph object back into the atoms, relationship, provenance, and context you just learned.

    Open
    1. Open the Portal and choose one person, project, organization, or concept you can recognize.
    2. Identify the atom used to represent it. Note which metadata helps you believe it refers to the intended subject.
    3. Find one connected claim and rewrite it explicitly as subject — predicate — object.
    4. Identify who created or supported the claim and what evidence or context is visible.
    5. Write down one important detail the interface does not establish.
    Your deliverable

    A short claim record containing the atom, one triple, its visible provenance, and one unresolved uncertainty.

    Open Intuition Portal
3

Interpret

Read conviction without calling it truth

Understand signal and incentives, then practice describing market-weighted information honestly.

  1. 8
    Course lesson 13 min

    Signals: conviction, not truth

    What economic signal adds to a claim, what opposing positions reveal, and why weight must never be presented as certainty.

  2. 9
    Course lesson 14 min

    Vaults, shares, and information markets

    A conceptual model of the containers and accounting that let participants take economic positions around knowledge.

  3. 10
    Course lesson 14 min

    Incentives, canonicalization, and failure modes

    How economic coordination can strengthen a knowledge graph—and the manipulation, fragmentation, and bias it can introduce.

  4. 11
    No-code field activity 15 min

    Write an honest signal interpretation

    Practice turning support and opposition into a useful explanation without promoting economic weight into truth.

    Open
    1. Choose an atom or claim with visible economic activity.
    2. Record the support, opposition, position count, or other signal the interface exposes.
    3. Separate what you directly observed from what you are tempted to infer.
    4. Name one alternative explanation for the activity, such as popularity, speculation, coordination, or early discovery.
    5. Write the precise label you would show a user instead of “verified,” “true,” or “safe.”
    Your deliverable

    A five-line interpretation that states the observed signal, its provenance, a plausible inference, an alternative explanation, and an honest UI label.

    Inspect signal in Portal
4

Decide

Recognize a strong use case

Apply the complete mental model to a product idea and choose the specialist path that fits.

  1. 12
    Course lesson 12 min

    Reading the graph responsibly

    How applications move from indexed protocol data to interpretations without concealing provenance, latency, or uncertainty.

  2. 13
    Course lesson 13 min

    Recognizing strong Intuition use cases

    A framework for deciding when shared identifiers, claims, provenance, and economic signal materially improve a product.

  3. 14
    Course lesson 14 min

    Design challenge and final knowledge check

    Apply the complete Foundations model to a package-trust directory, then test the distinctions that make Intuition products credible.

  4. 15
    No-code field activity 20 min

    Write your Intuition fit memo

    Use the course’s four-part fit test to decide whether an idea deserves shared protocol infrastructure.

    Open
    1. Name one product or feature you might want to improve with Intuition.
    2. Identify the entities that independent applications would need to recognize as the same things.
    3. List the claims that become more useful when they are portable and attributable.
    4. Explain whether plural support and opposition add meaningful information.
    5. Describe how another application could reuse or extend the resulting graph.
    6. Name the privacy, permanence, incentive, or interpretation risk introduced by making this shared.
    7. Conclude with “use Intuition,” “use a conventional database,” or “research further,” and defend the decision.
    Your deliverable

    A one-page decision memo plus your recommended next path: app, data, onchain integration, or agent trust.

After Foundations

Choose what you want to make useful.

Your fit memo should make the next direction clearer. These specialist curricula remain visible while their courses and labs are being verified.

Frontend and full-stack builders

Build an Intuition App

Ship a Testnet application with graph reads, wallet UX, and protocol writes.

Curriculum preview

Data and backend builders

Query and Interpret the Graph

Ship a provenance-aware graph explorer, dashboard, or ranking system.

Curriculum preview

Smart contract builders

Integrate Intuition Onchain

Build and test a contract-level integration against Intuition Testnet.

Curriculum preview

AI and agent builders

Build Agent Trust Systems

Ship an agent context or ERC-8004 trust integration with inspectable provenance.

Curriculum preview