@atlashub/smartstack-cli 4.74.0 → 4.76.0

package/templates/skills/business-analyse/references/multi-app-detection.md

@@ -0,0 +1,149 @@
+# Multi-App Detection Algorithm
+
+> **Purpose:** Detect and extract multiple applications from user prompts using a two-tier approach.
+> Executed early in initialization to determine `workflow_mode` ("application" vs "project").
+
+## Overview
+
+When the user's prompt describes multiple applications or spans multiple business domains, we must recognize this immediately and set `workflow.mode = "project"` to avoid doing cadrage for a single app.
+
+## Tier 1 — Explicit Patterns (ANY match = multi-app detected)
+
+### French patterns:
+- "une application X ... une application Y" (two occurrences of "une application")
+- "application 1: X ... application 2: Y" (numbered applications)
+- "première application ... deuxième application"
+- "app 1: ... app 2: ..."
+
+### English patterns:
+- "an application (for) X ... an application (for) Y" (two occurrences)
+- "application #1: ... application #2: ..." (numbered)
+- "first app ... second app"
+
+### Decision:
+
+If ANY of these patterns is found in `{feature_description}`:
+→ `isMultiApp = true`, `detectionTier = "explicit"`
+
+## Tier 2 — Domain Diversity Analysis (when Tier 1 does not match)
+
+### Definition
+
+A "domain" is an autonomous business perimeter with its own entities and processes (e.g., HR, CRM, Finance, Projects, Sales, Inventory).
+
+### Algorithm
+
+ULTRATHINK: Analyze `{feature_description}` to extract distinct business domains.
+
+1. List all business domains mentioned or implied in the description
+2. Classify each domain:
+   - **DISTINCT** — has its own entities, processes, and lifecycle (e.g., HR vs CRM)
+   - **RELATED** — is a sub-domain of another (e.g., Payroll is a sub-domain of HR)
+3. Count DISTINCT domains only
+
+### Threshold
+
+2+ DISTINCT domains → `isMultiApp = true`, `detectionTier = "domain-diversity"`
+
+### False Positive Protection
+
+- "RH complet avec employés, congés, paie, pointage" = 1 domain (HR) with 4 modules, NOT 4 domains
+- "HR and Payroll management" = 1 domain (HR) with 2 modules — Payroll is RELATED to HR
+- "gestion commerciale avec devis, commandes et facturation" = 1 domain (Sales) with 3 modules
+- Only count as DISTINCT when domains have genuinely independent entity models and processes
+
+## Extraction Algorithm (depends on detection tier)
+
+### IF Tier 1 (explicit):
+
+1. **Identify boundaries:** Split the prompt at each "une application" / "an application" occurrence. Each block = one candidate.
+2. **Extract per candidate:** For each block, derive `name` (application name), `description` (summary of purpose), and `modules[]` (listed modules/features).
+   - Example: `[{ name: "RH", description: "gestion des employés, congés, temps", modules: ["Employés", "Congés", "Temps"] }, ...]`
+3. **Detect shared modules:** Collect all module names across all candidates. Any module appearing in more than one candidate is a shared module.
+   - Example: `sharedModules = ["Temps"]` (appears in both RH and Projet)
+
+### IF Tier 2 (domain-diversity):
+
+1. Each DISTINCT domain = 1 candidate application:
+   - `name` = short domain label (e.g., "RH", "CRM", "Finance")
+   - `description` = user's expressed need for that domain
+   - `modules[]` = sub-functionalities mentioned (can be empty → "(à définir au cadrage)")
+2. Group RELATED sub-domains under their parent DISTINCT domain as modules
+3. **Detect shared modules:** Same logic as Tier 1 — modules appearing in multiple candidates
+
+## Confirmation Dialogue
+
+Display detection result:
+
+```
+{detectionTier == "explicit"
+  ? (language == "fr"
+    ? "### Détection multi-application\n\nJ'ai détecté **{candidates.length} applications** dans votre description :"
+    : "### Multi-application detection\n\nI detected **{candidates.length} applications** in your description:")
+  : (language == "fr"
+    ? "### Détection multi-application\n\nVotre description couvre **{candidates.length} domaines métier distincts**. Chaque domaine pourrait constituer une application séparée :"
+    : "### Multi-application detection\n\nYour description covers **{candidates.length} distinct business domains**. Each domain could be a separate application:")}
+
+| # | Application | Modules identifiés |
+|---|-------------|-------------------|
+{for each candidate: index | name | modules.join(", ") || "(à définir au cadrage)"}
+
+{sharedModules.length > 0
+  ? "⚠️ **Modules partagés détectés :** {sharedModules.join(', ')} — ces modules apparaissent dans plusieurs applications. Ils pourraient constituer une application transversale dédiée."
+  : ""}
+```
+
+### AskUserQuestion Options
+
+```
+question: "{language == 'fr' ? 'Confirmez-vous cette structure multi-application ?' : 'Do you confirm this multi-application structure?'}"
+header: "Architecture"
+options:
+  - label: "{language == 'fr' ? 'Oui, {candidates.length} applications' : 'Yes, {candidates.length} applications'}"
+    description: "{language == 'fr' ? 'Créer un projet avec les applications identifiées' : 'Create a project with the identified applications'}"
+  - label: "{language == 'fr' ? 'Extraire les modules partagés' : 'Extract shared modules'}" (only if sharedModules.length > 0)
+    description: "{language == 'fr' ? 'Créer une application dédiée pour {sharedModules.join(', ')} ({candidates.length + 1} applications au total)' : 'Create a dedicated app for {sharedModules.join(', ')} ({candidates.length + 1} total)'}"
+  - label: "{language == 'fr' ? 'Regrouper certains domaines' : 'Regroup some domains'}" (only if detectionTier == "domain-diversity")
+    description: "{language == 'fr' ? 'Fusionner des domaines en moins d\\'applications' : 'Merge domains into fewer applications'}"
+  - label: "{language == 'fr' ? 'Application unique' : 'Single application'}"
+    description: "{language == 'fr' ? 'Tout regrouper en une seule application avec plusieurs modules' : 'Group everything into one application with multiple modules'}"
+```
+
+## Handling User Responses
+
+### IF "Oui, N applications" or "Extraire les modules partagés":
+
+```yaml
+workflow_mode: "project"
+project_name: derived from feature_description
+candidate_applications: [{ name, description, modules, context }]
+shared_modules_extracted: boolean  # true if user chose extraction
+```
+
+→ Skip step 4 (application name) — applications will be confirmed in step-01-cadrage
+→ Continue to step 5 (language selection)
+
+### IF "Regrouper certains domaines" (Tier 2 only):
+
+Ask via AskUserQuestion:
+```
+question: "{language == 'fr' ? 'Comment souhaitez-vous regrouper ces domaines ? (ex: \"RH + Paie ensemble, CRM seul\")' : 'How would you like to regroup these domains? (e.g., \"HR + Payroll together, CRM alone\")'}"
+header: "Regroupement"
+```
+
+Process user response:
+1. Parse the grouping instructions (natural language)
+2. Rebuild `candidate_applications` based on the specified groups
+3. Re-display the confirmation dialogue with the updated candidates
+
+### IF "Application unique":
+
+```yaml
+workflow_mode: "application"
+```
+
+→ Continue to step 4 normally
+
+### IF no multi-app detected (neither Tier 1 nor Tier 2):
+
+→ Continue to step 4 normally

