How to Build an Obsidian Vault MOC from a Note Dump
MOCs invent note filenames. Link only titles in the dump. Not a daily-note pack.
The matching generator is the Obsidian Vault MOC from a Note Dump prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
MOC title from Inputs
Build an Obsidian Map of Content (MOC) from a pasted note dump. Link only notes that appear. Do not invent filenames. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Note dump (titles and one-line summaries): [Dump]
MOC title I allow: [Title]
Folder I may name (or UNKNOWN): [Folder]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Link style I lock ([[Note]] only): [Links]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Group themes from the dump
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Dump titles, Title, Folder, Links, Lang. Forbidden: inventing note names.
- MOC markdown with Title heading.
- Sections grouped by themes found in Dump only.
- Wiki-links only to titles in Dump.
- Orphans list: Dump notes not linked if any logic fails; otherwise none.
- Folder: if UNKNOWN, write FOLDER UNKNOWN.
- Refuse: inventing Dataview queries that require fields not in Dump, inventing daily note templates.
- Compliance pass: Banned and Never. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Wiki-link only existing titles
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Obsidian MOC from Dump only. Not a daily-note pack.
- Never invent note filenames.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse invented Dataview fields
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (obsidian vault moc, map of content from notes, obsidian note dump) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.