oc-authoring-ruleslisted

# Authoring-Rules — managing the project's folder-scoped law **Announce at the start (in pt-br):** "Usando authoring-rules para escrever/editar a lei de pasta no mecanismo nativo certo." Standardizes how durable, actionable rules are written into this harness's **native** rule mechanism. Each rule organizes knowledge into the same 3 canonical categories used everywhere in the harness. **There is no `.claude/rules/*.md` here, and there is no `paths:` frontmatter.** Those are Claude-Code-only mechanics with no OpenCode equivalent. In this harness a rule's SCOPE is its **tree location**: a rule that governs one folder lives in that folder's nested `AGENTS.md` (read by up-traversal), a project-wide rule lives in the root `AGENTS.md`/`CLAUDE.md`, and a harness-wide rule is never authored here at all — it is proposed to `kaizen.md`. The blast-radius routing below mirrors `skill({ name: "oc-distilling-learnings" })` exactly, because both write into the same native destinations. ## When to use - Create a new rule for a folder/subsystem that does not yet have one. - Add a Convention / Pattern / Gotcha to an existing folder rule. - Review/edit folder rules. - Decide whether something should be a folder rule, a root router-table row, a `kaizen.md` proposal, or just a one-off in the commit. ## Where rules live — the native mechanism (no `paths:`) Scope is decided by WHERE the file sits in the tree, not by a glob field. This replaces the Claude `paths:` mechanism one-for-one. | Sc