intentdna 1.7.5 → 1.8.0

package/dist/templates/workflow-completion-audit.dna.yaml

@@ -0,0 +1,254 @@
+# workflow-completion-audit: completion claim audit before PASS, rollout, evolution, or sync
+# Source: extracted from Flutter rewrite dogfood module completion reviews
+# Purpose: make "prove completion before claiming completion" a reusable workflow asset
+
+version: "0.1.0"
+id: template_workflow_completion_audit
+name: Workflow Completion Audit
+purpose: Prove PASS, CONTINUE, REQUEST_CHANGES, or BLOCKED from current canonical evidence before completion is claimed.
+maturity: reviewed
+fit:
+  - Workflow or module completion claims that need diagnosis, verification, red classification, and skipped-test comparison.
+  - Manager review before adoption, rollout, evolution, or runtime sync.
+not_for:
+  - Counting stale summaries, partial focused runs, or chat memory as completion proof.
+  - Hiding remaining UNIMPLEMENTED, BUG, INFRA, or placeholder-test work.
+inputs:
+  - diagnosis or baseline artifact
+  - progress artifact
+  - current verification summary
+  - red or skipped classification artifact
+outputs:
+  - completion audit findings
+  - reviewed completion verdict
+  - durable audit artifact and manager route
+lineage:
+  source: Flutter rewrite dogfood module completion reviews
+  reference: /Users/samuel/lawark/lwk_flutter_v2-rewrite/.dna/fix-progress
+type: project
+namespace: wca
+
+cascade:
+  inherits: ["species:default"]
+  priority: 100
+
+variables:
+  diagnosis_path:
+    description: "Approved diagnosis or baseline artifact path"
+    default: ".dna/specs/diagnosis-$ARGUMENTS.md"
+  progress_path:
+    description: "Module or workflow progress artifact path"
+    default: ".dna/fix-progress/$ARGUMENTS.json"
+  current_summary_path:
+    description: "Current parsed test or verification summary path"
+    default: ".dna/fix-progress/$ARGUMENTS-current-test-summary.json"
+  red_classification_path:
+    description: "Current red/skipped classification artifact path"
+    default: ".dna/fix-progress/$ARGUMENTS-red-classification.json"
+  audit_path:
+    description: "Completion audit artifact path"
+    default: ".dna/completion-audit/$ARGUMENTS.audit.json"
+
+evidence:
+  - label: Flutter rewrite module completion reviews
+    kind: reference
+    path: /Users/samuel/lawark/lwk_flutter_v2-rewrite/.dna/fix-progress
+    description: Dogfood module progress markdown, JSON, parsed summaries, red classifications, machine logs, and skipped-test comparisons used before PASS decisions.
+  - label: Flutter rewrite diagnosis baselines
+    kind: reference
+    path: /Users/samuel/lawark/lwk_flutter_v2-rewrite/.dna/specs
+    description: Diagnosis baselines that define UNIMPLEMENTED, TEST_BUG, INFRA, REMOVED, and other classifications for completion checks.
+
+genes:
+  completion_requires_canonical_evidence:
+    description: PASS, rollout, evolution, or sync requires current canonical evidence, not chat memory or stale summaries
+    codons:
+      - type: attract
+        target: diagnosis_baseline_read
+      - type: attract
+        target: current_verification_summary_read
+      - type: attract
+        target: red_classification_read
+      - type: repel
+        target: completion_from_chat_memory
+      - type: threshold
+        condition: "canonical_completion_evidence_read == true"
+        action: block
+
+  skipped_unimplemented_blocks_pass:
+    description: Diagnosis-backed UNIMPLEMENTED skipped tests remain active work and block PASS
+    codons:
+      - type: attract
+        target: skipped_test_comparison
+      - type: repel
+        target: skipped_unimplemented_hidden_as_green
+      - type: threshold
+        condition: "remaining_unimplemented_skipped_count == 0"
+        action: block
+
+  placeholder_and_regression_guard:
+    description: Placeholder assertions, new red tests, and unsupported partial evidence block completion claims
+    codons:
+      - type: attract
+        target: placeholder_assertion_scan
+      - type: attract
+        target: new_red_count_check
+      - type: attract
+        target: full_or_accepted_scope_evidence
+      - type: repel
+        target: partial_focused_run_as_module_pass
+      - type: sense
+        signal: weak_completion_evidence
+        response: request_completion_audit
+
+contexts: {}
+
+roles:
+  completion_auditor:
+    description: Reads diagnosis, progress, current verification, red classification, and skipped-test evidence before any completion claim.
+    tool_permissions:
+      allow: [Read, Grep, Glob]
+      deny: [Edit, Write, Bash, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/**", "docs/**"]
+      write: []
+    instructions:
+      - Read {{diagnosis_path}}, {{progress_path}}, {{current_summary_path}}, and {{red_classification_path}} before judging completion.
+      - Compare current skipped tests against diagnosis-backed UNIMPLEMENTED items.
+      - Treat remaining UNIMPLEMENTED skipped tests, actionable BUG/UNIMPLEMENTED red tests, new red tests, missing summaries, or placeholder assertions as not complete.
+      - Distinguish full-suite evidence, accepted focused evidence, and weak partial evidence.
+      - Keep Obsidian/wiki as internal memory only; do not use it as product evidence.
+
+  audit_reviewer:
+    description: Reviews the completion audit for weak evidence, hidden remaining work, and unsupported PASS claims.
+    tool_permissions:
+      allow: [Read, Grep, Glob]
+      deny: [Edit, Write, Bash, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/**", "docs/**"]
+      write: []
+    instructions:
+      - Reject PASS if diagnosis-backed UNIMPLEMENTED skipped tests remain.
+      - Reject PASS if current summary, red classification, or progress evidence is missing, stale, contradicted, or partial without an explicit accepted scope.
+      - Reject PASS if placeholder behavior-lock assertions or test-only tautologies are still being counted as proof.
+      - Return PASS_ALLOWED, CONTINUE, REQUEST_CHANGES, or BLOCKED with concise reasons and evidence paths.
+
+  audit_recorder:
+    description: Writes durable completion audit evidence without mutating app code, workflow assets, org profiles, or runtime artifacts.
+    tool_permissions:
+      allow: [Read, Write, Grep, Glob]
+      deny: [Edit, Bash, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/**", "docs/**"]
+      write: [".dna/completion-audit/**"]
+    instructions:
+      - Write {{audit_path}} as JSON with status, evidence_paths, diagnosis_counts, current_counts, skipped_comparison, new_red_count, remaining_count, remaining_unimplemented_skipped_count, placeholder_risk, reviewer_verdict, next_commands, and updated_at.
+      - State whether PASS, manager review, adoption, rollout, evolution preview, marker mutation, or runtime sync is allowed.
+      - Do not edit code, tests, templates, organization profiles, evolution markers, dashboard state, or runtime sync artifacts.
+
+  manager_reviewer:
+    description: Produces a manager-readable completion route from the audit artifact.
+    tool_permissions:
+      allow: [Read, Grep, Glob]
+      deny: [Edit, Write, Bash, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/**", "docs/**"]
+      write: []
+    instructions:
+      - Read {{audit_path}} and summarize whether completion is PASS_ALLOWED, CONTINUE, REQUEST_CHANGES, or BLOCKED.
+      - Name the evidence paths and the exact reason completion is allowed or blocked.
+      - If remaining work exists, route back to fix/review or blocked-scope triage before adoption, rollout, evolution mutation, or sync.
+      - End with an explicit mutation boundary.
+
+workflows:
+  completion-audit:
+    name: Completion Audit
+    description: Audit completion claims against diagnosis baseline, current verification, red classifications, skipped-test comparison, and progress evidence.
+    steps:
+      - id: audit-completion
+        role: completion_auditor
+        description: Check whether completion is actually proven by current canonical evidence.
+        prompt: |
+          Audit completion for $ARGUMENTS.
+          Read {{diagnosis_path}}, {{progress_path}}, {{current_summary_path}}, and {{red_classification_path}}.
+          Compare skipped tests against diagnosis-backed UNIMPLEMENTED items.
+          Check for new red tests, remaining actionable failures, placeholder assertions, and weak partial evidence.
+        handoff:
+          produces:
+            - type: summary
+              name: completion_audit_findings
+              description: Evidence-backed completion findings, remaining work, blockers, and allowed next actions.
+      - id: review-audit
+        role: audit_reviewer
+        depends_on: [audit-completion]
+        description: Review the completion audit for unsupported PASS claims and hidden remaining work.
+        prompt: |
+          Review completion audit findings for $ARGUMENTS.
+          Reject PASS if canonical evidence is missing, stale, contradicted, partial, or hides UNIMPLEMENTED skipped tests.
+          Return PASS_ALLOWED, CONTINUE, REQUEST_CHANGES, or BLOCKED.
+        handoff:
+          consumes:
+            - type: summary
+              name: completion_audit_findings
+              from: audit-completion
+              description: Completion audit findings.
+          produces:
+            - type: summary
+              name: completion_audit_verdict
+              description: Reviewed completion verdict and required next action.
+      - id: record-audit
+        role: audit_recorder
+        depends_on: [review-audit]
+        description: Write durable completion audit evidence.
+        prompt: |
+          Write {{audit_path}} for $ARGUMENTS.
+          Include status, evidence paths, counts, skipped comparison, new red count, remaining counts, placeholder risk, reviewer verdict, next commands, and updated_at.
+          State whether PASS, adoption, rollout, evolution preview, marker mutation, or runtime sync is allowed.
+        checkpoints:
+          - assert: completion_audit_artifact_written
+            command: "test -s \"{{audit_path}}\""
+            message: "Completion audit artifact must exist before manager route."
+            action: block
+        handoff:
+          consumes:
+            - type: summary
+              name: completion_audit_verdict
+              from: review-audit
+              description: Reviewed completion verdict.
+          produces:
+            - type: file
+              path: "{{audit_path}}"
+              description: Durable completion audit JSON.
+      - id: manager-route
+        role: manager_reviewer
+        depends_on: [record-audit]
+        description: Produce manager-readable completion route from audit evidence.
+        prompt: |
+          Read {{audit_path}} for $ARGUMENTS.
+          State PASS_ALLOWED, CONTINUE, REQUEST_CHANGES, or BLOCKED with evidence and next command.
+          Do not approve adoption, rollout, evolution mutation, or sync while completion evidence is weak or remaining work is hidden.
+        handoff:
+          consumes:
+            - type: file
+              path: "{{audit_path}}"
+              from: record-audit
+              description: Completion audit artifact.
+          produces:
+            - type: summary
+              name: manager_completion_route
+              description: Manager-readable route to continue, approve, request changes, or block.
+
+controllers:
+  completion-audit:
+    name: Completion Audit
+    description: "Audit completion evidence before PASS, manager review, adoption, rollout, evolution mutation, or sync."
+    kind: sequential
+    workflow: completion-audit
+    max_rounds: 1
+    progress_artifact_path: ".dna/completion-audit/$ARGUMENTS.controller.json"
+    roles:
+      completion_auditor: completion_auditor
+      audit_reviewer: audit_reviewer
+      audit_recorder: audit_recorder
+      manager_reviewer: manager_reviewer
+    stop_format: configured_stop_report

package/dist/templates/workflow-cross-boundary-resource-approval.dna.yaml

@@ -0,0 +1,249 @@
+# workflow-cross-boundary-resource-approval: review shared resource changes before implementation
+# Source: extracted from Flutter rewrite Pay i18n/shared resource blocker
+# Purpose: route cross-module, localization, shared resource, or outside-diagnosis changes through explicit approval before edits
+
+version: "0.1.0"
+id: template_workflow_cross_boundary_resource_approval
+name: Workflow Cross Boundary Resource Approval
+purpose: Route cross-module, localization, shared resource, config, or policy changes through explicit owner approval before implementation.
+maturity: reviewed
+fit:
+  - Work that crosses the approved module, package, localization, or resource boundary.
+  - Shared resource changes requiring owner or manager approval.
+not_for:
+  - Local changes already inside the approved task boundary.
+  - Silent cross-boundary edits hidden inside implementation.
+inputs:
+  - cross-boundary change request
+  - source evidence or progress artifact
+  - owner approval verdict
+outputs:
+  - approval request artifact
+  - manager approval verdict
+  - authorized implementation route
+lineage:
+  source: Flutter rewrite Pay i18n blocker
+  reference: /Users/samuel/lawark/lwk_flutter_v2-rewrite/.dna/fix-progress/Pay.json
+type: project
+namespace: wcbr
+
+cascade:
+  inherits: ["species:default"]
+  priority: 100
+
+variables:
+  request_path:
+    description: "Cross-boundary change request artifact"
+    default: ".dna/cross-boundary/$ARGUMENTS.request.json"
+  approval_path:
+    description: "Manager approval verdict artifact"
+    default: ".dna/cross-boundary/$ARGUMENTS.approval.json"
+  evidence_path:
+    description: "Source evidence or progress artifact"
+    default: ".dna/fix-progress/$ARGUMENTS.json"
+  resource_scope:
+    description: "Shared resource, localization, module, package, or policy boundary"
+    default: "$ARGUMENTS"
+
+evidence:
+  - label: Flutter rewrite Pay cross-boundary i18n blocker
+    kind: reference
+    path: /Users/samuel/lawark/lwk_flutter_v2-rewrite/.dna/fix-progress/Pay.json
+    description: Pay dogfood evidence records a needs_human, outside_diagnosis blocker because preserving payment_tips_prefix localization requires shared lwk_i18n work outside feature_pay.
+  - label: Flutter rewrite dogfood progress
+    kind: reference
+    path: /Users/samuel/lawark/lwk_flutter_v2-rewrite/.dna/fix-progress
+    description: Module-level dogfood progress where blocked/outside-scope work must be separated from implementation before manager review, rollout, or sync.
+
+genes:
+  boundary_authority_required:
+    description: Cross-boundary edits require explicit owner and approval before implementation
+    codons:
+      - type: attract
+        target: owner_named_for_shared_resource
+      - type: attract
+        target: approval_before_edit
+      - type: repel
+        target: silent_cross_boundary_change
+      - type: threshold
+        condition: "approval_verdict_recorded == true"
+        action: block
+
+  localization_resource_preserved:
+    description: Localization and shared resource changes must preserve source behavior and ownership
+    codons:
+      - type: attract
+        target: localization_key_mapping
+      - type: attract
+        target: source_behavior_reference
+      - type: repel
+        target: generated_placeholder_translation
+      - type: sense
+        signal: missing_localization_resource
+        response: request_resource_approval
+
+  outside_scope_is_not_hidden:
+    description: Work outside diagnosis or module scope must be routed, not hidden as blocked completion
+    codons:
+      - type: attract
+        target: outside_scope_reason
+      - type: attract
+        target: next_authorized_command
+      - type: repel
+        target: blocked_without_route
+      - type: threshold
+        condition: "outside_scope_route_visible == true"
+        action: block
+
+contexts: {}
+
+roles:
+  boundary_analyst:
+    description: Identifies the shared resource boundary, affected owner, and source behavior that would be changed.
+    tool_permissions:
+      allow: [Read, Grep, Glob]
+      deny: [Edit, Write, Bash, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/**", "docs/**"]
+      write: []
+    instructions:
+      - Read {{evidence_path}} and identify why {{resource_scope}} crosses the current workflow or module boundary.
+      - Name the shared resource owner, affected modules, localization keys, config files, generated artifacts, or policy layer.
+      - Separate behavior preservation requirements from optional improvements.
+      - Do not edit app code, localization files, templates, org profiles, sync artifacts, or markers.
+
+  approval_planner:
+    description: Writes a precise request for manager or resource-owner approval.
+    tool_permissions:
+      allow: [Read, Write, Grep, Glob]
+      deny: [Edit, Bash, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/**", "docs/**"]
+      write: [".dna/cross-boundary/**"]
+    instructions:
+      - Write {{request_path}} with resource_scope, owner, requested_files, behavior_to_preserve, risk, alternatives, and next_commands.
+      - Include why the change is outside the current diagnosis or workflow scope.
+      - Include the smallest safe follow-up command after approval.
+      - Do not approve the request yourself.
+
+  manager_reviewer:
+    description: Reviews the cross-boundary request and records APPROVE, REQUEST_CHANGES, or BLOCKED.
+    tool_permissions:
+      allow: [Read, Write, Grep, Glob]
+      deny: [Edit, Bash, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/**", "docs/**"]
+      write: [".dna/cross-boundary/**"]
+    instructions:
+      - Read {{request_path}} before deciding.
+      - Reject vague shared-resource changes without owner, file scope, behavior reference, or rollback path.
+      - If approved, state exactly which files or resources may change and what verification is required.
+      - Write {{approval_path}} with verdict, approved_scope, blocked_scope, verification_required, next_commands, and updated_at.
+
+  implementation_router:
+    description: Routes approved work back to the correct workflow without performing the implementation.
+    tool_permissions:
+      allow: [Read, Grep, Glob]
+      deny: [Edit, Write, Bash, NotebookEdit]
+    scope:
+      read: ["**/*", ".dna/**", "docs/**"]
+      write: []
+    instructions:
+      - Read {{approval_path}} and decide whether implementation may proceed.
+      - If APPROVE, route back to the owning fix/rewrite workflow with the approved boundary and required verification.
+      - If REQUEST_CHANGES or BLOCKED, keep rollout, sync, and completion claims blocked.
+      - End with a clear mutation boundary.
+
+workflows:
+  cross-boundary-resource-approval:
+    name: Cross Boundary Resource Approval
+    description: Review shared resource, localization, config, policy, or cross-module changes before implementation.
+    steps:
+      - id: analyze-boundary
+        role: boundary_analyst
+        description: Identify resource ownership and why the change crosses scope.
+        prompt: |
+          Analyze the cross-boundary resource request for $ARGUMENTS.
+          Read {{evidence_path}} and identify owner, affected resources, source behavior, risk, and why the work is outside current scope.
+        handoff:
+          produces:
+            - type: summary
+              name: boundary_analysis
+              description: Resource owner, affected files/resources, behavior to preserve, and boundary reason.
+      - id: write-approval-request
+        role: approval_planner
+        depends_on: [analyze-boundary]
+        description: Write the approval request artifact.
+        prompt: |
+          Write {{request_path}} for $ARGUMENTS.
+          Include resource_scope, owner, requested_files, behavior_to_preserve, risk, alternatives, outside_scope_reason, and next_commands.
+        checkpoints:
+          - assert: approval_request_written
+            command: "test -s \"{{request_path}}\""
+            message: "Cross-boundary approval request must exist before manager review."
+            action: block
+        handoff:
+          consumes:
+            - type: summary
+              name: boundary_analysis
+              from: analyze-boundary
+              description: Boundary analysis.
+          produces:
+            - type: file
+              path: "{{request_path}}"
+              description: Cross-boundary approval request.
+      - id: manager-review
+        role: manager_reviewer
+        depends_on: [write-approval-request]
+        description: Review and record approval or blocking verdict.
+        prompt: |
+          Review {{request_path}} for $ARGUMENTS.
+          Write {{approval_path}} with APPROVE, REQUEST_CHANGES, or BLOCKED; approved scope; blocked scope; verification required; next commands; and updated_at.
+        checkpoints:
+          - assert: approval_verdict_written
+            command: "test -s \"{{approval_path}}\""
+            message: "Manager approval verdict must exist before implementation routing."
+            action: block
+        handoff:
+          consumes:
+            - type: file
+              path: "{{request_path}}"
+              from: write-approval-request
+              description: Cross-boundary approval request.
+          produces:
+            - type: file
+              path: "{{approval_path}}"
+              description: Approval verdict and approved scope.
+      - id: route-implementation
+        role: implementation_router
+        depends_on: [manager-review]
+        description: Route the approved or blocked work back to the owning workflow.
+        prompt: |
+          Read {{approval_path}} for $ARGUMENTS.
+          If APPROVE, route implementation back to the owning workflow with approved scope and verification requirements.
+          If REQUEST_CHANGES or BLOCKED, keep rollout, sync, and completion claims blocked.
+        handoff:
+          consumes:
+            - type: file
+              path: "{{approval_path}}"
+              from: manager-review
+              description: Manager approval verdict.
+          produces:
+            - type: summary
+              name: implementation_route
+              description: Approved implementation route or blocked next action.
+
+controllers:
+  cross-boundary-resource-approval:
+    name: Cross Boundary Resource Approval
+    description: "Analyze, request, review, and route cross-boundary shared resource changes before implementation."
+    kind: sequential
+    workflow: cross-boundary-resource-approval
+    max_rounds: 1
+    progress_artifact_path: ".dna/cross-boundary/$ARGUMENTS.controller.json"
+    roles:
+      boundary_analyst: boundary_analyst
+      approval_planner: approval_planner
+      manager_reviewer: manager_reviewer
+      implementation_router: implementation_router
+    stop_format: configured_stop_report