Full-text search across the DPC Zettelkasten — a knowledge base describing how the Dan's Plugins Community Minecraft plugins work (Medieval Factions and the repositories around it). Start here when you have a topic rather than a note id. Returns matching notes with summaries; follow up with get_note for the full text and its citations. Every claim in this collection is grounded in a file in a Dans-Plugins repository, pinned at a commit SHA. When you use a note, cite its sources rather than presenting the claim as your own knowledge — the permalinks are what make the answer checkable.

Fetch one note in full: its Markdown body, its links and backlinks, and every citation with a commit-pinned GitHub permalink. Use this once search_notes or list_maps has given you an id. Every claim in this collection is grounded in a file in a Dans-Plugins repository, pinned at a commit SHA. When you use a note, cite its sources rather than presenting the claim as your own knowledge — the permalinks are what make the answer checkable.

The structure of the collection: every Map of Content and the concept notes that call it home. Use this to orient before searching, or to answer 'what does this collection cover?'. Each concept note belongs to exactly one map.

Every source of truth behind a note, or across the whole collection — repository, file path, line range, the specific claim it supports, and a permalink pinned at a commit SHA. Use this to check whether a claim is actually supported, or to find which notes cite a given repository.

Run a GraphQL query against the collection's structure. Use this for questions the other tools cannot answer — which notes are most connected, what a cluster contains, which repositories ground the most claims, how two notes relate.

Read-only: no mutations, fragments, or variables. Inline argument values.

Examples: { notes(orderBy: degree, first: 5) { title degree moc { title } } } { notes(moc: "moc-faction-domain-model") { title summary } } { note(id: "demesne-limit") { title links { title } sources { claim url } } } { repositories { name citationCount noteCount } }

SCHEMA:

The zettelkasten as a graph. Read-only — queries only.

enum NoteType { concept moc } enum NoteOrder { title degree citations }

type Query { notes(type: NoteType, moc: ID, tag: String, repo: String, search: String, linkedTo: ID, orderBy: NoteOrder, first: Int): [Note!]! note(id: ID!): Note mocs: [Note!]! concepts(first: Int): [Note!]! tags: [Tag!]! repositories: [Repository!]! stats: Stats }

type Note { id: ID title: String type: NoteType summary: String tags: [String!]! updated: String path: String url: String moc: Note links(first: Int): [Note!]! backlinks(first: Int): [Note!]! neighbors(first: Int): [Note!]! linkCount: Int backlinkCount: Int degree: Int sources: [Source!]! sourceCount: Int repositories: [String!]! }

type Source { repo: String path: String ref: String shortRef: String lines: String claim: String url: String }

type Tag { name: String count: Int notes: [Note!]! }

type Repository { name: String url: String citationCount: Int noteCount: Int pinnedRefs: [String!]! notes: [Note!]! }

type Stats { noteCount: Int mocCount: Int conceptCount: Int citationCount: Int linkCount: Int repositoryCount: Int repositories: [String!]! updated: String }

The GraphQL schema for the collection, as SDL. Call this before writing a non-trivial query with the graphql tool.