Guidance

Create-or-refresh is one mode. Adoption semantics follow docs/wiki/maintenance.md § Adopted guidance; non-compliant areas belong in the page's ## Known gaps, and closing them is separate /to-backlog work this skill never creates.

Follow $wiki for record mechanics — ownership, evidence, sources, validation, staging, commits. Stay on the current branch; never touch docs/tasks.

Authority

Obtain explicit owner approval before each page create-or-refresh transaction, unless the caller holds standing approval for it — $to-guidance for the subjects that invocation named, $to-epic and $to-backlog for the subjects the owner named at their evidence decisions, $to-product for every subject an autonomous run reaches. That approval also supersedes $wiki's per-transaction pauses for exactly those transactions.

Regardless of caller: never publish guidance for a subject repository evidence does not show in use; never deprecate or delete a page; never mutate docs/backlog; and always pause per item under step 6 — only $to-product's autonomous contract covers reversing an adopted rule, and it reports each reversal individually.

Subjects

A subject is one of:

• a technology — language, framework, runtime, library, or major tool → one page under docs/wiki/engineering/technologies/;
• a standard — a cross-cutting security, privacy, accessibility, protocol, or regulatory standard (OWASP ASVS, WCAG, a wire-format specification) → one page under docs/wiki/engineering/standards/.