vault-tech-note

Activation Contract

Load when asked to create, extend, or refactor a technical note in the user's Obsidian vault, for any language, library, or tool (Java, Docker, Spring, SQL...).

Not for: project plans, design decisions, Kanban boards, or config guides — those have their own note types.

Hard Rules

• Never state a version, API, or behavior from memory. Verify it against the source that owns the fact.
• One note = one topic. Two topics means two notes, cross-linked.
• Frontmatter in English; body in the user's language; code and identifiers always English.
• Every note links upward to its domain index, and the index links back.
• Never invent the vault's rules. Read the vault README.md first: it is the contract.
• Follow references/note-anatomy.md. Do not improvise sections.

Decision Gates

Which source owns the fact: