@atlashub/smartstack-cli 4.48.0 → 4.50.0

package/templates/skills/apex/steps/step-03d-layer3-frontend.md

@@ -9,6 +9,38 @@ parent_step: steps/step-03-execute.md
 
 # Layer 3 — Frontend (Pages + I18n + Documentation)
 
+### Companion Specs Loading (delegate mode)
+
+```javascript
+if (delegate_mode && specification_loading_plan) {
+  const specsDir = path.dirname(delegate_prd_path);
+  // Layer 3 loads: screens + usecases companions
+  for (const file of specification_loading_plan.layer3_frontend) {
+    const specPath = path.join(specsDir, file);
+    if (fileExists(specPath)) {
+      const specData = readJSON(specPath);
+      if (specData.screens) {
+        // Full screen definitions: columns[], fields[], filters[], actions[], kpis[]
+        // Use for: DataTable columns, form fields, filter configs, action buttons, dashboard KPIs
+        console.log(`Loaded screens: ${specData.screens.length} screen specs with columns/fields/filters`);
+      }
+      if (specData.useCases || specData.usecases) {
+        const ucs = specData.useCases || specData.usecases;
+        // UC steps inform form validation, navigation flows, error states
+        console.log(`Loaded usecases: ${ucs.length} use cases for form flows`);
+      }
+    }
+  }
+}
+```
+
+> When companion specs are loaded:
+> - **List pages**: use `screen.columns[]` for exact DataTable column definitions (key, label, type, sortable)
+> - **Form pages**: use `screen.fields[]` for exact form field definitions (name, type, required, validation)
+> - **Filter configs**: use `screen.filters[]` for search/filter UI generation
+> - **Dashboard pages**: use `screen.kpis[]` for KPI card and chart definitions
+> - **Actions**: use `screen.actions[]` for action buttons (create, export, bulk operations)
+
 ### ⛔ HARD RULE — /ui-components is NON-NEGOTIABLE (read BEFORE any Layer 3 action)
 
 > **VIOLATION CHECK:** If ANY .tsx page file was created by Write tool WITHOUT

package/templates/skills/application/references/backend-controller-hierarchy.md

