universal-dev-standards 5.6.0 → 5.7.1

package/bundled/ai/standards/agent-communication-protocol.ai.yaml

@@ -1,6 +1,6 @@
 # Agent Communication Protocol - DEPRECATED STUB
-# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
-# Canonical location: dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/agent-communication-protocol.md (remains in UDS)
@@ -14,20 +14,19 @@ standard:
     deprecated: true
     deprecated_since: "5.4.0"
     removal_version: "6.0.0"
-    canonical_owner: devap
-    canonical_path: "dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/agent-communication-protocol.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (orchestration layer).
-      Install DevAP and load standards/orchestration/agent-communication-protocol.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any agent communication operation
       instruction: >
-        This standard (agent-communication-protocol.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml
 
         The human-readable standard remains at:
           universal-dev-standards/core/agent-communication-protocol.md
@@ -36,7 +35,7 @@ standard:
     - id: ACP-001
       trigger: "訊息缺少必要欄位"
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/orchestration/agent-communication-protocol.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable communication protocol.
 
         Minimal fallback: Reject messages missing required Envelope fields and report INVALID_ENVELOPE.

package/bundled/ai/standards/agent-dispatch.ai.yaml

@@ -1,6 +1,6 @@
 # Agent Dispatch & Parallel Coordination - DEPRECATED STUB
-# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
-# Canonical location: dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/agent-dispatch.md (remains in UDS)
@@ -14,20 +14,19 @@ standard:
     deprecated: true
     deprecated_since: "5.4.0"
     removal_version: "6.0.0"
-    canonical_owner: devap
-    canonical_path: "dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/agent-dispatch.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (orchestration layer).
-      Install DevAP and load standards/orchestration/agent-dispatch.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any agent dispatch operation
       instruction: >
-        This standard (agent-dispatch.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml
 
         The human-readable standard remains at:
           universal-dev-standards/core/agent-dispatch.md
@@ -36,7 +35,7 @@ standard:
     - id: AD-003
       trigger: "所有並行代理完成"
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/orchestration/agent-dispatch.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable dispatch protocol.
 
         Minimal fallback: Run full test suite after all parallel agents complete.

package/bundled/ai/standards/branch-completion.ai.yaml

@@ -1,6 +1,6 @@
 # Branch Completion Workflow - DEPRECATED STUB
-# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
-# Canonical location: dev-autopilot/standards/flow/branch-completion.ai.yaml
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/branch-completion.md (remains in UDS)
@@ -14,31 +14,29 @@ standard:
     deprecated: true
     deprecated_since: "5.4.0"
     removal_version: "6.0.0"
-    canonical_owner: devap
-    canonical_path: "dev-autopilot/standards/flow/branch-completion.ai.yaml"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/branch-completion.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (flow orchestration layer).
-      Install DevAP and load standards/flow/branch-completion.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any branch completion operation
       instruction: >
-        This standard (branch-completion.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/flow/branch-completion.ai.yaml
 
         The human-readable standard remains at:
           universal-dev-standards/core/branch-completion.md
 
-        To install DevAP: npm install -g @devap/cli
       priority: required
 
     - id: BC-003
       trigger: "前置條件未滿足"
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/flow/branch-completion.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable branch completion flow.
 
         Minimal fallback: Block branch completion when prerequisites (tests, lint,

package/bundled/ai/standards/capability-declaration.ai.yaml

@@ -100,10 +100,10 @@ standard:
       consequence: "記錄 CAPABILITY_MISMATCH 事件，降級至 FAIL_CLOSED_DEFAULTS"
 
   applicable_components:
-    - "DevAP AgentAdapter（ClaudeAdapter / OpenCodeAdapter / CliAdapter）"
-    - "DevAP Tool 呼叫系統"
-    - "VibeOps ToolExecutor"
-    - "VibeOps Agent（planner / builder / evaluator 等）"
+    - "AgentAdapter implementations (e.g., ClaudeAdapter / OpenCodeAdapter / CliAdapter at the adoption layer)"
+    - "Tool 呼叫系統（採用層 runtime）"
+    - "ToolExecutor 實作（採用層）"
+    - "Agent（採用層；planner / builder / evaluator 等角色）"
     - "所有 MCP 工具插件"
 
   error_codes:

package/bundled/ai/standards/change-batching-standards.ai.yaml

@@ -1,6 +1,6 @@
 # Change Batching Standards - DEPRECATED STUB
-# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
-# Canonical location: dev-autopilot/standards/flow/change-batching-standards.ai.yaml
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/change-batching-standards.md (remains in UDS)
@@ -14,31 +14,29 @@ standard:
     deprecated: true
     deprecated_since: "5.4.0"
     removal_version: "6.0.0"
-    canonical_owner: devap
-    canonical_path: "dev-autopilot/standards/flow/change-batching-standards.ai.yaml"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/change-batching-standards.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (flow orchestration layer).
-      Install DevAP and load standards/flow/change-batching-standards.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any batch change operation
       instruction: >
-        This standard (change-batching-standards.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/flow/change-batching-standards.ai.yaml
 
         The human-readable standard remains at:
           universal-dev-standards/core/change-batching-standards.md
 
-        To install DevAP: npm install -g @devap/cli
       priority: required
 
     - id: atomic-commits
       trigger: merging a batch
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/flow/change-batching-standards.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable batch orchestration rules.
 
         Minimal fallback: Enforce all-or-nothing batch merging — either all changes

package/bundled/ai/standards/circuit-breaker.ai.yaml

@@ -20,7 +20,7 @@ standard:
     - "任何重試機制必須使用斷路器包裝，不得直接無限重試"
     - "斷路器狀態必須透過遙測可觀測（circuit_breaker_state_change 事件）"
     - "OPEN 狀態下的請求必須立即失敗（fail fast），不等待 timeout"
-    - "failureThreshold 預設值為 3，與 claude-code-book 及 DevAP Fix Loop 一致"
+    - "failureThreshold 預設值為 3，與 claude-code-book 及常見 Fix Loop 實作慣例一致"
     - "斷路器必須按照「功能單元」建立，不得全域共享單一斷路器"
 
   states:
@@ -80,12 +80,12 @@ standard:
       when: "每次狀態轉換時上傳"
 
   applicable_scenarios:
-    - "DevAP Fix Loop Agent 呼叫重試"
-    - "DevAP Judge / Quality Gate 重試"
-    - "DevAP API 呼叫（LLM API 不穩定保護）"
-    - "VibeOps Feedback Loop 重試"
-    - "VibeOps FLARE 主動檢索重試"
-    - "VibeOps AutoCompact（原始靈感來源）"
+    - "Fix Loop Agent 呼叫重試（採用層）"
+    - "Judge / Quality Gate 重試（採用層）"
+    - "LLM API 呼叫（不穩定保護）"
+    - "Feedback Loop 重試（採用層）"
+    - "FLARE 主動檢索重試（採用層）"
+    - "AutoCompact 風格的對話壓縮重試（claude-code-book 為原始靈感來源）"
 
   error_codes:
     CB-001: "CIRCUIT_OPEN — 斷路器開路，請求被拒絕"

package/bundled/ai/standards/disaster-recovery-drill.ai.yaml

@@ -20,7 +20,7 @@ requirements:
       (Recovery Point Objective) targets. These must be agreed with stakeholders
       before any DR drill can be considered meaningful.
     examples:
-      - "VibeOps commercial: RTO < 1 hour, RPO < 24 hours (daily backup)"
+      - "Commercial-grade SaaS example: RTO < 1 hour, RPO < 24 hours (daily backup)"
 
   - id: REQ-02
     title: Backup Restore Test

package/bundled/ai/standards/dual-phase-output.ai.yaml

@@ -97,9 +97,9 @@ standard:
     note: "Savings accumulate in repeated review scenarios (Fix Loop, Feedback Loop)"
 
   applicable_agents:
-    - DevAP Judge Agent
-    - VibeOps Evaluator Agent
-    - VibeOps Guardian Agent
+    - Judge Agent (adoption layer)
+    - Evaluator Agent (adoption layer)
+    - Guardian Agent (adoption layer)
     - Any LLM-driven AutoCompact / summarization component
 
   error_codes:

package/bundled/ai/standards/execution-history.ai.yaml

@@ -1,6 +1,6 @@
 # Execution History Repository Standards - DEPRECATED STUB
-# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
-# Canonical location: dev-autopilot/standards/orchestration/execution-history.ai.yaml
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Source spec: cross-project/specs/XSPEC-003-execution-history-standard-sdd.md
@@ -14,29 +14,27 @@ standard:
     deprecated: true
     deprecated_since: "5.4.0"
     removal_version: "6.0.0"
-    canonical_owner: devap
-    canonical_path: "dev-autopilot/standards/orchestration/execution-history.ai.yaml"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: cross-project/specs/XSPEC-003-execution-history-standard-sdd.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (orchestration layer).
-      Install DevAP and load standards/orchestration/execution-history.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: any execution history operation
       instruction: >
-        This standard (execution-history.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/orchestration/execution-history.ai.yaml
 
-        Note: DevAP's packages/core already implements execution history (ExecutionHistoryStorage).
         The YAML standard is now co-located with the implementation.
       priority: required
 
     - id: record-on-completion
       trigger: "Agent 任務執行完畢"
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/orchestration/execution-history.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable history protocol.
 
         Minimal fallback: Write required artifacts to .execution-history/{task-id}/{run-number}/

package/bundled/ai/standards/failure-source-taxonomy.ai.yaml

@@ -22,7 +22,7 @@ standard:
     - "failureSource 為 optional 欄位，不得破壞現有不含此欄位的程式碼"
     - "在同一失敗事件中，選擇最根本的來源作為 failureSource（例如 branch_divergence 比 compilation 更根本）"
     - "failureSource 應由偵測到失敗的元件設定（QualityGate / Adapter / SafetyHook / BranchDriftChecker）"
-    - "跨專案（DevAP / VibeOps）各自獨立定義 FailureSource type，語義保持一致"
+    - "各採用層各自獨立定義 FailureSource type，語義保持一致（避免跨層耦合）"
 
   failure_sources:
     prompt_delivery:
@@ -103,13 +103,11 @@ standard:
       - "resource_exhaustion > 其他（資源耗盡時無意義重試）"
       - "其他情況取最先偵測到的來源"
 
+  # Integration guidance (informative only; concrete file paths are
+  # adoption-layer concerns and intentionally omitted from the standard).
   integration_points:
-    devap:
-      files:
-        - "packages/core/src/types.ts — TaskResult.failureSource / FailureSource type"
-        - "packages/core/src/quality-gate.ts — QualityGateResult.failureSource 推斷"
-        - "packages/adapter-claude/src/claude-adapter.ts — resource_exhaustion 映射"
-    vibeops:
-      files:
-        - "src/types/index.ts — IterationRecord.failureSource（獨立定義，AGPL 隔離）"
-        - "src/runner/pipeline-runner.ts — agent:error 事件 payload"
+    expected_call_sites:
+      - "core types module — TaskResult.failureSource / FailureSource type"
+      - "quality-gate module — QualityGateResult.failureSource 推斷"
+      - "agent adapter — resource_exhaustion / network_error 映射"
+      - "pipeline runner — agent:error / agent:retry 事件 payload"

package/bundled/ai/standards/git-worktree.ai.yaml

@@ -23,7 +23,7 @@ standard:
   lifecycle:
     - phase: setup
       steps:
-        - "選擇 worktree 目錄位置（優先順序：existing → .devap/worktrees → 詢問使用者）"
+        - "選擇 worktree 目錄位置（優先順序：existing → .uds/worktrees → 詢問使用者）"
         - "執行 git check-ignore 確認目錄被忽略"
         - "建立 worktree + 新分支"
         - "安裝依賴（若需要）"

package/bundled/ai/standards/governance-layer.ai.yaml

@@ -0,0 +1,114 @@
+# Governance Layer Standard - AI Optimized
+# Source: core/governance-layer.md
+
+id: governance-layer
+meta:
+  version: "1.0.0"
+  updated: "2026-05-07"
+  source: core/governance-layer.md
+  description: "治理層標準（Vision/Mission/Goals 三層架構 + KPI + 紅線清單）"
+  scope: universal
+  priority: meta
+
+# This is Standard #0 — evaluated before all other standards
+priority_order:
+  rule: "Governance layer overrides all other standards on conflict"
+  resolution_order:
+    1: governance-layer (this standard)
+    2: domain standards (testing, commit, deployment, etc.)
+    3: project-specific overrides
+
+# Three-layer schema requirements
+schema:
+  vision:
+    required: true
+    format: "Single sentence, ≤ 50 tokens"
+    content: "Long-term direction; timeless; no metrics"
+    change_frequency: annual
+
+  mission:
+    required: true
+    format: "3–5 commitments + red_lines table (≤ 300 tokens total)"
+    content: "What we do / don't do; red lines with trigger conditions + actions"
+    change_frequency: quarterly
+    red_lines:
+      required_fields:
+        - id           # Unique identifier (e.g., R1, GUARD-001)
+        - category     # quality | safety | compliance | ethics
+        - clause       # Human-readable forbidden/required statement
+        - action       # block | warn | escalate_to_human
+      recommended_fields:
+        - mission_clause_ref  # Reference to the mission commitment this enforces
+
+  goals:
+    required: true
+    format: "KPI table, ≤ 500 tokens"
+    change_frequency: per_sprint
+    falsifiability: "Every KPI must be measurable — no 'improve', 'enhance', 'better'"
+    kpi:
+      required_fields:
+        - id                 # Unique identifier (e.g., KPI-01)
+        - metric_name        # Name of the tracked metric
+        - threshold          # Quantified target (e.g., ≥ 95%, < 200 ms)
+        - measurement_method # How and when the metric is measured
+
+# Red line action semantics
+red_line_actions:
+  block:
+    description: "Halt pipeline immediately; do not proceed"
+  warn:
+    description: "Log violation and continue; escalate if threshold exceeded"
+  escalate_to_human:
+    description: "Pause and require human decision before continuing"
+
+# AI evaluator integration
+evaluator:
+  scoring_axes:
+    correctness:
+      weight: 0.4
+      veto_threshold: 0.3
+    mission_alignment:
+      weight: 0.3
+      veto_threshold: 0.3
+    goal_achievement:
+      weight: 0.3
+      veto_threshold: 0.3
+  veto_rule: "Any single axis < 0.3 → FAIL regardless of weighted sum"
+
+# Risk acceptance for relaxed gates
+risk_acceptance:
+  trigger: "gate.mode = trace_only (or any human gate bypass)"
+  required_fields:
+    - date
+    - signatory
+    - gates_bypassed
+    - risks_accepted
+  fail_closed: "Pipeline MUST refuse to start without a valid Risk Acceptance Clause"
+
+# Governance file structure
+file_structure:
+  directory: "governance/"
+  files:
+    - name: "vision.md"
+      content: "Single-sentence vision statement"
+    - name: "mission.md"
+      content: "Commitments + red lines table; Risk Acceptance Clause if applicable"
+    - name: "goals.md"
+      content: "KPI table (updated each Sprint)"
+
+# Compliance checklist (AI-verifiable)
+compliance_checks:
+  - id: CK-01
+    check: "Vision is a single sentence ≤ 50 tokens with no metrics"
+  - id: CK-02
+    check: "Mission has 3–5 commitments and a red_lines table"
+  - id: CK-03
+    check: "Every red line has: id, category, clause, action"
+  - id: CK-04
+    check: "Goals table present with all KPIs containing required fields"
+  - id: CK-05
+    check: "No KPI uses vague language (improve / enhance / better)"
+  - id: CK-06
+    check: "If gate.mode=trace_only, Risk Acceptance Clause exists in mission.md"
+  - id: CK-07
+    check: "Evaluator weights 0.4/0.3/0.3 with fail-closed veto at < 0.3"

package/bundled/ai/standards/mock-boundary.ai.yaml

@@ -20,7 +20,7 @@ core_problem:
     a specification of mock behavior rather than system behavior.
     The tests pass in CI while the real system silently fails.
   real_world_example: |
-    // SPEC-002.test.ts (VibeOps) — hollow test example
+    // SPEC-002.test.ts (multi-agent pipeline project) — hollow test example
     vi.mock('../../src/runner/agent-runner.js')      // Core dependency mocked
     vi.mock('../../src/runner/guardian-hooks.js')     // Core dependency mocked
     vi.mock('../../src/runner/prototyper.js')         // Core dependency mocked

package/bundled/ai/standards/model-selection.ai.yaml

@@ -103,7 +103,7 @@ standard:
           description: "數學推理準確率"
           benchmark: "gsm8k"
         instruction_following:
-          description: "複雜多步驟指令遵循率（VibeOps 最重視）"
+          description: "複雜多步驟指令遵循率（多 Agent pipeline 場景最重視）"
           benchmark: "internal-instruction-bench"
         long_context_quality:
           description: "長文件中間段資訊存取（Lost-in-the-Middle）"

package/bundled/ai/standards/packaging-standards.ai.yaml

@@ -4,12 +4,12 @@
 standard:
   id: packaging
   name: Packaging Standards
-  description: Recipe-based packaging framework for user projects using UDS/DevAP toolchain
+  description: Recipe-based packaging framework for user projects using a UDS-aware toolchain
   guidelines:
     - "Recipe-based: use built-in or custom recipes for each packaging target"
-    - "Declarative: declare targets in .devap/packaging.yaml"
+    - "Declarative: declare targets in your project's packaging config (path is adoption-layer specific)"
     - "Customizable: override config, inject hooks, or write custom recipes"
-    - "Pipeline-integrated: packaging runs between Review and Deploy in VibeOps"
+    - "Pipeline-integrated: packaging runs between Review and Deploy in the adoption-layer pipeline"
 
   meta:
     version: "1.0.0"
@@ -19,7 +19,7 @@ standard:
   principles:
     core:
       - recipe_based: "Every packaging target references a named Recipe; no ad-hoc scripts in pipeline YAML"
-      - declarative_targets: "Projects declare targets in .devap/packaging.yaml; DevAP resolves and executes"
+      - declarative_targets: "Projects declare targets in their packaging config (file path is adoption-layer specific); the adoption-layer runtime resolves and executes"
       - customizable: "Four customization layers allow config overrides, hook injection, custom Recipes, and escape hatches"
       - pipeline_integrated: "Packaging runs as a named stage between Review and Deploy"
 
@@ -82,15 +82,15 @@ built_in_recipes:
 customization_layers:
   L1:
     name: config_override
-    mechanism: "config: block in .devap/packaging.yaml"
+    mechanism: "config: block in .uds/packaging.yaml"
     when: "Change default values (registry URL, tag, output dir)"
   L2:
     name: hook_injection
-    mechanism: "hooks: block in .devap/packaging.yaml"
+    mechanism: "hooks: block in .uds/packaging.yaml"
     when: "Run extra commands before/after build or publish"
   L3:
     name: custom_recipe
-    mechanism: "New .yaml file in project's .devap/recipes/"
+    mechanism: "New .yaml file in project's .uds/recipes/"
     when: "Entirely different build process; built-ins don't apply"
   L4:
     name: escape_hatch
@@ -138,5 +138,5 @@ recipe_selection_guide:
 physical_spec:
   type: custom_script
   validator:
-    command: "test -f .devap/packaging.yaml"
+    command: "test -f .uds/packaging.yaml"
     rule: "packaging_config_declared"

package/bundled/ai/standards/pipeline-integration-standards.ai.yaml

@@ -1,6 +1,6 @@
 # Pipeline Integration Standards - DEPRECATED STUB
-# This file has been migrated to DevAP per DEC-049 (UDS/DevAP responsibility split).
-# Canonical location: dev-autopilot/standards/flow/pipeline-integration-standards.ai.yaml
+# Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+# Adoption layer must implement an equivalent runtime; UDS retains only the human-readable concept under core/.
 # Migration: XSPEC-086 Phase 2 (2026-04-27)
 #
 # Human-readable standard: core/pipeline-integration-standards.md (remains in UDS)
@@ -14,20 +14,19 @@ standard:
     deprecated: true
     deprecated_since: "5.4.0"
     removal_version: "6.0.0"
-    canonical_owner: devap
-    canonical_path: "dev-autopilot/standards/flow/pipeline-integration-standards.ai.yaml"
+    canonical_owner: adoption-layer
+    canonical_path: "" # adoption-layer responsibility
     source: core/pipeline-integration-standards.md
     description: >
-      DEPRECATED: This standard has moved to DevAP (flow orchestration layer).
-      Install DevAP and load standards/flow/pipeline-integration-standards.ai.yaml instead.
+      DEPRECATED: Runtime details relocated to adoption layer (runtime moved to adoption layer 2026-04-28).
+      Adoption layer must implement an equivalent runtime.
 
   rules:
     - id: deprecation-notice
       trigger: starting pipeline execution
       instruction: >
-        This standard (pipeline-integration-standards.ai.yaml) has been migrated to DevAP.
+        Runtime details for this standard are now adoption-layer responsibility (runtime moved to adoption layer 2026-04-28).
         For the canonical executable definition, load:
-          dev-autopilot/standards/flow/pipeline-integration-standards.ai.yaml
 
         The human-readable standard remains at:
           universal-dev-standards/core/pipeline-integration-standards.md
@@ -36,7 +35,7 @@ standard:
     - id: fail-safe-defaults
       trigger: toggle not found in configuration
       instruction: >
-        DEPRECATED — load dev-autopilot/standards/flow/pipeline-integration-standards.ai.yaml
+        DEPRECATED — see universal-dev-standards/core/ for human-readable concept; runtime is adoption-layer responsibility
         for the current executable pipeline integration rules.
 
         Minimal fallback: Default all unset pipeline toggles to OFF (manual mode).

package/bundled/ai/standards/pipeline-security-gates.ai.yaml

@@ -1,5 +1,9 @@
 # Pipeline Security Gates (AI-Optimized v1)
 # Source: core/pipeline-security-gates.md
+# DEPRECATION NOTICE (XSPEC-086 Phase 3, 2026-04-28):
+#   Security gate orchestration (pipeline stage ordering, escalation flow) is now
+#   adoption-layer responsibility — UDS no longer ships an executable runtime.
+#   This file retains gate definitions, tools, severity levels, and failure_behavior only.
 
 standard:
   id: pipeline-security-gates

package/bundled/ai/standards/recovery-recipe-registry.ai.yaml

@@ -187,14 +187,10 @@ standard:
           on_exhaust: RecoveryStrategy
           message: "string (optional)"
 
+  # Integration guidance (informative; concrete file paths are adoption-layer concerns).
   integration_points:
-    devap:
-      files:
-        - "packages/core/src/types.ts — RecoveryRecipe / RecoveryStrategy type"
-        - "packages/core/src/recovery-registry.ts — Registry 實作與預設 recipe"
-        - "packages/core/src/orchestrator.ts — fix loop 前查詢 Registry"
-    vibeops:
-      files:
-        - "src/types/index.ts — 獨立定義 RecoveryRecipe（AGPL 隔離）"
-        - "src/runner/recovery-registry.ts — 獨立實作"
-        - "recovery-recipes.yaml — 預設 recipe 配置"
+    expected_call_sites:
+      - "core types module — RecoveryRecipe / RecoveryStrategy type"
+      - "recovery-registry module — Registry 實作與預設 recipe"
+      - "orchestrator module — fix loop 前查詢 Registry"
+      - "recovery-recipes config — 預設 recipe 配置（檔名由採用層決定）"

package/bundled/ai/standards/security-decision.ai.yaml

@@ -76,9 +76,9 @@ standard:
       message: "[WARN] projectSettings security override rejected: {operation}"
 
   applicable_components:
-    - "DevAP Safety Hook"
-    - "VibeOps CommandPolicy"
-    - "VibeOps Governance Framework (SPEC-049)"
+    - "Safety Hook 實作（採用層）"
+    - "CommandPolicy 實作（採用層）"
+    - "Governance Framework（採用層；OPA / Cedar / 自訂 policy engine 皆可）"
     - "任何多來源規則合併的安全仲裁場景"
 
   error_codes:

package/bundled/ai/standards/server-ops-security.ai.yaml

@@ -180,7 +180,7 @@ categories:
       aws: [Security Groups, NACLs, VPC Flow Logs]
       gcp: [VPC Firewall Rules, Cloud Armor]
     outbound_allowlist_format: |
-      # Example: /etc/vibeops/outbound-allowlist.conf
+      # Example: /etc/ai-agent/outbound-allowlist.conf
       ALLOW api.openai.com:443
       ALLOW registry.npmjs.org:443
       DENY *:* (default deny)