@arcbridge/core 0.2.1 → 0.3.0

package/dist/index.js

@@ -832,6 +832,41 @@ ${input.quality_priorities.map((q, i) => `| ${i + 1} | ${q} | *Describe what ${q
   };
 }
 
+// src/templates/arc42/02-constraints.ts
+function constraintsTemplate(input) {
+  return {
+    frontmatter: {
+      section: "constraints",
+      schema_version: 1
+    },
+    body: `# Architecture Constraints
+
+Document the constraints that shape architectural decisions for ${input.name}. Constraints are non-negotiable requirements from the environment \u2014 they are not chosen, they are given.
+
+## Technical Constraints
+
+| Constraint | Description |
+|-----------|-------------|
+| *e.g., Must run on Node.js 22+* | *Explain why this constraint exists* |
+| *e.g., No native dependencies* | *Required for CI/CD compatibility* |
+
+## Organizational Constraints
+
+| Constraint | Description |
+|-----------|-------------|
+| *e.g., Team of 1-2 developers* | *Impacts architecture complexity budget* |
+| *e.g., Must ship MVP in 4 weeks* | *Impacts scope and technology choices* |
+
+## Legal / Compliance Constraints
+
+| Constraint | Description |
+|-----------|-------------|
+| *e.g., GDPR compliance required* | *Impacts data storage and processing* |
+| *e.g., MIT-compatible dependencies only* | *Impacts library selection* |
+`
+  };
+}
+
 // src/templates/arc42/03-context.ts
 function techStack(template) {
   switch (template) {
@@ -887,6 +922,47 @@ ${techStack(input.template)}
   };
 }
 
+// src/templates/arc42/04-solution-strategy.ts
+function solutionStrategyTemplate(input) {
+  return {
+    frontmatter: {
+      section: "solution-strategy",
+      schema_version: 1
+    },
+    body: `# Solution Strategy
+
+Document the fundamental decisions and solution approaches that drive the architecture of ${input.name}. This section explains *why* the architecture looks the way it does \u2014 connecting quality goals to technical decisions.
+
+## Technology Decisions
+
+| Decision | Rationale | Quality Goal |
+|----------|-----------|-------------|
+| *e.g., Use TypeScript* | *Type safety reduces runtime errors* | *Reliability, Maintainability* |
+| *e.g., Use SQLite for local storage* | *Zero-config, no external service dependency* | *Maintainability* |
+
+## Architecture Approach
+
+*Describe the high-level architecture pattern and why it was chosen.*
+
+- *e.g., Layered architecture with clear module boundaries (enforced by ArcBridge building blocks)*
+- *e.g., YAML as source of truth, DB as queryable cache \u2014 enables version control and human readability*
+
+## Quality Goal Strategies
+
+| Quality Goal | Strategy |
+|-------------|----------|
+${input.quality_priorities.map((q) => `| ${q} | *How will you achieve ${q}?* |`).join("\n")}
+
+## Decomposition Approach
+
+*How is the system broken down into building blocks? What principles guide the decomposition?*
+
+- *e.g., Feature-based: each major feature is a building block with clear interfaces*
+- *e.g., Layer-based: presentation, business logic, data access*
+`
+  };
+}
+
 // src/templates/arc42/05-building-blocks.ts
 import { existsSync as existsSync2, readdirSync } from "fs";
 import { join as join3 } from "path";
@@ -2297,7 +2373,9 @@ function generateArc42(targetDir, input) {
   mkdirSync2(decisionsDir, { recursive: true });
   const sections = [
     { file: "01-introduction.md", template: introductionTemplate },
+    { file: "02-constraints.md", template: constraintsTemplate },
     { file: "03-context.md", template: contextTemplate },
+    { file: "04-solution-strategy.md", template: solutionStrategyTemplate },
     { file: "05-building-blocks.md", template: buildingBlocksTemplate },
     { file: "06-runtime-views.md", template: runtimeViewsTemplate },
     { file: "07-deployment.md", template: deploymentTemplate },
@@ -2335,7 +2413,7 @@ function phasePlanTemplate(_input) {
       id: "phase-0-setup",
       name: "Project Setup",
       phase_number: 0,
-      status: "in-progress",
+      status: "planned",
       description: "Initialize project structure, install dependencies, configure tooling",
       gate_requirements: [
         "Project builds successfully",
@@ -2600,7 +2678,7 @@ function phasePlanTemplate2(_input) {
       id: "phase-0-setup",
       name: "Project Setup",
       phase_number: 0,
-      status: "in-progress",
+      status: "planned",
       description: "Initialize Vite + React project, configure TypeScript, install dependencies",
       gate_requirements: [
         "Project builds successfully with Vite",
@@ -2866,7 +2944,7 @@ function phasePlanTemplate3(_input) {
       id: "phase-0-setup",
       name: "Project Setup",
       phase_number: 0,
-      status: "in-progress",
+      status: "planned",
       description: "Initialize API service, configure TypeScript, set up database and middleware",
       gate_requirements: [
         "Project builds successfully",
@@ -3049,7 +3127,7 @@ function phasePlanTemplate4(_input) {
       id: "phase-0-setup",
       name: "Project Setup",
       phase_number: 0,
-      status: "in-progress",
+      status: "planned",
       description: "Initialize ASP.NET Core project, configure DI, set up database and middleware pipeline",
       gate_requirements: [
         "Project builds and runs successfully",
@@ -3248,7 +3326,7 @@ function phasePlanTemplate5(_input) {
       id: "phase-0-setup",
       name: "Project Setup",
       phase_number: 0,
-      status: "in-progress",
+      status: "planned",
       description: "Initialize Unity project structure, configure input system, core game loop, and assembly definitions",
       gate_requirements: [
         "Unity project opens and runs without errors",
@@ -3533,7 +3611,9 @@ You are responsible for maintaining these sections in \`.arcbridge/arc42/\`. Upd
 | Section | File | When to update |
 |---------|------|----------------|
 | **01 Introduction & Goals** | \`01-introduction.md\` | When project scope, stakeholders, or key goals change |
+| **02 Architecture Constraints** | \`02-constraints.md\` | When new constraints are discovered (technical, organizational, legal) |
 | **03 Context & Scope** | \`03-context.md\` | When adding/removing external systems, APIs, or integrations |
+| **04 Solution Strategy** | \`04-solution-strategy.md\` | When fundamental technology or architecture decisions change |
 | **05 Building Blocks** | \`05-building-blocks.md\` | When adding new modules, changing responsibilities, or restructuring layers |
 | **06 Runtime Views** | \`06-runtime-views.md\` | When adding key workflows (e.g., auth flow, order processing, data sync) |
 | **07 Deployment** | \`07-deployment.md\` | When changing infrastructure, environments, or deployment strategy |