@@ -38,14 +38,24 @@ Api/Controllers/
 The generated controller uses NavRoute attribute:
 
 ```csharp
-[NavRoute("{full_path}")]
 [ApiController]
-[Authorize]
+[NavRoute("{full_path}")]
+[Microsoft.AspNetCore.Authorization.Authorize]
+[Produces("application/json")]
+[Tags("{EntityNamePlural}")]
 public class {EntityName}Controller : ControllerBase
 {
+    private readonly ISender _mediator;
+
+    public {EntityName}Controller(ISender mediator) => _mediator = mediator;
+
     [HttpGet]
-    [RequirePermission(Permissions.{Application}.{Module}.Read)]
-    public async Task<ActionResult<IEnumerable<{EntityName}Dto>>> GetAll() { ... }
+    [RequirePermission(Permissions.{Application}.{Module}.View)]
+    [ProducesResponseType(typeof(List<{EntityName}ListDto>), StatusCodes.Status200OK)]
+    [ProducesResponseType(StatusCodes.Status401Unauthorized)]
+    [ProducesResponseType(StatusCodes.Status403Forbidden)]
+    public async Task<ActionResult<List<{EntityName}ListDto>>> GetAll(CancellationToken ct)
+        => Ok(await _mediator.Send(new Get{EntityNamePlural}Query(), ct));
 
     // ... other CRUD methods
 }

package/templates/skills/business-analyse/patterns/suggestion-catalog.md

@@ -27,6 +27,7 @@ Suggests companion modules based on primary module type:
 | **Notifications** | notification, alert, email, message, broadcast | Templates, Channels, Scheduling, Preferences | Notification systems need template management, multi-channel support, scheduling |
 | **Reporting** | report, dashboard, analytics, BI, metrics | Dashboards, Exports, Scheduling, AlertRules | Reporting needs visualization, scheduled distribution, and data export |
 | **API Management / Integrations** | api, external, integration, webhook, export, data-export, machine-to-machine | ExternalApps, DataExportEndpoints, ExportAccess, AuditLogs, ApiKeys | API platforms need app registration, key management, granular endpoint access, rate limiting, and audit logging |
+| **Client Portal** | portal, external, client, fournisseur, partenaire, tiers | MyRequests, ClientDashboard, PortalNotifications | Les utilisateurs externes ont besoin de vues self-service, suivi de statut et soumission limitée |
 
 ---
 
@@ -48,6 +49,7 @@ Suggests standard sections based on detected conditions:
 | **Report generation** | Reporting Engine | Automated business reporting | Add section with template library, scheduling, distribution |
 | **External integrations** | Integration Layer | System-to-system communication | Add section with API specifications, webhook handling, sync strategy |
 | **Regulatory compliance** | Compliance & Audit | Legal/industry requirements | Add section with audit logging, data retention, retention periods |
+| **Utilisateurs externes / portail détecté** | Sections portail client | Les utilisateurs externes ont besoin d'un espace dédié simplifié | Pour chaque module "shared" : suggérer section portal-specific (ex: `my-requests`, `portal-dashboard`) avec permissions read-only ou write limitée. Pour modules "external" : s'assurer que les sections ont une UX adaptée portail (navigation simplifiée, pas de fonctions admin). |
 
 ---
 

package/templates/skills/business-analyse/questionnaire/02-stakeholders-scope.md

@@ -88,6 +88,7 @@
 | Question | Si la réponse est vague | Relance recommandée |
 |----------|------------------------|---------------------|
 | Q2.1 (utilisateurs) | Un seul type mentionné | "Pensez aux différents moments de la journée : qui saisit ? Qui consulte les rapports ? Qui gère les cas particuliers ?" |
+| Q2.1 (utilisateurs) | Utilisateurs hors entreprise mentionnés (clients, fournisseurs, partenaires) | "Ces utilisateurs externes accéderont-ils via un espace dédié (portail) ou la même interface que vos employés ?" |
 | Q2.5 (tâches) | Tâches génériques | "Quand il arrive le matin et ouvre le système, quelle est sa première action ?" |
 | Q2.9 (restrictions) | Réponse ambiguë | "Un employé voit-il les données salariales ? Un manager voit-il uniquement son équipe ou toute l'entreprise ?" |
 | Q2.13 (indispensable) | Tout est indispensable | "Si vous ne pouviez garder que 3 fonctionnalités pour un premier lancement, lesquelles ?" |
@@ -103,6 +104,7 @@
 | Tout est vital (> 10 vitaux) | Classification non réfléchie | Appliquer le test de classification : "Si on enlevait X, le système aurait-il encore de la valeur ?" |
 | Aucune exclusion identifiée | Périmètre non borné | "Y a-t-il des aspects qui relèvent d'un autre projet ou d'une version future ?" |
 | Parcours linéaire sans alternative | Seul le cas idéal est décrit | "Que se passe-t-il à l'étape X si la condition Y n'est pas remplie ?" |
+| "Nos clients doivent pouvoir..." ou "Les fournisseurs voient..." | Utilisateurs externes accédant au système | Déclencher détection portail : classifier les profils en interne/externe. SmartStack gère le déploiement multi-tenant automatiquement. |
 
 ---
 

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

@@ -66,6 +66,12 @@
           "type": "string",
           "description": "Lucide icon name for application navigation entry (e.g., users, shopping-cart). Confirmed in step-02."
         },
+        "portalMode": {
+          "type": "string",
+          "enum": ["internal-only", "portal-only", "dual"],
+          "default": "internal-only",
+          "description": "Whether the app serves internal users, external portal users, or both"
+        },
         "workflow": {
           "type": "object",
           "description": "Iterative module loop state",
@@ -126,7 +132,12 @@
               "involvement": { "type": "string", "enum": ["approver", "decision-maker", "consulted", "informed", "end-user"] },
               "tasks": { "type": "array", "items": { "type": "string" } },
               "frequency": { "type": "string" },
-              "painPoints": { "type": "array", "items": { "type": "string" } }
+              "painPoints": { "type": "array", "items": { "type": "string" } },
+              "audience": {
+                "type": "string",
+                "enum": ["internal", "external", "shared"],
+                "description": "Whether this stakeholder is internal, external portal user, or both"
+              }
             }
           }
         },
@@ -204,6 +215,11 @@
                 "type": "array",
                 "items": { "type": "string" },
                 "description": "Anticipated resources (Level 5) for this requirement — e.g., user-grid, user-form, user-card"
+              },
+              "audience": {
+                "type": "string",
+                "enum": ["internal", "external", "shared"],
+                "description": "Target audience. Only set when portalMode is 'dual'."
               }
             }
           }
@@ -257,6 +273,11 @@
             "type": "string",
             "enum": ["simple", "medium", "complex"]
           },
+          "audience": {
+            "type": "string",
+            "enum": ["internal", "external", "shared"],
+            "description": "Target audience. Derived from coverage matrix."
+          },
           "anticipatedSections": {
             "type": "array",
             "description": "Anticipated sections (Level 4) with their resources (Level 5), from cadrage coverage matrix",
@@ -266,6 +287,20 @@
               "properties": {
                 "code": { "type": "string", "description": "Section code (e.g., list, detail, create, edit, dashboard)" },
                 "description": { "type": "string" },
+                "sectionType": {
+                  "type": "string",
+                  "enum": ["primary", "functional", "view", "embedded"],
+                  "description": "Section classification: primary (menu entry), functional (independent), view (sub-page of parent), embedded (widget in parent)"
+                },
+                "permissionMode": {
+                  "type": "string",
+                  "enum": ["crud", "custom", "read-only", "inherit"],
+                  "description": "Permission model: crud (standard CRUD), custom (section-specific), read-only, inherit (from parent)"
+                },
+                "parentSectionCode": {
+                  "type": ["string", "null"],
+                  "description": "Parent section code for view/embedded sections (e.g., 'list'). Null for primary/functional sections."
+                },
                 "resources": {
                   "type": "array",
                   "items": { "type": "string" },

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

@@ -516,6 +516,20 @@
         "required": ["code", "labels", "route", "permission", "wireframe", "useCases", "resources"],
         "properties": {
           "code": { "type": "string", "description": "Section code (kebab-case: list, detail, dashboard, approve, import, etc.)" },
+          "sectionType": {
+            "type": "string",
+            "enum": ["primary", "functional", "view", "embedded"],
+            "description": "Section classification: primary (menu entry), functional (independent), view (sub-page of parent), embedded (widget in parent)"
+          },
+          "permissionMode": {
+            "type": "string",
+            "enum": ["crud", "custom", "read-only", "inherit"],
+            "description": "Permission model: crud (standard CRUD), custom (section-specific), read-only, inherit (from parent)"
+          },
+          "parentSectionCode": {
+            "type": ["string", "null"],
+            "description": "Parent section code for view/embedded sections (e.g., 'list'). Null for primary/functional sections."
+          },
           "labels": {
             "type": "object",
             "properties": {
@@ -531,6 +545,11 @@
           "wireframe": { "type": "string", "description": "Reference to uiWireframes[].screen" },
           "useCases": { "type": "array", "items": { "type": "string" } },
           "businessRules": { "type": "array", "items": { "type": "string" } },
+          "audience": {
+            "type": "string",
+            "enum": ["internal", "external", "shared"],
+            "description": "Target audience. Inherited from module unless overridden."
+          },
           "resources": {
             "type": "array",
             "description": "Level 5 (Resource) components within this section",

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

@@ -122,10 +122,10 @@ 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 explicitly describes multiple applications, we must recognize this immediately
-> and set `workflow.mode = "project"` to avoid doing cadrage for a single app.
+> 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.
 
-**Detection patterns (ANY match = multi-app detected):**
+### Tier 1 — Explicit patterns (ANY match = multi-app detected)
 
 French patterns:
 - "une application X ... une application Y" (two occurrences of "une application")
@@ -138,30 +138,65 @@ English patterns:
 - "application #1: ... application #2: ..." (numbered)
 - "first app ... second app"
 
-If ANY of these patterns is found in `{feature_description}`, set `isMultiApp = true`.
+If ANY of these patterns is found in `{feature_description}`:
+→ `isMultiApp = true`, `detectionTier = "explicit"`
 
-**IF multi-app detected:**
+### Tier 2 — Domain diversity analysis (when Tier 1 does not match)
 
-1. Extract candidate applications from the prompt:
+ULTRATHINK: Analyze `{feature_description}` to extract distinct business domains.
 
-**Extraction algorithm (3 steps):**
+**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 result: `[{ name: "RH", description: "gestion des employes, conges, temps", modules: ["Employes", "Conges", "Temps"] }, ...]`
+   - 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)
 
-3. Display detection result and confirm:
+**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:
 
 ```