package/templates/skills/business-analyse/references/portal-classification.md

@@ -0,0 +1,52 @@
+# Portal Classification
+
+> **Note :** La detection initiale des utilisateurs externes a lieu dans le batch 1 (4a).
+> Ce bloc RESOUT la detection en classifiant les stakeholders et configurant le portail.
+
+## External Signals Detection
+
+```
+EXTERNAL_SIGNALS = ["client", "customer", "fournisseur", "supplier", "partenaire",
+  "partner", "portail", "portal", "externe", "external", "tiers", "third-party",
+  "organisation cliente"]
+```
+
+## SmartStack Native Support
+
+> **SmartStack gère nativement les utilisateurs externes :**
+> - **Person Extension Pattern** : User → Employee, Contact, Customer via `UserId` FK
+> - **Organisation Extension** : Organisation → Client, Supplier via `OrganisationId` FK
+> - **Multi-tenant** : portail et interne déployés sur des tenants séparés automatiquement
+
+## Classification and Portal Mode Resolution
+
+SI `_portalDetected` (from batch 1) OU un profil stakeholder (batch 2) match EXTERNAL_SIGNALS :
+  → **Auto-classifier** chaque stakeholder : `audience: "internal" | "external" | "shared"`
+  → **Auto-déduire** `_portalMode` :
+
+| Stakeholders détectés | `_portalMode` |
+|----------------------|---------------|
+| Internes + Externes | `"dual"` |
+| Uniquement externes | `"portal-only"` |
+| Uniquement internes | `"internal-only"` |
+
+## Portal Module Rule (SCOPE LOCK)
+
+SI `_portalMode = "dual"` ou `"portal-only"`:
+  Un portail = UN module "Portal" avec des sections view par entite.
+  INTERDICTION de creer des modules separes MyAccount, MyProjects, MyInvoices.
+  Le module Portal aura des sections (view/inherit) pour chaque zone accessible.
+
+## Client Notification
+
+→ **Informer le client** (statement, PAS de question) :
+
+```
+"{language == 'fr'
+  ? 'J\'ai détecté des utilisateurs externes ({profiles}). SmartStack déploiera automatiquement un portail dédié ({_portalMode}) avec isolation multi-tenant. Les extensions Person/Organisation gèrent nativement la séparation des profils internes et externes.'
+  : 'I detected external users ({profiles}). SmartStack will automatically deploy a dedicated portal ({_portalMode}) with multi-tenant isolation. Person/Organisation extensions natively handle the separation of internal and external profiles.'}"
+```
+
+## Default Case
+
+SI aucun profil ne match EXTERNAL_SIGNALS → `_portalMode = "internal-only"` (défaut silencieux, rien à informer).

