Таски готовы

.specify/templates/plan-template.md

@@ -31,7 +31,7 @@
 
 *GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
 
-[Gates determined based on constitution file]
+[Evaluate against constitution.md and semantics.md. Explicitly confirm semantic protocol compliance, complexity-driven contract coverage, UX-state compatibility, async boundaries, API-wrapper rules, RBAC/security constraints, and any required belief-state/logging constraints for Complexity 4/5 Python modules.]
 
 ## Project Structure
 
@@ -94,6 +94,22 @@ ios/ or android/
 **Structure Decision**: [Document the selected structure and reference the real
 directories captured above]
 
+## Semantic Contract Guidance
+
+> Use this section to drive Phase 1 artifacts, especially `contracts/modules.md`.
+
+- Classify each planned module/component with `@COMPLEXITY: 1..5` or `@C:`.
+- Use `@TIER` only if backward compatibility is needed; never use it as the primary contract rule.
+- Match contract density to complexity:
+  - Complexity 1: anchors only, `@PURPOSE` optional
+  - Complexity 2: `@PURPOSE`
+  - Complexity 3: `@PURPOSE`, `@RELATION`; UI also `@UX_STATE`
+  - Complexity 4: `@PURPOSE`, `@RELATION`, `@PRE`, `@POST`, `@SIDE_EFFECT`; Python also meaningful `logger.reason()` / `logger.reflect()` path
+  - Complexity 5: level 4 + `@DATA_CONTRACT`, `@INVARIANT`; Python also `belief_scope`; UI also `@UX_FEEDBACK`, `@UX_RECOVERY`, `@UX_REACTIVITY`
+- Write relations only in canonical form: `@RELATION: [PREDICATE] ->[TARGET_ID]`
+- If any relation target, DTO, or contract dependency is unknown, emit `[NEED_CONTEXT: target]` instead of inventing placeholders.
+- Preserve medium-appropriate anchor/comment syntax for Python, Svelte markup, and Svelte script contexts.
+
 ## Complexity Tracking
 
 > **Fill ONLY if Constitution Check has violations that must be justified**