64 lines
3.0 KiB
Markdown
64 lines
3.0 KiB
Markdown
|
# Wiki Workspace Instructions
|
||
|
|
|
||
|
|
## Scope
|
||
|
|
|
||
|
|
These instructions control the current `wiki/` directory. Read this file before every weave, ask, or wiki maintenance task.
|
||
|
|
|
||
|
|
This file is operational control metadata. Do not treat it as project knowledge, cite it as evidence, or include it in `wiki/index.md`.
|
||
|
|
|
||
|
|
## Current Layout
|
||
|
|
|
||
|
|
Keep maintained knowledge pages directly under `wiki/` because the current ask skill retrieves `wiki/*.md` non-recursively.
|
||
|
|
|
||
|
|
```text
|
||
|
|
wiki/
|
||
|
|
|-- AGENTS.md
|
||
|
|
|-- index.md
|
||
|
|
|-- source-summary-<slug>.md
|
||
|
|
`-- concept-<slug>.md
|
||
|
|
```
|
||
|
|
|
||
|
|
## Classification And Naming
|
||
|
|
|
||
|
|
- `wiki/source-summary-*`: one source, one page.
|
||
|
|
- `wiki/concept-*`: long-term knowledge page.
|
||
|
|
|
||
|
|
- Use lowercase kebab-case slugs based on subject, not date or author.
|
||
|
|
- Keep one primary category per page and update an existing matching page instead of creating a near-duplicate.
|
||
|
|
- Preserve `source-summary-*` and `concept-*` names required by the weave skill.
|
||
|
|
- Use only the categories listed here unless this file is intentionally revised for the stage.
|
||
|
|
|
||
|
|
## Page Requirements
|
||
|
|
|
||
|
|
Every maintained knowledge page must include:
|
||
|
|
|
||
|
|
- the `source_refs` field: repository-relative evidence paths;
|
||
|
|
- the `Useful for` field: supported questions or decisions;
|
||
|
|
- the `Human check` field: facts, interpretations, or approvals requiring review;
|
||
|
|
- the `Uncertainty and conflicts` field, or its `None identified` state;
|
||
|
|
- a concise body appropriate to its category.
|
||
|
|
|
||
|
|
Do not present proposals or assumptions as approved requirements or decisions.
|
||
|
|
|
||
|
|
## Document Language
|
||
|
|
|
||
|
|
- Use one human-readable language per maintained page and index entry: select the dominant language of its evidence unless the user explicitly requests another language.
|
||
|
|
- Translate all visible headings, descriptions, and explanatory text into that language. Do not mix translated and untranslated headings.
|
||
|
|
- Keep only necessary technical identifiers, code, protocol names, product names, and literal source quotations in their original form.
|
||
|
|
- Preserve the four Page Requirements fields as stable semantic concepts. Translate only their visible headings according to this mapping:
|
||
|
|
|
||
|
|
| Canonical field | Chinese visible heading | English visible heading |
|
||
|
|
| --- | --- | --- |
|
||
|
|
| `source_refs` | 来源 | Source refs |
|
||
|
|
| `Useful for` | 用途 | Useful for |
|
||
|
|
| `Human check` | 人工核查 | Human check |
|
||
|
|
| `Uncertainty and conflicts` | 不确定性与冲突 | Uncertainty and conflicts |
|
||
|
|
| `None identified` | 未发现 | None identified |
|
||
|
|
|
||
|
|
- Do not require an English metadata key, YAML frontmatter, or HTML comment when the selected document language provides an unambiguous visible heading from this mapping.
|
||
|
|
- When a page is updated, normalize its existing visible text to this rule within the edited scope.
|
||
|
|
|
||
|
|
## Index
|
||
|
|
|
||
|
|
- Maintain `wiki/index.md` as the retrieval entry point, grouped in this order: source summaries, concepts. Translate these visible group headings into the index's selected document language.
|
||
|
|
- For each indexed page, include a link, one-sentence retrieval description, and important uncertainty.
|