# {{project_name}} — RULES > **What this is.** Project-wide always-follow rules. Authoritative for every > milestone, slice, and task — including deferred ones. Read by every agent > before action. > > **Precedence.** [`COMPLETENESS.md`](COMPLETENESS.md) (foundation, always) > > `RULES.md` (project-wide, always) > `M-CONTEXT.md` (phase-locked) > > `S-PLAN.md` (slice-scoped) > defaults. > > **Foundation.** Every rule below sits on top of the 12-rule Completeness > Mandate at [`COMPLETENESS.md`](COMPLETENESS.md). When a project rule and > the Completeness Mandate would conflict, the Completeness Mandate wins — > it is mechanically enforced by the linter and the Nubosloop. > > **Scope.** Anything that should apply on day 1 AND on day 1000. If a rule is > phase-bound, it belongs in `M-CONTEXT.md`, not here. Created: {{created_date}} --- > **How to fill this file (agent / human author):** > > - Every section below is **MUST FILL** before the project's first `/np:plan-phase` call. A section left as `_TBD` blocks the planner — there is no "fill later" path that produces a clean plan. > - **Cardinality:** Each section expects **at least 1** concrete rule. Sections that are truly empty for this project use the form `- _none — _` (e.g. `- _none — purely internal tool, no external secrets._`). Bare `_TBD` is rejected. > - Use the inline HTML-comment examples in each section as a starting point — replace each `- _TBD —` placeholder with one or more project-specific bullets. > - Rules are imperatives ("Always X", "Never Y"), not aspirations ("We try to X"). A rule that cannot be checked from the diff or the verify output is not a rule, it's a wish. --- ## Always-Follow - _TBD — fill with project-wide invariants._ ## Forbidden - _TBD — fill with banned patterns._ ## Dependencies - _TBD — fill with dependency policy._ ## Security - _TBD — fill with security defaults._ ## Logging & Observability - _TBD — fill with logging policy._ ## Conventions > **How your code must be built.** These rules bind the architect (`np-task-architect`), > the test-writer (`np-test-writer`), the executor, and the style critic > (`np-critic-style`). They are read on every task. Each subsection is **MUST FILL** — > use `- _none — _` only when a subsection genuinely does not apply. ### Class / Module Structure - _TBD — fill with class/module construction rules._ ### Naming - _TBD — fill with naming conventions._ ### Code Style - _TBD — fill with style policy._ ### Patterns & Paradigms - _TBD — fill with required/banned patterns._ ## Out-of-Scope (Forever) - _TBD — fill with permanent exclusions._ --- ## How to update this file 1. Anyone can append a draft rule via `/np:add-todo --type rule ""`. 2. The next `/np:discuss-phase` for the active milestone reviews drafts. 3. Locked rules land here verbatim with a date stamp; rejected drafts are archived under the relevant milestone's `M-CONTEXT.md` deferred section. Rules promoted from `M-CONTEXT.md` should reference the originating decision: `D- from M` for traceability.