@geraldmaron/construct 1.0.16 → 1.0.17

package/lib/service-manager.mjs

@@ -442,9 +442,22 @@ async function tryStartDockerDaemon({
   return false;
 }
 
+// The optional services a user can pick from with `construct dev --select` /
+// `--only=`. Pressure Guard (cleanup) and Doctor (the L0 supervisor daemon)
+// are infrastructure, always on — they are intentionally not selectable.
+
+export const SELECTABLE_SERVICES = Object.freeze([
+  { key: 'postgres', label: 'Postgres', description: 'Managed pgvector container (or external DATABASE_URL).' },
+  { key: 'dashboard', label: 'Dashboard', description: 'Local operations dashboard on http://127.0.0.1:4242.' },
+  { key: 'telemetry', label: 'Telemetry', description: 'Trace export / local JSONL traces.' },
+  { key: 'memory', label: 'Memory (cm)', description: 'Persistent memory service (cm).' },
+  { key: 'opencode', label: 'OpenCode', description: 'OpenCode bridge server.' },
+]);
+
 export async function startServices({
   rootDir,
   homeDir = os.homedir(),
+  selected = null,
   describeRuntimeSupportFn = describeRuntimeSupport,
   getRuntimePortsFn = getRuntimePorts,
   startDashboardFn = startDashboard,
@@ -461,6 +474,11 @@ export async function startServices({
   const ports = await getRuntimePortsFn(homeDir);
   const envPath = getUserEnvPath(homeDir);
 
+  // A null selection means "start everything" (the default). A Set restricts
+  // startup to the chosen optional services; always-on infrastructure ignores it.
+
+  const wants = (key) => selected === null || selected.has(key);
+
   // On macOS, auto-launch Docker Desktop when the CLI is present but the
   // daemon is down. Polls up to 60s so downstream Postgres startup sees a working
   // compose runner instead of "Docker not available".
@@ -487,7 +505,7 @@ export async function startServices({
   const databaseUrl = liveEnv.DATABASE_URL || '';
   const usesManagedPostgres = isManagedConstructPostgresUrl(databaseUrl);
 
-  if (usesManagedPostgres) {
+  if (wants('postgres') && usesManagedPostgres) {
     if (!isConstructPostgresRunning()) {
       const pgStart = startConstructPostgres({ rootDir, homeDir, spawnSyncFn: spawnSync, detectDockerComposeFn: detectDockerComposeFn });
       if (pgStart.status === 'started') {
@@ -515,20 +533,23 @@ export async function startServices({
         note: pgvector ? 'pgvector enabled' : 'pgvector not installed',
       });
     }
-  } else if (databaseUrl) {
+  } else if (wants('postgres') && databaseUrl) {
     results.push({ name: 'Postgres', url: databaseUrl, status: 'configured', note: 'external database' });
   }
 
   // Dashboard
-  const dashboard = await startDashboardFn({ rootDir, homeDir, preferredPort: ports.dashboard });
-  results.push({
-    name: 'Dashboard',
-    url: dashboard.url,
-    status: dashboard.reused ? 'reused' : 'started',
-  });
+  if (wants('dashboard')) {
+    const dashboard = await startDashboardFn({ rootDir, homeDir, preferredPort: ports.dashboard });
+    results.push({
+      name: 'Dashboard',
+      url: dashboard.url,
+      status: dashboard.reused ? 'reused' : 'started',
+    });
+  }
 
   const telemetryUrl = liveEnv.CONSTRUCT_TELEMETRY_URL ?? '';
   const traceBackend = resolveTraceBackend(liveEnv);
+  if (wants('telemetry')) {
   if (traceBackend === 'local') {
     results.push({
       name: 'Telemetry',
@@ -561,21 +582,22 @@ export async function startServices({
   } else {
     results.push({ name: 'Telemetry', status: 'unavailable', note: 'remote export requested but endpoint is not configured' });
   }
+  }
 
   // Memory (cm)
-  if (support.cm) {
+  if (wants('memory') && support.cm) {
     if (await memoryProbeFn(ports.memory)) {
       results.push({ name: 'Memory (cm)', url: `http://127.0.0.1:${ports.memory}`, status: 'reused' });
     } else {
       spawnDetachedFn('cm', ['serve', '--port', String(ports.memory)], homeDir, 'cm.log');
       results.push({ name: 'Memory (cm)', url: `http://127.0.0.1:${ports.memory}`, status: 'started' });
     }
-  } else {
+  } else if (wants('memory')) {
     results.push({ name: 'Memory (cm)', status: 'unavailable', note: 'cm not installed — run: construct init or brew install dicklesworthstone/tap/cm' });
   }
 
   // OpenCode (optional)
-  if (support.opencode) {
+  if (wants('opencode') && support.opencode) {
     if (await openCodeProbeFn(ports.bridge)) {
       results.push({ name: 'OpenCode', url: `http://127.0.0.1:${ports.bridge}`, status: 'reused' });
     } else {

package/lib/setup.mjs

@@ -45,7 +45,12 @@ function printHelp() {
   console.log(`Construct install — machine setup (once per machine)
 
 Usage:
-  construct install [--yes] [--no-docker]
+  construct install [--yes] [--no-docker] [--reconfigure]
+
+Flags:
+  --yes          accept detected defaults without prompting
+  --no-docker    skip local Postgres / Docker service setup
+  --reconfigure  re-prompt for service consent, ignoring cached answers
 
 What it does:
   - creates ~/.construct/config.env
@@ -58,8 +63,7 @@ What it does:
   - runs construct doctor
   - detects the project tech stack and writes .cx/project-profile.json
 
-For project setup (once per repo): construct init
-Use --yes to run without prompts and accept detected environment defaults.`);
+For project setup (once per repo): construct init`);
 }
 
 function runConstruct(argsList, { optional = false } = {}) {
@@ -505,12 +509,24 @@ export async function runSetup({ rootDir = ROOT_DIR, args = [], homeDir = HOME }
   const argSet = new Set(args);
   const isYes = argSet.has('--yes');
   const skipDocker = argSet.has('--no-docker');
+  const reconfigure = argSet.has('--reconfigure');
 
   if (argSet.has('--help') || argSet.has('-h')) {
     printHelp();
     return;
   }
 
+  // Reject unknown flags loudly so a typo (e.g. --reconfig) fails fast with the
+  // help text instead of silently running defaults.
+
+  const KNOWN_FLAGS = new Set(['--yes', '--no-docker', '--reconfigure', '--help', '-h']);
+  const unknownFlags = args.filter((a) => a.startsWith('-') && !KNOWN_FLAGS.has(a));
+  if (unknownFlags.length) {
+    console.error(`Unknown flag(s): ${unknownFlags.join(', ')}`);
+    printHelp();
+    throw new Error(`Unknown setup flag(s): ${unknownFlags.join(', ')}`);
+  }
+
   console.log('Construct setup');
   console.log('────────────────');
 
@@ -565,6 +581,7 @@ export async function runSetup({ rootDir = ROOT_DIR, args = [], homeDir = HOME }
     const pgConsent = await consentToInstall({
       name: 'postgres',
       isYes,
+      force: reconfigure,
       alreadyConfigured: Boolean(process.env.DATABASE_URL),
       alreadyConfiguredNote: 'DATABASE_URL already set — using external database.',
       envPath,
@@ -620,6 +637,7 @@ export async function runSetup({ rootDir = ROOT_DIR, args = [], homeDir = HOME }
     const cheapestConsent = await consentToInstall({
       name: 'cheapest-provider',
       isYes,
+      force: reconfigure,
       alreadyConfigured: false,
       envPath,
       defaultYes: false,

package/lib/validators/skills.mjs

@@ -6,6 +6,8 @@
  *   ---
  *   name: <kebab-case>
  *   description: "<≤1024 chars, includes a 'use when' trigger>"
+ *   [inputs: [<string>, …]  — optional, surfaced by capability discovery]
+ *   [artifactType: <string> — optional, surfaced by capability discovery]
  *   [role/applies_to/inherits/version/profiles/cap for role files]
  *   ---
  *   # <Title>
@@ -100,6 +102,23 @@ function validateDescription(description) {
   return null;
 }
 
+// Optional embedded-contract metadata: surfaced by capability discovery when
+// present. Validated only when present so the field stays opt-in and is
+// populated incrementally — inputs is a list of strings, artifactType a string.
+
+function validateOptionalMetadata(frontmatter) {
+  const issues = [];
+  if ('inputs' in frontmatter && frontmatter.inputs !== null) {
+    if (!Array.isArray(frontmatter.inputs) || frontmatter.inputs.some((i) => typeof i !== 'string')) {
+      issues.push('frontmatter.inputs must be a list of strings when present');
+    }
+  }
+  if ('artifactType' in frontmatter && frontmatter.artifactType !== null && typeof frontmatter.artifactType !== 'string') {
+    issues.push('frontmatter.artifactType must be a string when present');
+  }
+  return issues;
+}
+
 export function validateSkills(roots) {
   const dirs = Array.isArray(roots) ? roots : [roots];
   const errors = [];
@@ -150,6 +169,8 @@ export function validateSkills(roots) {
       const descErr = validateDescription(frontmatter.description);
       if (descErr) errors.push(`${rel}: ${descErr}`);
 
+      for (const issue of validateOptionalMetadata(frontmatter)) errors.push(`${rel}: ${issue}`);
+
       const { title, opener } = extractTitleAndOpener(body);
 
       if (!title) {

package/package.json

@@ -1,11 +1,17 @@
 {
   "name": "@geraldmaron/construct",
-  "version": "1.0.16",
+  "version": "1.0.17",
   "type": "module",
   "description": "Construct — agent orchestration layer for OpenCode, Claude Code, and other coding surfaces",
   "bin": {
     "construct": "bin/construct"
   },
+  "exports": {
+    ".": "./lib/embedded-contract/index.mjs",
+    "./embedded-contract": "./lib/embedded-contract/index.mjs",
+    "./lib/*": "./lib/*",
+    "./package.json": "./package.json"
+  },
   "files": [
     "bin/construct",
     "bin/construct-postinstall.mjs",
@@ -78,8 +84,8 @@
   },
   "optionalDependencies": {
     "@opentelemetry/api": "^1.9.0",
-    "@opentelemetry/core": "^1.25.0",
-    "@opentelemetry/exporter-trace-otlp-http": "^0.52.0",
+    "@opentelemetry/core": "^2.7.1",
+    "@opentelemetry/exporter-trace-otlp-http": "^0.218.0",
     "@opentelemetry/resources": "^1.25.0",
     "@opentelemetry/sdk-trace-node": "^1.25.0",
     "@opentelemetry/semantic-conventions": "^1.25.0"

package/scripts/sync-specialists.mjs

@@ -172,8 +172,17 @@ function detectConstructProject(cwd) {
 
 const detectedProject = (!PROJECT_FLAG && !GLOBAL_FLAG) ? detectConstructProject(process.cwd()) : null;
 const projectDir = PROJECT_FLAG ? process.cwd() : detectedProject;
-const lockPath = path.join(projectDir || root, ".cx", "sync.lock");
-const stagingDir = path.join(projectDir || root, ".cx", "sync-staging");
+
+// Lock and staging are scoped to the tier we actually mutate: a project dir for
+// project-tier writes, the user's HOME for global-tier writes (which land in
+// ~/.claude, ~/.codex, …). Keying the global tier to HOME — not the repo root —
+// means two --global syncs against different HOMEs (e.g. parallel test files in
+// isolated sandboxes) never collide on a shared repo-root lock, and staging
+// renames stay on the same filesystem as their destinations.
+
+const stateBase = projectDir || home;
+const lockPath = path.join(stateBase, ".cx", "sync.lock");
+const stagingDir = path.join(stateBase, ".cx", "sync-staging");
 
 // Project-tier writes carry every registry entry. Global-tier writes carry only
 // the `construct` front-door agent — specialists live with the project, not the
@@ -243,7 +252,7 @@ function writeFile(file, content, { stamp = true } = {}) {
   }
 
   // Two-phase: write to staging, commit later.
-  const rel = path.relative(projectDir || root, file);
+  const rel = path.relative(stateBase, file);
   const stagingPath = path.join(stagingDir, rel);
   mkdirp(path.dirname(stagingPath));
   fs.writeFileSync(stagingPath, stamped);

package/skills/ai/agent-dev.md

@@ -1,6 +1,8 @@
 ---
 name: ai-agent-dev
 description: Use this skill when building AI agents, tool-use systems, or multi-agent workflows.
+inputs: [agent-spec, task-context]
+artifactType: agent-implementation
 ---
 # AI Agent Development
 

package/skills/ai/llm-security.md

@@ -1,6 +1,8 @@
 ---
 name: ai-llm-security
 description: Use this skill when securing LLM-powered applications against prompt injection, data leakage, and misuse.
+inputs: [prompt, model-output, agent-spec]
+artifactType: guidance
 ---
 # LLM Security
 

package/skills/ai/ml-ops.md

@@ -1,6 +1,8 @@
 ---
 name: ai-ml-ops
 description: Patterns, anti-patterns, and reference guidance for ML Operations (MLOps). Use when the task involves ml operations (mlops).
+inputs: [eval-dataset, model-output]
+artifactType: guidance
 ---
 # ML Operations (MLOps)
 

package/skills/ai/orchestration-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: ai-orchestration-workflow
 description: Use this skill when the request involves agent orchestration, phase transitions, task keys, handoff quality, workflow state, or project alignment.
+inputs: [agent-spec, workflow-state]
+artifactType: guidance
 ---
 # Construct Orchestration Workflow
 

package/skills/ai/prompt-and-eval.md

@@ -1,6 +1,8 @@
 ---
 name: ai-prompt-and-eval
 description: Use this skill when designing prompts, evaluating model performance, or optimizing LLM behavior.
+inputs: [prompt, eval-dataset, model-output]
+artifactType: eval-report
 ---
 # Prompt Engineering and Evaluation
 

package/skills/ai/prompt-optimizer.md

@@ -1,6 +1,8 @@
 ---
 name: ai-prompt-optimizer
 description: Closed-loop prompt auto-optimization guide. Use when the task matches the trigger conditions described in the body.
+inputs: [prompt, model-output, eval-dataset]
+artifactType: prompt
 ---
 # Prompt Auto-Optimization Loop
 

package/skills/ai/rag-system.md

@@ -1,6 +1,8 @@
 ---
 name: ai-rag-system
 description: Use this skill when building retrieval-augmented generation pipelines, vector search, or knowledge-grounded AI systems.
+inputs: [eval-dataset, prompt]
+artifactType: guidance
 ---
 # RAG System Design
 

package/skills/ai/trace-triage.md

@@ -0,0 +1,36 @@
+---
+name: ai-trace-triage
+description: "Use when: agent telemetry traces need triage to find where a run went wrong — the failing step, the cause category, and whether it is a regression or a one-off."
+inputs: [telemetry-traces]
+artifactType: trace-findings
+---
+# Trace Triage
+
+Use this skill when agent telemetry traces need to be triaged to locate failures and separate systemic regressions from one-off noise.
+
+A stable median score hides high-variance agents failing silently. Triage works the tail and the deltas, not the average.
+
+## Steps
+
+1. **Frame the window and baseline.** Compare the current window against a prior baseline of the same agents/skills; an absolute score means little without the delta.
+2. **Sort by the tail, not the mean.** Surface the worst p10 runs and the largest score drops since baseline — that is where real failures live.
+3. **For each failing run, locate the failing step**: which role/tool call produced the bad output or error. Read the span, not just the verdict.
+4. **Classify the cause**: prompt/instruction gap, wrong model tier, missing context/evidence, tool error, or genuine task ambiguity. Do not default to "prompt issue".
+5. **Regression vs one-off**: does the same failure recur across runs (systemic) or appear once (noise)? Only systemic failures warrant a fix; flag one-offs for watch.
+6. **Hand off** systemic findings with the trace id, the failing span, the cause class, and a proposed direction (to prompt-optimizer, engineer, or evaluator).
+
+## Output shape
+
+```
+## Window: <range> vs baseline <range>
+| traceId | agent/skill | failing step | cause class | regression? | Δ score |
+|---|---|---|---|---|---|
+
+## Systemic (fix) vs one-off (watch)
+```
+
+## Verification bar
+
+- Every finding cites a real traceId and the specific span that failed.
+- Regression claims are backed by recurrence across runs, not a single bad sample.
+- Cause classification is evidence-based; "unclear" is a valid class when the trace doesn't show why.

package/skills/architecture/api-design.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-api-design
 description: Use this skill when designing REST, GraphQL, or gRPC APIs.
+inputs: [system-design, requirements]
+artifactType: api-design
 ---
 # API Design
 

package/skills/architecture/caching.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-caching
 description: Use this skill when designing caching strategies for applications, APIs, or infrastructure.
+inputs: [system-design, requirements]
+artifactType: guidance
 ---
 # Caching
 

package/skills/architecture/cloud-native.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-cloud-native
 description: Use this skill when designing containerized, orchestrated, or microservice-based systems.
+inputs: [system-design, requirements]
+artifactType: guidance
 ---
 # Cloud-Native Architecture
 

package/skills/architecture/message-queue.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-message-queue
 description: Use this skill when designing asynchronous communication, event-driven systems, or message-based integrations.
+inputs: [system-design, requirements]
+artifactType: guidance
 ---
 # Message Queues and Event-Driven Architecture
 

package/skills/architecture/security-arch.md

@@ -1,6 +1,8 @@
 ---
 name: architecture-security-arch
 description: Use this skill when designing authentication, authorization, network security, or zero-trust architectures.
+inputs: [system-design, requirements]
+artifactType: guidance
 ---
 # Security Architecture
 

package/skills/compliance/ai-disclosure.md

@@ -1,6 +1,8 @@
 ---
 name: compliance-ai-disclosure
 description: Use this skill when reviewing AI features for disclosure requirements, transparency obligations, or emerging AI regulation compliance.
+inputs: [artifact, data-flow]
+artifactType: privacy-assessment
 ---
 # AI Disclosure
 

package/skills/compliance/data-privacy.md

@@ -1,6 +1,8 @@
 ---
 name: compliance-data-privacy
 description: Use this skill when reviewing data collection, storage, processing, or retention for privacy regulation compliance.
+inputs: [data-flow, artifact]
+artifactType: privacy-assessment
 ---
 # Data Privacy
 

package/skills/compliance/license-audit.md

@@ -1,6 +1,8 @@
 ---
 name: compliance-license-audit
 description: Use this skill when auditing dependency licenses, evaluating OSS compliance risk, or preparing license inventories for legal review.
+inputs: [dependency-manifest]
+artifactType: license-report
 ---
 # License Audit
 

package/skills/compliance/regulatory-review.md

@@ -1,6 +1,8 @@
 ---
 name: compliance-regulatory-review
 description: Use this skill when conducting a compliance review before shipping features that handle user data, financial transactions, AI decisions, or regulated content.
+inputs: [artifact, data-flow, dependency-manifest]
+artifactType: compliance-review
 ---
 # Regulatory Review
 

package/skills/development/cpp.md

@@ -1,6 +1,8 @@
 ---
 name: development-cpp
 description: Use this skill when writing, reviewing, or debugging C or C++ code.
+inputs: [code, repo]
+artifactType: code
 ---
 # C/C++ Best Practices
 

package/skills/development/go.md

@@ -1,6 +1,8 @@
 ---
 name: development-go
 description: Use this skill when writing, reviewing, or debugging Go code.
+inputs: [code, repo]
+artifactType: code
 ---
 # Go Best Practices
 

package/skills/development/java.md

@@ -1,6 +1,8 @@
 ---
 name: development-java
 description: Use this skill when writing, reviewing, or debugging Java or Kotlin code on the JVM.
+inputs: [code, repo]
+artifactType: code
 ---
 # Java Best Practices
 

package/skills/development/kotlin.md

@@ -1,6 +1,8 @@
 ---
 name: development-kotlin
 description: Patterns, anti-patterns, and reference guidance for Kotlin / Android Development. Use when the task involves kotlin / android development.
+inputs: [code, repo]
+artifactType: code
 ---
 # Kotlin / Android Development
 

package/skills/development/mobile-crossplatform.md

@@ -1,6 +1,8 @@
 ---
 name: development-mobile-crossplatform
 description: Before choosing a framework, answer:. Use when the task matches the trigger conditions described in the body.
+inputs: [requirements, code]
+artifactType: guidance
 ---
 # Mobile Cross-Platform Development
 

package/skills/development/python.md

@@ -1,6 +1,8 @@
 ---
 name: development-python
 description: Use this skill when writing, reviewing, or debugging Python code.
+inputs: [code, repo]
+artifactType: code
 ---
 # Python Best Practices
 

package/skills/development/rust.md

@@ -1,6 +1,8 @@
 ---
 name: development-rust
 description: Use this skill when writing, reviewing, or debugging Rust code.
+inputs: [code, repo]
+artifactType: code
 ---
 # Rust Best Practices
 

package/skills/development/shell.md

@@ -1,6 +1,8 @@
 ---
 name: development-shell
 description: Use this skill when writing, reviewing, or debugging Bash, Zsh, or POSIX shell scripts.
+inputs: [code, repo]
+artifactType: code
 ---
 # Shell Scripting Best Practices
 

package/skills/development/swift.md

@@ -1,6 +1,8 @@
 ---
 name: development-swift
 description: Swift 6 enforces data-race safety at compile time. Annotate isolation boundary explicitly:. Use when the task matches the trigger conditions described in the body.
+inputs: [code, repo]
+artifactType: code
 ---
 # Swift / iOS Development
 

package/skills/development/typescript.md

@@ -1,6 +1,8 @@
 ---
 name: development-typescript
 description: Use this skill when writing, reviewing, or debugging TypeScript or JavaScript code.
+inputs: [code, repo]
+artifactType: code
 ---
 # TypeScript Best Practices
 

package/skills/devops/ci-cd.md

@@ -1,6 +1,8 @@
 ---
 name: devops-ci-cd
 description: Use this skill when designing, debugging, or optimizing CI/CD pipelines.
+inputs: [pipeline-config, repo]
+artifactType: ci-pipeline
 ---
 # CI/CD
 

package/skills/devops/containerization.md

@@ -1,6 +1,8 @@
 ---
 name: devops-containerization
 description: Use this skill when writing Dockerfiles, optimizing image size, or securing container builds.
+inputs: [service, repo]
+artifactType: dockerfile
 ---
 # Containerization
 

package/skills/devops/cost-optimization.md

@@ -1,6 +1,8 @@
 ---
 name: devops-cost-optimization
 description: Use this skill when reducing cloud spend, right-sizing resources, or implementing FinOps practices.
+inputs: [service, cost-data]
+artifactType: cost-optimization-plan
 ---
 # Cloud Cost Optimization
 

package/skills/devops/data-engineering.md

@@ -1,6 +1,8 @@
 ---
 name: devops-data-engineering
 description: "1. **Idempotency**: pipelines can run multiple times without duplicating data 2. **Observability**: every pipeline run logs row counts, latency, and anomalies 3. **Data contracts**: producers and consumers agree on schema and SLAs 4. **Lineage**: know where every column came from and what it feeds. Use when the task matches the trigger conditions described in the body."
+inputs: [pipeline-config, data-contract]
+artifactType: data-pipeline
 ---
 # Data Engineering
 

package/skills/devops/database.md

@@ -1,6 +1,8 @@
 ---
 name: devops-database
 description: Use this skill when designing schemas, writing migrations, optimizing queries, or selecting databases.
+inputs: [schema, query]
+artifactType: schema-design
 ---
 # Database Patterns
 

package/skills/devops/dependency-management.md

@@ -1,6 +1,8 @@
 ---
 name: devops-dependency-management
 description: Use this skill when managing package upgrades, resolving CVEs, or establishing lock file and versioning policy.
+inputs: [dependency-manifest, repo]
+artifactType: dependency-report
 ---
 # Dependency Management
 

package/skills/devops/devsecops.md

@@ -1,6 +1,8 @@
 ---
 name: devops-devsecops
 description: Use this skill when integrating security into CI/CD pipelines, managing supply chain risk, or automating security scanning.
+inputs: [pipeline-config, service]
+artifactType: security-plan
 ---
 # DevSecOps
 

package/skills/devops/git-workflow.md

@@ -1,6 +1,8 @@
 ---
 name: devops-git-workflow
 description: Use this skill when establishing branching strategies, commit conventions, or code integration practices.
+inputs: [repo, task-context]
+artifactType: guidance
 ---
 # Git Workflow
 

package/skills/devops/incident-response.md

@@ -1,6 +1,8 @@
 ---
 name: devops-incident-response
 description: "Define severity in your runbook and assign it early: it determines escalation and comms cadence. Use when the task matches the trigger conditions described in the body."
+inputs: [incident, alert]
+artifactType: incident-runbook
 ---
 # Incident Response