Wiki Schema

Domain

This wiki is a personal second brain: a durable, interlinked knowledge base for projects, people, meetings, IdeaFlow notes, useful decisions, and recurring workflows.

The goal is to preserve context that compounds over time: what matters, who is involved, why decisions were made, what changed, what patterns recur, and what workflows should be reused.

Conventions

• File names: lowercase, hyphens, no spaces (e.g., project-alpha.md, weekly-review-workflow.md).
• Every wiki page starts with YAML frontmatter using the schema below.
• Use [[wikilinks]] to link between pages. Aim for at least 2 outbound links per page once enough pages exist.
• When updating a page, always bump the updated date.
• Every new page must be added to index.md under the correct section.
• Every action must be appended to log.md.
• Keep pages scannable: summarize first, details later.
• Prefer stable synthesized context over raw transcripts. Put source material in raw/; put durable conclusions in wiki pages.
• Do not store private secrets, credentials, tokens, passwords, or sensitive personal data unless explicitly directed.
• Mark uncertainty. If a conclusion is tentative, set confidence: low or medium and explain why.
• Provenance markers: On pages that synthesize 3+ sources, append markers like ^[raw/transcripts/source-file.md] or ^[raw/articles/source-file.md] at the end of paragraphs whose claims come from specific raw sources.

Directory Structure

wiki/

├── SCHEMA.md

├── index.md

├── log.md

├── raw/

│   ├── articles/       # Clippings, external docs, useful references

│   ├── papers/         # Papers, reports, long-form PDFs

│   ├── transcripts/    # Meetings, calls, interviews, voice-note transcripts

│   └── assets/         # Images, diagrams, screenshots

├── entities/           # People, organizations, tools, products, projects if entity-like

├── concepts/           # Ideas, principles, topics, recurring themes, workflows

├── comparisons/        # Tradeoff analyses and decision comparisons

├── queries/            # Filed answers worth preserving

├── _meta/              # Topic maps, maintenance notes, navigation helpers

└── _archive/           # Superseded pages

Frontmatter

Every wiki page in entities/, concepts/, comparisons/, and queries/ must begin with:

---

title: Page Title

created: YYYY-MM-DD

updated: YYYY-MM-DD

type: entity | concept | comparison | query | summary

tags: [from taxonomy below]

sources: [raw/transcripts/source-name.md]

# Optional quality signals:

confidence: high | medium | low

contested: true

contradictions: [other-page-slug]

status: active | dormant | archived | reference

---

Notes:

• sources may be empty ([]) for pages created from direct user instruction rather than a source file.
• confidence: high means the page is well-supported or directly user-confirmed.
• confidence: medium means useful but not fully corroborated.
• confidence: low means tentative, inferred, stale, or needs review.
• Use status especially for projects and workflows.

raw/ Frontmatter

Raw sources should be immutable and begin with:

---

source_url: https://example.com/article   # original URL, if applicable

ingested: YYYY-MM-DD

sha256: <hex digest of the raw content below the frontmatter>

source_type: article | paper | transcript | clipping | note | asset

---

Compute sha256 over the body only, after the closing ---. Future re-ingests should compare hashes to detect unchanged sources or drift.

Tag Taxonomy

Add new tags here before using them.

Core domains

• project — projects, initiatives, deliverables, programs
• person — people, collaborators, stakeholders, mentors
• organization — companies, teams, communities, institutions
• meeting — meeting summaries, recurring calls, discussion context
• ideaflow — IdeaFlow notes, idea capture, thought streams
• decision — useful decisions, rationale, tradeoffs, commitments
• workflow — repeatable processes, operating procedures, habits
• reference — external knowledge, useful docs, reusable facts

Project/work tracking

• goal — goals, outcomes, success criteria
• milestone — phases, deadlines, checkpoints
• risk — blockers, risks, constraints, open issues
• dependency — prerequisites, linked systems, external dependencies
• status — current state, progress snapshots, lifecycle notes

