Oracle

Knowledge management — documentation and wiki for game development projects.

Oracle is where you write. Game design documents, lore bibles, marketing plans, meeting notes, technical specs — all stored as rich text inside your project vault.

Think of it as Obsidian or Notion, but integrated with the game data in Forge. A character sheet you wrote in Oracle can link directly to the same character's authored stats in Forge, and a wikilink in either direction stays alive.

Who Oracle is for

Any game developer who needs to write and organise project documentation. Oracle is intended as the free entry point to GameDevBuddy — the module that gets people in the door.

Pricing: Free, ships with the base app.

What Oracle gives you

• A Plate.js rich-text editor with split source-mode (CodeMirror)
• Wikilinks: [[link]], [[link|alias]], [[link#section]], with autocomplete
• Backlinks across the whole vault, including unlinked mentions
• A graph view of how your notes connect
• Embeds — ![[note]], ![[image.png]], PDFs, all transcluded
• YAML frontmatter editing
• Eight built-in game-dev templates (GDD, Level Design, Character Sheet, …)
• Daily notes with date-organised folders
• Canvas — Obsidian-compatible .canvas boards
• Full-text search, hierarchical tags, version history with diff & restore
• Vault import from Obsidian (with wikilink conversion) or Notion

Concepts

A few key ideas to get oriented:

• Vault — the folder of .md files that backs an Oracle project. One vault per project.
• Wikilink — [[Some Note]] is a soft, name-based link. Renames are propagated.
• Backlink — every note shows you which other notes link to it.
• Frontmatter — YAML at the top of a note, used for tags, status, custom fields. Forge entities surface their key fields here so you can filter docs by character / location / etc.

Next steps

• Wikilinks — the heart of Oracle's linking model
• Backlinks — finding what points where
• Embeds — transcluding notes, images and PDFs
• Frontmatter — tagging and structured fields