package/templates/skills/business-analyse/references/robustness-checks.md

@@ -61,7 +61,7 @@ Ensures each module has ALL required components before being marked as "specifie
 | 5.1 | Sections count | ≥2 | YES | Modules need list + form minimum |
 | 5.2 | Wireframes count | 1 per section | YES | EVERY section MUST have wireframe |
 | 5.3 | Navigation entries | ≥1 | YES | Module must be accessible in menu |
-| 5.4 | Navigation route patterns | No `/list` or `/detail/:id` suffixes | YES | list route = module route (index), detail route = module + /:id. FORBIDDEN: `/module/list`, `/module/detail/:id` |
+| 5.4 | Navigation route patterns | No `/detail/:id` suffix | YES | ALL sections use uniform route: module route + /{section-code}. list route MUST end with `/list`. FORBIDDEN: `/module/detail/:id` (detail is implicit) |
 
 #### SECTION 6: I18N & Messages (3 checks)
 

package/templates/skills/business-analyse/references/validation-checklist.md

@@ -169,20 +169,20 @@ const checklist = {
   },
 
   navigationRoutePatterns: {
-    check: "Navigation routes do NOT contain CRUD suffixes (/list, /detail/:id)",
+    check: "Navigation routes do NOT contain forbidden patterns (/detail/:id)",
     status: (() => {
       const allRoutes = [
         ...(specification.seedDataCore?.navigationSections || []).map(s => s.route),
         ...(specification.sections || []).map(s => s.route),
         ...(specification.navigation?.entries || []).map(e => e.route)
       ].filter(Boolean);
-      const forbidden = allRoutes.filter(r => r.match(/\/list$/) || r.match(/\/detail\/:id$/));
+      const forbidden = allRoutes.filter(r => r.match(/\/detail\/:id$/));
       return forbidden.length === 0 ? "PASS" : "FAIL";
     })(),
     blocking: true,
-    details: "FORBIDDEN: /module/list (use /module), /module/detail/:id (use /module/:id). " +
-             "list route = module route (React Router index route). " +
-             "detail route = module route + /:id (React Router :id child). " +
+    details: "FORBIDDEN: /module/detail/:id (detail is implicit, not a section). " +
+             "ALL sections use uniform route: module route + /{section-code}. " +
+             "list route = module route + /list. " +
              "Other sections (dashboard, approve) add /{section} normally."
   },
 
@@ -262,7 +262,36 @@ const checklist = {
     details: "Modules need field validation rules"
   },
 
