# Wiki Flavors

Use these as starting points. The wiki's `wiki.config.md` can override any structure.

## Research Wiki

Best for an ongoing topic with many source types.

Suggested pages:

- `wiki/index.md` for overview and navigation.
- `wiki/maps/research-map.md` for the conceptual map.
- `wiki/concepts/<concept>.md` for durable ideas.
- `wiki/sources/<source>.md` for important source writeups.
- `wiki/questions/<question>.md` for open investigations.
- `derived/briefs/` for synthesis memos and outlines.

## Paper Wiki

Best for a paper, cluster of papers, or literature review.

Suggested pages:

- `wiki/index.md` for paper set overview.
- `wiki/papers/<paper-slug>.md` for individual papers.
- `wiki/concepts/<concept>.md` for reusable technical ideas.
- `wiki/comparisons/<topic>.md` for cross-paper comparisons.
- `wiki/questions/<question>.md` for research gaps.

Paper pages should usually cover problem, method, results, limitations, implementation notes, and related papers.

## Domain Wiki

Best for learning or tracking an entire field.

Suggested pages:

- `wiki/index.md` for high-level map.
- `wiki/landscape.md` for actors, concepts, tools, and debates.
- `wiki/timelines/<topic>.md` for historical development.
- `wiki/glossary.md` for terms.
- `wiki/questions/<question>.md` for active uncertainties.

## Product Wiki

Best for products, tools, APIs, or platforms.

Suggested pages:

- `wiki/index.md` for product summary.
- `wiki/features/<feature>.md` for feature pages.
- `wiki/use-cases/<use-case>.md` for applied workflows.
- `wiki/competitors/<competitor>.md` for alternatives.
- `wiki/questions/<question>.md` for evaluation gaps.

Product pages should distinguish documented behavior, observed behavior, pricing or availability, limitations, and integration notes.

## Person Wiki

Best for a researcher, founder, writer, or public expert.

Suggested pages:

- `wiki/index.md` for profile and navigation.
- `wiki/work/<work-slug>.md` for papers, talks, posts, projects, or artifacts.
- `wiki/themes/<theme>.md` for recurring ideas.
- `wiki/timeline.md` for dated milestones.
- `wiki/questions/<question>.md` for unresolved context.

Use source-grounded language and avoid unsupported biographical claims.

## Organization Wiki

Best for labs, companies, communities, or institutions.

Suggested pages:

- `wiki/index.md` for overview.
- `wiki/projects/<project>.md` for important initiatives.
- `wiki/people/<person>.md` for relevant people.
- `wiki/timeline.md` for milestones.
- `wiki/strategy.md` for source-grounded strategic analysis.

Separate facts from interpretation, especially for strategy or intent.

## Project Wiki

Best for an internal build, research initiative, course, or content project.

Suggested pages:

- `wiki/index.md` for status and navigation.
- `wiki/decisions/<decision>.md` for important choices.
- `wiki/specs/<spec>.md` for requirements.
- `wiki/notes/<note>.md` for working notes.
- `derived/briefs/` for summaries and handoffs.

Project wikis should make the current state obvious to the next agent.