| name | wiki |
| description | Defines the .wiki/ knowledge base for @samchon/lint-plugin-evidence — what belongs in it, its Korean and no-wrap writing rules, and the obligation to correct it the moment a claim proves false. Use when researching prior art, recording an architectural decision, or discovering that a wiki claim is wrong; do not use for user-facing documentation, which the documentation skill owns. |
Wiki
Why It Exists
This project is built by reading three large codebases that no one holds in memory at once. Research that lives only in a conversation is lost when that conversation ends, and the next agent re-derives it — differently, and sometimes wrongly. .wiki/ is where a finding becomes durable.
It is an internal knowledge base, not documentation. Its audience is whoever works on this repository next, including you.
What Belongs
.wiki/references/<project>.md — what a prior-art project actually does. One file per project..wiki/design/decisions.md — what this repository decided, why, and what it gave up.
A page holds distilled conclusions, not transcripts. If a paragraph would not change what a reader does next, it does not belong.
Writing Rules
- Korean. The wiki is the one Korean artifact in an English repository; see the Language section of AGENTS.md.
- Never hard-wrap. One paragraph is one source line, with as many blank-line paragraph breaks as the ideas require.
- Cite as
path/to/file.ts:42 so any claim can be re-verified at its source.
- Mark a guess as a guess. Write
미검증 on anything not read directly. An inference that reads as a fact is the specific failure this file exists to prevent.
- One topic per file, short enough to re-read whole.