-  // SECTION 10: GHERKIN SCENARIOS (BLOCKING for format, WARNING for count)
+  // SECTION 10: ANALYSIS DEPTH (BLOCKING)
+  analysisDepthRules: {
+    check: "Business rules include domain-specific rules (not just generic CRUD)",
+    status: countDomainSpecificRules(analysis.businessRules) >= 2 ? "PASS" : "FAIL",
+    blocking: true,
+    details: "Module must have at least 2 domain-specific rules beyond basic validation. " +
+             "Generic rules: date coherence, required fields, unique constraints, basic workflow transitions. " +
+             "Domain-specific: half-day absences, team capacity limits, carry-over expiry, " +
+             "invoice sequential numbering, credit note linking, opportunity probability rules, etc. " +
+             "If C-pre (Business Rules Domain Research) was executed, these should come from web research."
+  },
+
+  sectionCompleteness: {
+    check: "Workflow modules have contextual filtered views",
+    status: (moduleFeatureType === "workflow" && hasContextualViews(analysis.anticipatedSections)) ? "PASS" : "FAIL",
+    blocking: true,
+    details: "Workflow modules must have at least 1 contextual filtered view " +
+             "(e.g., open-requests, rejected, my-X, history) beyond the base CRUD sections. " +
+             "A workflow module with only list/detail/approve is incomplete."
+  },
+
+  webResearchPerformed: {
+    check: "Web research was performed for this module",
+    status: module.domainResearchSource !== "built-in-only" ? "PASS" : "WARNING",
+    blocking: false,
+    details: "Modules without web research have lower completeness confidence. " +
+             "Domain-specific rules and sections may be missing."
+  },
+
+  // SECTION 11: GHERKIN SCENARIOS (BLOCKING for format, WARNING for count)
   gherkinFormat: {
     check: "gherkinScenarios is ARRAY (not single object)",
     status: Array.isArray(specification.gherkinScenarios) ? "PASS" : "FAIL",

package/templates/skills/business-analyse/schemas/sections/analysis-schema.json

@@ -24,23 +24,67 @@
         "type": "object",
         "required": ["id", "name", "category", "statement"],
         "properties": {
-          "id": { "type": "string", "pattern": "^BR-(VAL|CALC|WF|SEC|DATA)-[A-Z]{2,4}-\\d{3}$", "description": "Module-prefixed BR ID (e.g., BR-VAL-RM-001)" },
+          "id": { "type": "string", "pattern": "^BR-(VAL|CALC|WF|SEC|DATA|NOTIF)-[A-Z]{2,4}-\\d{3}$", "description": "Module-prefixed BR ID (e.g., BR-VAL-RM-001)" },
           "name": { "type": "string" },
-          "category": { "type": "string", "enum": ["validation", "calculation", "workflow", "security", "data"] },
+          "category": { "type": "string", "enum": ["validation", "calculation", "workflow", "security", "data", "notification"] },
           "statement": { "type": "string", "description": "IF ... THEN ... ELSE ..." },
           "priority": { "type": "string", "enum": ["must", "should", "could"] },
-          "conditions": { "type": "array", "items": { "type": "string" } },
+          "conditions": {
+            "type": "array",
+            "items": {
+              "oneOf": [
+                { "type": "string" },
+                {
+                  "type": "object",
+                  "properties": {
+                    "entity": { "type": "string" },
+                    "field": { "type": "string" },
+                    "operator": { "type": "string", "enum": ["==", "!=", ">", "<", ">=", "<=", "in", "not-in", "is-null", "is-not-null"] },
+                    "value": {}
+                  }
+                }
+              ]
+            }
+          },
           "examples": {
             "type": "array",
+            "description": "Test-ready examples: each example = a test case with concrete values. Minimum 2 per rule (happy_path + error). These feed Gherkin generation and automated tests.",
             "items": {
               "type": "object",
+              "required": ["input", "expected"],
               "properties": {
-                "input": { "type": "string" },
-                "expected": { "type": "string" }
+                "input": { "type": "string", "description": "LEGACY fallback. Prefer given/when/then format." },
+                "expected": { "type": "string", "description": "LEGACY fallback. Prefer given/when/then format." },
+                "scenario": { "type": "string", "enum": ["happy_path", "error", "boundary", "calculation", "security"], "description": "Test scenario type" },
+                "description": { "type": "string", "description": "Human-readable test case description" },
+                "given": { "type": "object", "description": "Initial state: Entity.field → concrete value. Ex: {\"Employee.code\": \"EMP-001\", \"existingCodes\": [\"EMP-001\"]}", "additionalProperties": true },
+                "when": { "type": "string", "description": "Triggering action. Ex: 'create', 'update', 'submit', 'calculate_remaining'" },
+                "then": { "type": "object", "description": "Expected outcome: {result: 'success'|'error', Entity.field: value, message: '...', field: '...'}", "additionalProperties": true }
+              }
+            }
+          },
+          "entities": {
+            "type": "array",
+            "items": { "type": "string" },
+            "description": "Entity names this rule applies to"
+          },
+          "testability": { "type": "string" },
+          "formula": { "type": "string", "description": "BR-CALC calculation formulas" },
+          "sectionCode": { "type": "string", "description": "Section code the rule applies to" },
+          "severity": { "type": "string", "enum": ["blocking", "warning", "info"] },
+          "consequences": {
+            "type": "array",
+            "items": {
+              "type": "object",
+              "required": ["type", "target"],
+              "properties": {
+                "type": { "type": "string", "enum": ["notification", "field-update", "status-change", "block-action", "recalculate"] },
+                "target": { "type": "string" },
+                "description": { "type": "string" }
               }
             }
           },
-          "testability": { "type": "string" }
+          "domainSpecific": { "type": "boolean", "default": false, "description": "True if from domain research" }
         }
       }
     },

