Activities - Deploy Software Process

#	Name	Abbrev.	Guidance	Actions
Elaboration 6
1	Verify ESM Artifacts	DSP-1	Verify ESM Artifacts Objective Verify that all required artifacts from the Envision the System (ESM) …	Read the 'DSP-1 Verify ESM Artifacts' activity from playbook 'Junior Edda' (workflow 'Deploy Software Process'). Follow its guidance when assisting me. # Verify ESM Artifacts ## Objective Verify that all required artifacts from the Envision the System (ESM) workflow exist before proceeding to AI IDE configuration. If any are missing, direct the user to run the ESM workflow first. --- ## Process ### 1. Scan for Required ESM Artifacts Check for the existence and non-emptiness of: \| Artifact \| Expected Location \| ESM Activity \| \|----------\|-------------------\|--------------\| \| User Journey \| `docs/features/user_journey.md` \| ESM-02 \| \| Dialogue Maps / Screen Flows \| `docs/ux/` (at least one `.drawio` or screen flow file) \| ESM-04 \| \| Feature Files \| `docs/features/act-/` (at least one `.feature` file or scenario markdown) \| ESM-05 \| \| IA Guidelines* \| `docs/ux/IA_guidelines.md` \| ESM-03 \| ### 2. Evaluate Results For each artifact, report status: ``` ESM Artifact Check: User Journey \| ✅ Found (docs/features/user_journey.md, 104KB) Dialogue Maps \| ✅ Found (docs/ux/2_dialogue-maps/, 3 files) Feature Files \| ✅ Found (docs/features/act-/, 12 acts) IA Guidelines \| ❌ Missing ``` ### 3. If Any Missing → Redirect to ESM If one or more artifacts are missing: > ⚠️ ESM artifacts incomplete.* > The following are missing: {list}. > Please run the Envision the System (ESM) workflow first. > See: `.windsurf/workflows/ESM/_workflow.md` Stop here — do not proceed to DSP-02 until all ESM artifacts are present. ### 4. If All Present → Proceed > ✅ All ESM artifacts verified. Proceeding to DSP-02 (Verify DTA Artifacts). --- ## Deliverables - ✅ ESM artifact checklist evaluated - ✅ All artifacts present — or user redirected to ESM workflow - ✅ Ready to proceed to DSP-02
2	Verify DTA Artifacts	DSP-2	Verify DTA Artifacts Objective Verify that the System Architecture Overview (SAO.md) from the Define Architecture …	Read the 'DSP-2 Verify DTA Artifacts' activity from playbook 'Junior Edda' (workflow 'Deploy Software Process'). Follow its guidance when assisting me. # Verify DTA Artifacts ## Objective Verify that the System Architecture Overview (SAO.md) from the Define Architecture (DTA) workflow exists and contains the required architectural decisions. If missing, direct the user to run the DTA workflow first. --- ## Process ### 1. Scan for SAO.md Check for existence and non-emptiness of: \| Artifact \| Expected Location \| DTA Activity \| \|----------\|-------------------\|--------------\| \| SAO.md \| `docs/architecture/SAO.md` \| DTA-18 \| ### 2. Validate SAO.md Content If the file exists, verify it contains key sections (search for headings): \| Required Section \| Purpose \| Used By DSP-05 \| \|-----------------\|---------\|-----------------\| \| Executive Summary \| Project overview for AI config \| Yes — project description \| \| System Architecture \| High-level components \| Yes — architecture section \| \| Design Principles \| Key decisions \| Yes — coding conventions \| \| Technology Stack or equivalent \| Languages, frameworks, tools \| Yes — tech stack reference \| \| Project Structure \| Directory layout \| Yes — directory map \| \| Testing Infrastructure \| Test strategy \| Yes — testing conventions \| Report status: ``` DTA Artifact Check: SAO.md exists \| ✅ Found (docs/architecture/SAO.md, 2671 lines) Executive Summary \| ✅ Present System Architecture \| ✅ Present Design Principles \| ✅ Present Technology Stack \| ❌ Missing — no explicit tech stack table Project Structure \| ✅ Present Testing Infrastructure \| ✅ Present ``` ### 3. If SAO.md Missing or Incomplete → Redirect to DTA If SAO.md does not exist: > ⚠️ SAO.md not found. > Please run the Define Architecture (DTA) workflow first. > See: `.windsurf/workflows/DTA/_workflow.md` If SAO.md exists but is missing key sections: > ⚠️ SAO.md incomplete. > Missing sections: {list}. > Please complete the relevant DTA activities: {activity list}. Stop here — do not proceed to DSP-03 until SAO.md is complete. ### 4. If Complete → Proceed > ✅ SAO.md verified with all required sections. Proceeding to DSP-03 (Verify Architecture & Code Organization). --- ## Deliverables - ✅ SAO.md existence verified - ✅ SAO.md content validated for required sections - ✅ All sections present — or user redirected to DTA workflow - ✅ Ready to proceed to DSP-03
3	Verify Architecture & Code Organization	DSP-3	Verify Architecture & Code Organization Objective Verify that the project has a defined code organization, …	Read the 'DSP-3 Verify Architecture & Code Organization' activity from playbook 'Junior Edda' (workflow 'Deploy Software Process'). Follow its guidance when assisting me. # Verify Architecture & Code Organization ## Objective Verify that the project has a defined code organization, technology stack, and working project structure. This goes beyond SAO.md existence (DSP-02) to check that the architectural decisions have been realized in the actual codebase or are clearly documented for a greenfield project. --- ## Process ### 1. Check Project Structure Exists For an existing project, verify: \| Check \| What to Look For \| Source \| \|-------\|------------------\|--------\| \| Project root \| `manage.py`, `package.json`, `Cargo.toml`, or equivalent entry point \| DTA-04 \| \| Source directories \| Application code directories matching SAO.md structure \| DTA-04 \| \| Test directories \| `tests/` or equivalent with at least one test file \| DTA-06 \| \| Dependency file \| `requirements.txt`, `package.json`, `Cargo.toml`, etc. \| DTA-04 \| \| CI/CD config \| `.github/workflows/`, `Jenkinsfile`, etc. (optional for greenfield) \| DTA-10 \| For a greenfield project (no code yet), verify that SAO.md contains: - Explicit directory layout plan (from DTA-04) - Technology stack decisions (languages, frameworks, databases) - These will be used by BSP (Bootstrap Project) workflow to create the structure ### 2. Check Workflow & Skill Coverage Scan `.windsurf/workflows/` for available workflows: ``` Available Workflows: ESM \| Envision the System \| 7 activities \| ✅ DTA \| Define Architecture \| 18 activities \| ✅ DSP \| Deploy Software Process \| 6 activities \| ✅ (this workflow) BSP \| Bootstrap Project \| 8 activities \| ✅ BPE \| Build Feature \| N activities \| ✅ EST \| Estimate the Project \| 8 activities \| ✅ ``` Scan for available skills (if any exist in workflow `skills/` directories): ``` Available Skills: BSP/skills/ \| 3 skills found (others) \| ... ``` Scan for available artifact templates: ``` Available Artifact Templates: ESM/artifacts/ \| user_journey_template.md, feature_file_template.feature, ... DTA/artifacts/ \| sao_document_template.md DSP/artifacts/ \| claude_md_template.md, copilot_instructions_template.md, ... ``` ### 3. Evaluate Readiness Ready to proceed if: - SAO.md has technology stack and directory layout (from DSP-02) - Either project structure exists OR SAO.md documents the planned structure - At least BPE workflow is available (the AI needs to know how to build features) Not ready if: - No technology stack defined in SAO.md → redirect to DTA-02 (Define Application Blocks) - No directory layout in SAO.md → redirect to DTA-04 (Define Code Organization) - No BPE workflow available → this is a critical gap, inform user ### 4. Report Summary ``` Architecture & Code Organization Check: Technology stack defined \| ✅ Django 5 + SQLite + HTMX Directory layout defined \| ✅ In SAO.md Section "Project Structure" Project structure exists \| ✅ 4 Django apps, tests/, docs/ BPE workflow available \| ✅ .windsurf/workflows/BPE/ Skills available \| ✅ 3 skills in BSP/skills/ Artifact templates \| ✅ 7 templates across workflows ``` --- ## Deliverables - ✅ Project structure verified or planned - ✅ Workflow coverage inventoried - ✅ Skill coverage inventoried - ✅ Artifact template coverage inventoried - ✅ All prerequisites met — or user redirected to specific DTA/ESM activities - ✅ Ready to proceed to DSP-04
4	Choose Target AI IDE	DSP-4	Choose Target AI IDE Objective Ask the user which AI-assisted IDE they will use for …	Read the 'DSP-4 Choose Target AI IDE' activity from playbook 'Junior Edda' (workflow 'Deploy Software Process'). Follow its guidance when assisting me. # Choose Target AI IDE ## Objective Ask the user which AI-assisted IDE they will use for development, then record the choice to determine the output format for DSP-05 (Generate AI IDE Configuration). --- ## Process ### 1. Present Options Ask the user to choose their primary AI IDE: \| Target \| Output File(s) \| Format \| \|--------\|----------------\|--------\| \| Claude Code \| `CLAUDE.md` at project root \| Single Markdown file with all context \| \| GitHub Copilot \| `.github/copilot-instructions.md` \| Single Markdown file in `.github/` \| \| Windsurf \| `.windsurf/rules/.md` files \| Multiple rule files + workflow references \| \| Cursor* \| `.cursor/rules/.mdc` files \| Multiple rule files in MDC format \| ### 2. Clarify Multi-IDE Usage If the user works with multiple IDEs (e.g., Windsurf for daily work + Claude Code for complex tasks): - Generate configs for all selected targets* - Ensure consistency across configs (same conventions, same references) - Note: Windsurf and Cursor share the same workflow/rule structure but use different directories ### 3. Record Choice Document the selected target(s) for DSP-05: ``` Target AI IDE Selection: Primary: Windsurf Secondary: Claude Code Output files to generate: 1. .windsurf/rules/ (multiple .md files) 2. CLAUDE.md (single file) ``` ### 4. Confirm Output Structure Explain to the user what will be generated: For Claude Code / GitHub Copilot (single file): - One comprehensive Markdown file covering: - Project overview and architecture - Directory layout and docs map - Available workflows, skills, and artifact templates - AI/human collaboration patterns and quality gates - Coding conventions and testing discipline - How to build features (BPE workflow reference) - How to run locally For Windsurf / Cursor (multiple files): - The project already uses `.windsurf/rules/` and `.windsurf/workflows/` — these ARE the config - DSP-05 will audit and supplement existing rules to ensure completeness - A summary `_ai-context.md` rule file will be generated pointing to all docs, workflows, skills, and templates - Existing rules will NOT be overwritten --- ## Deliverables - ✅ Target AI IDE selected (one or more) - ✅ Output format understood by user - ✅ Ready to proceed to DSP-05 (Generate AI IDE Configuration)
5	Generate AI IDE Configuration	DSP-5	Generate AI IDE Configuration Objective Assemble a comprehensive configuration file for the chosen AI IDE …	Read the 'DSP-5 Generate AI IDE Configuration' activity from playbook 'Junior Edda' (workflow 'Deploy Software Process'). Follow its guidance when assisting me. # Generate AI IDE Configuration ## Objective Assemble a comprehensive configuration file for the chosen AI IDE target, pulling from SAO.md, ESM artifacts, available workflows, skills, artifact templates, and coding conventions. The output file gives the AI agent everything it needs to understand the project and start building features. --- ## Process ### 1. Gather Inputs Collect all source material identified in DSP-01 through DSP-03: \| Source \| What to Extract \| Config Section \| \|--------\|----------------\|----------------\| \| `docs/architecture/SAO.md` \| Executive summary, architecture, design principles, tech stack, directory layout \| Sections 1-3 \| \| `docs/features/user_journey.md` \| Acts, user journey overview \| Section 4 (Docs Map) \| \| `docs/features/act-/` \| Feature file inventory \| Section 4 (Docs Map) \| \| `docs/ux/IA_guidelines.md` \| UI patterns, design system \| Section 4 (Docs Map) \| \| `.windsurf/workflows//` \| Workflow names, descriptions, activity counts \| Section 5 (Workflows) \| \| `.windsurf/workflows//skills/` \| Skill titles, capability domains, tech stacks \| Section 6 (Skills) \| \| `.windsurf/workflows//artifacts/` \| Template file names and descriptions \| Section 7 (Artifact Templates) \| \| `.windsurf/rules/.md` \| Coding conventions, testing discipline, commit format \| Section 9 (Conventions) \| ### 2. Assemble Config File Use the appropriate template from `DSP/artifacts/` based on the target chosen in DSP-04. The config file MUST contain these sections (section numbers vary by template): #### Section: What Is {ProjectName} Extract from SAO.md Executive Summary. One paragraph explaining what the project does and its key innovation. #### Section: Architecture Extract from SAO.md: - High-level component diagram (ASCII or Mermaid) - Directory layout (from Project Structure section) - Data model hierarchy - Key design decisions (top 3-5) #### Section: Documentation Map Point to all key docs with brief descriptions: ```markdown \| What \| Where \| When to Read \| \|------\|-------\|--------------\| \| System architecture \| `docs/architecture/SAO.md` \| Before big changes \| \| User journey / all Acts \| `docs/features/user_journey.md` \| Feature planning \| \| Feature specs (BDD) \| `docs/features/act-/` \| Before implementing any feature \| \| UI patterns & IA \| `docs/ux/IA_guidelines.md` \| Before building UI \| \| Development rules \| `.windsurf/rules/.md` \| Always active \| \| Process workflows \| `.windsurf/workflows//` \| When running a workflow \| \| Agent reference architecture \| Playbook artifact 56 \| When SAO §17 applies \| \| Test architecture (TFK-01) \| `docs/architecture/test-architecture.md` \| Agent test lanes, CI gates \| ``` When SAO §17 applies, add agent-lane rows to the docs map: ```markdown \| Agent integration proofs (PRF-) \| skill Agent Integration Proof Patterns* \| Before agent slices \| \| Agent task eval (TASK-) \| skill Agent Task Eval* \| Promotion / nightly only \| \| assert_agent_story helper \| `tests/support/agent_story.py` \| TFK-02 bootstrap \| ``` #### Section: Available Workflows List each workflow with its purpose, activity count, and when to use it: ```markdown \| Workflow \| Purpose \| Activities \| When to Use \| \|----------\|---------\|------------\|-------------\| \| ESM \| Envision the System \| 7 \| Defining what to build \| \| DTA \| Define Architecture \| 18 \| Making architectural decisions \| \| DSP \| Deploy Software Process \| 6 \| Setting up AI IDE \| \| BSP \| Bootstrap Project \| 8 \| Scaffolding new project \| \| BPE \| Build Feature \| N \| Primary workflow for feature delivery \| \| EST \| Estimate the Project \| 8 \| Estimation and planning \| ``` #### Section: Available Skills List skills found in workflow `skills/` directories: ```markdown \| Skill \| Capability Domain \| Tech Stack \| Location \| \|-------\|-------------------\|------------\|----------\| \| {SkillTitle} \| {Domain} \| {Stack} \| `.windsurf/workflows/{WF}/skills/{file}` \| ``` When SAO §17 applies, ensure these agent-test skills appear in the inventory (link from playbook, do not duplicate bodies): ```markdown \| Agent Integration Proof Patterns \| TEST_INTEGRATION \| pytest, CAP-004, artifact-56 \| playbook skill \| \| Agent Task Eval \| TEST_INTEGRATION \| golden-tasks, live LLM \| playbook skill \| \| Pytest Log Story Assertions \| LOG_STORY_TESTING \| pytest caplog \| playbook skill \| \| Test Trophy Architecture \| TEST_STRATEGY \| pytest+behave \| playbook skill \| \| pytest Runner Configuration \| TEST_FRAMEWORK \| pytest markers \| playbook skill \| ``` If no skills exist yet, note: "No skills defined yet. Skills provide technology-specific implementation guidance for workflow activities." #### Section: Artifact Templates List templates found in workflow `artifacts/` directories: ```markdown \| Template \| Workflow \| Purpose \| Location \| \|----------\|----------\|---------\|----------\| \| User Journey Template \| ESM \| Structure for user journey doc \| `ESM/artifacts/user_journey_template.md` \| \| IA Guidelines Template \| ESM \| Design system & UI patterns spec \| `ESM/artifacts/ia_guidelines_template.md` \| \| Feature File Template \| ESM \| BDD scenario format \| `ESM/artifacts/feature_file_template.feature` \| \| SAO Template \| DTA \| Architecture document structure \| `DTA/artifacts/sao_document_template.md` \| \| CLAUDE.md Template \| DSP \| AI config for Claude Code \| `DSP/artifacts/claude_md_template.md` \| \| Copilot Instructions Template \| DSP \| AI config for GitHub Copilot \| `DSP/artifacts/copilot_instructions_template.md` \| \| Windsurf/Cursor Rules Template \| DSP \| AI config for Windsurf/Cursor \| `DSP/artifacts/windsurf_cursor_rules_template.md` \| \| Makefile Template \| BSP \| Project orchestration Makefile \| `BSP/artifacts/makefile_template.mk` \| \| Helm Chart Template \| DCD \| K8s Helm chart structure \| `DCD/artifacts/` (reference structure) \| \| Infra Repo Scaffold \| DCI \| CDK infra repo structure \| `DCI/artifacts/` (reference structure) \| \| Implementation Plan Template \| BPE \| Feature implementation plan \| `BPE/artifacts/implementation_plan_template.md` \| \| Definition of Done Checklist Template \| BPE \| DoD checklist for feature sign-off \| `BPE/artifacts/definition_of_done_checklist_template.md` \| \| AI Agent Reference Architecture \| DTA \| CAP-, PRF-, TASK-* catalogs \| `DTA/artifacts/` artifact 56 \| ``` #### Section: AI/Human Collaboration Patterns Absorbed from the former DSP-05 content. Include: AI Agent Responsibilities: - Code generation following established patterns - Test implementation (unit, integration, e2e) - Documentation generation (docstrings, README updates) - Refactoring within architectural boundaries Human Developer Responsibilities: - Architectural decisions and boundary setting - Code review and quality validation - Security-sensitive implementations - Production deployment decisions Quality Gates for AI-Generated Code: 1. All tests pass (unit, integration, linting) 2. Code coverage meets project threshold 3. Documentation generated for public APIs 4. Code follows established patterns from SAO.md 5. Human review and approval before merge Escalation Rules: - Ambiguous requirements → ask human - Architectural decisions outside patterns → ask human - Security-sensitive code → flag for human review #### Section: Coding Conventions Extract from `.windsurf/rules/` or document directly: - Commit format (Angular convention) - Method size limits (20-30 lines max for public methods) - Import organization (module-level only) - Logging standards (INFO level, what/why/where/when) - Testing discipline (test-first, pytest, no mocks in integration tests except CAP-004 ScriptedLLM in `@agent_proof` tests) When SAO §17 applies, append agent test lane conventions: ```markdown ### Agent test lanes (SAO §17) \| Lane \| Gate \| Command \| Rule / skill \| \|------\|------\|---------\|--------------\| \| 1 Control-plane proofs \| PR when AGENTS_ENABLED \| `make test-agent-proof` \| `do-assert-agent-story`, Agent Integration Proof Patterns \| \| 2 Deterministic shell \| PR integration \| normal `make test` \| no LLM mock \| \| 3 Live contract eval \| Nightly / CD optional \| `agent-eval.yml` \| temp=0 contracts \| \| 4 Task performance \| Promotion \| `make test-agent-quality` \| Agent Task Eval, not PR merge \| - Behave AT proves user-visible behavior; `@pytest.mark.agent_proof` proves PRF orchestration — do not merge them. - Ban FakeLLM and silent queue exhaustion — CAP-004 ScriptedLLM only (`do-not-mock-in-integration-tests`). - Plan slices declare Agent Proof Table (BPE-01 Section G); MIN manifest may set `checkpoint.agent_proof_command`. ``` #### Section: Development Workflow (How to Build Features) Reference the BPE workflow with a condensed summary: 1. Read the feature spec in `docs/features/act-/` 2. Read SAO.md for architectural context 3. Backend: models → services → views 4. Frontend: templates + interactions 5. Tests: write before implementation, 100% pass rate required 6. When SAO §17: behavior + log story + agent proof green in same slice 7. PR with all changes #### Section: Running Locally Extract from SAO.md or document: - Setup commands (venv, install, migrate) - Start dev server - Run tests - Load demo data When SAO §17 applies, append agent test commands: ```bash make test-agent-proof # lane 1 PRF proofs (no-op when AGENTS_ENABLED unset) make test-agent-quality # lane 4 TASK- eval (nightly / manual) pytest -m agent_proof tests/integration/agent/ -x ``` ### 3. Customize for Target Format Claude Code (`CLAUDE.md`): - Single file, flat Markdown sections with `---` separators - Use `##` for main sections - Keep under ~500 lines (Claude Code reads this on every conversation) GitHub Copilot (`.github/copilot-instructions.md`): - Single file, similar to CLAUDE.md but may use different heading conventions - Focus on coding patterns and conventions (Copilot is code-completion oriented) Windsurf (`.windsurf/rules/_ai-context.md`): - Create a summary context rule that points to existing rules and workflows - Do NOT duplicate content already in `.windsurf/rules/.md` - Focus on the docs map, workflow inventory, and skills inventory - Add conditional trigger: "When starting a new conversation or task" Cursor* (`.cursor/rules/_ai-context.mdc`): - Similar to Windsurf but uses MDC format with YAML frontmatter - Mirror the Windsurf content adapted to Cursor conventions ### 4. Present to User Show the generated config file to the user before writing it: - Highlight any sections that are thin or missing source material - Ask if any project-specific conventions should be added - Confirm file location is correct --- ## Deliverables - ✅ AI IDE config file generated for chosen target(s) - ✅ All 10 sections populated from source material - ✅ Agent test lanes + skills inventoried when SAO §17 applies - ✅ User reviewed the generated content - ✅ Ready to proceed to DSP-06 (Review & Commit) ## Artifacts Produced None ## Artifacts Consumed ESM Templates (inventoried for Section 7 — Artifact Templates): - User Journey Template (`ESM/artifacts/user_journey_template.md`) - IA Guidelines Template (`ESM/artifacts/ia_guidelines_template.md`) - Feature File Template (`ESM/artifacts/feature_file_template.feature`) DTA Templates: - System Architecture Overview Template (`DTA/artifacts/sao_document_template.md`) DSP Templates (used to generate the output config file in step 2): - CLAUDE.md Template (`DSP/artifacts/claude_md_template.md`) - Copilot Instructions Template (`DSP/artifacts/copilot_instructions_template.md`) - Windsurf/Cursor Rules Template (`DSP/artifacts/windsurf_cursor_rules_template.md`) BSP Templates (inventoried for Section 7): - Makefile Template (`BSP/artifacts/makefile_template.mk`) DCD Templates (inventoried for Section 7): - Helm Chart Template (`DCD/artifacts/` — reference structure) BPE Templates (inventoried for Section 7): - Implementation Plan Template (`BPE/artifacts/implementation_plan_template.md`) - Definition of Done Checklist Template (`BPE/artifacts/definition_of_done_checklist_template.md`) DCI Templates (inventoried for Section 7): - Infra Repo Scaffold (`DCI/artifacts/` — reference structure) ## Notes No additional notes.
6	Review & Commit	DSP-6	Review & Commit Objective Review the generated AI IDE configuration file(s) with the user, make …	Read the 'DSP-6 Review & Commit' activity from playbook 'Junior Edda' (workflow 'Deploy Software Process'). Follow its guidance when assisting me. # Review & Commit ## Objective Review the generated AI IDE configuration file(s) with the user, make any requested adjustments, and commit to the repository. --- ## Process ### 1. Present Generated Config for Review Show the user the generated file(s) from DSP-05: For each generated file, verify: \| Check \| Criteria \| \|-------\|----------\| \| Completeness \| All 10 sections present and populated \| \| Accuracy \| Architecture matches current SAO.md \| \| Docs Map \| All referenced files actually exist \| \| Workflows \| All available workflows listed \| \| Skills \| All available skills listed (or "none yet" noted) \| \| Artifact Templates \| All templates referenced with correct paths \| \| Conventions \| Coding standards match team practice \| \| Running Locally \| Commands are correct and tested \| ### 2. Collect User Feedback Ask the user: 1. Is anything missing? — project-specific conventions, team norms, special tools? 2. Is anything wrong? — outdated architecture, incorrect paths, stale conventions? 3. Is anything unnecessary? — sections that add noise without value? 4. Tone and style — too verbose? Too terse? Right level of detail? ### 3. Apply Adjustments Make requested changes to the generated file(s). Common adjustments: - Add project-specific environment variables or secrets handling - Add team-specific review processes - Adjust emphasis on certain workflows over others - Add links to external resources (CI/CD dashboards, design tools, etc.) ### 4. Validate File Locations Confirm files are in the correct locations: \| Target \| Expected Location \| Exists? \| \|--------\|-------------------\|---------\| \| Claude Code \| `CLAUDE.md` (project root) \| ✅/❌ \| \| GitHub Copilot \| `.github/copilot-instructions.md` \| ✅/❌ \| \| Windsurf \| `.windsurf/rules/_ai-context.md` \| ✅/❌ \| \| Cursor \| `.cursor/rules/_ai-context.mdc` \| ✅/❌ \| ### 5. Commit Commit the generated config file(s) with: ``` docs(dsp): generate AI IDE configuration for {target} - Generated {filename} from SAO.md, ESM artifacts, and workflow inventory - Includes: architecture, docs map, workflows, skills, artifact templates, AI/human collaboration patterns, coding conventions, BPE workflow reference - Target IDE: {Claude Code \| GitHub Copilot \| Windsurf \| Cursor} ``` --- ## Deliverables - ✅ Config file(s) reviewed by user - ✅ Adjustments applied per user feedback - ✅ File locations validated - ✅ Committed to repository - ✅ AI IDE configured — DSP is complete. ## Next Step If BSP (Bootstrap Project) is not yet complete: run BSP now. BSP creates the Makefile, installs dependencies, and stands up the welcome page — all required by PIN-01. If BSP is already complete: proceed to BSP-08 for the Construction Handoff and mode selection. Do not start BPE or PIN directly from DSP — the project must be bootstrapped first.

Activities in Deploy Software Process