@atlashub/smartstack-cli 4.40.0 → 4.42.0

package/templates/skills/business-analyse/questionnaire/03-data-ui.md

@@ -35,6 +35,35 @@
 | Q3.12 | Informations clés par écran ? Quelles colonnes dans la liste, quels champs dans le formulaire ? | Par écran |
 | Q3.13 | Actions possibles par écran ? (créer, éditer, supprimer, valider, exporter, changer statut) | Par écran |
 
+## 3.5 Volumétrie et performance
+
+| # | Question | Type de réponse |
+|---|----------|-----------------|
+| Q3.17 | Combien de [entité] prévoyez-vous ? (par mois et total à 2 ans) | Estimation chiffrée |
+| Q3.18 | Y a-t-il des pics d'utilisation ? (fin de mois, clôture annuelle) | Description des pics |
+
+- Relance si vague : "Moins de 100 ? Entre 100-10 000 ? Plus de 10 000 ?"
+- Mapping → `entities.json` : champ `estimatedVolume` (`monthly`, `total2y`)
+
+## 3.6 Recherche et filtres
+
+| # | Question | Type de réponse |
+|---|----------|-----------------|
+| Q3.19 | Par quels critères cherchez-vous un [entité] ? (nom, date, statut, code...) | Liste de critères |
+| Q3.20 | Quels filtres rapides sont indispensables dans la liste ? | Liste de filtres |
+
+- Relance : "Triez-vous souvent par date ? Filtrez-vous par statut ?"
+- Mapping → `entities.json` : champs `searchableFields[]` et `defaultFilters[]`
+
+## 3.7 Notifications et alertes
+
+| # | Question | Type de réponse |
+|---|----------|-----------------|
+| Q3.21 | Quels événements doivent déclencher une notification ? (création, approbation, deadline...) | Liste d'événements |
+| Q3.22 | Qui doit être notifié ? Par quel canal ? (in-app, email) | Cible + canal |
+
+- Mapping → `rules.json` : règles de catégorie `notification`
+
 ## 3.4 Tableaux de bord
 
 | # | Question | Type de réponse |
@@ -58,6 +87,7 @@
 | Q3.11 (écrans) | "Un écran de liste" | "Avec pages dédiées pour création et édition ? Détail en page avec onglets ?" |
 | Q3.13 (actions) | "CRUD classique" | "Actions métier spécifiques ? (valider, dupliquer, archiver, changer statut, assigner)" |
 | Q3.14 (dashboards) | "Juste des chiffres" | "Les tendances ne seraient-elles pas plus lisibles en graphique ?" |
+| Q3.17 (volume) | "Je ne sais pas" | "Commençons petit : combien d'employés dans l'entreprise ? Combien de factures par mois environ ?" |
 
 ### Anti-patterns à détecter
 
@@ -90,3 +120,6 @@
 | Q3.7-Q3.9 | `rules.json` (règles métier de validation et sécurité) |
 | Q3.10-Q3.13 | `screens.json` (sections, resources, colonnes, actions) |
 | Q3.14-Q3.16 | `screens.json` (sections dashboard, KPI resources) |
+| Q3.17-Q3.18 | `entities.json` (estimatedVolume) |
+| Q3.19-Q3.20 | `entities.json` (searchableFields, defaultFilters) |
+| Q3.21-Q3.22 | `rules.json` (règles category: notification) |

package/templates/skills/business-analyse/questionnaire/04-risks-metrics.md

@@ -3,4 +3,4 @@
 > **NOT USED** — Les risques projet, hypotheses, lecons du passe, metriques de succes et conditions de livraison
 > ne sont pas du scope de la BA en vibe coding.
 >
-> La documentation technique est generee automatiquement par `/documentation` apres `/ralph-loop`.
+> La documentation technique est generee automatiquement par `/documentation` apres `/business-analyse-develop`.

package/templates/skills/business-analyse/react/components.md

@@ -1,7 +1,7 @@
 # React Components - Business Analyse Viewer
 
 > **Usage:** React component that renders index.json directly
-> **Loaded in:** /ba-generate-html
+> **Loaded in:** /business-analyse-html
 > **Data source (module):** `docs/{app}/{module}/business-analyse/v{X.Y}/index.json`
 > **Data source (application):** `docs/{app}/business-analyse/v{X.Y}/index.json`
 > **Related:** `react/application-viewer.md` for application-level view