People/context

• relationship — who works with whom, responsibilities, communication preferences
• stakeholder — decision makers, reviewers, users, customers
• communication — messaging patterns, meeting notes, expectations

Thinking and synthesis

• idea — concepts, speculative notes, hypotheses
• principle — durable beliefs, heuristics, operating rules
• question — unresolved questions, research prompts, unknowns
• comparison — tradeoffs, side-by-side analyses
• retrospective — lessons learned, after-action reviews

Meta and maintenance

• meta — wiki maintenance, structure, taxonomy, index helpers
• archive — archived or superseded material

Rule: every tag on a page must appear in this taxonomy. If a new tag is needed, add it here first, then use it.

Page Thresholds

• Create a page when a project, person, workflow, decision, or concept is central to a source or likely to recur.
• Add to an existing page when new material mentions something already covered.
• Do not create pages for passing mentions, one-off details, or context unlikely to be reused.
• Split a page when it exceeds about 200 lines or starts mixing unrelated concerns.
• Archive a page when its content is fully superseded: move it to _archive/, remove it from index.md, and update backlinks.

Page Types

Entity Pages

Use for people, organizations, tools, products, and project-like entities.

Include:

• Overview / what it is
• Current status or relationship to the user
• Key facts, dates, and responsibilities
• Relevant decisions, meetings, and workflows
• Relationships to other entities via [[wikilinks]]
• Open questions or follow-ups if useful

Concept Pages

Use for ideas, workflows, recurring themes, principles, and topic notes.

Include:

• Definition or purpose
• When it applies
• Current best understanding
• Related projects, people, decisions, and workflows via [[wikilinks]]
• Examples or source references

Meeting Pages

Meeting pages may live in concepts/ if they describe a recurring meeting pattern, or in queries/ if they are filed summaries. Raw transcripts belong in raw/transcripts/.

For meeting synthesis pages, include:

• Date or recurrence
• Attendees / related people
• Decisions made
• Action items or unresolved questions
• Links to related projects and decisions

Decision Pages

Use type: concept with tag decision, or type: comparison for explicit tradeoffs.

Include:

• Decision statement
• Date and decision maker(s), if known
• Options considered
• Rationale
• Consequences / follow-ups
• Links to affected projects and workflows

Workflow Pages

Use type: concept with tag workflow.

Include:

• Trigger: when to use the workflow
• Steps
• Inputs and outputs
• Pitfalls
• Verification / definition of done
• Links to related projects or decisions

Comparison Pages

Side-by-side analyses. Include:

• What is being compared and why
• Dimensions of comparison, preferably as a table
• Verdict or synthesis
• Sources and confidence

Query Pages

Filed answers worth preserving. Include:

• Question asked
• Short answer
• Evidence / linked pages
• Follow-up questions

Update Policy

When new information conflicts with existing content:

1. Check dates and source quality.
2. Do not silently overwrite important prior conclusions.
3. Note both positions with dates and sources.
4. If genuinely contradictory, mark contested: true and add contradictions: [page-slug] in frontmatter.
5. Flag for user review in the log entry or lint report.

Index Policy

• index.md is the navigational catalog.
• Every wiki page must appear exactly once under the correct section.
• Entries should be one line: - [[page-slug]] — short summary.
• Keep entries alphabetical within each section.
• Update the index date and total page count after creating, archiving, or deleting pages.

Log Policy

• log.md is append-only.
• Every action gets an entry: create, ingest, update, query, lint, archive, delete.
• Format: ## [YYYY-MM-DD] action | subject.
• List files created or updated.
• Rotate when over 500 entries: rename to log-YYYY.md and start a new log.md.

Lint Expectations

A healthy wiki has:

• No broken wikilinks.
• Few or no orphan pages.
• All pages listed in index.md.
• Required frontmatter on every wiki page.
• Tags limited to this taxonomy.
• Low-confidence and contested pages visible for review.
• Raw source hashes intact.