package/templates/skills/business-analyse/steps/step-00-init.md

@@ -121,138 +121,9 @@ existing_projects: array of { projectName, projectId, applications[], version }
 
 ## Step 3b: Early Multi-Application Detection from Prompt (NEW)
 
-> **Detect multi-app structure BEFORE asking for a single application name.**
-> When the user's prompt describes multiple applications or spans multiple business domains,
-> we must recognize this immediately and set `workflow.mode = "project"` to avoid doing cadrage for a single app.
+> → **Load** `references/multi-app-detection.md` for the multi-app detection algorithm (Tier 1 patterns, Tier 2 domain diversity scoring, extraction, confirmation).
 
-### Tier 1 — Explicit patterns (ANY match = multi-app detected)
-
-French patterns:
-- "une application X ... une application Y" (two occurrences of "une application")
-- "application 1: X ... application 2: Y" (numbered applications)
-- "première application ... deuxième application"
-- "app 1: ... app 2: ..."
-
-English patterns:
-- "an application (for) X ... an application (for) Y" (two occurrences)
-- "application #1: ... application #2: ..." (numbered)
-- "first app ... second app"
-
-If ANY of these patterns is found in `{feature_description}`:
-→ `isMultiApp = true`, `detectionTier = "explicit"`
-
-### Tier 2 — Domain diversity analysis (when Tier 1 does not match)
-
-ULTRATHINK: Analyze `{feature_description}` to extract distinct business domains.
-
-**Definition:** A "domain" is an autonomous business perimeter with its own entities and processes (e.g., HR, CRM, Finance, Projects, Sales, Inventory).
-
-**Algorithm:**
-1. List all business domains mentioned or implied in the description
-2. Classify each domain:
-   - **DISTINCT** — has its own entities, processes, and lifecycle (e.g., HR vs CRM)
-   - **RELATED** — is a sub-domain of another (e.g., Payroll is a sub-domain of HR)
-3. Count DISTINCT domains only
-
-**Threshold:** 2+ DISTINCT domains → `isMultiApp = true`, `detectionTier = "domain-diversity"`
-
-**False positive protection:**
-- "RH complet avec employés, congés, paie, pointage" = 1 domain (HR) with 4 modules, NOT 4 domains
-- "HR and Payroll management" = 1 domain (HR) with 2 modules — Payroll is RELATED to HR
-- "gestion commerciale avec devis, commandes et facturation" = 1 domain (Sales) with 3 modules
-- Only count as DISTINCT when domains have genuinely independent entity models and processes
-
-### Extraction algorithm (depends on detection tier)
-
-**IF Tier 1 (explicit):**
-
-1. **Identify boundaries:** Split the prompt at each "une application" / "an application" occurrence. Each block = one candidate.
-2. **Extract per candidate:** For each block, derive `name` (application name), `description` (summary of purpose), and `modules[]` (listed modules/features).
-   - Example: `[{ name: "RH", description: "gestion des employés, congés, temps", modules: ["Employés", "Congés", "Temps"] }, ...]`
-3. **Detect shared modules:** Collect all module names across all candidates. Any module appearing in more than one candidate is a shared module.
-   - Example: `sharedModules = ["Temps"]` (appears in both RH and Projet)
-
-**IF Tier 2 (domain-diversity):**
-
-1. Each DISTINCT domain = 1 candidate application:
-   - `name` = short domain label (e.g., "RH", "CRM", "Finance")
-   - `description` = user's expressed need for that domain
-   - `modules[]` = sub-functionalities mentioned (can be empty → "(à définir au cadrage)")
-2. Group RELATED sub-domains under their parent DISTINCT domain as modules
-3. **Detect shared modules:** Same logic as Tier 1 — modules appearing in multiple candidates
-
-### Confirmation dialogue
-
-Display detection result:
-
-```
-{detectionTier == "explicit"
-  ? (language == "fr"
-    ? "### Détection multi-application\n\nJ'ai détecté **{candidates.length} applications** dans votre description :"
-    : "### Multi-application detection\n\nI detected **{candidates.length} applications** in your description:")
-  : (language == "fr"
-    ? "### Détection multi-application\n\nVotre description couvre **{candidates.length} domaines métier distincts**. Chaque domaine pourrait constituer une application séparée :"
-    : "### Multi-application detection\n\nYour description covers **{candidates.length} distinct business domains**. Each domain could be a separate application:")}
-
-| # | Application | Modules identifiés |
-|---|-------------|-------------------|
-{for each candidate: index | name | modules.join(", ") || "(à définir au cadrage)"}
-
-{sharedModules.length > 0
-  ? "⚠️ **Modules partagés détectés :** {sharedModules.join(', ')} — ces modules apparaissent dans plusieurs applications. Ils pourraient constituer une application transversale dédiée."
-  : ""}
-```
-
-Ask via AskUserQuestion:
-```
-question: "{language == 'fr' ? 'Confirmez-vous cette structure multi-application ?' : 'Do you confirm this multi-application structure?'}"
-header: "Architecture"
-options:
-  - label: "{language == 'fr' ? 'Oui, {candidates.length} applications' : 'Yes, {candidates.length} applications'}"
-    description: "{language == 'fr' ? 'Créer un projet avec les applications identifiées' : 'Create a project with the identified applications'}"
-  - label: "{language == 'fr' ? 'Extraire les modules partagés' : 'Extract shared modules'}" (only if sharedModules.length > 0)
-    description: "{language == 'fr' ? 'Créer une application dédiée pour {sharedModules.join(', ')} ({candidates.length + 1} applications au total)' : 'Create a dedicated app for {sharedModules.join(', ')} ({candidates.length + 1} total)'}"
-  - label: "{language == 'fr' ? 'Regrouper certains domaines' : 'Regroup some domains'}" (only if detectionTier == "domain-diversity")
-    description: "{language == 'fr' ? 'Fusionner des domaines en moins d\\'applications' : 'Merge domains into fewer applications'}"
-  - label: "{language == 'fr' ? 'Application unique' : 'Single application'}"
-    description: "{language == 'fr' ? 'Tout regrouper en une seule application avec plusieurs modules' : 'Group everything into one application with multiple modules'}"
-```
-
-**IF "Oui, N applications" or "Extraire les modules partagés":**
-
-```yaml
-workflow_mode: "project"
-project_name: derived from feature_description
-candidate_applications: [{ name, description, modules, context }]
-shared_modules_extracted: boolean  # true if user chose extraction
-```
-
-→ Skip step 4 (application name) — applications will be confirmed in step-01-cadrage
-→ Continue to step 5 (language selection)
-
-**IF "Regrouper certains domaines" (Tier 2 only):**
-
-Ask via AskUserQuestion:
-```
-question: "{language == 'fr' ? 'Comment souhaitez-vous regrouper ces domaines ? (ex: \"RH + Paie ensemble, CRM seul\")' : 'How would you like to regroup these domains? (e.g., \"HR + Payroll together, CRM alone\")'}"
-header: "Regroupement"
-```
-
-Process user response:
-1. Parse the grouping instructions (natural language)
-2. Rebuild `candidate_applications` based on the specified groups
-3. Re-display the confirmation dialogue with the updated candidates
-
-**IF "Application unique":**
-
-```yaml
-workflow_mode: "application"
-```
-
-→ Continue to step 4 normally
-
-**IF no multi-app detected (neither Tier 1 nor Tier 2):**
-→ Continue to step 4 normally
+Execute the multi-app detection. IF multi-app detected → set `workflow_mode = "project"` and skip step 4 (application name). ELSE continue to step 4 normally.
 
 ## Step 4: Determine Project Name & Application Name
 
