@polymorphism-tech/morph-spec 8.2.1 → 8.4.0

package/framework/standards/ai-agents/observability-patterns.md

@@ -0,0 +1,156 @@
+# Observability Patterns — OpenTelemetry, enrichment, investigation
+
+> **Scope:** stacks=["dotnet"]
+> **Layer:** 1 (on-keyword)
+> **Keywords:** observability, telemetry, opentelemetry, logging, tracing, log investigation, troubleshooting, aspire dashboard, span, correlation id
+> **Read by Claude in:** implement (wiring telemetry into an agent) and troubleshoot (investigating a production issue)
+
+**Verified against:** MAF 1.0 GA. Last-verified: 2026-07-22.
+
+---
+
+## Por que isso importa
+
+Um agente MAF em produção não é uma função — é uma cadeia (LLM call → tool call → sub-agent → RAG/DB) que pode ter qualquer profundidade. Sem telemetria estruturada, um bug em produção ("o agente respondeu errado", "a automação não disparou") é indistinguível de uma caixa-preta: não dá pra saber qual chamada falhou, quanto cada etapa levou, ou qual tool retornou o quê. Este standard cobre as três partes do problema: **como instrumentar** (setup), **o que registrar** (enrichment) e **como investigar** (análise) — nessa ordem, porque setup sem enrichment produz traces vazios, e enrichment sem prática de investigação não ajuda ninguém no momento do incidente.
+
+---
+
+## Setup — OpenTelemetry
+
+```csharp
+using OpenTelemetry;
+using OpenTelemetry.Trace;
+using OpenTelemetry.Metrics;
+using Microsoft.Agents.AI;
+
+// Habilitar em agents individuais
+agent.WithOpenTelemetry();
+
+// Program.cs — setup completo
+builder.Services.AddOpenTelemetry()
+    .WithTracing(tracing =>
+    {
+        tracing.AddSource(AgentOpenTelemetryConsts.DefaultSourceName);   // MAF 1.0 GA source
+        tracing.AddSource(builder.Environment.ApplicationName);          // seus spans customizados (ver Enrichment)
+        tracing.AddAspNetCoreInstrumentation();
+        tracing.AddHttpClientInstrumentation();
+        tracing.AddOtlpExporter();
+    })
+    .WithMetrics(metrics =>
+    {
+        metrics.AddMeter(AgentOpenTelemetryConsts.DefaultSourceName);
+        metrics.AddAspNetCoreInstrumentation();
+        metrics.AddHttpClientInstrumentation();
+        metrics.AddRuntimeInstrumentation();
+    });
+
+builder.Logging.AddOpenTelemetry(logging =>
+{
+    logging.IncludeFormattedMessage = true;
+    logging.IncludeScopes = true;           // necessário para correlação — ver Enrichment
+    logging.AddOtlpExporter();
+});
+```
+
+> **Source name:** sempre `AgentOpenTelemetryConsts.DefaultSourceName` de `Microsoft.Agents.AI`.
+> **NÃO usar** o source string `"Experimental.[pacote-antigo].*"` — pertence à família `Microsoft.Extensions.AI` 9.x, incompatível com MAF 1.0 GA.
+> **Produção:** desabilite dados sensíveis — `EnableSensitiveTelemetryData = false` no agent — para não vazar prompt/response completos no backend de export.
+
+### Aspire Dashboard (dev/local)
+
+Visualiza em tempo real: fluxo completo de conversas entre agents, ciclos de tool call (Model → Tool → Model), token usage e latência por chamada, error traces e retry patterns. Para ambientes hospedados (Coolify), exporte via OTLP para o backend de observability do projeto — ver `infrastructure-docker-coolify-deploy` para o setup de Serilog/JSON console log que alimenta o mesmo pipeline de agregação.
+
+---
+
+## Enrichment — o que preencher em spans e logs
+
+Setup sem enrichment produz traces tecnicamente corretos mas operacionalmente inúteis — você vê "uma chamada ao LLM aconteceu", não "por que ela demorou 8s" ou "qual feature/task gerou essa chamada". Preencha sempre:
+
+### Correlação entre trace, feature e requisição
+
+```csharp
+using var activity = Activity.Current;
+activity?.SetTag("morph.feature", featureName);
+activity?.SetTag("morph.task_id", taskId);
+activity?.SetTag("morph.correlation_id", correlationId);   // mesmo ID em toda a cadeia de uma requisição de usuário
+```
+
+Sem um `correlation_id` propagado manualmente através de chamadas assíncronas/filas (Hangfire, background jobs), você não consegue religar "o usuário reclamou às 14:32" a um trace específico — o `TraceId` do OpenTelemetry sozinho não sobrevive a um boundary de fila.
+
+### Atributos de custo e uso do modelo
+
+```csharp
+activity?.SetTag("gen_ai.request.model", modelAlias);       // alias do Model Registry, nunca o nome hardcoded
+activity?.SetTag("gen_ai.usage.prompt_tokens", usage.PromptTokens);
+activity?.SetTag("gen_ai.usage.completion_tokens", usage.CompletionTokens);
+activity?.SetTag("gen_ai.response.finish_reason", finishReason);
+```
+
+Nomeação `gen_ai.*` segue a convenção semântica OpenTelemetry para GenAI — mantém compatibilidade se o backend de observability tiver dashboards prontos para essa convenção.
+
+### Logging estruturado com `ILogger` — sempre com scope
+
+```csharp
+using (_logger.BeginScope(new Dictionary<string, object>
+{
+    ["FeatureId"] = featureName,
+    ["TaskId"] = taskId,
+    ["AgentId"] = agentPersonaId
+}))
+{
+    _logger.LogInformation("Tool call {ToolName} started with args {Args}", toolName, args);
+    // ... chamada ...
+    _logger.LogInformation("Tool call {ToolName} completed in {ElapsedMs}ms", toolName, elapsed);
+}
+```
+
+- **Sempre** parâmetros nomeados no template (`{ToolName}`, não string interpolada) — permite querying estruturado no backend em vez de grep de texto livre.
+- **Nunca** logar o conteúdo completo do prompt/response em `Information` — isso é PII/dado sensível do cliente por padrão. Logar em `Debug` apenas, e só se `EnableSensitiveTelemetryData` estiver habilitado explicitamente para o ambiente.
+- **Nível de log por tipo de evento:** `Information` para início/fim de tool call e decisões do agent; `Warning` para retry/fallback de provider; `Error` apenas para falhas que geram resposta degradada ao usuário (não para toda exceção capturada e tratada).
+
+---
+
+## Investigação e análise — quando algo dá errado
+
+Workflow para diagnosticar um incidente relatado ("o agente X respondeu errado/lento/nada às HH:MM"):
+
+1. **Ancore no correlation_id ou janela de tempo.** Se o relato tem um identificador (número de WhatsApp, feature, conversationId), busque por ele nos atributos (`morph.correlation_id`, `gen_ai.*`) — não pelo texto do log. Sem identificador, restrinja pela janela de tempo + `morph.feature`/`AgentId` antes de olhar qualquer trace individual.
+2. **Suba do trace raiz para os spans filhos.** O span raiz mostra a duração total; os filhos (`Function Calling`, `IChatClient`) mostram onde o tempo/erro realmente está. Não assuma — meça. Um "agente lento" é quase sempre UM tool call específico (chamada de API externa, query sem índice), não o LLM.
+3. **Correlacione com métricas antes de teorizar.** Confira a tabela "What to Monitor" abaixo pelo período do incidente — um pico de `tool call failure rate` ou `token usage` aponta a causa mais rápido que ler traces individuais um a um.
+4. **Reproduza com Debug ligado, nunca em produção.** Se a causa não estiver clara nos atributos estruturados, habilite `Debug` (com dados sensíveis, se necessário) num ambiente de staging com o mesmo input — nunca habilite log de prompt/response completo em produção para investigar.
+5. **Documente a causa raiz em `decisions.md`** se a investigação levar a uma mudança de arquitetura (novo middleware de retry, novo timeout, novo cache) — não só no commit message.
+
+### What to Monitor
+
+| Metric | Purpose | Alert Threshold |
+|--------|---------|------------------|
+| Token usage per request | Cost control | > 10K tokens/request |
+| Latency per agent call | Performance | > 5s for simple tasks |
+| Tool call failure rate | Reliability | > 5% failures |
+| Cache hit rate | Cost optimization | < 50% (tune strategy) |
+| Model drift | Quality | Evaluation score drop > 10% |
+
+---
+
+## Checklist (verifiable by morph-eval)
+
+- [ ] OpenTelemetry configurado com `AgentOpenTelemetryConsts.DefaultSourceName` (traces + metrics + logging)
+- [ ] `EnableSensitiveTelemetryData = false` fora de dev/staging
+- [ ] Todo tool call relevante tem `correlation_id` propagado manualmente através de boundaries assíncronos (filas, background jobs)
+- [ ] Logging via `ILogger` com `BeginScope` estruturado, nunca string interpolada em templates de log
+- [ ] Nenhum log em `Information`/produção contém prompt/response completo
+- [ ] Alertas configurados para os thresholds da tabela "What to Monitor" relevantes ao projeto
+
+---
+
+## References
+
+- `ai-agents-production` — panorama de produção; esta seção era resumida lá, tratamento canônico agora aqui
+- `ai-agents-middleware-patterns` — middleware de telemetria no nível `IChatClient` (`TelemetryMiddleware`)
+- `infrastructure-docker-coolify-deploy` — Serilog/JSON console log para o pipeline de agregação em produção
+- [OpenTelemetry Semantic Conventions for GenAI](https://opentelemetry.io/docs/specs/semconv/gen-ai/)
+- [Agent Observability](https://learn.microsoft.com/agent-framework/user-guide/observability/)
+
+---
+
+*MORPH-SPEC by Polymorphism Tech — ai-agents/observability-patterns.md v1.0 (2026-07-22)*

package/framework/standards/ai-agents/production.md

@@ -179,54 +179,9 @@ public async Task<WeatherResponse> GetWeatherAsync(
 
 ## Observability / OpenTelemetry
 
-```csharp
-using OpenTelemetry;
-using OpenTelemetry.Trace;
-using OpenTelemetry.Metrics;
-using Microsoft.Agents.AI;
-
-// Enable on individual agents
-agent.WithOpenTelemetry();
-
-// Program.cs — full setup
-builder.Services.AddOpenTelemetry()
-    .WithTracing(tracing =>
-    {
-        tracing.AddSource(AgentOpenTelemetryConsts.DefaultSourceName);   // MAF 1.0 GA source
-        tracing.AddSource(builder.Environment.ApplicationName);
-        tracing.AddAspNetCoreInstrumentation();
-        tracing.AddHttpClientInstrumentation();
-        tracing.AddOtlpExporter();
-    })
-    .WithMetrics(metrics =>
-    {
-        metrics.AddMeter(AgentOpenTelemetryConsts.DefaultSourceName);    // MAF 1.0 GA meter
-        metrics.AddAspNetCoreInstrumentation();
-        metrics.AddHttpClientInstrumentation();
-        metrics.AddRuntimeInstrumentation();
-    });
-```
-
-> **Source name:** sempre `AgentOpenTelemetryConsts.DefaultSourceName` de `Microsoft.Agents.AI`.
-> **NÃO usar** o source string `"Experimental.[pacote-antigo].*"` — pertence à família `Microsoft.Extensions.AI 9.x`, incompatível com MAF 1.0 GA.
-
-### Aspire Dashboard
-
-Visualiza traces de agents incluindo:
-- Fluxo completo de conversas entre agents
-- Tool call cycles (Model → Tool → Model)
-- Token usage e latência por chamada
-- Error traces e retry patterns
-
-### What to Monitor
+Setup, enrichment (span attributes, correlation IDs, structured logging) e o workflow de investigação/análise de logs em produção têm **tratamento canônico** em **`ai-agents-observability-patterns`**. Não duplicado aqui.
 
-| Metric | Purpose | Alert Threshold |
-|--------|---------|----------------|
-| Token usage per request | Cost control | > 10K tokens/request |
-| Latency per agent call | Performance | > 5s for simple tasks |
-| Tool call failure rate | Reliability | > 5% failures |
-| Cache hit rate | Cost optimization | < 50% (tune strategy) |
-| Model drift | Quality | Evaluation score drop > 10% |
+> Em produção: source name sempre `AgentOpenTelemetryConsts.DefaultSourceName`; `EnableSensitiveTelemetryData = false` fora de dev/staging. Ver `ai-agents-observability-patterns` para o setup completo, o que preencher em cada span/log, e o workflow de investigação quando um incidente for reportado.
 
 ---
 
@@ -262,6 +217,7 @@ Visualiza traces de agents incluindo:
 - `ai-agents-sweet-spot` — decisão de arquitetura antes de middleware
 - `ai-agents-providers-model-registry` — Model Registry para `_modelRegistry.GetChatClient(...)`
 - `ai-agents-middleware-patterns` — **tratamento canônico** de middleware (código dos 3 níveis, telemetria, resilência, anti-hallucination)
+- `ai-agents-observability-patterns` — **tratamento canônico** de observability (setup OpenTelemetry, enrichment de spans/logs, workflow de investigação)
 - `ai-agents-mcp-tools` — agente MAF consumindo MCP servers externos
 - `ai-agents-mcp-server` — projeto expondo capacidades como MCP server
 - `ai-agents-rag-custom-pgvector` — implementação completa de busca semântica (referida em Caching)

package/framework/templates/REGISTRY.json

@@ -109,55 +109,6 @@
       "technology": "handlebars",
       "validatePlaceholders": true
     },
-    {
-      "id": "context",
-      "kind": "template",
-      "name": "Project Context",
-      "path": "context/CONTEXT.md",
-      "location": "framework",
-      "category": "context",
-      "phase": "proposal",
-      "required": false,
-      "description": "Project-level context with tech stack, active features, agents, standards",
-      "outputName": "CONTEXT.md",
-      "placeholders": [
-        "AGENT_COUNT",
-        "AGENT_TEAMS_DISPLAY_MODE",
-        "AGENT_TEAMS_THRESHOLDS",
-        "APP_INSIGHTS",
-        "AZURE_LOCATION",
-        "CONTAINER_ENV",
-        "COOLIFY_APP_URL",
-        "COOLIFY_SERVER",
-        "DEVOPS_AREA_PATH",
-        "DEVOPS_BUILD_PIPELINE",
-        "DEVOPS_ORG",
-        "DEVOPS_PROJECT",
-        "DEVOPS_RELEASE_PIPELINE",
-        "DEVOPS_WIKI_NAME",
-        "DOTNET_VERSION",
-        "EF_VERSION",
-        "INFERRED_STANDARDS",
-        "MORPH_VERSION",
-        "NEON_PROJECT_ID",
-        "NEON_REGION",
-        "NEXTJS_VERSION",
-        "OPENAI_MODEL",
-        "PROJECT_DESCRIPTION",
-        "PROJECT_NAME",
-        "PROJECT_TYPE",
-        "REPOSITORY_URL",
-        "SQL_DATABASE",
-        "SQL_SERVER",
-        "TIMESTAMP",
-        "UI_LIBRARY"
-      ],
-      "stackSpecific": false,
-      "engine": "handlebars",
-      "deprecated": false,
-      "technology": "handlebars",
-      "validatePlaceholders": true
-    },
     {
       "id": "architecture",
       "kind": "template",
@@ -176,50 +127,6 @@
       "technology": "handlebars",
       "validatePlaceholders": true
     },
-    {
-      "id": "context-feature",
-      "kind": "template",
-      "name": "Feature Context",
-      "path": "context/CONTEXT-FEATURE.md",
-      "location": "framework",
-      "category": "context",
-      "phase": "proposal",
-      "required": false,
-      "description": "Feature-level context with progress, agents, tasks, decisions, validations",
-      "outputName": "CONTEXT-FEATURE.md",
-      "placeholders": [
-        "ACTIVE_AGENTS_COUNT",
-        "AGENT_TEAMS_DECISION",
-        "COMPLEXITY",
-        "CONTRACTS_PATH",
-        "CURRENT_TASK",
-        "DECISIONS_PATH",
-        "DESCRIPTION",
-        "FEATURE_ID",
-        "FEATURE_NAME",
-        "MORPH_VERSION",
-        "PHASE",
-        "PHASE_DESCRIPTION",
-        "PROPOSAL_PATH",
-        "RECAP_PATH",
-        "SPEC_PATH",
-        "STATUS",
-        "TASKS_BLOCKED",
-        "TASKS_COMPLETED",
-        "TASKS_IN_PROGRESS",
-        "TASKS_PATH",
-        "TASKS_PROGRESS",
-        "TASKS_TOTAL",
-        "TEAM_LEAD",
-        "TIMESTAMP",
-        "VALIDATION_TIMESTAMP"
-      ],
-      "stackSpecific": false,
-      "engine": "handlebars",
-      "deprecated": false,
-      "technology": "handlebars",
-      "validatePlaceholders": true
-    },
     {
       "id": "spec-examples",
       "kind": "template",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polymorphism-tech/morph-spec",
-  "version": "8.2.1",
+  "version": "8.4.0",
   "description": "MORPH-SPEC: NLH (Natural Language Harness) for spec-driven development with Claude Code",
   "keywords": [
     "claude-code",

package/src/commands/observability/telemetry.js

@@ -0,0 +1,75 @@
+/**
+ * `morph-spec telemetry [--json] [--feature <name>] [--limit <n>]`
+ *
+ * The reader surface over the harness event stream (.morph/logs/events.jsonl,
+ * written by the telemetry-log hook). Reconstructs the whole execution path of
+ * an NLH session: top skills, personas dispatched, standards (knowledge base)
+ * read, the tool mix, and the recent prompts (user + sub-agent).
+ *
+ * Read-only, always exits 0 (fail-open — an empty stream is an answer).
+ */
+
+import chalk from 'chalk';
+import { loadTelemetry, aggregateTelemetry } from '../../lib/telemetry/telemetry-reader.js';
+
+// The knowledge-base count reflects EXPLICIT reads only. The core standards
+// load via @-refs in rules (Layer 0/1 auto-load) — those are injected by
+// Claude Code's rules system, not via the Read tool, so no hook ever sees them.
+// A low count here means "few on-demand reads", NOT "standards barely used".
+const STANDARDS_CAVEAT =
+  'Só reads explícitos (via Read) são observáveis; standards auto-carregados por @-ref nas rules (Layer 0/1) não passam por tool call e ficam invisíveis aqui.';
+
+function section(title, rows, fmt) {
+  if (!rows.length) return;
+  console.log('\n' + chalk.white.bold(title));
+  for (const r of rows) console.log('  ' + fmt(r));
+}
+
+/**
+ * @param {{ json?: boolean, feature?: string, limit?: number, cwd?: string }} [options]
+ */
+export function telemetryCommand(options = {}) {
+  const events = loadTelemetry(options.cwd || process.cwd());
+  const summary = aggregateTelemetry(events, { feature: options.feature });
+
+  if (options.json) {
+    console.log(JSON.stringify({ ...summary, notes: { standards: STANDARDS_CAVEAT } }));
+    process.exit(0);
+  }
+
+  if (summary.total === 0) {
+    const scope = options.feature ? ` para a feature "${options.feature}"` : '';
+    console.log(chalk.gray(`Telemetria vazia${scope} — nenhum evento capturado ainda em .morph/logs/events.jsonl.`));
+    process.exit(0);
+  }
+
+  const scope = options.feature ? chalk.cyan(` · feature ${options.feature}`) : '';
+  console.log(chalk.white.bold(`Telemetria do harness — ${summary.total} eventos${scope}`));
+  if (summary.features.length) {
+    console.log(chalk.gray(`Features: ${summary.features.join(', ')}`));
+  }
+
+  section('Skills', summary.skills, s => `${chalk.green(s.name.padEnd(24))} ${s.count}`);
+  section('Personas despachadas', summary.personas, p => `${chalk.magenta(p.name.padEnd(24))} ${p.count}`);
+  section('Base de conhecimento (standards lidos explicitamente)', summary.standards,
+    s => `${chalk.yellow(String(s.count).padStart(3))}×  ${s.path}`);
+  if (summary.standards.length || summary.tools.some(t => t.name === 'Read')) {
+    console.log(chalk.gray(`  ⚠ ${STANDARDS_CAVEAT}`));
+  }
+  section('Mix de tools', summary.tools, t => `${t.name.padEnd(16)} ${t.count}`);
+
+  const limit = Number.isInteger(options.limit) && options.limit > 0 ? options.limit : 10;
+  const prompts = summary.prompts.slice(-limit);
+  if (prompts.length) {
+    console.log('\n' + chalk.white.bold(`Prompts (últimos ${prompts.length})`));
+    for (const p of prompts) {
+      const tag = p.source === 'user' ? chalk.blue('user ') : chalk.magenta('agent');
+      const where = p.feature ? chalk.gray(` [${p.feature}/${p.phase || '-'}]`) : '';
+      const oneLine = String(p.text || '').replace(/\s+/g, ' ').trim();
+      const preview = oneLine.length > 120 ? oneLine.slice(0, 117) + '...' : oneLine;
+      console.log(`  ${tag}${where} ${preview}`);
+    }
+  }
+
+  process.exit(0);
+}

package/src/commands/project/doctor.js

@@ -14,6 +14,7 @@ import {
 import { resetMorphSettings } from '../../utils/claude-settings-manager.js';
 import { checkMissingAgents, checkAgentsDrift } from '../../utils/agents-installer.js';
 import { getProjectTags } from '../../lib/stack-filter.js';
+import { auditFeatureLifecycle } from '../../core/state/lifecycle-audit.js';
 
 const isWindows = platform() === 'win32';
 /**
@@ -896,6 +897,22 @@ export async function doctorCommand(options = {}) {
     hasWarnings = true;
   }
 
+  // Feature-lifecycle consistency — the consolidated inconsistency report:
+  // gate-order violations (N approved with N-1 pending), identity-less
+  // features (no description), orphan folders and stale index entries. Warn
+  // only (advisory); the per-feature detail is printed after the summary.
+  const lifecycleIssues = auditFeatureLifecycle(targetPath);
+  if (lifecycleIssues.length === 0) {
+    checks.push({ name: 'feature lifecycle', status: 'ok' });
+  } else {
+    checks.push({
+      name: 'feature lifecycle',
+      status: 'warn',
+      msg: `${lifecycleIssues.length} inconsistenc${lifecycleIssues.length === 1 ? 'y' : 'ies'} (see below)`,
+    });
+    hasWarnings = true;
+  }
+
   // Check key templates exist (in framework package, not project copy)
   const frameworkTemplatesRoot = join(import.meta.dirname, '..', '..', '..', 'framework', 'templates');
   const keyTemplates = [
@@ -944,6 +961,17 @@ export async function doctorCommand(options = {}) {
     }
   }
 
+  // Per-feature detail for the lifecycle inconsistencies (item: doctor lists
+  // what's already wrong in the repo, e.g. plan approved with proposal pending).
+  if (lifecycleIssues.length) {
+    logger.blank();
+    console.log(chalk.yellow('  Feature lifecycle inconsistencies:'));
+    for (const issue of lifecycleIssues) {
+      console.log(chalk.gray(`    • ${issue.feature} [${issue.type}] — ${issue.detail}`));
+    }
+    console.log(chalk.gray("    Fix: 'morph-spec approve' (order), '--description' on create, or 'morph-spec delete' for dead scaffolds."));
+  }
+
   logger.blank();
 
   if (hasErrors) {

package/src/commands/state/advance.js

@@ -2,6 +2,7 @@ import chalk from 'chalk';
 import { existsSync, mkdirSync } from 'fs';
 import { join } from 'path';
 import { getFeature, setApprovalGate, derivePhase } from '../../core/state/state-manager.js';
+import { unmetPrereqs } from '../../core/state/gate-order.js';
 
 /**
  * `morph-spec advance <feature>` — approve the current phase's gate AND scaffold
@@ -57,6 +58,22 @@ export async function advanceCommand(featureName, options = {}) {
     const gate = PHASE_GATE[phase];
     const approvedBy = resolveApprovedBy(options);
 
+    // Gate monotonicity (mirrors approve.js): advance is a gate write-path too,
+    // so it must not stamp gate N while a predecessor is pending. In the
+    // sanctioned flow advance is always in-order (it approves G1 before the plan
+    // artifact that flips the phase to plan exists), but an anomalous filesystem
+    // state — e.g. 2-plan/spec.md present without Gate 1, the lead-termometro
+    // shape — would otherwise let advance deepen the violation by stamping G2.
+    // Escape via --force for deliberate recovery.
+    if (gate) {
+      const unmet = unmetPrereqs(gate, feature.approvalGates);
+      if (unmet.length && !options.force) {
+        console.error(chalk.red(`\n❌ Cannot advance past the ${phase} phase — prerequisite gate(s) not approved: ${unmet.join(', ')}.`));
+        console.error(chalk.gray(`   Gates must be approved in order (${unmet.join(' → ')} → ${gate}). Approve them first, or pass --force.\n`));
+        process.exit(1);
+      }
+    }
+
     // Hotfix backstop (defensive, mirrors approve.js): the phase==='review'
     // early-return above already stops advance from ever reaching a
     // gate==='review' approval, but guard the approval itself too so this

package/src/commands/state/approve.js

@@ -3,6 +3,7 @@ import chalk from 'chalk';
 import { existsSync } from 'fs';
 import { join } from 'path';
 import { getFeature, setApprovalGate, getApprovalGate, getApprovalHistory, derivePhase } from '../../core/state/state-manager.js';
+import { unmetPrereqs } from '../../core/state/gate-order.js';
 
 /**
  * Unapprove action function - Revoke a previously approved gate
@@ -99,6 +100,18 @@ export async function approveCommand(featureName, gateName, options = {}) {
       return;
     }
 
+    // Gate monotonicity: a gate may only be approved once its predecessors are
+    // approved (proposal → plan → review; uiux requires proposal). Prevents the
+    // lead-termometro shape — plan.approved with proposal pending. Policy-stamped
+    // gates count as approved, so chore/hotfix satisfy prereqs naturally.
+    // Escape via --force for deliberate recovery.
+    const unmet = unmetPrereqs(gateName, feature.approvalGates);
+    if (unmet.length && !options.force) {
+      console.error(chalk.red(`\n❌ Cannot approve "${gateName}" — prerequisite gate(s) not approved: ${unmet.join(', ')}.`));
+      console.log(chalk.gray(`   Gates must be approved in order (${unmet.map((u) => u).join(' → ')} → ${gateName}). Approve them first, or pass --force.\n`));
+      process.exit(1);
+    }
+
     // Resolve who approved BEFORE the hotfix backstop — the backstop gates on
     // the resolved signature, not the raw --mode string (see below).
     //

package/src/commands/state/create.js

@@ -1,5 +1,5 @@
 import chalk from 'chalk';
-import { mkdirSync, cpSync, readFileSync, writeFileSync } from 'fs';
+import { mkdirSync, cpSync, readFileSync, writeFileSync, existsSync } from 'fs';
 import { join } from 'path';
 import { createFeature, setApprovalGate, getFeature } from '../../core/state/state-manager.js';
 import { WORK_TYPES, DEFAULT_WORK_TYPE, POLICY_APPROVER_PREFIX, isValidWorkType, getWorkType } from '../../core/work-types.js';
@@ -98,10 +98,30 @@ export async function createCommand(featureName, options = {}) {
     const now = new Date().toISOString();
     const { workType, workTypeDetection } = resolveWorkType(options, now);
 
+    // Identity at birth: every feature is stamped name (slug by default) +
+    // description, so it is never an anonymous {status,updatedAt} shell.
+    // `--request` (which the router already consumes) doubles as the
+    // description seed. A NEW feature with no description source is refused —
+    // the description is the one identity field a human must supply. An
+    // idempotent re-run on an EXISTING feature never demands it.
+    const description = options.description ?? options.request ?? null;
+    // Existence check via the filesystem, NOT getFeature/loadState — loadState
+    // throws when no state exists yet (a feature can be the first morph action
+    // in a fresh project), which would break birth-from-nothing.
+    const alreadyExists = existsSync(join(process.cwd(), '.morph', 'features', featureName, 'feature.json'));
+    if (!alreadyExists && (description === null || String(description).trim() === '')) {
+      console.error(chalk.red(`\n❌ A feature needs a description at birth: "${featureName}"`));
+      console.error(chalk.gray('   Pass --description "<what/why>" (or --request "<pedido>", which seeds it).'));
+      console.error(chalk.gray('   This keeps features identifiable — no more anonymous scaffolds.\n'));
+      process.exit(1);
+    }
+
     const { feature, created } = await createFeature(featureName, {
       status: options.status,
       workType,
       workTypeDetection,
+      name: options.name,
+      description: description ?? undefined,
     });
 
     const featureDir = join(process.cwd(), '.morph', 'features', featureName);