Build a category map, not a pile of disconnected facts

A list of isolated cue-and-answer pairs can create a large deck without creating a useful mental structure. A category map starts with entities and typed relationships: person created work, event occurred in place and period, concept contrasts with neighbor, title belongs to form, source supports claim. The map does not replace retrieval practice; it gives practice more meaningful routes.

Choose a bounded category question

Begin with a question such as which relationships distinguish two nearby movements, how a set of works connects to creators and periods, or where a scientific term sits in a process. Set an initial boundary and a stopping rule. A map that tries to contain all knowledge becomes another unreviewable pile.

• Name the category and the decision it should support
• List the core entity kinds
• Choose a small closed set of relationship labels
• Attach a source to every objective edge
• Keep conflicting or review-only observations separate
• Mark missing coverage instead of inventing connective tissue

Turn edges into two-way prompts

A relationship supports several cues: creator to work, work to creator, event to date, date to event, item to category, and category to examples. Not every direction deserves equal practice. Select the direction that matches the intended retrieval job, then occasionally test the reverse or a contrast to expose shallow association.

A graph edge is an evidence-bound observation, not automatic truth, causality, endorsement, or identity. Review-only edges should not become confident study cards.

Use the graph to find coverage gaps

Count opportunities by entity kind, relationship, subcategory, and source—not only total cards. A dense cluster can make the library look rich while entire branches remain absent. Coverage metrics should report the known corpus boundary and avoid implying that the publication has measured the universe of possible material.

Keep presentation objective-specific

Use a timeline for chronological sequences, a hierarchy only when the relationship is truly single-parent, and a capped local neighborhood for exploration. A force-directed hairball is not a study plan. The renderer should state its visible-vertex limit and the layout objective, then give the learner a textual path that works without the graphic.

Export only the public layer

The public subject graph may carry reviewed source and content metadata. The learner's cards, responses, confidence, timing, weak areas, notes, and private category map remain in product-private storage. A public graph can help discover evidence; it must never become a profile of an individual's knowledge.

Explore the release-bound Jeopardy graph capability; the current source-only release may correctly report that category content is unavailable.