dflow-sdd-ddd 0.3.0 → 0.4.0

package/docs/release-versioning-policy.md

@@ -44,6 +44,19 @@ Examples:
 - Changing command behavior in a way that invalidates existing docs.
 - Replacing a workflow contract that AI agents rely on.
 
+Counter-examples (NOT breaking):
+
+- Replacing stack-specific framing with stack-neutral umbrella terms when
+  the architectural meaning is unchanged (e.g., "Code-Behind" →
+  "delivery/entrypoint code") — adopter's existing files are not
+  rewritten by Dflow.
+- Renaming an init placeholder if the previous name still resolves via a
+  backward-compat alias and the substituted value is identical (e.g.,
+  `{ASP.NET Core version}` continuing to resolve while `{Framework version}`
+  becomes canonical).
+- Adding a new optional placeholder; existing templates that don't use it
+  are unaffected.
+
 ## Release Ownership
 
 Dflow currently has four release surfaces:

package/lib/init.js

@@ -383,7 +383,16 @@ async function detectProjectSignals(cwd) {
       name.endsWith('.csproj') ||
       name === 'program.cs' ||
       name === 'startup.cs' ||
-      name === 'package.json'
+      name === 'package.json' ||
+      name === 'pom.xml' ||
+      name === 'build.gradle' ||
+      name === 'build.gradle.kts' ||
+      name === 'pyproject.toml' ||
+      name === 'requirements.txt' ||
+      name === 'go.mod' ||
+      name === 'cargo.toml' ||
+      name === 'composer.json' ||
+      name === 'gemfile'
     );
 
   const hasWebFormsFiles = Array.from(baseNames).some((name) =>
@@ -412,9 +421,36 @@ async function detectProjectSignals(cwd) {
     trackHint = 'brownfield';
   }
 
+  const stackHints = [];
+  if (coreSignal || webFormsSignal || csprojFiles.length > 0) {
+    stackHints.push('dotnet');
+  }
+  if (baseNames.has('pom.xml') || baseNames.has('build.gradle') || baseNames.has('build.gradle.kts')) {
+    stackHints.push('java');
+  }
+  if (baseNames.has('package.json')) {
+    stackHints.push('nodejs');
+  }
+  if (baseNames.has('pyproject.toml') || baseNames.has('requirements.txt')) {
+    stackHints.push('python');
+  }
+  if (baseNames.has('go.mod')) {
+    stackHints.push('go');
+  }
+  if (baseNames.has('cargo.toml')) {
+    stackHints.push('rust');
+  }
+  if (baseNames.has('composer.json')) {
+    stackHints.push('php');
+  }
+  if (baseNames.has('gemfile')) {
+    stackHints.push('ruby');
+  }
+
   return {
     hasSourceTree: hasSourceTree || relNames.has('src'),
-    trackHint
+    trackHint,
+    stackHints
   };
 }
 
@@ -1104,13 +1140,20 @@ async function readPackagedTemplate(edition, sourceRel) {
   }
 }
 
