Solve Unprocessed Inputs Before Search
The core thesis of a compiled knowledge base: fix unprocessed material before blaming search tools. Collecting more links never cures shallow synthesis.
Compile each source into a note with summary, personal judgment, links to prior ideas, and concrete reuse scenarios.
Key points
- Why does this source deserve keeping?
- Which belief did it update?
- What output can it power?
Exercise Select three saved sources and write one personal takeaway plus one reuse scenario for each.
Separate Raw, Wiki, and Outputs
Keep raw sources in raw/, synthesized insights in wiki/, operating conventions in schema, and navigation in index.md, letting articles and specs grow cleanly into outputs/.
Validate the workflow with plain Markdown files first—no heavy database required on day one.
Key points
- raw: immutable provenance
- wiki: curated synthesis
- index & outputs: navigation & shipping
Exercise Create three
wikiMarkdown entries and register them in anindex.mdwith one-line summaries.
Weave New Notes Back Into Old Ones
Ingestion does not end when a new file is saved. New evidence either supports, refines, or contradicts earlier notes—a step we call back-weaving.
Always explain why two notes connect instead of scattering unexplained backlinks.
Key points
- Which existing note relates?
- Does it support, extend, or conflict?
- How should the older note be updated?
Exercise Add one annotated relation to a new note and update the older note it refines.
Validate Your Knowledge Base by Shipping
Plain local Markdown remains the source of truth; indexes exist to serve retrieval, never to lock your writing inside proprietary silos.
The real test: can your notes produce a clear article, sharpen a product decision, or save you from repeating an old mistake?
Key points
- Traceable provenance
- Reusable personal judgments
- Produces a concrete artifact
Exercise Using only your three wiki notes, write a 200-word answer to a real question and mark any missing evidence.