Design challenge and final knowledge check

This final lesson is a design exercise, not a coding project. Its purpose is to test whether you can reason from Intuition's primitives to a responsible product model.

The brief

Design a public directory that helps teams evaluate open-source packages. It should combine maintainership, audits, compatibility, recommendations, and warnings contributed by independent communities. No organization is the universal authority.

Before reading the worked model, write down:

1. the important entities and concepts;
2. three useful relationship types;
3. which claims require scope or time context;
4. who might support or oppose them;
5. what the interface must never imply.

A worked knowledge model

Possible atoms include packages, repositories, versions, maintainers, auditors, programming ecosystems, licenses, vulnerabilities, and concepts such as “production ready.” Some should remain distinct: a package is not its repository, and a package family is not a specific release.

Possible triples include:

• Nova — maintains → Atlas;
• Atlas 2.1 — audited by → Secure Labs;
• Atlas — compatible with → Helix;
• Mira — recommends → Atlas 2.1;
• Atlas 2.1 — affected by → vulnerability Q.

The version-specific terms prevent an old audit from silently applying to new code. Attributable recommendation triples preserve who made subjective judgments.

Signal and interpretation

Participants may signal support or opposition around identifiers and claims. The directory can use this activity for discovery, but raw totals should not become a safety score. A security view might prioritize recent auditor evidence; a maintenance view might prioritize current maintainers and release activity.

The interface should disclose the ranking policy and let users inspect evidence, sources, dates, opposition, and signal concentration.

Failure review

Before launch, test at least these risks:

• duplicate atoms split the package's history;
• a malicious atom impersonates a real repository;
• old claims appear current;
• wealthy participants dominate rankings;
• coordinated accounts manufacture support;
• a broad predicate such as “safe” hides audit scope;
• derived summaries lose their provenance;
• users read market activity as verification.

Final knowledge check

1. What is the difference between an atom and the real-world thing it identifies?Reveal answer

An atom is an addressable protocol identifier. Its metadata and relationships may help connect it to a real subject, but the identifier is not the subject and does not prove authenticity by itself.

2. What does creating a triple establish?Reveal answer

It establishes that a structured subject–predicate–object claim exists with recorded provenance. It does not automatically establish that the assertion is true.

3. Why does predicate choice matter?Reveal answer

The predicate defines the relationship's meaning and direction. Vague or fragmented predicates make reuse and interpretation unreliable.

4. What information does economic signal add?Reveal answer

It records economically backed positions, which may reveal conviction, attention, coordination, or opposition. It is evidence about participation, not certainty about the underlying meaning.

5. Why can a high-signal claim still be wrong?Reveal answer

Participants may be mistaken, strategic, coordinated, or unequally wealthy. Market state captures behavior under incentives, not all external evidence.

6. Why is an indexer distinct from the protocol?Reveal answer

The protocol governs authoritative state transitions. An indexer derives a convenient read model and may introduce latency, transformations, or calculated fields.

7. Name two signs of a strong Intuition use case.Reveal answer

Any two of these: independent parties share identifiers, claims need portable attribution, support and opposition matter, or multiple applications can compose the knowledge.

8. What is an application's central responsibility when presenting the graph?Reveal answer

It must make its interpretation honest: preserve relevant provenance and context, distinguish signal from verification, communicate limitations, and explain consequential ranking choices.

Official references

• Intuition use cases
• Intuition primitives
• Intuition economics