Page Schema

中文 | English

Use concise markdown pages with predictable sections.

Source Pages

Suggested structure:

# <title>

## Source
- File:
- Translated file:
- Origin:
- Added:

## Summary

## Key Claims

## Visual Notes

## OCR Excerpts

## Connections

## Open Questions

Concept, Entity, and Topic Pages

Suggested structure:

# <name>

## Summary

## Key Points

## Related Pages

## Sources

Link Style

• Prefer relative markdown links such as [LLM Wiki](../../../../../../wiki/concepts/llm-wiki.md).
• For local file targets that contain spaces, wrap the destination in angle brackets, for example [Raw file](<../../../../Harness engineering leveraging Codex in an agent-first world.md>).
• Do not use absolute local filesystem paths in repository markdown; keep links repository-relative.
• Obsidian wikilinks such as [[concepts/llm-wiki]] are allowed, but use them consistently.
• Keep one canonical page per durable concept.

Bilingual Pairing

• English pages use the canonical unsuffixed path.
• Chinese pages use sibling .zh.md files.
• Markdown raw source translations use sibling .zh.md files in raw/.
• Raw translation siblings should stay faithful to the source text; summaries and editorial rewrites belong in wiki/, not in raw/*.zh.md.
• Human-facing repo docs such as README.md and docs/*.md use sibling .zh.md files as well.
• Put a language switch link directly under the title, for example:

[中文](page.zh.md) | English

or:

中文 | [English](page.md)

• Keep both language variants structurally aligned.
• Source pages follow the same rule and should link both the original raw file and the translated raw file when both exist.
• Markdown raw source files should also place a simple language switch link near the top, immediately after frontmatter when present.
• If raw files move, repair their path-dependent language-switch links and other local navigation metadata in the same pass.
• Standalone screenshot or image assets do not need duplicate .zh image siblings; keep bilingual interpretation in the source pages.

Translation Freshness

• When a translated sibling is behind the source, add translation_status: stale to the translated file's frontmatter.
• Remove the stale marker once the translation catches up.

Change Discipline

• If a new source conflicts with an older page, keep the conflict visible.
• Avoid deleting old claims silently; annotate why they changed.
• Update index.md whenever you add a durable page.
• Keep older log.md entries intact, but insert new entries at the top of the entry list.

Index And Log

Suggested index.md style:

## Concepts
- [Page Name](wiki/concepts/page-name.md) - One-line description.

Suggested log.md style:

## [2026-04-08 14:32] ingest | Source Title

What changed and why.

Keep both files brief and highly scan-friendly. New log entries should be precise to the minute. log.md should read newest-first. Use log.md for operation records only: ingest, durable query, and lint passes that materially changed the vault.