Wiki Schema

Domain（域）

This wiki is Buu’s personal explicit-knowledge wiki.
It is not a general encyclopedia and not a clone of Wikipedia.
It exists to accumulate Buu’s reusable explicit knowledge across domains over time.

“Explicit knowledge” here means knowledge that can be written, reviewed, compared, updated, linked, and reused.
That includes facts, definitions, standards, heuristics, judgments, decisions, comparisons, working methods, and structured observations.

Ownership（归属）

owner: Buu
maintainer: LLM-assisted

Primary Organization Principle（主要组织原则）

This wiki uses a mixed structure:

Objects matter: providers, models, tools, companies, people, projects
Decisions matter: how Buu evaluates, chooses, compares, and updates judgment

So the wiki is organized around both object pages and decision/query pages.

Directory Structure（目录结构）

wiki/

SCHEMA.md
index.md
log.md
raw/
- articles/
- papers/
- transcripts/
- assets/
entities/
concepts/
comparisons/
queries/
decisions/
source-notes/

Core Rules（核心规则）

File names must be lowercase with hyphens
Every wiki page must start with YAML frontmatter
Every page must be listed in index.md
Every change must be logged in log.md
Raw files in raw/ are immutable
Pages should use [[wikilinks]] to connect to related pages
Pages should distinguish facts from interpretation
Claims without sources must not be written as high-confidence conclusions

Required Frontmatter（必备前置字段）

---
title: Page Title
aliases: []
owner: Buu
created: YYYY-MM-DD
updated: YYYY-MM-DD
type: entity | concept | comparison | query | decision | source-note
status: active | tentative | archived
confidence: low | medium | high
tags: [from taxonomy below]
sources: [raw/articles/example.md]
related: [page-a, page-b]
---

Controlled Types（受控类型）

entity

Use for concrete objects:

company
provider
model
tool
person
project
product

concept

Use for concepts, frameworks, definitions, standards, recurring themes.

comparison

Use for side-by-side evaluation.
Must include comparison dimensions and a current conclusion.

query

Use for substantial questions with durable answers.
Not for trivial one-off lookups.

decision

Use for Buu’s actual standards, judgments, policies, preferences, and choice logic.
Examples:

how Buu evaluates provider real cost
when a tool is worth integrating
what counts as trustworthy pricing information

source-note

Use for structured notes derived from one source.
This is not the immutable raw source itself.
It is the interpreted, filed, reusable summary of a source.

Required Body Sections by Type（各类型必备正文结构）

entity pages must contain

Overview
Facts
Interpretation
Relevance to Buu
Related Pages
Open Questions
Next Checks

concept pages must contain

Definition
Facts
Interpretation
Boundaries / Non-Examples
Related Pages
Open Questions
Next Checks

comparison pages must contain

Scope
Compared Items
Comparison Table
Facts
Interpretation
Current Conclusion
Conditions / Caveats
Open Questions
Next Checks

query pages must contain

Question
Short Answer
Facts
Interpretation
Related Pages
Open Questions
Next Checks

decision pages must contain

Decision
Context
Criteria
Facts
Interpretation
Current Rule
Exceptions
Review Trigger
Related Pages

source-note pages must contain

Source Summary
Extracted Facts
Interpretation
Candidate Page Updates
Related Pages
Follow-up Questions

Add a new recurring tag here before using it widely.

Naming Rules（命名规则）

Use type-aware file names.

Visible page titles are human-facing. For formal wiki pages written for Buu,
prefer readable Chinese titles when natural.
For raw materials, keep the original source title as the visible title.
Preserve official spelling and casing for proper names such as products,
services, brands, and models in visible titles and first formal mentions.
For product-specific terms, prefer the exact English term from the product’s
code, docs, API, or UI, and pair it with the exact Chinese UI wording when
that wording is available.
If the same English concept uses different Chinese labels on different pages,
record the page-specific pair instead of forcing one global translation.
Filenames remain lowercase with hyphens as stable slugs; they do not need to
match the visible title exactly.
Use aliases for alternate names, abbreviations, multilingual variants, and
common spellings.

Examples:

entities/provider-fal-ai.md
entities/model-nano-banana-2.md
concepts/explicit-knowledge.md
comparisons/pricing-nano-banana-2-fal-vs-yunwu.md
queries/what-is-real-provider-cost.md
decisions/how-buu-evaluates-provider-cost.md
source-notes/fal-nano-banana-2-pricing-page.md

Creation Rules（创建规则）

Create an entity page when the object is likely to recur
Create a concept page when a term or framework needs a stable definition
Create a comparison page when the value comes from side-by-side evaluation
Create a query page when the answer would be annoying to reconstruct later
Create a decision page when Buu’s standard or rule is important enough to preserve
Create a source-note when a source contains reusable information but should not directly become a final conclusion page

Update Rules（更新规则）

Prefer updating an existing page over creating a duplicate
New facts go into the most specific relevant page
New judgments that affect choices should update decision pages
Contradictions must be stated explicitly, not silently overwritten
When confidence changes, update the confidence field
When a conclusion depends on weak evidence, keep status: tentative

Confidence Rules

low: weak evidence, provisional, or single-source observation
medium: usable working conclusion, but still revisable
high: well-supported, repeatedly confirmed, or stable enough for reuse

Distinguishing Facts vs Interpretation（区分事实与解释）

Facts:

what a source explicitly says
measurable numbers
direct quotations or direct data points

Interpretation:

comparisons
judgments
implications
Buu-oriented conclusions

Never collapse these into one undifferentiated block.

Growth Policy（增长策略）

This schema is intentionally strong.
It is designed so LLMs can maintain the wiki consistently even when they are not very smart.
Future refinement is allowed, but changes should preserve stability unless a better long-term structure is clearly needed.

Tags should begin from the current controlled set and grow gradually. Add new tags
only when they recur and clearly improve retrieval or organization.

Buu Wiki

Explorer