intentdna 1.7.4 → 1.8.0

package/dist/templates/metadata.js

@@ -1,3 +1,123 @@
+export const WORKFLOW_ASSET_IDS = {
+    default: "flutter-rewrite",
+    behaviorLock: "flutter-behavior-lock",
+    refactoringRescue: "flutter-refactoring-rescue",
+    rewriteDiagnosisReview: "flutter-rewrite-diagnosis-review",
+    rewriteFixReviewLoop: "flutter-rewrite-fix-review-loop",
+    rewriteActiveFollowup: "flutter-rewrite-active-followup",
+    author: "workflow-author",
+    blockedScopeTriage: "workflow-blocked-scope-triage",
+    crossBoundaryResourceApproval: "workflow-cross-boundary-resource-approval",
+    verificationCommandRouting: "workflow-verification-command-routing",
+};
+export const WORKFLOW_SUGGESTION_IDS = {
+    activeFollowup: "template-active-followup",
+    blockedTriage: "template-blocked-triage",
+    c5CapturedRunFacts: "c5-captured-run-facts",
+    crossBoundaryResourceApproval: "template-cross-boundary-resource-approval",
+    modelVerifier: "template-model-verifier",
+};
+const REWRITE_GOVERNANCE_INTENT = {
+    keywords: [
+        "logic equivalence",
+        "逻辑对等",
+        "behavior preserving",
+        "behavior-preserving",
+        "行为保持",
+        "行为锁定",
+        "意图锁定",
+        "v1/v2",
+        "v1 to v2",
+        "精准改写",
+    ],
+    signal: "rewrite-governance-intent",
+    weight: 5,
+};
+const FLUTTER_DOMAIN_INTENT = {
+    keywords: ["flutter"],
+    signal: "flutter-domain",
+    weight: 2,
+};
+const REFACTORING_RESCUE_INTENT = {
+    keywords: [
+        "rescue",
+        "migrated but broken",
+        "broken migration",
+        "already migrated",
+        "already done",
+        "feature chain",
+        "one chain at a time",
+        "v1 is oracle",
+        "v1 as oracle",
+        "迁移救援",
+        "链路修复",
+    ],
+    signal: "refactoring-rescue-intent",
+    weight: 12,
+};
+const BLOCKED_SCOPE_INTENT = {
+    keywords: [
+        "blocked scope",
+        "blocked triage",
+        "blocked by review",
+        "needs human",
+        "human approval",
+        "outside diagnosis",
+        "outside scope",
+        "deferred scope",
+        "intentionally deferred",
+        "remaining skipped",
+        "人工确认",
+        "超出诊断范围",
+    ],
+    signal: "blocked-scope-intent",
+    weight: 12,
+};
+const CROSS_BOUNDARY_RESOURCE_INTENT = {
+    keywords: [
+        "cross boundary",
+        "cross-boundary",
+        "shared resource",
+        "localization",
+        "i18n",
+        "translation key",
+        "resource approval",
+        "shared config",
+        "shared package",
+        "outside diagnosis",
+        "outside scope",
+        "跨边界",
+        "共享资源",
+        "本地化",
+        "国际化",
+        "资源审批",
+        "超出诊断范围",
+    ],
+    signal: "cross-boundary-resource-intent",
+    weight: 14,
+};
+const VERIFICATION_ROUTING_INTENT = {
+    keywords: [
+        "verification command",
+        "test command",
+        "test command routing",
+        "wrong root",
+        "wrong cwd",
+        "package root",
+        "test root",
+        "machine log",
+        "parsed summary",
+        "red classification",
+        "canonical verification",
+        "verification route",
+        "验证命令",
+        "测试目录",
+        "运行目录",
+        "证据采集",
+    ],
+    signal: "verification-routing-intent",
+    weight: 12,
+};
 export const TEMPLATE_MATCH_METADATA = [
     { name: "code-review-pipeline", keywords: ["review", "code review", "pr review", "pull request", "审查"] },
     { name: "safe-refactoring", keywords: ["refactor", "refactoring", "restructure", "rewrite safely", "重构"] },
@@ -5,6 +125,14 @@ export const TEMPLATE_MATCH_METADATA = [
     { name: "full-pipeline", keywords: ["pipeline", "plan implement test", "full workflow", "完整流水线"] },
     { name: "systematic-debugging", keywords: ["debug", "debugging", "bug fix", "troubleshoot", "调试"] },
     { name: "verification-loop", keywords: ["verify", "verification", "validate", "check", "验证"] },
+    { name: "workflow-evidence-review", keywords: ["evidence review", "evidence package", "manager review", "adoption review", "evolution gate", "workflow evidence", "证据审查"] },
+    { name: WORKFLOW_ASSET_IDS.crossBoundaryResourceApproval, keywords: ["cross boundary", "cross-boundary", "shared resource", "localization", "i18n", "translation key", "resource approval", "outside diagnosis", "outside scope", "shared config", "跨边界", "共享资源", "本地化", "国际化", "资源审批", "超出诊断范围"], intent_signals: [CROSS_BOUNDARY_RESOURCE_INTENT] },
+    { name: WORKFLOW_ASSET_IDS.blockedScopeTriage, keywords: ["blocked scope", "blocked triage", "skip triage", "skipped tests", "deferred scope", "intentionally deferred", "blocked items", "remaining skipped", "blocked by review", "needs human", "human approval", "outside diagnosis", "outside scope", "阻塞", "人工确认", "超出诊断范围", "跳过", "延期"], intent_signals: [BLOCKED_SCOPE_INTENT] },
+    { name: "workflow-completion-audit", keywords: ["completion audit", "completion gate", "pass audit", "pass allowed", "done audit", "remaining work", "unimplemented skipped", "prove completion", "完成审计", "完成检查", "剩余工作"] },
+    { name: "workflow-runtime-smoke-review", keywords: ["runtime smoke", "smoke review", "sync verification", "post sync", "rollout smoke", "runtime distribution", "e2e smoke", "deployed url verification", "下发验收", "同步后验证", "运行面验收"] },
+    { name: WORKFLOW_ASSET_IDS.author, keywords: ["workflow author", "author workflow", "authoring packet", "create workflow", "new workflow", "workflow builder", "工作流创作", "创建工作流"] },
+    { name: "workflow-module-inventory", keywords: ["module inventory", "feature inventory", "global scan", "module scan", "page action inventory", "module priority", "workflow inventory", "全局扫描", "模块盘点", "功能清单", "动作清单"] },
+    { name: WORKFLOW_ASSET_IDS.verificationCommandRouting, keywords: ["verification command", "test command routing", "wrong root", "wrong cwd", "package root", "test root", "machine log", "parsed summary", "red classification", "canonical verification", "verification route", "验证命令", "测试目录", "运行目录", "证据采集"], intent_signals: [VERIFICATION_ROUTING_INTENT] },
     { name: "secure-dev", keywords: ["security", "secure", "owasp", "vulnerability", "安全"] },
     { name: "enterprise-baseline", keywords: ["enterprise", "organization", "company", "corporate", "企业"] },
     { name: "frontend-quality", keywords: ["frontend", "react", "vue", "css", "ui", "前端"] },
@@ -13,9 +141,11 @@ export const TEMPLATE_MATCH_METADATA = [
     { name: "documentation-writer", keywords: ["doc", "documentation", "readme", "wiki", "文档"] },
     { name: "devops-cicd", keywords: ["devops", "ci", "cd", "deploy", "pipeline", "运维"] },
     { name: "monorepo-governance", keywords: ["monorepo", "workspace", "packages", "governance"] },
-    { name: "flutter-behavior-lock", keywords: ["flutter", "behavior lock", "behavior spec", "行为锁定"] },
-    { name: "flutter-rewrite", keywords: ["flutter", "rewrite", "migration", "flutter rewrite"] },
-    { name: "flutter-refactoring-rescue", keywords: ["flutter", "rescue", "refactoring rescue"] },
+    { name: WORKFLOW_ASSET_IDS.behaviorLock, keywords: ["flutter", "behavior lock", "behavior spec", "行为锁定"] },
+    { name: WORKFLOW_ASSET_IDS.default, keywords: ["flutter", "rewrite", "migration", "flutter rewrite", "logic equivalence", "逻辑对等", "意图锁定", "精准改写", "行为保持"], intent_signals: [REWRITE_GOVERNANCE_INTENT, FLUTTER_DOMAIN_INTENT] },
+    { name: WORKFLOW_ASSET_IDS.rewriteDiagnosisReview, keywords: ["diagnosis review", "classify before editing", "rewrite diagnosis", "diagnosis gate", "v1/v2 evidence", "flutter diagnosis", "诊断审查", "先诊断"] },
+    { name: "flutter-rewrite-new", keywords: ["flutter", "rewrite", "migration", "governed rewrite", "flutter rewrite new"] },
+    { name: WORKFLOW_ASSET_IDS.refactoringRescue, keywords: ["flutter", "rescue", "refactoring rescue", "migrated but broken", "broken migration", "already migrated", "already done", "feature chain", "one feature chain", "one chain at a time", "v1 is oracle", "v1 as oracle", "rescue small steps", "迁移救援", "链路修复", "v1事实源"], intent_signals: [REFACTORING_RESCUE_INTENT, FLUTTER_DOMAIN_INTENT] },
     { name: "multi-perspective-review", keywords: ["multi perspective", "multiple reviewer", "多角度"] },
     { name: "subagent-parallel", keywords: ["parallel", "subagent", "concurrent", "并行"] },
     { name: "yolo-with-guardrails", keywords: ["yolo", "fast", "guardrails", "move fast"] },
@@ -25,6 +155,9 @@ export const TEMPLATE_MATCH_METADATA = [
     { name: "migration-safety", keywords: ["migration", "migrate", "upgrade", "database migration", "dependency upgrade", "迁移"] },
     { name: "incident-response", keywords: ["incident", "production issue", "hotfix", "outage", "postmortem", "事故"] },
     { name: "performance-audit", keywords: ["performance", "profiling", "benchmark", "optimize", "latency", "性能"] },
+    { name: "ui-visual-regression-qa", keywords: ["ui qa", "visual regression", "screenshot qa", "responsive", "overflow", "视觉回归", "界面验收"] },
+    { name: "release-evidence-gate", keywords: ["release evidence", "deploy gate", "vercel verification", "deployed url", "release gate", "发布证据", "部署门禁"] },
+    { name: "multi-agent-handoff-coordination", keywords: ["multi-agent", "handoff", "parallel lanes", "worktree coordination", "lane isolation", "多智能体", "交接"] },
 ];
 const TEMPLATE_MATCH_METADATA_BY_NAME = new Map(TEMPLATE_MATCH_METADATA.map((entry) => [entry.name, entry]));
 export function getTemplateMatchMetadata(name) {

package/dist/templates/mobile-dev.dna.yaml

@@ -4,6 +4,25 @@
 version: "0.1.0"
 id: template_mobile_dev
 name: Mobile Development Standards
+purpose: Provide a mobile development baseline for quality, performance, security, and platform-specific review.
+maturity: draft
+fit:
+  - Flutter, React Native, iOS, or Android projects needing local mobile guardrails.
+  - Mobile tasks where performance and security constraints should be explicit.
+not_for:
+  - Replacing app-specific behavior locks, device QA, or release smoke evidence.
+  - Treating generic mobile standards as a complete workflow asset.
+inputs:
+  - mobile feature or module scope
+  - platform and device constraints
+  - quality, performance, and security requirements
+outputs:
+  - mobile development guardrails
+  - performance and security review notes
+  - platform-specific quality checklist
+lineage:
+  source: built-in mobile development standards template
+  reference: src/templates/mobile-dev.dna.yaml
 type: project
 namespace: mob
 

package/dist/templates/multi-agent-handoff-coordination.dna.yaml

@@ -0,0 +1,156 @@
+version: "0.1.0"
+id: template_multi_agent_handoff_coordination
+name: Multi-Agent Handoff Coordination
+purpose: Coordinate parallel agent lanes through isolated scopes, machine-checkable handoffs, and an explicit integration review.
+maturity: reviewed
+fit:
+  - Large tasks that need multiple agents working on disjoint write scopes.
+  - Integration work where each lane must report evidence before merge or adoption.
+not_for:
+  - Unbounded parallel work without ownership or conflict escalation.
+  - Letting worker lanes rewrite the global plan or hide shared-file conflicts.
+inputs:
+  - feature, bug, or productization scope
+  - lane ownership and write boundaries
+  - per-lane handoff artifacts
+outputs:
+  - coordination artifact directory
+  - lane handoff evidence
+  - final integration plan
+lineage:
+  source: Codex/OMX multi-agent handoff pattern
+  reference: docs/archive/2026H1/references/branch-consolidation-handoff-20260709.md
+type: project
+namespace: mah
+
+cascade:
+  inherits: ["species:default"]
+  priority: 100
+
+variables:
+  task_scope:
+    description: "Feature, bug, or productization scope to split"
+    default: "$ARGUMENTS"
+  handoff_dir:
+    description: "Coordination and handoff artifact directory"
+    default: ".dna/handoffs/$ARGUMENTS"
+  integration_plan_path:
+    description: "Final integration plan artifact"
+    default: ".dna/handoffs/$ARGUMENTS.integration.json"
+
+evidence:
+  - label: Parallel productization boundary
+    kind: doc
+    path: docs/archive/2026H1/references/three-products-boundary.md
+    description: Route-lock reference for keeping lanes isolated and preserving product boundaries.
+
+genes:
+  lane_isolation:
+    description: Parallel agents must own disjoint write scopes and report conflicts upward
+    codons:
+      - type: attract
+        target: explicit_write_scope_per_lane
+      - type: attract
+        target: independent_commits_per_lane
+      - type: repel
+        target: shared_file_freelancing
+      - type: threshold
+        condition: "lane_write_scopes_overlap == false"
+        action: block
+
+  handoff_evidence:
+    description: Every lane must produce a machine-checkable handoff before integration
+    codons:
+      - type: attract
+        target: changed_files_list
+      - type: attract
+        target: verification_command_output
+      - type: attract
+        target: boundary_tests
+      - type: threshold
+        condition: "handoff_artifact_present == true"
+        action: block
+
+  integration_review:
+    description: Integration must review boundaries before merging lane results
+    codons:
+      - type: attract
+        target: route_lock_recheck
+      - type: repel
+        target: mixed_diff_commit
+      - type: sense
+        signal: boundary_drift_detected
+        response: block_integration
+
+contexts: {}
+
+roles:
+  coordinator:
+    description: Splits work into independent lanes and owns integration review.
+    tool_permissions:
+      allow: [Read, Write, Grep, Glob, Bash]
+      deny: [Edit, NotebookEdit]
+    scope:
+      read: ["**/*", "docs/**", ".omx/plans/**"]
+      write: [".dna/handoffs/**"]
+    instructions:
+      - Read the route-lock docs before assigning lanes.
+      - Define each lane with owner, write scope, acceptance tests, verification commands, and boundary risks.
+      - Reject lanes with overlapping write scopes unless sequenced explicitly.
+      - Write coordination artifacts under {{handoff_dir}}.
+
+  lane_executor:
+    description: Executes one assigned lane inside its write scope.
+    tool_permissions:
+      allow: [Read, Edit, Write, Grep, Glob, Bash]
+    scope:
+      read: ["**/*"]
+      write: ["src/**", "apps/**", "test/**", "docs/**", ".dna/handoffs/**"]
+    instructions:
+      - Execute only the assigned lane and stay within the declared write scope.
+      - Do not revert unrelated edits or incidental local state.
+      - Run lane verification and write a handoff with changed files, tests, boundary checks, and residual risks.
+      - Escalate scope conflicts to the coordinator instead of editing shared files silently.
+
+  integration_reviewer:
+    description: Reviews lane handoffs, boundary compliance, and final integration order.
+    tool_permissions:
+      allow: [Read, Write, Grep, Glob, Bash]
+      deny: [Edit, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/handoffs/**"]
+      write: [".dna/handoffs/**"]
+    instructions:
+      - Read all lane handoffs before integration.
+      - Verify each lane has separate commits or a clean staged diff.
+      - Check local runtime truth, marketplace, online projection, hidden transport, and external-reference boundaries.
+      - Write {{integration_plan_path}} with merge order, blockers, verification commands, and final audit checklist.
+
+workflows:
+  coordinate-handoffs:
+    name: Multi-Agent Handoff Coordination
+    description: Split independent lanes, execute scoped work, and review handoffs before integration.
+    steps:
+      - id: split-lanes
+        role: coordinator
+        description: Define independent lanes and handoff requirements.
+        prompt: |
+          Split {{task_scope}} into independent lanes.
+          For each lane, define owner, write scope, acceptance tests, verification commands, and product-boundary risks.
+          Write lane specs under {{handoff_dir}}.
+      - id: execute-lane
+        role: lane_executor
+        depends_on: [split-lanes]
+        description: Execute an assigned lane and write its handoff.
+        prompt: |
+          Execute only your assigned lane for {{task_scope}}.
+          Stay within the declared write scope.
+          Write a handoff under {{handoff_dir}} with changed files, tests, boundary checks, and residual risks.
+      - id: review-integration
+        role: integration_reviewer
+        depends_on: [execute-lane]
+        description: Review handoffs and write the final integration plan.
+        prompt: |
+          Review all handoffs under {{handoff_dir}}.
+          Verify lane isolation, boundary compliance, and required tests.
+          Write {{integration_plan_path}} with integration order and final audit checklist.

package/dist/templates/multi-perspective-review.dna.yaml

@@ -6,6 +6,25 @@
 version: "0.1.0"
 id: template_multi_perspective_review
 name: Multi-Perspective Review
+purpose: Review high-risk decisions from opposing perspectives and produce an explicit arbitration verdict.
+maturity: reviewed
+fit:
+  - Architecture, product, or implementation choices with meaningful tradeoffs.
+  - Changes that need advocate, critic, and arbiter separation before adoption.
+not_for:
+  - Rubber-stamp reviews or vague opinions without actionable evidence.
+  - Replacing owner approval for destructive or business decisions.
+inputs:
+  - proposed change or decision
+  - supporting evidence and alternatives
+  - risk and constraint context
+outputs:
+  - advocate review
+  - critic review
+  - arbiter decision and follow-up actions
+lineage:
+  source: multi-role debate and review workflow pattern
+  reference: src/templates/multi-perspective-review.dna.yaml
 type: project
 namespace: mpr
 

package/dist/templates/persistent-executor.dna.yaml

@@ -1,6 +1,25 @@
 version: "0.1.0"
 id: template_persistent_executor
 name: Persistent Executor (PRD-Driven)
+purpose: Execute PRD-backed stories to completion with acceptance criteria, verification, and explicit remaining-work reporting.
+maturity: reviewed
+fit:
+  - Story or PRD-driven implementation where completion must map to acceptance criteria.
+  - Work that benefits from separate executor and verifier roles.
+not_for:
+  - Open-ended exploration without a task spec.
+  - Claiming partial work as done without explicit remaining scope.
+inputs:
+  - PRD or story specification
+  - acceptance criteria
+  - verification commands
+outputs:
+  - implemented story diff
+  - verifier evidence
+  - completion or remaining-work report
+lineage:
+  source: PRD-driven persistent execution workflow
+  reference: src/templates/persistent-executor.dna.yaml
 type: project
 namespace: pe
 

package/dist/templates/qa-loop.dna.yaml

@@ -1,6 +1,24 @@
 version: "0.1.0"
 id: template_qa_loop
 name: QA Loop (Test-Fix Cycle)
+purpose: Drive a bounded test-fix loop with separate tester and fixer roles until evidence converges or blockers are explicit.
+maturity: reviewed
+fit:
+  - Test failures that need diagnosis, prioritized fixes, and repeated verification.
+  - Separating evidence collection from code modification.
+not_for:
+  - Infinite retry loops without progress tracking.
+  - Self-approval by the same role that made the fix.
+inputs:
+  - failing test output
+  - changed code scope
+  - previous round evidence
+outputs:
+  - categorized failures
+  - scoped fixes
+  - convergence or blocker report
+lineage:
+  source: test-fix cycle template
 type: project
 namespace: ql
 

package/dist/templates/release-evidence-gate.dna.yaml

@@ -0,0 +1,131 @@
+version: "0.1.0"
+id: template_release_evidence_gate
+name: Release Evidence Gate
+purpose: Require release deploy-plan and deployed-route evidence before public web or release completion claims.
+maturity: reviewed
+fit:
+  - Public web, release, or deploy changes that need deployed URL verification.
+  - Teams separating local build/test readiness from production release evidence.
+not_for:
+  - Treating local preview, screenshots, or successful deploy commands as release completion.
+  - Moving workflow execution or runtime authority into Online.
+inputs:
+  - changed files or release scope
+  - release deploy-plan JSON
+  - deployed URL and checked routes
+outputs:
+  - read-only release plan
+  - release verification evidence
+  - release boundary decision
+lineage:
+  source: IntentDNA release runbook and Online V2 release evidence
+  reference: docs/archive/2026H1/workflows/release-runbook.md
+type: project
+namespace: reg
+
+cascade:
+  inherits: ["species:default"]
+  priority: 100
+
+variables:
+  changed_files:
+    description: "Changed files or release scope"
+    default: "$ARGUMENTS"
+  release_plan_path:
+    description: "Read-only release deploy-plan JSON"
+    default: ".dna/release/$ARGUMENTS.deploy-plan.json"
+  release_evidence_path:
+    description: "Release verification evidence artifact"
+    default: ".dna/release/$ARGUMENTS.evidence.json"
+
+evidence:
+  - label: Three-product deployment boundary
+    kind: doc
+    path: docs/archive/2026H1/references/three-products-boundary.md
+    description: Boundary that deployment is separate from runtime sync and online projection must not become policy truth.
+
+genes:
+  deploy_plan_before_deploy:
+    description: Public web release work must run deploy-plan before any deploy claim
+    codons:
+      - type: attract
+        target: run_release_deploy_plan
+      - type: repel
+        target: deploy_without_gate
+      - type: threshold
+        condition: "deploy_plan_status_known == true"
+        action: block
+
+  deployed_url_verification:
+    description: A web deploy is incomplete until the deployed URL is verified
+    codons:
+      - type: attract
+        target: verify_public_routes_after_deploy
+      - type: attract
+        target: record_deployment_url
+      - type: repel
+        target: build_as_deploy_evidence
+      - type: threshold
+        condition: "required_deployed_routes_verified == true"
+        action: block
+
+  release_boundary:
+    description: Release verification does not execute workflows or runtime policy
+    codons:
+      - type: threshold
+        condition: "release_gate_executed_runtime_sync == false"
+        action: block
+      - type: repel
+        target: online_dashboard_as_policy_truth
+
+contexts: {}
+
+roles:
+  release_planner:
+    description: Runs the read-only deploy-plan gate and decides required release evidence.
+    tool_permissions:
+      allow: [Read, Write, Grep, Glob, Bash]
+      deny: [Edit, NotebookEdit]
+    scope:
+      read: ["**/*"]
+      write: [".dna/release/**"]
+    instructions:
+      - Run dna release deploy-plan for {{changed_files}} and save JSON to {{release_plan_path}}.
+      - If deployment_required, list exact local build/test/deploy/readiness/URL verification commands.
+      - If not required, record why no Vercel deployment is needed.
+      - Do not deploy, sync runtime artifacts, or change dashboard state in this role.
+
+  release_verifier:
+    description: Verifies release evidence after local commands and any required deployed URL checks.
+    tool_permissions:
+      allow: [Read, Write, Grep, Glob, Bash]
+      deny: [Edit, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/release/**"]
+      write: [".dna/release/**"]
+    instructions:
+      - Read {{release_plan_path}} before running verification.
+      - Run only commands required by the plan and capture outputs.
+      - If deployment is required, record deployment URL plus checked routes.
+      - Write {{release_evidence_path}} with status, commands, URLs, blockers, and boundary notes.
+
+workflows:
+  release-gate:
+    name: Release Evidence Gate
+    description: Decide whether deploy is required, then verify release evidence without moving runtime authority.
+    steps:
+      - id: plan-release
+        role: release_planner
+        description: Run read-only deploy-plan and save the release plan.
+        prompt: |
+          Run dna release deploy-plan for {{changed_files}} and save JSON to {{release_plan_path}}.
+          Do not deploy or sync runtime artifacts in this step.
+      - id: verify-release
+        role: release_verifier
+        depends_on: [plan-release]
+        description: Execute the required verification path and write release evidence.
+        prompt: |
+          Read {{release_plan_path}}.
+          Run the local commands required by the plan.
+          If deployment_required, deploy only after local verification and then verify the deployed URL routes listed by the plan.
+          Write {{release_evidence_path}} with evidence, blockers, and next actions.

package/dist/templates/requirements-gate.dna.yaml

@@ -5,6 +5,25 @@
 version: "0.1.0"
 id: template_requirements_gate
 name: Requirements Clarity Gate
+purpose: Block implementation until requirements are clear enough and the weakest ambiguity is addressed one question at a time.
+maturity: reviewed
+fit:
+  - Tasks with unclear intent, boundaries, success criteria, or constraints.
+  - Planning lanes where implementation should wait for a structured requirement packet.
+not_for:
+  - Already scoped implementation with stable acceptance criteria.
+  - Endless interviewing after the blocking ambiguity is resolved.
+inputs:
+  - raw user request or task brief
+  - current known constraints
+  - clarity threshold
+outputs:
+  - structured requirement assessment
+  - next clarifying question
+  - implementation readiness verdict
+lineage:
+  source: requirements-first interview workflow
+  reference: src/templates/requirements-gate.dna.yaml
 type: project
 namespace: rg
 

package/dist/templates/research-orchestration.dna.yaml

@@ -4,6 +4,25 @@
 version: "0.1.0"
 id: template_research_orchestration
 name: Research Orchestration (Parallel Hypotheses)
+purpose: Run hypothesis-driven research with independent evidence gathering, cross-verification, and structured synthesis.
+maturity: reviewed
+fit:
+  - Research tasks that need multiple hypotheses, subquestions, and evidence grading.
+  - Technical or product investigations where facts and inferences must be separated.
+not_for:
+  - Single-source summaries without verification.
+  - Implementation work that should be governed by a delivery workflow.
+inputs:
+  - research question
+  - initial hypotheses
+  - source and evidence constraints
+outputs:
+  - subquestion findings
+  - evidence quality grades
+  - synthesized conclusion with residual uncertainty
+lineage:
+  source: parallel hypothesis research workflow
+  reference: src/templates/research-orchestration.dna.yaml
 type: project
 namespace: ro
 

package/dist/templates/root-cause-analysis.dna.yaml

@@ -1,6 +1,25 @@
 version: "0.1.0"
 id: template_root_cause_analysis
 name: Root Cause Analysis (Competing Hypotheses)
+purpose: Diagnose failures by generating competing hypotheses, gathering evidence, and proving a minimal root cause before fixing.
+maturity: reviewed
+fit:
+  - Bugs, regressions, outages, or test failures with uncertain cause.
+  - Investigations where premature fixes would hide the underlying failure mode.
+not_for:
+  - Cosmetic changes or known one-line fixes with clear cause.
+  - Shipping a fix before reproduction and evidence support the root cause.
+inputs:
+  - symptom or failure report
+  - logs, tests, traces, or reproduction steps
+  - suspected change scope
+outputs:
+  - competing hypothesis list
+  - evidence ranking
+  - minimal reproduction and root-cause verdict
+lineage:
+  source: systematic debugging and competing-hypothesis workflow
+  reference: src/templates/root-cause-analysis.dna.yaml
 type: project
 namespace: rca