package/templates/skills/business-analyse/react/schema.md

@@ -1,7 +1,7 @@
 # TypeScript Schema - Feature JSON Types
 
 > **Usage:** TypeScript interfaces aligned with index.json and application-schema.json
-> **Loaded in:** /ba-generate-html (for web app rendering)
+> **Loaded in:** /business-analyse-html (for web app rendering)
 > **Source (module):** `docs/{app}/{module}/business-analyse/v{X.Y}/index.json`
 > **Source (application):** `docs/{app}/business-analyse/v{X.Y}/index.json`
 

package/templates/skills/business-analyse/references/acceptance-criteria.md

@@ -1,6 +1,6 @@
 # Module Acceptance Criteria (Shared Reference)
 
-> **Loaded by:** step-03-specify (post-check), ralph-loop step-01-task (input validation)
+> **Loaded by:** step-03-specify (post-check), business-analyse-develop step-01-task (input validation)
 > **Purpose:** Define measurable, bash-verifiable acceptance criteria that a module MUST pass before being marked "specified".
 > **Key principle:** These checks read the REAL JSON files on disk — NOT in-memory data the model "thinks" it wrote.
 
@@ -137,11 +137,11 @@ console.log('PASS: All acceptance criteria met (AC-01 to AC-17)');
 After writing module JSON files, run the bash script above.
 IF FAIL → re-execute section 11 write with corrected data → re-run until PASS.
 
-### 2. ralph-loop step-01-task.md (input validation)
+### 2. business-analyse-develop step-01-task.md (input validation)
 
 At PRD load time, run the bash script on each module index.json.
 IF FAIL → BLOCKING: "Module {name} does not meet acceptance criteria — run /business-analyse to fix".
-This prevents ralph-loop from generating code from incomplete specifications.
+This prevents business-analyse-develop from generating code from incomplete specifications.
 
 ---
 

package/templates/skills/business-analyse/references/consolidation-structural-checks.md

@@ -20,7 +20,7 @@
 | `specification.wireframes[]` | YES | Must have >=1 wireframe with `layout` object |
 | `specification.lifeCycles[]` | IF entities have status | States must be objects (NOT strings) |
 | `specification.seedDataCore` | YES | Must have 9 arrays: navigationApplications, applicationRoles, navigationModules, navigationSections, navigationResources, navigationTranslations, permissions, rolePermissions, permissionConstants |
-| `specification.seedDataBusiness` | NO (WARNING) | Business seed data is generated during implementation (ralph-loop), not during BA. If present, validates format. |
+| `specification.seedDataBusiness` | NO (WARNING) | Business seed data is generated during implementation (business-analyse-develop), not during BA. If present, validates format. |
 | `specification.gherkinScenarios` | YES | Must be `[{feature, scenarios[]}]` (array of objects, NOT single object or flat array) |
 | `specification.navigation` | YES | Must have entries[] |
 | `specification.i18nKeys[]` | YES | Must have >=1 key with fr, en, it, de |

package/templates/skills/business-analyse/references/detection-strategies.md