+const PLACEHOLDER_ALIASES = {
+  '{Framework version}': ['{ASP.NET Core version}', '{ASP.NET WebForms version}', '{.NET Framework version}'],
+  '{ORM / persistence}': ['{ORM / Data Access}'],
+  '{ORM version}': ['{EF Core version}'],
+  '{Mediator}': ['{MediatR version}']
+};
+
 function buildSubstitutionMap(cwd, answers) {
   const extracted = extractTechStackPlaceholders(answers.techStackSummary);
   const gitSelection = answers.optionalFiles.filter((key) => key === 'git-trunk' || key === 'git-flow');
   const gitStyle = gitSelection.length === 1 ? (gitSelection[0] === 'git-trunk' ? 'trunk' : 'gitflow') : null;
   const systemName = path.basename(cwd);
 
-  return new Map([
+  const map = new Map([
     ['{YYYY-MM-DD}', currentLocalDate()],
     ['{System Name}', systemName],
     ['{系統名稱}', systemName],
@@ -1120,15 +1163,26 @@ function buildSubstitutionMap(cwd, answers) {
     ['{migration-context}', answers.migrationContext],
     ['{prose-language}', answers.proseLanguage],
     ['{dflow-version}', pkg.version],
-    ['{ASP.NET Core version}', extracted.aspNetCoreVersion || '{ASP.NET Core version}'],
-    ['{EF Core version}', extracted.efCoreVersion || '{EF Core version}'],
-    ['{MediatR version}', extracted.mediatRVersion || '{MediatR version}'],
+    ['{Language}', extracted.language || '{Language}'],
+    ['{Framework}', extracted.framework || '{Framework}'],
+    ['{Framework version}', extracted.frameworkVersion || '{Framework version}'],
+    ['{ORM / persistence}', extracted.ormPersistence || '{ORM / persistence}'],
+    ['{ORM version}', extracted.ormVersion || '{ORM version}'],
+    ['{Mediator}', extracted.mediator || '{Mediator}'],
     ['{Test framework}', extracted.testFramework || '{Test framework}'],
-    ['{ASP.NET WebForms version}', extracted.webFormsVersion || '{ASP.NET WebForms version}'],
-    ['{.NET Framework version}', extracted.dotNetFrameworkVersion || '{.NET Framework version}'],
-    ['{ORM / Data Access}', extracted.ormDataAccess || '{ORM / Data Access}'],
     ['{gitflow|trunk}', gitStyle || '{gitflow|trunk}']
   ]);
+
+  for (const [canonical, aliases] of Object.entries(PLACEHOLDER_ALIASES)) {
+    const value = map.get(canonical);
+    if (value === undefined) continue;
+    const canonicalResolved = value !== canonical;
+    for (const alias of aliases) {
+      map.set(alias, canonicalResolved ? value : alias);
+    }
+  }
+
+  return map;
 }
 
 function substitutePlaceholders(content, substitution) {
@@ -1139,19 +1193,104 @@ function substitutePlaceholders(content, substitution) {
   return result;
 }
 
+const LANGUAGE_PATTERNS = [
+  /\bC#\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bC#\b/,
+  /\bTypeScript\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bTypeScript\b/i,
+  /\bJavaScript\b/i,
+  /\bKotlin\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bKotlin\b/i,
+  /\bJava\s*[0-9]+\b/i,
+  /\bJava\b/i,
+  /\bPython\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bPython\b/i,
+  /\bGolang\b/i,
+  /\bGo\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bPHP\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bPHP\b/i,
+  /\bRuby\b/i
+];
+
+const FRAMEWORK_VERSION_PATTERNS = [
+  /\bASP\.?NET\s+Core\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\b(?:ASP\.?NET\s+WebForms|WebForms)(?:\s+[0-9]+(?:\.[0-9]+)?)?\b/i,
+  /\b\.NET\s+Framework\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bSpring\s+Boot\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bSpring\s+MVC\b/i,
+  /\bNestJS\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bFastify\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bExpress(?:\.js)?\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bDjango\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bFastAPI\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bFlask\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bGin\s+v?[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bEcho\s+v?[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bLaravel\s*[0-9]+(?:\.[0-9]+)?\b/i
+];
+
+const FRAMEWORK_PATTERNS = [
+  /\bASP\.?NET\s+Core\b/i,
+  /\b(?:ASP\.?NET\s+WebForms|WebForms)\b/i,
+  /\b\.NET\s+Framework\b/i,
+  /\bSpring\s+Boot\b/i,
+  /\bSpring\s+MVC\b/i,
+  /\bNestJS\b/i,
+  /\bFastify\b/i,
+  /\bExpress(?:\.js)?\b/i,
+  /\bDjango\b/i,
+  /\bFastAPI\b/i,
+  /\bFlask\b/i,
+  /\bGin\b/i,
+  /\bEcho\b/i,
+  /\bLaravel\b/i
+];
+
+const ORM_VERSION_PATTERNS = [
+  /\b(?:EF\s+Core|Entity\s+Framework\s+Core)\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\b(?:EF6|Entity\s+Framework\s+6)\b/i,
+  /\bHibernate\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bSpring\s+Data\s+JPA\b/i,
+  /\bJPA\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bSQLAlchemy\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bPrisma\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bTypeORM\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bMikro-?ORM\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bGORM\s+v?[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bEloquent\s*[0-9]+(?:\.[0-9]+)?\b/i,
+  /\bDoctrine\s*[0-9]+(?:\.[0-9]+)?\b/i
+];
+
+const ORM_PERSISTENCE_PATTERNS = [
+  /\b(?:EF\s+Core|Entity\s+Framework\s+Core)\b/i,
+  /\b(?:EF6|Entity\s+Framework\s+6|Dapper|ADO\.NET)\b/i,
+  /\bHibernate\b/i,
+  /\bSpring\s+Data\s+JPA\b/i,
+  /\bJPA\b/i,
+  /\bSQLAlchemy\b/i,
+  /\bSQLModel\b/i,
+  /\bPrisma\b/i,
+  /\bTypeORM\b/i,
+  /\bMikro-?ORM\b/i,
+  /\bGORM\b/i,
+  /\bsqlx\b/i,
+  /\bEloquent\b/i,
+  /\bDoctrine\b/i
+];
+
 function extractTechStackPlaceholders(text) {
   if (!text || text.toLowerCase() === 'unknown') {
     return {};
   }
 
   return {
-    aspNetCoreVersion: firstMatch(text, /\bASP\.?NET\s+Core\s*[0-9]+(?:\.[0-9]+)?\b/i),
-    efCoreVersion: firstMatch(text, /\b(?:EF\s+Core|Entity\s+Framework\s+Core)\s*[0-9]+(?:\.[0-9]+)?\b/i),
-    mediatRVersion: firstMatch(text, /\bMediatR\s*[0-9]+(?:\.[0-9]+)?\b/i),
-    testFramework: extractTestFramework(text),
-    webFormsVersion: firstMatch(text, /\b(?:ASP\.?NET\s+WebForms|WebForms)(?:\s*[0-9]+(?:\.[0-9]+)?)?\b/i),
-    dotNetFrameworkVersion: firstMatch(text, /\b\.NET\s+Framework\s*[0-9]+(?:\.[0-9]+)?\b/i),
-    ormDataAccess: firstMatch(text, /\b(?:EF6|Entity\s+Framework\s+6|Dapper|ADO\.NET)\b/i)
+    language: firstPatternMatch(text, LANGUAGE_PATTERNS),
+    framework: firstPatternMatch(text, FRAMEWORK_PATTERNS),
+    frameworkVersion: firstPatternMatch(text, FRAMEWORK_VERSION_PATTERNS),
+    ormPersistence: firstPatternMatch(text, ORM_PERSISTENCE_PATTERNS),
+    ormVersion: firstPatternMatch(text, ORM_VERSION_PATTERNS),
+    mediator: firstMatch(text, /\bMediatR\s*[0-9]+(?:\.[0-9]+)?\b/i),
+    testFramework: extractTestFramework(text)
   };
 }
 
@@ -1160,15 +1299,38 @@ function firstMatch(text, regex) {
   return match ? match[0] : null;
 }
 
-function extractTestFramework(text) {
-  if (/\bxUnit\b/i.test(text)) {
-    return 'xUnit';
-  }
-  if (/\bNUnit\b/i.test(text)) {
-    return 'NUnit';
+function firstPatternMatch(text, patterns) {
+  for (const pattern of patterns) {
+    const match = text.match(pattern);
+    if (match) {
+      return match[0];
+    }
   }
-  if (/\bMSTest\b/i.test(text)) {
-    return 'MSTest';
+  return null;
+}
+
+function extractTestFramework(text) {
+  const patterns = [
+    [/\bxUnit\b/i, 'xUnit'],
+    [/\bNUnit\b/i, 'NUnit'],
+    [/\bMSTest\b/i, 'MSTest'],
+    [/\bJUnit\s*[0-9]+\b/i, null],
+    [/\bJUnit\b/i, 'JUnit'],
+    [/\bVitest\b/i, 'Vitest'],
+    [/\bJest\b/i, 'Jest'],
+    [/\bMocha\b/i, 'Mocha'],
+    [/\bpytest\b/i, 'pytest'],
+    [/\bunittest\b/i, 'unittest'],
+    [/\bgo\s+test\b/i, 'go test'],
+    [/\bPHPUnit\b/i, 'PHPUnit'],
+    [/\bPest\b/i, 'Pest']
+  ];
+
+  for (const [pattern, name] of patterns) {
+    const match = text.match(pattern);
+    if (match) {
+      return name || match[0];
+    }
   }
   return null;
 }
@@ -1386,6 +1548,7 @@ Recommended next steps:
 - For a new feature, use the Dflow new-feature workflow when it becomes available as a CLI command.
 - For brownfield changes, use the Dflow modify-existing workflow when it becomes available as a CLI command.
 - Before generating more specs, make sure dflow/specs/shared/_conventions.md has the correct Prose Language section.
+- For stack-specific examples (.NET, Java/Spring, Node/TypeScript, Python, Go, PHP/Laravel), see docs/examples-by-stack.md in the Dflow repo.
 `);
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dflow-sdd-ddd",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Spec-first SDD/DDD workflow kit for AI-assisted development",
   "type": "commonjs",
   "bin": {

package/templates/brownfield/scaffolding/CLAUDE-md-snippet.md

@@ -21,7 +21,7 @@ when merging into an existing `CLAUDE.md`.
 ## Snippet to merge into `CLAUDE.md`
 
 ```markdown
-# Project: {系統名稱} — ASP.NET WebForms
+# Project: {系統名稱} — {Framework}
 
 **重要：所有開發工作都必須遵循本文件定義的流程。**
 
@@ -33,10 +33,12 @@ when merging into an existing `CLAUDE.md`.
 
 ### Background
 
-這是一個運行中的 ASP.NET WebForms 系統，{一句話描述業務領域：例如
+這是一個運行中的既有系統，使用 {Framework} / {Language}，{一句話描述業務領域：例如
 「提供員工費用報銷」/「處理 HR 人事流程」/「訂單管理」}。採用 Dflow
-（SDD/DDD workflow guardian skill）引導開發流程，同時為未來遷移到
-ASP.NET Core 做準備。
+（SDD/DDD workflow guardian skill）引導開發流程，逐步將 business logic
+embedded in delivery/entrypoint code（presentation/UI layer、controllers、
+handlers、jobs、message consumers、data pipelines、stored procedures）抽離，
+並朝 target architecture 前進。
 
 {選填：補上團隊規模、使用者規模、主要 stakeholders 等 context，
 1-3 行即可。完整內容放在 `dflow/specs/shared/_overview.md`。}
@@ -46,7 +48,7 @@ ASP.NET Core 做準備。
 ```
 dflow/specs/
 ├── shared/                   # 專案級治理文件（由 Dflow CLI init 寫入）
-│   ├── _overview.md          # 系統現況與遷移策略
+│   ├── _overview.md          # 系統現況與 target architecture
 │   ├── _conventions.md       # 規格撰寫慣例
 │   └── Git-principles-*.md   # Git 規範（gitflow 或 trunk 版）
 ├── domain/                   # 領域知識
@@ -68,12 +70,20 @@ dflow/specs/
     └── tech-debt.md
 
 src/
-├── Domain/                   # 抽離的領域邏輯（純 C#）
+├── Domain/                   # 抽離的領域邏輯（framework-pure）
 │   ├── {BoundedContext}/
 │   └── SharedKernel/
-└── Pages/                    # 既有 WebForms 頁面
+└── Delivery/                 # delivery-layer code（entrypoints, controllers, handlers）
 ```
 
+> **目錄命名說明**：上方 `src/Domain/` / `src/Delivery/` 是 Clean
+> Architecture 通用示意，不限 stack。請依專案實際慣例對應（例：Java/Spring 用
+> `src/main/java/com/example/domain/`、Node/TS 用 `src/domain/` /
+> `src/routes/`、Python 用 `domain/` package、Go 用 `internal/domain/` /
+> `internal/handler/`、.NET 用 `src/{Project}.Domain/` + `.csproj` 分層）。
+> 完整 per-stack 範例見 `docs/examples-by-stack.md`。重點是
+> `src/Domain/`（或對應命名）保持與 delivery/entrypoint code 獨立。
+
 ---
 
 ## Development Workflow
@@ -83,9 +93,9 @@ src/
 ### Core Principles
 
 1. **Spec Before Code** — 沒有規格就不寫實作（依 Ceremony Scaling 調整嚴謹度）
-2. **Domain Extraction** — 業務邏輯屬於 `src/Domain/`，不屬於 Code-Behind
+2. **Domain Extraction** — 業務邏輯屬於 `src/Domain/`，不屬於 delivery/entrypoint code
 3. **Ubiquitous Language** — 使用 `dflow/specs/domain/glossary.md` 中定義的術語
-4. **Migration Awareness** — 每個決策都要考慮未來 ASP.NET Core 遷移
+4. **Migration Awareness** — 每個決策都要考慮 target architecture
 
 ### Dflow Skill — Canonical Decision Logic Lives in the Skill
 
@@ -114,7 +124,7 @@ AI 的完整決策樹、Workflow Transparency、Ceremony Scaling 三層判準
 
 - **Git 分支策略**：見 `dflow/specs/shared/Git-principles-{gitflow|trunk}.md`
 - **規格撰寫慣例**：見 `dflow/specs/shared/_conventions.md`
-- **系統現況與遷移**：見 `dflow/specs/shared/_overview.md`
+- **系統現況與 target architecture**：見 `dflow/specs/shared/_overview.md`
 - {其他專案特有規則，例如「JPY 金額必須以最小貨幣單位（yen）儲存」/
   「所有費用報銷需主管審核」/「跨時區行程以 UTC 記錄」}
 
@@ -122,18 +132,18 @@ AI 的完整決策樹、Workflow Transparency、Ceremony Scaling 三層判準
 
 此目錄中的程式碼必須遵守（與 Dflow skill 的 Domain Layer Rules 一致）：
 
-- ❌ 不可引用 `System.Web` 或任何 WebForms 命名空間
+- ❌ 不可引用任何 delivery-framework 命名空間（例：HTTP 請求/回應物件、Session/Cookie context、job runner context、CLI flag parser、ViewState 類等）
 - ❌ 不可直接存取資料庫（使用 interface + Repository pattern）
-- ❌ 不可使用 `HttpContext`、`Session`、`ViewState`
+- ❌ 不可使用 delivery-framework runtime context（例：HTTP request/response、session/cookie、job runner state、CLI args）
 - ❌ 不可有 UI 相關邏輯
-- ✅ 純 C# 類別，可直接搬到 ASP.NET Core 專案
-- ✅ 所有公開行為都能在沒有 Web 基礎設施的情況下測試
+- ✅ 語言純粹的 class（不依賴 delivery framework），可直接搬到 target architecture
+- ✅ 所有公開行為都能在沒有 delivery infrastructure 的情況下測試
 
 ### AI Collaboration Notes
 
 - 遇到開發需求時，優先引導使用 `/dflow:` 命令
 - 回答 Domain 相關問題時，優先參考 `dflow/specs/domain/` 中的文件
-- 發現 Code-Behind 中的業務邏輯時，建議抽離到 `src/Domain/`
+- 發現 delivery/entrypoint code 中的業務邏輯時，建議抽離到 `src/Domain/`
 - 建立分支前，確認命名符合規範且對應 spec 存在
 - 詳細 Git 操作規則見 `dflow/specs/shared/Git-principles-{gitflow|trunk}.md`
 ```

package/templates/brownfield/scaffolding/Git-principles-gitflow.md

@@ -170,7 +170,7 @@ before making key Git operations:
       `behavior.md` reflect the feature's net BR changes
 - [ ] `dflow/specs/domain/glossary.md` updated with any new terms
 - [ ] `dflow/specs/migration/tech-debt.md` updated with any debt discovered
-- [ ] Domain layer (`src/Domain/`) has no `System.Web` references
+- [ ] Domain layer (`src/Domain/`) has no delivery-framework references
 
 ---
 

package/templates/brownfield/scaffolding/Git-principles-trunk.md

@@ -134,7 +134,7 @@ and circle the chosen one.
       `behavior.md` reflect the feature's net BR changes
 - [ ] `dflow/specs/domain/glossary.md` updated with any new terms
 - [ ] `dflow/specs/migration/tech-debt.md` updated with any debt discovered
-- [ ] Domain layer (`src/Domain/`) has no `System.Web` references
+- [ ] Domain layer (`src/Domain/`) has no delivery-framework references
 - [ ] CI green
 - [ ] PR has at least one review approval
 

package/templates/brownfield/scaffolding/_conventions.md

@@ -108,7 +108,7 @@ situations.
 |------------------------------|--------------------|-----|
 | {e.g. Year-end reporting tweak without BR change} | T2 | Touches logic path even though no new BR; extract to `lightweight-spec.md` for trace |
 | {e.g. Pure label / display text translation} | T3 | No BR change; inline row in `_index.md` |
-| {e.g. UI refresh across multiple pages} | T1 (project convention) | We treat multi-page UI refresh as T1 for this project even though Dflow default would be T2, because our WebForms UI changes often leak into Code-Behind |
+| {e.g. UI refresh across multiple entrypoints} | T1 (project convention) | We treat multi-entrypoint UI/API refresh as T1 for this project even though Dflow default would be T2, because these changes often leak into business logic embedded in delivery/entrypoint code (presentation/UI layer, controllers, handlers, jobs, message consumers, data pipelines, or stored procedures) |
 
 If the team disagrees on tier classification for a specific change,
 run through the T3 four-criteria checklist (in the Dflow skill) and

package/templates/brownfield/scaffolding/_overview.md

@@ -3,7 +3,7 @@
 # System Overview — {System Name}
 
 > Created: {YYYY-MM-DD}
-> Scope: current state and migration direction of {System Name}
+> Scope: current state and target-architecture direction of {System Name}
 > Audience: team members onboarding to the system + AI assistants reading
 > `dflow/specs/` for context.
 
@@ -30,33 +30,44 @@ delivers. Keep it non-technical enough that a new hire can skim it in
 
 ## Technical Architecture (Current)
 
-This project runs on ASP.NET WebForms. The SDD/DDD workflow is used to
-progressively prepare for migration (see "Migration Strategy" below).
+This project runs on {Framework}. The SDD/DDD workflow is used to
+progressively extract domain logic and prepare for the target architecture
+(see "Target Architecture Strategy" below).
 
 | Item | Current |
 |------|---------|
-| Framework | ASP.NET WebForms ({.NET Framework version}) |
-| Language | C# {version} |
+| Framework | {Framework} ({Framework version}) |
+| Language | {Language} |
 | Database | {e.g. SQL Server 2019, MySQL 8.0} |
-| ORM / data access | {e.g. Entity Framework 6, ADO.NET, stored procedures} |
-| UI | WebForms Pages + Code-Behind + {CSS framework if any} |
-| Auth | {e.g. Forms authentication, Windows auth} |
-| Hosting | {e.g. IIS on-prem, Azure App Service} |
+| ORM / persistence | {ORM / persistence} ({ORM version}) |
+| Delivery / entrypoint | {Framework} |
+| Auth | {e.g. session auth, OAuth/OIDC, API key, internal SSO} |
+| Hosting | {e.g. on-prem VM, container platform, managed app platform} |
 
 ### Code Layout (High Level)
 
+> **Note on directory naming**: The tree below uses generic Clean
+> Architecture folder names (`src/Domain/`, `src/Delivery/`). Adapt to your
+> stack's conventions — for example, Java/Spring `src/main/java/com/example/domain/`,
+> Node/TS `src/domain/` + `src/routes/`, Python `domain/` package, Go
+> `internal/domain/` + `internal/handler/`, PHP/Laravel `app/Domain/` +
+> `app/Http/`, .NET `src/{Project}.Domain/` + `src/{Project}.WebAPI/`
+> (separate `.csproj` per layer). For full per-stack examples see
+> `docs/examples-by-stack.md`.
+
 ```
 src/
-├── Domain/        # Extracted domain logic (pure C#; migration target)
+├── Domain/        # Extracted domain logic (framework-pure; target architecture)
 │   ├── {BoundedContext}/
 │   └── SharedKernel/
-└── Pages/         # WebForms pages (.aspx + Code-Behind)
+└── Delivery/      # delivery-layer code (entrypoints, controllers, handlers)
 ```
 
 The `src/Domain/` directory is where business logic lives **as it is
-extracted** from Code-Behind. Everything in `src/Domain/` must be pure
-C# with no `System.Web` dependencies (see `CLAUDE.md` and the Dflow
-skill for the full rule set).
+extracted** from delivery/entrypoint code (presentation/UI layer, controllers,
+handlers, jobs, message consumers, data pipelines, or stored procedures).
+Everything in `src/Domain/` must be framework-pure with no delivery-framework
+dependencies (see `CLAUDE.md` and the Dflow skill for the full rule set).
 
 ---
 
@@ -66,34 +77,34 @@ skill for the full rule set).
 top 3–5 known issues the team wants to address as part of migration.
 Link each to `migration/tech-debt.md` entries if they exist.}
 
-1. {e.g. Business logic scattered across Code-Behind; duplicated
-   calculations in multiple pages}
-2. {e.g. Direct SQL in Code-Behind; inconsistent error handling}
+1. {e.g. Business logic embedded in delivery/entrypoint code; duplicated
+   calculations across multiple flows}
+2. {e.g. Direct SQL in delivery/entrypoint code; inconsistent error handling}
 3. {e.g. Magic numbers / undocumented statuses}
 
 ---
 
-## Migration Strategy
+## Target Architecture Strategy
 
-This system is being prepared for migration to ASP.NET Core. The
-migration follows four principles; expand / adapt each to this project:
+This system is being prepared for the project's target architecture. The
+strategy follows four principles; expand / adapt each to this project:
 
-- **Migration Awareness** — Every feature decision considers future
-  migration. We ask "does this make the migration harder or easier?"
+- **Migration Awareness** — Every feature decision considers the target
+  architecture. We ask "does this make the target architecture harder or easier?"
 - **Domain Extraction** — Business logic gradually moves from
-  Code-Behind to `src/Domain/`. Each feature is an opportunity to
-  extract a little more.
+  delivery/entrypoint code to `src/Domain/`. Each feature is an
+  opportunity to extract a little more.
 - **Dual-Track Parallel** — We do not force-rewrite existing code; new
-  development preferentially uses the Domain layer, and legacy pages
+  development preferentially uses the Domain layer, and legacy entrypoints
   get touched only when they are being modified.
-- **Pragmatic First** — Migration does not block feature delivery. If
+- **Pragmatic First** — Target-architecture work does not block feature delivery. If
   a deadline is tight, record the debt in `migration/tech-debt.md`
   and continue.
 
-### Target Architecture (Post-Migration)
+### Target Architecture
 
-{1-2 sentences describing where this system is heading: e.g. "ASP.NET
-Core 8 + Clean Architecture + EF Core, deployed to Azure App Service."
+{1-2 sentences describing where this system is heading: e.g. "{Framework}
++ Clean Architecture + {ORM / persistence}, deployed to {hosting platform}."
 Link to any ADR or migration plan doc if one exists.}
 
 ---