-{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:"}
+{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(", ")}
+{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."
@@ -177,6 +212,8 @@ options:
     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'}"
 ```
@@ -193,6 +230,19 @@ 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
@@ -201,7 +251,7 @@ workflow_mode: "application"
 
 → Continue to step 4 normally
 
-**IF no multi-app patterns detected:**
+**IF no multi-app detected (neither Tier 1 nor Tier 2):**
 → Continue to step 4 normally
 
 ## Step 4: Determine Application Name

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

@@ -239,6 +239,44 @@ Ask in 1-2 batches. After each batch:
 - If "no restrictions" → probe: "Are there sensitive data (salary, contracts, personal info) that should be restricted to specific roles?"
 - If tasks are generic → ask for a concrete scenario: "Walk me through a typical day"
 
+#### 4b-bis. Détection Portail Client (ULTRATHINK — après batch stakeholders)
+
+Analyser les réponses stakeholders pour signaux d'utilisateurs externes :
+
+```
+EXTERNAL_SIGNALS = ["client", "customer", "fournisseur", "supplier", "partenaire",
+  "partner", "portail", "portal", "externe", "external", "tiers", "third-party",
+  "organisation cliente"]
+```
+
+SI un profil stakeholder match EXTERNAL_SIGNALS :
+  → Stocker dans `{pre_analysis}`: `_portalDetected: true`
+  → Poser la question via AskUserQuestion :
+
+```
+question: "{language == 'fr'
+  ? 'J\'ai détecté des utilisateurs externes ({profiles}). Votre application comportera-t-elle un portail client en plus de la partie interne ?'
+  : 'I detected external users ({profiles}). Will your application include a client portal in addition to the internal part?'}"
+header: "Portail client"
+options:
+  - label: "{language == 'fr' ? 'Oui, portail + interne' : 'Yes, portal + internal'}"
+    description: "{language == 'fr' ? 'L\'application servira des utilisateurs internes ET externes via un portail dédié' : 'The app will serve internal AND external users via a dedicated portal'}"
+  - label: "{language == 'fr' ? 'Non, interne uniquement' : 'No, internal only'}"
+    description: "{language == 'fr' ? 'Seuls les employés internes utiliseront l\'application' : 'Only internal employees will use the application'}"
+  - label: "{language == 'fr' ? 'Non, portail uniquement' : 'No, portal only'}"
+    description: "{language == 'fr' ? 'L\'application est exclusivement destinée aux utilisateurs externes' : 'The application is exclusively for external users'}"
+```
+
+| Réponse | Action |
+|---------|--------|
+| **Oui, portail + interne** | `_portalMode = "dual"` → Follow-up : classifier chaque stakeholder comme `audience: "internal" \| "external" \| "shared"` |
+| **Portail uniquement** | `_portalMode = "portal-only"` |
+| **Interne uniquement** | `_portalMode = "internal-only"` (défaut, pas d'action supplémentaire) |
+
+> **Note SmartStack :** Le déploiement multi-tenant est géré automatiquement par SmartStack. La partie interne et la partie portail seront déployées sur des tenants séparés.
+
+SI aucun profil ne match EXTERNAL_SIGNALS → `_portalMode = "internal-only"` (défaut silencieux, rien à demander).
+
 #### 4c. Functional Scope (ALWAYS — from `questionnaire/02-stakeholders-scope.md`)
 
 **Mandatory minimum:** Q2.13 (in-scope), Q2.15 (exclusions), Q2.16 (main journey).
@@ -596,6 +634,14 @@ BEFORE transitioning to step-02:
    - List anticipated resources (Level 5) for each section
    - List detail page tabs — for entities accessible via click from `list`
 
+   **SI `_portalMode === "dual"` :**
+   - Chaque entrée `coverageMatrix` reçoit `audience: "internal" | "external" | "shared"`
+   - Règles de dérivation :
+     - Items mentionnés uniquement par stakeholders internes → `"internal"`
+     - Items mentionnés uniquement par stakeholders externes → `"external"`
+     - Items mentionnés par les deux ou cross-cutting → `"shared"`
+   - Afficher colonne "Audience" dans le tableau de la matrice
+
 4. **RECONCILIATION CHECK (MANDATORY — BLOCKING):**
 
    > **Every explicitly requested item MUST appear in the coverage matrix.**
@@ -641,12 +687,13 @@ ba-writer.enrichSection({
   subsection: "cadrage.json",
   data: {
     metadata: {
-      tablePrefix: "{from Phase 5, section 6b — validated prefix, e.g., rh_}"
+      tablePrefix: "{from Phase 5, section 6b — validated prefix, e.g., rh_}",
+      portalMode: "{_portalMode || 'internal-only'}"
     },
     problem: {from Phase 3, section 4a — Q1.1 answer or refined problem},
     asIs: {from Phase 3, section 4a — Q1.4 answer},
     toBe: {from Phase 3, section 4a — Q1.8 answer},
-    stakeholders: [{from Phase 3, section 4b}],
+    stakeholders: [{from Phase 3, section 4b — each with audience: "internal"|"external"|"shared" if portalMode is "dual"}],
     globalScope: {
       inScope: [{from Phase 3, section 4c + Phase 4 accepted suggestions + coverage matrix}],
       outOfScope: [{from Phase 3, section 4c — Q2.15 exclusions}]

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

@@ -70,6 +70,9 @@ For each module:
   - Description
   - FeatureType (data-centric | workflow | reporting | integration | full-module)
   - Entities (preliminary list)
+  - Audience ("internal" | "external" | "shared") — if portalMode = "dual"
+    → Derived from coverageMatrix: if ALL items of the module are internal → "internal",
+      if ALL external → "external", else → "shared"
 ```
 
 ### 3. Section & Resource Anticipation
@@ -89,18 +92,20 @@ For each section:
 
 **Section classification rules:**
 
-| sectionType | permissionMode | When to use | Examples |
-|---|---|---|---|
-| `primary` | `crud` | Main entry point of the module, visible in menu | list |
-| `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) |
+| sectionType | permissionMode | When to use | Parent | Examples |
+|---|---|---|---|---|
+| `primary` | `crud` | Main entry point of the module, visible in menu | none | list |
+| `functional` | `crud` or `custom` | Independent functional section with own access control | none | approve, import, planning |
+| `view` | `inherit` | Sub-page reached from a primary/functional section (e.g., click a row) | `parentSectionCode` | detail, edit |
+| `embedded` | `read-only` | Widget or tab embedded in another section | `parentSectionCode` | dashboard (when embedded in module) |
+
+**Parent-child rule:** `view` and `embedded` sections MUST specify `parentSectionCode` — the code of the section they are reached from. A detail page is NOT a sibling of list; it is a **child** of list (user clicks a row in the list to reach the detail).
 
 Common patterns:
-- **Data-centric module**: list (`primary`/`crud`) + detail (`view`/`inherit`)
-- **Workflow module**: list (`primary`/`crud`) + detail (`view`/`inherit`) + approve (`functional`/`custom`)
-- **Reporting module**: dashboard (`primary`/`read-only`) + detail (`view`/`inherit`)
-- **Full module**: list (`primary`/`crud`) + detail (`view`/`inherit`) + dashboard (`embedded`/`read-only`)
+- **Data-centric**: list (`primary`/`crud`) → detail (`view`/`inherit`, parent: list)
+- **Workflow**: list (`primary`/`crud`) → detail (`view`/`inherit`, parent: list) + approve (`functional`/`custom`)
+- **Reporting**: dashboard (`primary`/`read-only`) → detail (`view`/`inherit`, parent: dashboard)
+- **Full module**: list (`primary`/`crud`) → detail (`view`/`inherit`, parent: list) + dashboard (`embedded`/`read-only`, parent: list)
 
 ### 4. Dependency Graph
 
@@ -139,21 +144,40 @@ For EACH identified element, ask yourself:
 - Does the form need tabs?
 - Are there missing filter components?
 
+**Split audience (if portalMode = "dual"):**
+- Pour chaque module "shared" : le portail voit-il les MÊMES données ou un sous-ensemble filtré ?
+- Y a-t-il des sections qui ne doivent apparaître QUE dans le portail ? (ex: "Mes demandes")
+- Y a-t-il des sections qui ne doivent apparaître QUE en interne ? (ex: reporting admin)
+
 ### 6. Present to User
 
 Display the complete hierarchy for validation:
 
+**Tree nesting rules:**
+- `view` sections are **indented under their parent** (the section they are reached from)
+- `functional` and `primary` sections stay at module level
+- `embedded` sections are indented under their parent section
+- Tabs are indented under detail
+
 ```
 [App: HumanResources]
   ├── [Module: Employees]
-  │   ├── list → SmartTable (employees-grid)
-  │   └── detail → SmartForm (employee-form)
+  │   ├── list (primary/crud) → employees-grid, employees-filters
+  │   │   └── detail (view/inherit) → employee-form
+  │   │       └── Tabs: Infos, Contrats
   ├── [Module: Absences]
-  │   ├── list → SmartTable (absences-grid)
-  │   ├── detail → SmartForm (absence-form)
-  │   └── calendar → SmartKanban (absences-calendar)
+  │   ├── list (primary/crud) → absences-grid, absences-filters
+  │   │   └── detail (view/inherit) → absence-form
+  │   └── calendar (functional) → absences-calendar
   └── [Module: Reports]
-      └── dashboard → SmartDashboard (hr-dashboard)
+      └── dashboard (primary/read-only) → hr-dashboard
+
+IF portalMode = "dual", annotate each module with its audience:
+
+[App: ServiceManagement]
+  ├── [Module: Projects] [partagé]
+  ├── [Module: TimeTracking] [interne]
+  └── [Module: ClientDashboard] [portail]
 ```
 
 Ask: "Does this structure match your vision? Any missing modules, sections, or resources?"
@@ -181,7 +205,7 @@ Write via ba-writer:
       "entities": ["Employee", "Contract"],
       "anticipatedSections": [
         { "code": "list", "label": "Liste", "sectionType": "primary", "permissionMode": "crud", "resources": [{ "code": "employees-grid", "type": "SmartTable" }] },
-        { "code": "detail", "label": "Fiche", "sectionType": "view", "permissionMode": "inherit", "resources": [{ "code": "employee-form", "type": "SmartForm" }] }
+        { "code": "detail", "label": "Fiche", "sectionType": "view", "permissionMode": "inherit", "parentSectionCode": "list", "resources": [{ "code": "employee-form", "type": "SmartForm" }] }
       ]
     }
   ],