@@ -73,7 +73,7 @@ function detectReviewMode(feature_description) {
 | Condition | Action |
 |-----------|--------|
 | `{feature_description}` starts with `-review` | Activate review mode detection |
-| ba-review.json found | Redirect user to `/ba-review` skill |
+| ba-review.json found | Redirect user to `/business-analyse-review` skill |
 | ba-review.json NOT found | Display error with fix instructions, STOP |
 | No applications exist | Display error, STOP |
 
@@ -416,7 +416,7 @@ interface DetectionResult {
 **Test Case 4: Review Mode**
 - Input: `"-review"`
 - Existing: `HumanResources` with ba-review.json present
-- Expected: Redirect user to `/ba-review` skill
+- Expected: Redirect user to `/business-analyse-review` skill
 
 **Test Case 5: Review Mode - File Missing**
 - Input: `"-review"`

package/templates/skills/business-analyse/references/entity-architecture-decision.md

@@ -135,7 +135,7 @@ L'entite {E} est-elle CORE pour cette application ?
 
 ## 4. Section Pattern for Modules
 
-> **REGLE FONDAMENTALE : Les sections representent des zones fonctionnelles, PAS des operations CRUD.**
+> **REGLE FONDAMENTALE : Les sections representent des sections fonctionnelles, PAS des operations CRUD.**
 
 ### Le pattern de navigation SmartStack
 

package/templates/skills/business-analyse/references/naming-conventions.md

@@ -71,11 +71,11 @@ Route = ToKebabCase($"/{appCode}/{moduleCode}")
 - `Projects` → `projects` (single word, no change)
 - `AI` → `ai` (acronym lowercase)
 
-**Implementation:** See `templates/skills/ralph-loop/references/core-seed-data.md` line 162
+**Implementation:** See `templates/skills/business-analyse-develop/references/core-seed-data.md` line 162
 
 ### JavaScript (BA Handoff Generation)
 
-**Location:** Used in /ba-generate-html when building seedDataCore
+**Location:** Used in /business-analyse-html when building seedDataCore
 
 **Usage:**
 ```javascript
@@ -113,7 +113,7 @@ function toKebabCase(str: string): string {
 
 ## Validation
 
-### During Generation (ralph-loop)
+### During Generation (business-analyse-develop)
 
 POST-CHECK after NavigationSeedData generation:
 
@@ -237,7 +237,7 @@ src/API/Controllers/HumanResources/TimeManagementController.cs
 
 ## References
 
-- **Template:** `templates/skills/ralph-loop/references/core-seed-data.md`
+- **Template:** `templates/skills/business-analyse-develop/references/core-seed-data.md`
 - **Validation:** `src/mcp/tools/validate-frontend-routes.ts`
-- **POST-CHECK:** `templates/skills/ralph-loop/steps/step-02-execute.md` (section 5)
-- **Handoff:** `/derive-prd` skill (handoff section)
+- **POST-CHECK:** `templates/skills/business-analyse-develop/steps/step-02-execute.md` (section 5)
+- **Handoff:** `/business-analyse-handoff` skill (handoff section)

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

@@ -5,7 +5,7 @@
 
 ## Overview
 
-This document consolidates all robustness checks implemented across the business-analyse workflow. Each check serves to catch issues early, before they cause ralph-loop failures or runtime errors.
+This document consolidates all robustness checks implemented across the business-analyse workflow. Each check serves to catch issues early, before they cause business-analyse-develop failures or runtime errors.
 
 ---
 
@@ -151,7 +151,7 @@ DO NOT PROCEED TO CONSOLIDATION UNTIL ALL CHECKS PASS
 
 ### Purpose
 
-Verifies ALL cross-module entity references are resolvable. Prevents FK constraint violations and runtime errors during ralph-loop code generation.
+Verifies ALL cross-module entity references are resolvable. Prevents FK constraint violations and runtime errors during business-analyse-develop code generation.
 
 ### Process
 
@@ -264,7 +264,7 @@ DEVELOPMENT CANNOT PROCEED WITH CIRCULAR DEPENDENCIES
 
 ---
 
-> **Note:** Ralph Readiness Validation (PRD files, handoff completeness, etc.) is handled by the `/derive-prd` skill.
+> **Note:** Ralph Readiness Validation (PRD files, handoff completeness, etc.) is handled by the `/business-analyse-handoff` skill.
 
 ---
 
@@ -416,7 +416,7 @@ WHERE: Return to step-03-specify.md for TimeTracking module
 
 **Success:**
 - Application marked as "consolidated"
-- Ready for `/ba-generate-html` and `/derive-prd`
+- Ready for `/business-analyse-html` and `/business-analyse-handoff`
 
 ---
 

package/templates/skills/business-analyse/references/spec-auto-inference.md

@@ -32,9 +32,9 @@
 
 ## Auto-Generated UI Components by featureType
 
-> **RULE:** Sections = functional zones only. `create`/`edit` are separate pages with own URL routes (`/create` and `/:id/edit`). `detail` is a tabbed page reached from `list`.
+> **RULE:** Sections are functional, not CRUD-based. `create`/`edit` are separate pages with own URL routes (`/create` and `/:id/edit`). `detail` is a tabbed page reached from `list`.
 
-| featureType | Sections (functional zones) | permissionMode | List page includes | Form pages | Detail page tabs |
+| featureType | Sections (functional) | permissionMode | List page includes | Form pages | Detail page tabs |
 |---|---|---|---|---|---|
 | data-centric | list | `crud` | grid, filters, create button | `/create` page, `/:id/edit` page | Infos, {relations} |
 | data-centric | (detail — implicit) | `inherit` | — | — | — |

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

@@ -2,7 +2,7 @@
 
 > **Authoritative minimums:** See `_shared.md` for the single source of truth on all minimum thresholds.
 > **CRITICAL:** This checklist MUST be FULLY COMPLETED before marking module status = "specified".
-> **Rationale:** Prevents incomplete modules from reaching handoff, reduces ralph-loop failures.
+> **Rationale:** Prevents incomplete modules from reaching handoff, reduces business-analyse-develop failures.
 
 ## Checklist Structure
 
@@ -232,8 +232,8 @@ const checklist = {
   seedDataBusiness: {
     check: "Business seed data template defined (if applicable — generated during implementation, not BA)",
     status: specification.seedDataBusiness !== undefined ? "PASS" : "WARN",
-    blocking: false,  // WARNING only — business seed data is generated during ralph-loop implementation, not during BA phase
-    details: "Business seed data (reference types, categories, statuses) is generated during implementation (ralph-loop). " +
+    blocking: false,  // WARNING only — business seed data is generated during business-analyse-develop implementation, not during BA phase
+    details: "Business seed data (reference types, categories, statuses) is generated during implementation (business-analyse-develop). " +
              "BA phase ensures seedDataCore is complete (navigation, permissions). seedDataBusiness is optional at this stage."
   },
 

package/templates/skills/business-analyse/schemas/feature-schema.json

@@ -43,7 +43,7 @@
     }
   },
 
-  "$comment": "Sub-schema loading guide per BA step: step-00-init → metadata-schema.json | step-01-cadrage → discovery-schema.json (module) OR application-schema.json (master) | step-02-structure → application-schema.json (modules[], dependencyGraph) | step-03-specify → analysis-schema.json + specification-schema.json | step-04-consolidate → validation-schema.json + application-schema.json (consolidation). HTML generation → /ba-generate-html skill. Review corrections → /ba-review skill. Handoff → /derive-prd skill",
+  "$comment": "Sub-schema loading guide per BA step: step-00-init → metadata-schema.json | step-01-cadrage → discovery-schema.json (module) OR application-schema.json (master) | step-02-structure → application-schema.json (modules[], dependencyGraph) | step-03-specify → analysis-schema.json + specification-schema.json | step-04-consolidate → validation-schema.json + application-schema.json (consolidation). HTML generation → /business-analyse-html skill. Review corrections → /business-analyse-review skill. Handoff → /business-analyse-handoff skill",
 
   "$defs": {
     "stepStatus": { "$ref": "shared/common-defs.json#/$defs/stepStatus" },

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

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "handoff-schema.json",
   "title": "SmartStack BA - Handoff",
-  "description": "Module-level handoff: file mapping (8 categories), BR-to-code mapping, API endpoint summary. Used by /derive-prd skill.",
+  "description": "Module-level handoff: file mapping (8 categories), BR-to-code mapping, API endpoint summary. Used by /business-analyse-handoff skill.",
   "type": "object",
   "properties": {
     "complexity": { "type": "string", "enum": ["simple", "medium", "complex"] },
@@ -61,7 +61,7 @@
     },
     "ralphPrd": {
       "type": "object",
-      "description": "Embedded Ralph Loop task breakdown (also exported to .ralph/prd.json by ss derive-prd)",
+      "description": "Embedded Ralph Loop task breakdown (also exported to .ralph/prd.json by ss business-analyse-handoff)",
       "properties": {
         "tasks": {
           "type": "array",

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

@@ -26,6 +26,7 @@
           "id": { "type": "string", "pattern": "^UC-[A-Z]{2,4}-\\d{3}$", "description": "Module-prefixed UC ID (e.g., UC-RM-001)" },
           "name": { "type": "string" },
           "primaryActor": { "type": "string" },
+          "sectionCode": { "type": "string", "description": "Code of the anticipatedSection this UC belongs to (e.g., list, detail, dashboard). Must match a code in anticipatedSections[]." },
           "permission": { "type": "string", "description": "Module-level: {app}.{module}.{action} or section-level: {app}.{module}.{section}.{action}" },
           "preconditions": { "type": "array", "items": { "type": "string" } },
           "postconditions": { "type": "array", "items": { "type": "string" } },
@@ -214,7 +215,7 @@
           },
           "layout": {
             "type": "object",
-            "description": "Structural layout for deterministic consumption by ralph-loop. Source of truth for code generation.",
+            "description": "Structural layout for deterministic consumption by business-analyse-develop. Source of truth for code generation.",
             "properties": {
               "type": { "type": "string", "enum": ["page", "dialog", "panel"] },
               "regions": {
@@ -509,7 +510,7 @@
     },
     "sections": {
       "type": "array",
-      "description": "Level 4 (Section) decomposition. Each section = 1 React page. MANDATORY for ralph-loop consumption.",
+      "description": "Level 4 (Section) decomposition. Each section = 1 React page. MANDATORY for business-analyse-develop consumption.",
       "items": {
         "type": "object",
         "required": ["code", "labels", "route", "permission", "wireframe", "useCases", "resources"],

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

@@ -101,7 +101,7 @@ Execute workflow detection algorithm:
    - Continue to application name determination.
 
 **Key decision points:**
-1. IF review mode → inform user to use `/ba-review` skill instead
+1. IF review mode → inform user to use `/business-analyse-review` skill instead
 2. IF no existing apps → workflow_type = "new"
 3. IF existing apps → analyze similarity → prompt user
 
@@ -418,7 +418,7 @@ This guard catches any accidental creation of module-only files at the wrong sco
 
 ## Step 10: Update Config
 
-Update `.business-analyse/config.json` with new feature information.
+Write ALL context variables to `.business-analyse/config.json`. This file is the **single source of truth** for session state — downstream steps MUST re-read it instead of assuming LLM memory.
 
 ```json
 {
@@ -427,12 +427,22 @@ Update `.business-analyse/config.json` with new feature information.
     "version": "{version}",
     "docsDir": "{docs_dir}",
     "workflowType": "{workflow_type}",
-    "application": "{application_name}"
+    "workflowMode": "{workflow_mode}",
+    "application": "{application_name}",
+    "applicationCode": "{applicationCode}",
+    "projectId": "{project_id}",
+    "language": "{language}",
+    "analysisMode": "interactive",
+    "mcpAvailable": true,
+    "candidateApplications": "{candidate_applications}",
+    "sharedModulesExtracted": "{shared_modules_extracted}"
   },
   "lastInitialized": "{ISO timestamp}"
 }
 ```
 
+> **CRITICAL:** Every downstream step (01-04) MUST start by reading this file to recover variables. Do NOT rely on LLM memory for `docs_dir`, `feature_id`, `applicationCode`, or `workflow_mode`.
+
 ## Step 11: Display Summary
 
 ```
@@ -505,7 +515,7 @@ If initialization was interrupted:
    **Status-based resume routing (check in this order):**
 
    - If status = `"handed-off"` or `"consolidated"`:
-     → Display: "BA workflow complete. Use /ba-generate-html to generate HTML, /ba-review for corrections."
+     → 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`:
@@ -535,5 +545,5 @@ If a project-level index.json is found (scope = "project"):
      → All applications specified → Resume at `step-04-consolidate.md`
 
    - If status = `"consolidated"`:
-     → Display: "BA workflow complete. Use /ba-generate-html to generate HTML."
+     → Display: "BA workflow complete. Use /business-analyse-html to generate HTML."
      → STOP

package/templates/skills/business-analyse/steps/step-01-cadrage.md

@@ -21,6 +21,15 @@ next_step: steps/step-02-structure.md
 - **NEVER skip the reformulation phase** — it is the foundation of good analysis
 - **NEVER auto-infer cadrage data without client validation** — every key decision is confirmed
 
+## CONTEXT RECOVERY
+
+Re-read session variables from `.business-analyse/config.json` (do NOT rely on LLM memory):
+```javascript
+const config = readJSON('.business-analyse/config.json').currentFeature;
+const { id: feature_id, docsDir: docs_dir, application: application_name,
+        applicationCode, workflowMode: workflow_mode, language, version } = config;
+```
+
 ## YOUR TASK
 
 Frame the analysis scope at the **application level** through an interactive conversation with the client: understand the problem, stakeholders, scope, and define application-level roles. The analysis phase is ALWAYS interactive — the AI listens, reformulates, challenges, and validates with the user.
@@ -127,9 +136,9 @@ Analyze `{feature_description}` silently:
 4. **Prepare challenge questions** — specific to this brief, not generic
 5. **Pre-identify anticipated sections and resources** per detected module
 
-Store in `{pre_analysis}` (internal use only, NOT written to index.json):
+Store in `{pre_analysis}` — Write pre_analysis to cadrage.json as a `_preAnalysis` field (transient — removed on cadrage completion). This ensures the data survives context compaction:
 ```yaml
-pre_analysis:
+_preAnalysis:
   problem_type: "new_tool|replace|automate|centralize"
   detected_modules: [{name, description, detected_sections}]
   shadow_zones: [{topic, why_it_matters, challenge_question}]
@@ -310,7 +319,7 @@ ULTRATHINK — Entity Architecture Analysis for {entity_name}:
    - Module code: {PascalCase}
    - Section `list`: {main entity grid + create action + navigation to detail}
    - Detail page tabs: [{tab_name: content}] (accessible by clicking a row in list)
-   - Additional sections: [{code: justification}] (ONLY functional zones: dashboard, approve, import, rapport...)
+   - Additional sections: [{code: justification}] (ONLY functional sections: dashboard, approve, import, rapport...)
    - Dependencies: [{which modules reference/are referenced by this entity}]
    - Topological position: layer {N} (foundation if no dependencies)
 ```
@@ -430,7 +439,7 @@ options:
 | Choice | Action |
 |--------|--------|
 | **Géré dans l'app** | Entity becomes a sub-entity of the parent module. Add as a **tab in the detail page** of the referencing module. Note in coverageMatrix with `parentModule` field. |
-| **Nouveau module dédié** | **Add new module to `{pre_analysis}.detected_modules[]`** with the proposed architecture (sections, detail tabs, dependencies). Add to `coverageMatrix` as inScope. The `list` section is ALWAYS the main section. Additional sections ONLY for distinct functional zones (dashboard, approve, import...). `create` and `edit` are ACTIONS within `list` and detail pages, NEVER standalone sections. |
+| **Nouveau module dédié** | **Add new module to `{pre_analysis}.detected_modules[]`** with the proposed architecture (sections, detail tabs, dependencies). Add to `coverageMatrix` as inScope. The `list` section is ALWAYS the main section. Additional sections ONLY for distinct functional sections (dashboard, approve, import...). `create` and `edit` are ACTIONS within `list` and detail pages, NEVER standalone sections. |
 | **Système externe** | Flag for integration specification. Add to `coverageMatrix` as integration. Load questionnaire materials on integrations if not already covered. |
 | **Liste simple en config** | Entity becomes a lookup/reference table (no dedicated module, no section). Note in coverageMatrix as config data. |
 
@@ -583,7 +592,7 @@ BEFORE transitioning to step-02:
    - Create an entry in `cadrage.coverageMatrix[]`
    - Assign it to inScope or outOfScope
    - Assign the module that will cover it (or null if cross-cutting)
-   - List anticipated sections (Level 4) — ONLY functional zones
+   - List anticipated sections (Level 4) — ONLY functional sections
    - List anticipated resources (Level 5) for each section
    - List detail page tabs — for entities accessible via click from `list`
 

package/templates/skills/business-analyse/steps/step-02-structure.md

@@ -11,6 +11,15 @@ next_step: steps/step-03-specify.md
 
 Identify the complete hierarchy **Application > Module > Section > Resource** from the cadrage data, then CHALLENGE each element to ensure nothing is missing or superfluous.
 
+## Context Recovery
+
+Re-read session variables from `.business-analyse/config.json`:
+```javascript
+const config = readJSON('.business-analyse/config.json').currentFeature;
+const { id: feature_id, docsDir: docs_dir, application: application_name,
+        applicationCode, workflowMode: workflow_mode, language } = config;
+```
+
 ## Prerequisites
 
 - Step 01 (cadrage) completed
@@ -83,7 +92,7 @@ For each section:
 | sectionType | permissionMode | When to use | Examples |
 |---|---|---|---|
 | `primary` | `crud` | Main entry point of the module, visible in menu | list |
-| `functional` | `crud` or `custom` | Independent functional zone with own access control | approve, import, planning |
+| `functional` | `crud` or `custom` | Independent functional section with own access control | approve, import, planning |
 | `view` | `inherit` | Subordinate view reached from a primary section | detail, edit |
 | `embedded` | `read-only` | Widget or tab embedded in another section | dashboard (when embedded in module) |
 
@@ -182,6 +191,13 @@ Write via ba-writer:
 }
 ```
 
+## Status Update
+
+After writing the structure, update the application status:
+```javascript
+ba-writer.updateStatus({feature_id}, "decomposed")
+```
+
 ## Transition
 
 → Step 03 (specify) — Sequential module specification