arkaos 2.19.1 → 2.19.2

package/VERSION

@@ -1 +1 @@
-2.19.1
+2.19.2

package/arka/SKILL.md

@@ -12,6 +12,50 @@ allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 > **The Operating System for AI Agent Teams**
 > 65 agents. 17 departments. 244+ skills. Multi-runtime. Dashboard. Knowledge RAG.
 
+## ⛔ Enforcement contract (read before responding)
+
+This overrides every default. If the UserPromptSubmit hook injected a
+`[ARKA:WORKFLOW-REQUIRED]` tag, you MUST, on the first line of your reply:
+
+```
+[arka:routing] <department-slug> -> <lead-agent>
+```
+
+Example first lines (pick the right department for the ask):
+
+- `[arka:routing] dev -> Paulo` — code, features, refactors, tests
+- `[arka:routing] brand -> Valentina` — identity, design, logos, voice
+- `[arka:routing] kb -> Clara` — knowledge base, research, Obsidian
+- `[arka:routing] mkt -> Luna` — marketing, growth, SEO, campaigns
+- `[arka:routing] content -> Rafael` — content, video, social, copy
+- `[arka:routing] landing -> Ines` — landing pages, funnels, offers
+- `[arka:routing] ecom -> Ricardo` — e-commerce, stores, conversion
+- `[arka:routing] saas -> Tiago` — SaaS, validation, PLG, metrics
+- `[arka:routing] sales -> Miguel` — pipeline, discovery, negotiation
+- `[arka:routing] pm -> Carolina` — roadmap, sprints, backlog, stories
+- `[arka:routing] ops -> Daniel` — automation, SOPs, workflows
+- `[arka:routing] strat -> Tomas` — strategy, positioning, moats
+- `[arka:routing] fin -> Helena` — finance, modeling, budgets
+- `[arka:routing] lead -> Rodrigo` — team health, feedback, hiring
+- `[arka:routing] org -> Sofia` — org design, COO, operations
+- `[arka:routing] community -> Beatriz` — communities, platforms, retention
+
+After the routing line, in order:
+
+1. State the workflow name and its phase count.
+2. Run Phase 1 (usually spec via `arka-spec` or plan via `arka-forge`) BEFORE writing any code.
+3. Execute sequential phases with visibility (one at a time, report status).
+4. Run the Quality Gate (Marta CQO + Eduardo Copy + Francisca Tech, model Opus) BEFORE marking done.
+
+The only exception is a trivial 1-file edit under 10 lines. In that case emit:
+
+```
+[arka:trivial] <one-sentence reason>
+```
+
+and proceed directly. Anything else without a routing line is a constitution
+violation (squad-routing, arka-supremacy, spec-driven, mandatory-qa).
+
 ## System Commands
 
 | Command | Description |

package/config/hooks/user-prompt-submit.sh

@@ -275,8 +275,41 @@ NO generic assistant replies. Announce the squad before responding.
 When [knowledge:N chunks] is present, cite at least one source.
 If [knowledge:N chunks] is absent on a non-trivial ArkaOS topic, query Obsidian first."
 
+# ─── Workflow Classifier (hard enforcement for creation/implementation) ──
+# Classifies the user prompt. If it looks like a creation/implementation/
+# modification request that is NOT already routed with an explicit /prefix,
+# emits a directive that the agent MUST acknowledge with [arka:routing]
+# BEFORE using any write tool. Trivial quick questions pass through
+# untouched. Explicit slash commands pass through untouched.
+_WORKFLOW_DIRECTIVE=""
+if [ -n "$user_input" ]; then
+  # Skip: explicit slash command (already routed)
+  _FIRST_CHAR=$(echo "$user_input" | head -c 1)
+  if [ "$_FIRST_CHAR" != "/" ] && [ "$_FIRST_CHAR" != "!" ]; then
+    # Match creation/implementation verbs in EN and PT (case-insensitive).
+    _VERB_PATTERN='(criar?|crie[ms]?|cria[mr]?|adicionar?|adiciona[mr]?|implementar?|implementa[mr]?|desenvolver?|desenvolve[mr]?|construir?|constru[ií]a?[mr]?|fazer?|faz[ae][mr]?|refactor(izar?)?|corrigir?|corrige[mr]?|consertar?|conserta[mr]?|create[sd]?|creating|build(s|ing)?|add(s|ed|ing)?|implement(s|ed|ing)?|develop(s|ed|ing)?|fix(es|ed|ing)?|refactor(s|ed|ing)?|make[sd]?|making)'
+    _NOUN_PATTERN='(feature|funcionalidade|skill|squad|agent[e]?|workflow|endpoint|api|component[e]?|module|m[oó]dulo|page|p[aá]gina|hook|pipeline|integration|integra[cç][aã]o|dashboard|report|report[eó]|script|test[es]?)'
+    if echo "$user_input" | grep -qiE "\b${_VERB_PATTERN}\b"; then
+      _WORKFLOW_DIRECTIVE="
+[ARKA:WORKFLOW-REQUIRED] Your user request matched a CREATION/IMPLEMENTATION pattern.
+You MUST, before using any Write, Edit, Bash with side-effects, or Agent tool:
+  1. Output on the first line: [arka:routing] <department-slug> -> <lead-agent>
+     (e.g. [arka:routing] dev -> Paulo, [arka:routing] brand -> Valentina,
+      [arka:routing] kb -> Clara, [arka:routing] mkt -> Luna)
+  2. State the workflow name and phase count in one short sentence.
+  3. Begin phase 1 (spec or plan) BEFORE any code is written.
+  4. Run the Quality Gate (Marta + Eduardo + Francisca, Opus) before claiming done.
+Trivial override: if the request is a single-file edit under 10 lines AND the user
+used an imperative like 'rename X', 'fix typo', you MAY emit [arka:trivial] <reason>
+and proceed directly. Anything else requires routing. This is enforced, not advisory.
+Skipping routing violates constitution rules squad-routing, arka-supremacy,
+spec-driven, mandatory-qa, sequential-validation."
+    fi
+  fi
+fi
+
 # ─── Output ──────────────────────────────────────────────────────────────
-_OUT_CONTEXT="${_ARKA_GREETING:-}${_SYNC_NOTICE:-}${_ROUTE_REMINDER} $python_result"
+_OUT_CONTEXT="${_ARKA_GREETING:-}${_SYNC_NOTICE:-}${_ROUTE_REMINDER}${_WORKFLOW_DIRECTIVE} $python_result"
 [ -n "$_HYGIENE" ] && _OUT_CONTEXT="$_OUT_CONTEXT $_HYGIENE"
 # Escape for JSON
 _OUT_JSON=$(python3 -c "import json,sys; print(json.dumps(sys.stdin.read()))" <<< "$_OUT_CONTEXT" 2>/dev/null)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arkaos",
-  "version": "2.19.1",
+  "version": "2.19.2",
   "description": "The Operating System for AI Agent Teams",
   "type": "module",
   "bin": {

package/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "arkaos-core"
-version = "2.19.1"
+version = "2.19.2"
 description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
 readme = "README.md"
 license = {text = "MIT"}