Imperial Sourcebook

Imperial Sourcebook is the sibling Obsidian vault for durable knowledge, study material, reference notes, worked examples, collected readings, and source-driven writing that should stay useful beyond the project or moment that produced it.

Why This Vault Exists

This vault was split out of Imperial Records so long-lived knowledge can grow separately from execution, maintenance, and rough capture. The goal is to make reference material easier to revisit, reorganize, and connect without crowding the main operational vault.

Relationship To Imperial Records

D:\Imperial Records is the main vault. Use it for capture, active projects, ongoing areas, experiments, prompts, future commitments, and daily operations.

D:\Imperial Sourcebook is the knowledge vault. Use it for material that should remain useful after the immediate task is done: study notes, reusable references, source clippings after triage, worked examples, readings, design references, and practical advice.

Records points here through its Resources marker folder. Sourcebook points back through this root documentation and PATH.md; no reciprocal marker folder is needed here.

Top-Level Map

• Bahas Soal: worked solutions, formula support, and practice breakdowns.
• Clippings: imported source material that belongs in Sourcebook but still needs cleanup, extraction, or routing.
• Collected Readings: curated readings, grouped excerpts, and texts worth keeping together.
• Curiosity Shelf: books, topics, and references worth keeping visible before mastery.
• Design: design study notes, design class material, and visual or product references.
• Glossary: atomic term-definition entries for concepts that need a canonical short definition.
• Inbox: low-friction intake for material already meant for Sourcebook.
• Language: language-specific dictionaries and compact reference notes, organized by language.
• Learning & Skills: study notes, technical references, learning systems, and skill-building material.
• Motivation: short notes that restore perspective or momentum.
• Notes: broad source-driven notes, topical references, and Notes/Random Questions for open curiosities.
• People: canonical pages for authors, mentors, scientists, and other repeatedly referenced people.
• Personal Advice: practical guidance, self-management material, and Personal Advice/Tips and Trick for compact tactical reminders.
• Science Reference: compact formulas, constants, theorems, laws, and science theory notes.
• Tugas: assignment outputs and school-task material worth preserving as reference.
• Tools & Software Reference: Obsidian, VS Code, CLI, Git, and other software reference guides.
• Attachments: supporting files only. Keep meaning, summaries, and decisions in markdown notes.

How To Use This Vault

1. Put operational capture, project plans, recurring systems, experiments, and future commitments in D:\Imperial Records.
2. Put source-heavy or topical knowledge in Notes, Clippings, Collected Readings, or Learning & Skills based on its role.
3. Keep atomic term definitions in Glossary, and keep author or thinker reference pages in People.
4. Keep language-specific vocabulary dictionaries and compact language references in Language.
5. Keep worked exercises and formula support in Bahas Soal.
6. Keep pre-mastery books, topics, and frontier references in Curiosity Shelf until they become active study or durable notes.
7. Store design references and design study material in Design.
8. Store practical rereadable guidance in Personal Advice, using Personal Advice/Tips and Trick for compact reminders and Motivation for short reset notes.
9. Store reusable formulas, constants, theorems, laws, and science theory in Science Reference when they are not worked solutions.
10. Store stable software guides in Tools & Software Reference rather than mixing tool manuals into learning notes.
11. Park unanswered knowledge questions in Notes/Random Questions.
12. Use Sourcebook Inbox only for knowledge material already destined for this vault.
13. Keep raw files in Attachments, but keep context, summaries, and decisions in markdown.

Conventions

• Prefer one clear note, question, source, or concept per file when possible.
• Use the nearest folder README.md before creating a new bucket or filing ambiguous notes.
• Let folders describe role; let note titles describe the specific material inside them.
• Keep article-derived notes close to their source role, then refine them when they become durable.
• Keep Glossary flat until repeated domain terms justify a split such as Math Glossary or Bio Glossary.
• Keep future commitments in D:\Imperial Records\Labs\Idea Backlog, not in this reference vault.
• Do not create new top-level buckets unless the existing map cannot hold the material clearly.

What Does Not Belong

• active project planning and deliverables that belong in D:\Imperial Records\Projects
• recurring operational systems that belong in D:\Imperial Records\Areas
• experiments, prompt work, and unstable tools that belong in D:\Imperial Records\Labs
• general rough capture that belongs in D:\Imperial Records\Inbox
• attachment-only storage without a markdown note carrying context

Review Rhythm

• Review Inbox and Clippings when they start hiding useful material.
• Review Notes, Learning & Skills, and Bahas Soal when a topic starts repeating.
• Promote or split material only when it improves retrieval.
• Prune low-value duplicates instead of adding structure too early.