@@ -365,20 +236,27 @@ ELSE:
 feature_id: string
 ```
 
-## Step 7: Create Output Directory Structure
+## Step 7: Create Output Directory Structure (EXECUTABLE)
 
 ```
 projectDir = "docs/" + projectSlug + "/v" + version
+docs_dir = projectDir
+```
 
-IF workflow_type = "new":
-  mkdir -p {projectDir}
-  docs_dir = projectDir
+**MANDATORY — Execute via Bash tool (NOT just pseudocode):**
 
-ELSE:
-  // Directory already exists from previous session
-  docs_dir = projectDir
+```bash
+mkdir -p "{projectDir}"
+```
+
+**POST-CHECK (BLOCKING):**
+
+```bash
+ls -d "{projectDir}" 2>/dev/null || echo "DIRECTORY_MISSING"
 ```
 
+If output contains `DIRECTORY_MISSING` → **BLOCKING ERROR: directory creation failed. Check permissions.**
+
 > **Key change (ba-006):** All project data lives under `docs/{projectSlug}/v{X.Y}/`.
 > No more `business-analyse/` intermediate directory. Applications and modules are
 > direct subdirectories: `docs/{projectSlug}/v{X.Y}/{appKebab}/{moduleKebab}/`.
@@ -575,57 +453,11 @@ analysisMode: "interactive"
 version: string
 ```
 
