specsmd 0.0.0-dev.70 → 0.0.0-dev.71

package/flows/fire/agents/builder/skills/run-execute/SKILL.md

@@ -132,11 +132,60 @@ Supports both single-item and multi-item (batch/wide) runs.
     <action>Get current_item from state.yaml active_run</action>
     <action>Load work item from .specs-fire/intents/{intent}/work-items/{id}.md</action>
     <action>Read intent brief for broader context</action>
-    <action>Load ALL project standards:</action>
-    <substep>.specs-fire/standards/tech-stack.md — Technology choices</substep>
-    <substep>.specs-fire/standards/coding-standards.md — Code style and patterns</substep>
-    <substep>.specs-fire/standards/testing-standards.md — Testing strategy and coverage</substep>
-    <substep>.specs-fire/standards/system-architecture.md — Architecture context and constraints</substep>
+    <action>Load project standards using hierarchical resolution:</action>
+
+    <standards_resolution critical="true">
+      <substep n="2a" title="Discover Standards Locations">
+        <action>Scan repository for: **/.specs-fire/standards/</action>
+        <action>Build list sorted by path depth (root = depth 0)</action>
+        <example>
+          depth 0: .specs-fire/standards/
+          depth 2: packages/api/.specs-fire/standards/
+          depth 2: apps/mobile/.specs-fire/standards/
+        </example>
+      </substep>
+
+      <substep n="2b" title="Load Constitution (Root Only)">
+        <action>Load .specs-fire/standards/constitution.md from ROOT</action>
+        <critical>IGNORE any constitution.md in nested directories</critical>
+        <critical>Constitution is ALWAYS inherited, NEVER overridden</critical>
+        <note>If constitution.md doesn't exist, skip gracefully</note>
+      </substep>
+
+      <substep n="2c" title="Resolve Module Standards">
+        <action>For each discovered standards location (excluding root):</action>
+
+        <resolution_algorithm>
+          FOR each standard_file IN [tech-stack.md, coding-standards.md,
+                                      testing-standards.md, system-architecture.md]:
+
+            IF {location}/standards/{standard_file} EXISTS:
+              → USE this file for scope {location.parent_path}/**
+            ELSE:
+              → Walk UP to find nearest ancestor with this file
+              → USE ancestor's file (ultimately root if none found)
+        </resolution_algorithm>
+      </substep>
+
+      <substep n="2d" title="Present Standards with Scoping">
+        <action>Present loaded standards with clear path-based scoping:</action>
+
+        <output_format>
+          ## Constitution (applies to ALL files)
+          [content of root constitution.md]
+
+          ## Standards for {module_path}/** files
+          When editing files under {module_path}/, apply:
+          - Tech Stack: [resolved tech-stack.md for this scope]
+          - Coding Standards: [resolved coding-standards.md for this scope]
+          - Testing Standards: [resolved testing-standards.md for this scope]
+
+          ## Default Standards (paths without specific scope)
+          For all other files, apply root standards.
+        </output_format>
+      </substep>
+    </standards_resolution>
+
     <action>Determine execution mode from work item</action>
   </step>
 
@@ -240,11 +289,27 @@ Supports both single-item and multi-item (batch/wide) runs.
     <substep n="5b">Track file operation (create/modify)</substep>
     <substep n="5c">Record decisions made</substep>
 
+    <standards_application critical="true">
+      When editing a file at path X:
+      1. Find the LONGEST matching standards scope (most specific)
+      2. Apply those standards to the file
+      3. If no specific scope matches, apply root standards
+
+      <example>
+        Editing packages/api/src/handler.go
+        → Apply "Standards for packages/api/**"
+
+        Editing scripts/deploy.sh
+        → Apply "Default Standards" (root)
+      </example>
+    </standards_application>
+
     <brownfield_rules>
       <rule>READ existing code before modifying</rule>
       <rule>MATCH existing naming conventions</rule>
       <rule>FOLLOW existing patterns in the codebase</rule>
       <rule>PRESERVE existing tests</rule>
+      <rule>USE module-specific standards when editing module files</rule>
     </brownfield_rules>
   </step>
 
@@ -487,6 +552,9 @@ Supports both single-item and multi-item (batch/wide) runs.
 
 <success_criteria>
   <criterion>Run initialized via init-run.js script</criterion>
+  <criterion>Standards loaded with hierarchical resolution</criterion>
+  <criterion>Constitution loaded from root (if exists)</criterion>
+  <criterion>Module-specific standards applied to module files</criterion>
   <criterion>plan.md created BEFORE implementation</criterion>
   <criterion>All work items implemented</criterion>
   <criterion>All tests pass</criterion>

package/flows/fire/agents/orchestrator/skills/project-init/SKILL.md

@@ -39,6 +39,19 @@ Initialize a new FIRE project by detecting workspace type and setting up standar
     <action>Detect tech stack (language, framework, database)</action>
     <action>Detect structure (monolith, monorepo)</action>
     <action>Infer coding patterns</action>
+
+    <monorepo_detection>
+      Check for monorepo indicators:
+      - nx.json, turbo.json, pnpm-workspace.yaml, lerna.json, rush.json
+      - package.json with "workspaces" field
+      - Cargo.toml with [workspace] section
+      - go.work file
+      - Multiple independent package/dependency manifests
+      - Common patterns: packages/*, apps/*, services/*, libs/*
+
+      If any indicator found → workspace.structure = "monorepo"
+    </monorepo_detection>
+
     <output>
       Here's what I found:
 
@@ -96,20 +109,64 @@ Initialize a new FIRE project by detecting workspace type and setting up standar
     <note>Can be changed later in .specs-fire/state.yaml</note>
   </step>
 
-  <step n="5" title="Create Structure">
+  <step n="5" title="Detect Modules" if="workspace.structure == monorepo">
+    <output>
+      Monorepo detected. Let me find and analyze the modules.
+    </output>
+
+    <action>Find module directories by exploring:</action>
+    <substep>Paths from workspace config (nx.json projects, pnpm-workspace.yaml, etc.)</substep>
+    <substep>Common patterns: packages/*, apps/*, services/*, libs/*, modules/*</substep>
+    <substep>Directories with their own dependency manifest</substep>
+
+    <action>For each discovered module, analyze (AI-driven, no hardcoded mappings):</action>
+    <substep>Primary language (from file extensions, config files)</substep>
+    <substep>Build/test commands (from CI config, package scripts, Makefile)</substep>
+    <substep>Linter/formatter (from config files in module)</substep>
+    <substep>Package manager (from lock files, manifests)</substep>
+
+    <output>
+      Found {{module_count}} modules:
+
+      | Module | Language | Test Command | Linter |
+      |--------|----------|--------------|--------|
+      {{#each modules}}
+      | {{path}} | {{language}} | {{test_cmd}} | {{linter}} |
+      {{/each}}
+
+      Create module-specific standards?
+      [c] All modules — create standards for all
+      [s] Select — choose which modules
+      [n] None — I'll create them manually later
+    </output>
+
+    <check if="response == c or response == s">
+      <action>For each selected module, create {module}/.specs-fire/standards/tech-stack.md</action>
+      <note>Only tech-stack.md by default — other standards inherit from root</note>
+    </check>
+  </step>
+
+  <step n="6" title="Create Structure">
     <action>Create .specs-fire/ directory</action>
     <action>Create .specs-fire/intents/</action>
     <action>Create .specs-fire/runs/</action>
     <action>Create .specs-fire/standards/</action>
-    <action>Generate .specs-fire/state.yaml (include autonomy_bias)</action>
+    <action>Generate .specs-fire/state.yaml (include autonomy_bias, workspace.structure)</action>
     <action>Generate standards using templates:</action>
+    <substep>constitution.md — templates/constitution.md.hbs</substep>
     <substep>tech-stack.md — templates/tech-stack.md.hbs</substep>
     <substep>coding-standards.md — templates/coding-standards.md.hbs</substep>
     <substep>testing-standards.md — templates/testing-standards.md.hbs</substep>
     <substep>system-architecture.md — templates/system-architecture.md.hbs</substep>
+
+    <check if="workspace.structure == monorepo and modules_selected">
+      <action>For each selected module:</action>
+      <substep>Create {module}/.specs-fire/standards/</substep>
+      <substep>Generate {module}/.specs-fire/standards/tech-stack.md with detected settings</substep>
+    </check>
   </step>
 
-  <step n="6" title="Complete">
+  <step n="7" title="Complete">
     <output>
       FIRE initialized!
 
@@ -120,10 +177,19 @@ Initialize a new FIRE project by detecting workspace type and setting up standar
       ├── intents/
       ├── runs/
       └── standards/
+          ├── constitution.md        # Universal policies (always inherited)
           ├── tech-stack.md
           ├── coding-standards.md
           ├── testing-standards.md
           └── system-architecture.md
+      {{#if modules_created}}
+
+      Module standards created:
+      {{#each modules_created}}
+      {{path}}/.specs-fire/standards/
+      └── tech-stack.md
+      {{/each}}
+      {{/if}}
       ```
 
       Ready to capture your first intent.
@@ -137,17 +203,23 @@ Initialize a new FIRE project by detecting workspace type and setting up standar
   | Artifact | Location | Template |
   |----------|----------|----------|
   | State | `.specs-fire/state.yaml` | — |
+  | Constitution | `.specs-fire/standards/constitution.md` | `templates/constitution.md.hbs` |
   | Tech Stack | `.specs-fire/standards/tech-stack.md` | `templates/tech-stack.md.hbs` |
   | Coding Standards | `.specs-fire/standards/coding-standards.md` | `templates/coding-standards.md.hbs` |
   | Testing Standards | `.specs-fire/standards/testing-standards.md` | `templates/testing-standards.md.hbs` |
   | System Architecture | `.specs-fire/standards/system-architecture.md` | `templates/system-architecture.md.hbs` |
+  | Module Tech Stack | `{module}/.specs-fire/standards/tech-stack.md` | AI-generated |
 </output_artifacts>
 
 <success_criteria>
-  <criterion>Workspace type correctly detected</criterion>
+  <criterion>Workspace type correctly detected (greenfield/brownfield)</criterion>
+  <criterion>Workspace structure correctly detected (monolith/monorepo)</criterion>
   <criterion>Tech stack identified or suggested</criterion>
   <criterion>Autonomy level selected</criterion>
   <criterion>.specs-fire/ directory structure created</criterion>
+  <criterion>constitution.md generated (universal policies)</criterion>
   <criterion>Standards files generated from templates</criterion>
   <criterion>state.yaml created with correct configuration</criterion>
+  <criterion>If monorepo: modules detected and analyzed</criterion>
+  <criterion>If monorepo: module standards created for selected modules</criterion>
 </success_criteria>

package/flows/fire/agents/orchestrator/skills/project-init/templates/constitution.md.hbs

@@ -0,0 +1,43 @@
+# Project Constitution
+
+> Universal policies that apply to ALL code in this project.
+> This file is always inherited from root — modules cannot override it.
+
+## Git Workflow
+
+- **Commit Style**: {{#if commit_style}}{{commit_style}}{{else}}Conventional commits (feat:, fix:, chore:, docs:, refactor:, test:){{/if}}
+- **Branch Strategy**: {{#if branch_strategy}}{{branch_strategy}}{{else}}Feature branches merged via pull request{{/if}}
+- **Main Branch**: {{#if main_branch}}{{main_branch}}{{else}}main{{/if}} is always deployable
+
+## Code Review
+
+- All changes require pull request review
+- {{#if approval_count}}{{approval_count}}{{else}}At least one{{/if}} approval required before merge
+- No self-merging to main/master
+- Security-sensitive changes require additional review
+
+## CI/CD
+
+{{#if ci_platform}}
+- **Platform**: {{ci_platform}}
+{{else}}
+- All PRs must pass CI checks before merge
+{{/if}}
+- Automated tests run on every push
+- Main branch deployments are automated
+
+## Security Policies
+
+- **No secrets in code** — use environment variables or secret management
+- Dependencies must be from trusted sources
+- Security vulnerabilities addressed within SLA
+- No credentials, API keys, or tokens in source control
+
+## Documentation
+
+- Public APIs must be documented
+- Breaking changes require migration notes
+- README kept up to date with setup instructions
+
+---
+*Generated by FIRE on {{date}}*

package/flows/fire/agents/orchestrator/skills/project-migrate/SKILL.md

@@ -0,0 +1,234 @@
+---
+name: project-migrate
+description: Migrate existing FIRE project to latest version. Adds constitution.md, updates schema, and optionally detects monorepo modules.
+version: 1.0.0
+---
+
+<objective>
+Upgrade an existing FIRE project to the latest version, adding new features
+(constitution.md, hierarchical standards) while preserving all existing work.
+</objective>
+
+<triggers>
+  - User runs `/fire-migrate`
+  - Orchestrator detects outdated project version
+</triggers>
+
+<principles critical="true">
+  <principle>NEVER delete or modify existing intents/work-items/runs</principle>
+  <principle>Create backup before any changes</principle>
+  <principle>Migration is idempotent — safe to run multiple times</principle>
+  <principle>Show changes before applying</principle>
+</principles>
+
+<flow>
+  <step n="1" title="Detect Current Version">
+    <action>Check if .specs-fire/ exists</action>
+    <check if="no .specs-fire/">
+      <output>Not a FIRE project. Use /fire to initialize.</output>
+      <exit/>
+    </check>
+
+    <action>Read .specs-fire/state.yaml</action>
+    <action>Check project.fire_version field</action>
+    <action>Read FIRE flow version from memory-bank.yaml</action>
+
+    <version_detection>
+      | Check | Meaning |
+      |-------|---------|
+      | project.fire_version missing | Pre-0.1.8 project |
+      | project.fire_version < current | Needs migration |
+      | project.fire_version == current | Up to date |
+
+      Also check for feature indicators:
+      | Missing Feature | Added In |
+      |-----------------|----------|
+      | constitution.md | 0.1.8 |
+      | workspace.structure | 0.1.8 |
+    </version_detection>
+
+    <check if="already up to date">
+      <output>Project is already at the latest version ({current_version}). No migration needed.</output>
+      <exit/>
+    </check>
+
+    <output>
+      Current version: {project_fire_version or "pre-0.1.8"}
+      Latest version: {fire_flow_version}
+      Migration required.
+    </output>
+  </step>
+
+  <step n="2" title="Analyze Migration Scope">
+    <action>Determine what needs to be migrated:</action>
+
+    <check_constitution>
+      Does .specs-fire/standards/constitution.md exist?
+      If no → needs_constitution = true
+    </check_constitution>
+
+    <check_schema>
+      Does state.yaml have workspace.structure field?
+      If no → needs_schema_update = true
+    </check_schema>
+
+    <check_monorepo>
+      Is this actually a monorepo? Check for:
+      - nx.json, turbo.json, pnpm-workspace.yaml, lerna.json
+      - package.json with "workspaces"
+      - Multiple package/dependency manifests
+      If detected → is_monorepo = true
+    </check_monorepo>
+
+    <output>
+      Migration Plan:
+      ┌─────────────────────────────────────────────────────┐
+      │ Changes to be made:                                 │
+      {{#if needs_constitution}}
+      │ ✓ Create constitution.md (universal policies)      │
+      {{/if}}
+      {{#if needs_schema_update}}
+      │ ✓ Update state.yaml schema                         │
+      {{/if}}
+      {{#if is_monorepo}}
+      │ ? Monorepo detected — offer module standards       │
+      {{/if}}
+      │                                                     │
+      │ Will NOT change:                                    │
+      │ • Existing intents and work items                   │
+      │ • Existing runs and logs                            │
+      │ • Existing standards (only add new ones)            │
+      └─────────────────────────────────────────────────────┘
+    </output>
+  </step>
+
+  <step n="3" title="Create Backup">
+    <action>Create backup: cp -r .specs-fire .specs-fire-backup-{timestamp}</action>
+    <output>Backup created: .specs-fire-backup-{timestamp}</output>
+  </step>
+
+  <step n="4" title="Confirm Migration">
+    <ask>
+      Ready to migrate. Backup saved.
+
+      Proceed with migration? [Y/n]
+    </ask>
+  </step>
+
+  <step n="5" title="Add Constitution" if="needs_constitution">
+    <ask>
+      How should I create constitution.md?
+
+      [a] Auto-generate — analyze project (git, CI, existing patterns)
+      [d] Default — use standard template
+      [c] Custom — I'll provide the content
+    </ask>
+
+    <check if="response == a">
+      <action>Analyze project for constitution content:</action>
+      <substep>Check .gitignore, CI config for workflow hints</substep>
+      <substep>Check existing PR templates, CONTRIBUTING.md</substep>
+      <substep>Infer commit style from git log</substep>
+      <action>Generate constitution.md from findings</action>
+    </check>
+
+    <check if="response == d">
+      <action>Create constitution.md from default template</action>
+    </check>
+
+    <check if="response == c">
+      <ask>Please describe your key policies (git workflow, PR process, security).</ask>
+      <action>Generate constitution.md from input</action>
+    </check>
+
+    <action>Write to .specs-fire/standards/constitution.md</action>
+    <output>Created: .specs-fire/standards/constitution.md</output>
+  </step>
+
+  <step n="6" title="Update State Schema" if="needs_schema_update">
+    <action>Read current state.yaml</action>
+    <action>Add missing fields with defaults:</action>
+    <substep>project.fire_version: "{current_fire_flow_version}"</substep>
+    <substep>workspace.structure: "monolith" (or "monorepo" if detected)</substep>
+    <action>Write updated state.yaml (preserve all existing data)</action>
+    <output>Updated: .specs-fire/state.yaml</output>
+  </step>
+
+  <step n="7" title="Monorepo Module Setup" if="is_monorepo" optional="true">
+    <action>Discover modules (same as project-init):</action>
+    <substep>Check workspace config for project list</substep>
+    <substep>Scan packages/*, apps/*, services/*, libs/*</substep>
+    <substep>Analyze each module's tech stack</substep>
+
+    <ask>
+      This appears to be a monorepo. Found {{module_count}} modules:
+
+      {{#each modules}}
+      • {{path}} ({{language}})
+      {{/each}}
+
+      Create module-specific standards?
+      [y] Yes — create for all modules
+      [s] Select — choose which modules
+      [n] No — skip for now
+    </ask>
+
+    <check if="response == y or response == s">
+      <action>For each selected module:</action>
+      <substep>Create {module}/.specs-fire/standards/</substep>
+      <substep>Generate tech-stack.md with detected settings</substep>
+    </check>
+  </step>
+
+  <step n="8" title="Verify Migration">
+    <action>Verify migration completed:</action>
+    <substep>Read state.yaml — valid YAML?</substep>
+    <substep>Check new files exist</substep>
+    <substep>Ensure no existing files corrupted</substep>
+
+    <check if="verification fails">
+      <output>Migration failed. Restoring from backup...</output>
+      <action>rm -rf .specs-fire && mv .specs-fire-backup-{timestamp} .specs-fire</action>
+      <output>Restored. Please report this issue.</output>
+      <exit status="error"/>
+    </check>
+  </step>
+
+  <step n="9" title="Report">
+    <output>
+      Migration complete!
+
+      Changes made:
+      {{#each changes_made}}
+      ✓ {{description}}
+      {{/each}}
+
+      Backup preserved at: .specs-fire-backup-{timestamp}
+      (Delete once you've verified everything works)
+
+      New features available:
+      • Constitution: Universal policies in constitution.md
+      {{#if is_monorepo}}
+      • Monorepo: Module-specific standards supported
+      {{/if}}
+    </output>
+  </step>
+</flow>
+
+<safety_guarantees>
+  <guarantee>Backup created before any changes</guarantee>
+  <guarantee>Idempotent — running twice is safe</guarantee>
+  <guarantee>Verify after — validates migration succeeded</guarantee>
+  <guarantee>Restore on failure — automatic rollback</guarantee>
+  <guarantee>Never deletes — only adds, never removes</guarantee>
+</safety_guarantees>
+
+<success_criteria>
+  <criterion>Current version detected correctly</criterion>
+  <criterion>Backup created before changes</criterion>
+  <criterion>constitution.md added if missing</criterion>
+  <criterion>state.yaml schema updated if needed</criterion>
+  <criterion>Monorepo modules detected and offered (if applicable)</criterion>
+  <criterion>Migration verified successfully</criterion>
+  <criterion>No existing data lost or corrupted</criterion>
+</success_criteria>

package/flows/fire/agents/orchestrator/skills/route/SKILL.md

@@ -22,8 +22,21 @@ Analyze project state and route user to the appropriate agent.
 <flow>
   <step n="1" title="Discover and Read State">
     <action>Read .specs-fire/state.yaml</action>
-    <action>Scan .specs-fire/intents/ for briefs not in state</action>
-    <action>Scan .specs-fire/intents/*/work-items/ for items not in state</action>
+
+    <file_system_scan critical="true">
+      Use these EXACT glob patterns:
+
+      <pattern purpose="Find intent briefs">
+        .specs-fire/intents/*/brief.md
+      </pattern>
+
+      <pattern purpose="Find work items">
+        .specs-fire/intents/*/work-items/*.md
+      </pattern>
+
+      Work items are {work-item-id}.md files directly in work-items/ folder.
+    </file_system_scan>
+
     <action>Reconcile: add discovered items to state as pending</action>
     <action>Parse current project state</action>
   </step>

package/flows/fire/memory-bank.yaml

@@ -1,6 +1,9 @@
 # FIRE Flow Configuration
 # Fast Intent-Run Engineering - Simplified AI-native development
 
+# FIRE Flow Version (used by migrate skill to detect outdated projects)
+version: "0.1.8"
+
 # Artifact folder (created at project initialization)
 artifact_root: ".specs-fire"
 
@@ -11,7 +14,23 @@ structure:
   - path: runs/
     description: "Execution logs and walkthroughs per run"
   - path: standards/
-    description: "Project standards (tech-stack, coding-standards, testing-standards)"
+    description: "Project standards (constitution, tech-stack, coding-standards, testing-standards)"
+
+# ─────────────────────────────────────────────────────────────────────────────────
+# HIERARCHICAL STANDARDS (Monorepo Support)
+# ─────────────────────────────────────────────────────────────────────────────────
+#
+# Standards can exist at root level AND at module level for monorepos.
+# Resolution rules:
+#   - constitution.md: ALWAYS from root, NEVER overridden by modules
+#   - All other standards: Override semantics (module overrides root if exists)
+#
+# Example monorepo structure:
+#   .specs-fire/standards/              <- Root standards (defaults)
+#   packages/api/.specs-fire/standards/ <- API module overrides
+#   apps/mobile/.specs-fire/standards/  <- Mobile module overrides
+#
+# The file system IS the registry - presence of .specs-fire/standards/ defines a scope.
 
 # Central state file (FIRE's source of truth)
 state:
@@ -22,7 +41,7 @@ state:
       - name: "Project name"
       - description: "Project description"
       - created: "ISO 8601 timestamp"
-      - framework: "fire-v1"
+      - fire_version: "FIRE flow version at project init (e.g., 0.1.8)"
     workspace:
       - type: "greenfield | brownfield"
       - structure: "monolith | monorepo | multi-part"
@@ -87,18 +106,58 @@ schema:
   run-log: ".specs-fire/runs/{run-id}/run.md"
   test-report: ".specs-fire/runs/{run-id}/test-report.md"
   walkthrough: ".specs-fire/runs/{run-id}/walkthrough.md"
+
+  # Root Standards
   standards: ".specs-fire/standards/"
+  constitution: ".specs-fire/standards/constitution.md"
   tech-stack: ".specs-fire/standards/tech-stack.md"
   coding-standards: ".specs-fire/standards/coding-standards.md"
   testing-standards: ".specs-fire/standards/testing-standards.md"
   system-architecture: ".specs-fire/standards/system-architecture.md"
 
+  # Module Standards (Monorepo) - paths relative to module root
+  module-standards: "{module-path}/.specs-fire/standards/"
+  module-tech-stack: "{module-path}/.specs-fire/standards/tech-stack.md"
+  module-coding-standards: "{module-path}/.specs-fire/standards/coding-standards.md"
+  module-testing-standards: "{module-path}/.specs-fire/standards/testing-standards.md"
+
   # Agent Ownership
   ownership:
     orchestrator: [state]
     planner: [intents, work-items, state]
     builder: [runs, state]
 
+# ─────────────────────────────────────────────────────────────────────────────────
+# STANDARDS BEHAVIOR
+# ─────────────────────────────────────────────────────────────────────────────────
+
+standards_behavior:
+  constitution:
+    inheritance: always
+    override: never
+    description: |
+      Universal policies (git workflow, PR process, security).
+      ALWAYS loaded from root. Modules cannot override.
+
+  tech-stack:
+    inheritance: fallback
+    override: allowed
+    description: |
+      If module has tech-stack.md, use it.
+      Otherwise inherit from nearest ancestor (ultimately root).
+
+  coding-standards:
+    inheritance: fallback
+    override: allowed
+
+  testing-standards:
+    inheritance: fallback
+    override: allowed
+
+  system-architecture:
+    inheritance: fallback
+    override: allowed
+
 # Execution Modes
 execution_modes:
   autopilot:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specsmd",
-  "version": "0.0.0-dev.70",
+  "version": "0.0.0-dev.71",
   "description": "Multi-agent orchestration system for AI-native software development. Delivers AI-DLC, Agile, and custom SDLC flows as markdown-based agent systems.",
   "main": "lib/installer.js",
   "bin": {