-## Error Handling
-
-| Error | Action |
-|-------|--------|
-| Config missing | Create fresh with defaults, continue |
-| Directory creation fails | Check permissions, display error, EXIT |
-| index.json creation fails | Validate ba-writer, retry or fallback |
-| Feature ID not unique | Generate new ID, retry |
-
-### Resume After Interruption
-
-If initialization was interrupted:
-
-1. Check `.business-analyse/config.json` for currentFeature or currentProject
-2. If project ID exists, search for project index.json in `docs/*/v*/` (or legacy `docs/business-analyse/`)
-   - If found with scope = "project": resume project mode (see Project Resume below)
-3. If feature ID exists, search for index.json in `docs/`
-4. If found, check status and `metadata.workflow.lastCompletedStep`:
-
-   **Status-based resume routing (check in this order):**
-
-   - If status = `"handed-off"` or `"consolidated"`:
-     → Display: "BA workflow complete. Use /business-analyse-html to generate HTML, /business-analyse-review for corrections."
-     → STOP
-
-   - If status = `"specified"` AND `metadata.workflow.allModulesSpecified === true`:
-     → Resume at `step-04-consolidate.md`
-     → Display: "All modules specified — resuming at consolidation..."
-
-   - If status = `"specified"` AND `metadata.workflow.completedModules.length > 0` AND `metadata.workflow.completedModules.length < metadata.workflow.moduleOrder.length`:
-     → Resume at `step-03-specify.md` (continue specifying remaining modules)
-     → Display: "Resuming module specification ({completedCount}/{totalCount})..."
-
-   - Otherwise: offer to resume from last completed step
-
-5. If not found, create fresh index.json
-
-**Project Resume (project mode):**
-
-If a project-level index.json is found (scope = "project"):
-
-   - If status = `"draft"` or `"framed"`:
-     → Resume at `step-01-cadrage.md`
-
-   - If status = `"decomposed"`:
-     → Check `metadata.workflow.currentApplicationIndex` and `completedApplications[]`
-     → Resume module specification for current application (step-02 or step-03)
+## Error Handling & Resume Logic
 
-   - If status = `"specified"`:
-     → All applications specified → Resume at `step-04-consolidate.md`
+> → **Load** `references/init-resume-logic.md` for error handling matrix, resume detection, and status-based routing (draft → framed → decomposed → specified → consolidated → handed-off).
 
-   - If status = `"consolidated"`:
-     → Display: "BA workflow complete. Use /business-analyse-html to generate HTML."
-     → STOP
+When re-running initialization, check for interrupted workflows:
+1. Read `.business-analyse/config.json` for currentFeature or currentProject
+2. Search for existing index.json files in `docs/` hierarchy
+3. Check status and route appropriately (see reference for status-based routing matrix)