aiwg 2026.6.12 → 2026.7.0

package/agentic/code/addons/agentic-installer/rules/RULES-INDEX.md

@@ -9,13 +9,11 @@ Safety and authoring rules for the `setup.aiwg.io/v1` SetupManifest language and
 ### HIGH
 
 #### installer-safety
-**Summary**: 7 mandatory safety behaviors for installer-agent and setup-run: show before run, confirm destructive operations, validate schema before execution, treat agentic steps as exception-handling only, collect all required params before execution begins, never put secrets in manifests, and treat platform mismatches as skips not errors.
-**When to apply**: Executing any SetupManifest, generating manifests, implementing setup-run or setup-validate skills, reviewing installer output for safety compliance
+**Summary**: 7 mandatory safety behaviors for installer-agent and setup-run: show before run, confirm destructive operations, validate schema before execution, treat agentic steps as exception-handling only, collect all required params before execution…
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/agentic-installer/rules/installer-safety.md
 
 #### installer-authoring
-**Summary**: 5 authoring rules for SetupManifest files and script templates: script-first design (agentic steps are exception handling only), always source lib scripts in bash/PowerShell templates, manifests describe while scripts act, one manifest per logical installation unit, every manifest needs a recovery procedure.
-**When to apply**: Writing or reviewing setup.manifest.yaml files, generating script templates, authoring setup-generate skill output, code review of installer artifacts
+**Summary**: 5 authoring rules for SetupManifest files and script templates: script-first design (agentic steps are exception handling only), always source lib scripts in bash/PowerShell templates, manifests describe while scripts act, one manifest per…
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/agentic-installer/rules/installer-authoring.md
 
 ---

package/agentic/code/addons/agentic-installer/rules/installer-authoring.md

@@ -1,4 +1,5 @@
 ---
+enforcement: high
 name: installer-authoring
 description: Authoring rules for setup.aiwg.io/v1 SetupManifest files and script templates. Enforces script-first design, template reuse, and consistent manifest structure.
 type: feedback
@@ -7,6 +8,7 @@ priority: HIGH
 
 # Installer Authoring Rules
 
+**Enforcement Level**: HIGH
 Rules for writing `setup.aiwg.io/v1` SetupManifest files and their accompanying scripts.
 
 ## Rule 1: Script-First Design

package/agentic/code/addons/agentic-installer/rules/installer-safety.md

@@ -1,4 +1,5 @@
 ---
+enforcement: high
 name: installer-safety
 description: Mandatory safety behaviors for the installer-agent and setup-run skill. Prevents destructive actions, enforces user authorization, and protects against script injection.
 type: feedback
@@ -7,6 +8,7 @@ priority: HIGH
 
 # Installer Safety Rules
 
+**Enforcement Level**: HIGH
 Mandatory behaviors for all agents and skills operating on `setup.aiwg.io/v1` manifests.
 
 ## Rule 1: Show Before Run

package/agentic/code/addons/aiwg-dev/rules/addon-boundaries.md

@@ -1,3 +1,7 @@
+---
+enforcement: medium
+---
+
 # Addon Boundaries
 
 **Enforcement Level**: MEDIUM

package/agentic/code/addons/aiwg-dev/rules/aiwg-ci-safety.md

@@ -1,3 +1,7 @@
+---
+enforcement: high
+---
+
 # AIWG CI Safety
 
 **Enforcement Level**: HIGH

package/agentic/code/addons/aiwg-dev/rules/aiwg-dir-reference-contract.md

@@ -1,3 +1,7 @@
+---
+enforcement: medium
+---
+
 # AIWG Directory Reference Contract
 
 **Enforcement Level**: MEDIUM

package/agentic/code/addons/aiwg-dev/rules/component-completeness.md

@@ -1,3 +1,7 @@
+---
+enforcement: medium
+---
+
 # Component Completeness Rules
 
 **Enforcement Level**: MEDIUM

package/agentic/code/addons/aiwg-dev/rules/no-circular-skill-calls.md

@@ -1,3 +1,7 @@
+---
+enforcement: high
+---
+
 # No Circular Skill Calls
 
 **Enforcement Level**: HIGH

package/agentic/code/addons/aiwg-dev/rules/skill-placement.md

@@ -1,3 +1,7 @@
+---
+enforcement: high
+---
+
 # Skill Placement Rules
 
 **Enforcement Level**: HIGH

package/agentic/code/addons/aiwg-utils/rules/RULES-INDEX.md

@@ -9,140 +9,113 @@ Core meta-utility rules for agent coordination, context management, and platform
 ### HIGH
 
 #### auto-compact-continue
-**Summary**: The answer to "should I keep working?" is always YES — until the task's measurable completion criteria are met or the user redirects. Context pressure, long tool outputs, and high iteration counts are not scope questions. When context fills, the right response is to compact, checkpoint to durable storage (activity log, progress file at `.aiwg/working/<task>-progress.md`, git history, AIWG memory), and continue. Trust platform auto-compact (REF-910); load-bearing state must live in `CLAUDE.md` / `AGENTS.md` / `AIWG.md` / activity log / progress file / git / `.aiwg/working/` — never only in conversation turns. Maintain a `## Compact Instructions` section so the summarizer preserves completion criteria, last successful step, failed approaches (do not let them be re-attempted), and authorization questions. Apply aggressive in-session compression (REF-122: passive=6% savings, aggressive=22.7%); update the progress file every 10–15 tool calls on long tasks. Exceptions: authorization gates (per `human-authorization`), 3-attempts-failed escalation (per `anti-laziness` Rule 6), explicit user redirect, genuinely ambiguous new directive classification (per `skill-discovery` Rule 0). "Should I continue?" is never the right question.
-**When to apply**: Any long-running session; before context fills; after long tool outputs; when crossing iteration thresholds; when resuming after compaction; when tempted to ask the user permission to keep going
+**Summary**: The answer to "should I keep working?" is always YES — until the task's measurable completion criteria are met or the user redirects.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/auto-compact-continue.md
 
 #### cli-secondary
-**Summary**: AIWG is agentic-first. The agent's strict priority order for any action: (1) **local skill** already loaded in context (kernel skills, framework quickrefs, deployed agents), (2) **discovered skill** via `aiwg discover` + `aiwg show`, (3) raw CLI command, (4) manual file edits as last resort. Raw CLI commands augment skill workflows; they do not replace skills. The skill carries the priming (pre-flight checks, dry-run preview, preservation logic, gates) and owns orchestration, final formatting, presentation, synthesis, and recovery that the CLI alone lacks. Sole exception: discovery/finder commands (`aiwg discover`, `aiwg show`, `aiwg list`, `aiwg status`, `aiwg version`, `aiwg runtime-info`, status/info subcommands) stay primary — they ARE the priming entry points and the bridge from priority 2 to priority 1. For mixed commands (`aiwg index`, `aiwg packages`, `aiwg ops`, `aiwg storage`), classify per subcommand. Includes a pairing table covering use/refresh/regenerate/doctor/init/promote/scaffold-*/add-*/doc-sync/lint/cleanup-audit/sdlc-accelerate/ralph/mc/steward/index build/ops actions/storage migrate.
-**When to apply**: Before invoking any AIWG CLI command, before writing skill/agent docs that reference CLI commands, when updating quickrefs or routing tables, when filing pairings audits
+**Summary**: AIWG is agentic-first.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/cli-secondary.md
 
 #### no-time-estimates
-**Summary**: Never produce wall-clock time estimates in AI-assisted work contexts. Human+AI development velocity is unknowable and varies non-linearly with operator skill, model quality, task decomposability, and centaur configuration. Instead, express effort in agent-oriented units: scope count (atomic deliverables), agent count and roles, parallelism map (parallel vs sequential batches), and pass estimate (iterations to quality gate). Prohibited phrases include "N days/hours/weeks," "expected duration," and "this should be quick."
-**When to apply**: Planning, task decomposition, sprint estimation, phase planning, completion reports, responding to "how long will this take?" questions
+**Summary**: Never produce wall-clock time estimates in AI-assisted work contexts.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/no-time-estimates.md
 
 #### god-session
-**Summary**: A single agent that tries to do everything — research, implement, test, document, deploy — is a god session. God sessions are hard to debug, impossible to parallelize, and produce inconsistent results. Agent definitions must have a focused scope of ≤5–7 distinct responsibilities. When an agent discovers adjacent work mid-session, file issues rather than absorbing them.
-**When to apply**: Agent definition creation, reviewing agent scope, mid-session scope creep detection, multi-domain task planning
+**Summary**: A single agent that tries to do everything — research, implement, test, document, deploy — is a god session.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/god-session.md
 
 #### vague-discretion
-**Summary**: Loop termination conditions and quality gates must be concrete and measurable. Vague conditions — "good enough", "zero bugs", "comprehensive", "thorough" — cannot be evaluated consistently and cause infinite loops, premature exits, or wildly varying quality. Replace with specific thresholds, counts, or verifiable outcomes. Every loop must also have a `max-cycles` or `max-iterations` escape hatch.
-**When to apply**: Writing skill loop conditions, Ralph completion criteria, phase gate criteria, quality rubrics, any "done when" specification
+**Summary**: Loop termination conditions and quality gates must be concrete and measurable.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/vague-discretion.md
 
 #### subagent-scoping
-**Summary**: Each subagent gets ONE focused task with minimal context. Decompose complex work into parallel subagents rather than overloading one. Prompt budget <20% of context window per subagent. No delegation chains deeper than 2 levels. Spawn many focused subagents over few overloaded ones. When `AIWG_CONTEXT_WINDOW` is set, concurrent parallel count must respect the budget limit.
-**When to apply**: Task delegation, subagent spawning, parallel dispatch, orchestrator fan-out, context budget planning
+**Summary**: Each subagent gets ONE focused task with minimal context.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/subagent-scoping.md
 
 #### instruction-comprehension
-**Summary**: Fully parse and confirm understanding of all user instructions before acting. Extract constraints (prohibitions first), then requirements, then preferences. Track multi-part requests to completion. Re-read original instructions on failure instead of guessing. Prevent instruction drift on long tasks by periodically re-checking against original requirements. Never override user preferences with "best practices."
-**When to apply**: Every user request, multi-part tasks, specification compliance, instruction drift detection, correction handling
+**Summary**: Fully parse and confirm understanding of all user instructions before acting.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/instruction-comprehension.md
 
 #### research-before-decision
-**Summary**: Research codebase, docs, and sources before making technical decisions. Prevents guessing APIs, blind retries, and missing context. Pattern: IDENTIFY > SEARCH > EXTRACT > REASON > ACT > VERIFY. When an action fails, research the root cause instead of retrying with variations (whack-a-mole detection). Read error messages completely — they frequently contain the answer. Check existing project patterns before creating new ones.
-**When to apply**: Technical decision-making, API usage, configuration changes, dependency selection, error diagnosis, import resolution
+**Summary**: Research codebase, docs, and sources before making technical decisions.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md
 
 #### escalation-discipline
-**Summary**: Agents must summarize before moving above their declared default model tier, confirm Tier 3 explicitly, and never auto-escalate unattended bots to premium tiers. Escalation confirmation is a human-authorization gate: state the need, target tier, and bounded next task before spending higher-tier tokens or routing to a stronger agent.
-**When to apply**: Model-tier routing, budget-sensitive agents, unattended bots, requests for deep/debug/thorough work, high-impact legal/financial/medical/security work, any recommendation to use a stronger or premium model
+**Summary**: Agents must summarize before moving above their declared default model tier, confirm Tier 3 explicitly, and never auto-escalate unattended bots to premium tiers.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/escalation-discipline.md
 
 #### tool-quota
-**Summary**: Tool-using agents must track per-session tool calls, stop repeating similar failed calls without progress, and honor `tool_quota` / `loop_detection` declarations when present. Defaults: same failing call retries <=3, similar-call window <=5, one tool <=30 calls in a focused session, high-cost external tools <=10. When a quota would be exceeded, summarize attempts, facts learned, and the narrow next action instead of continuing an unbounded loop.
-**When to apply**: Tool-heavy sessions, unattended bots, repeated tool failures, external fetch loops, shell retry loops, agent definitions with `tool_quota` or `loop_detection`
+**Summary**: Tool-using agents must track per-session tool calls, stop repeating similar failed calls without progress, and honor `tool_quota` / `loop_detection` declarations when present.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/tool-quota.md
 
 #### quiet-mode
-**Summary**: Chat and bot agents in group rooms should respond only when mentioned, replied to, or invoked by a direct command. Multi-bot rooms require yielding to the specifically addressed bot. Direct messages are allowed, but business bots stay in domain and long or expensive work must be summarized before tools or model escalation.
-**When to apply**: Telegram/group-chat bots, multi-bot rooms, DMs to business bots, scheduled chat agents, ambient room listeners, platforms without native behavior support
+**Summary**: Chat and bot agents in group rooms should respond only when mentioned, replied to, or invoked by a direct command.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/quiet-mode.md
 
 #### respect-repo-access-manifest
-**Summary**: Tool capability is not authorization. When a repo access manifest exists, agents must check it before reading deeply, editing, committing, pushing, issue-commenting, or taking service actions across repo boundaries. Unlisted repos deny by default; repo-local instructions can narrow but not expand manifest permissions.
-**When to apply**: Multi-repo workspaces, adjacent repo handoffs, issue comments in sibling repos, commits/pushes, service actions, any work outside the current repo root
+**Summary**: Tool capability is not authorization.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/respect-repo-access-manifest.md
 
 #### skill-discovery
-**Summary**: Most AIWG skills are NOT loaded into your context — only the kernel set (framework quickrefs + core utilities). The bulk lives at `<provider-dir>/.aiwg/skills/` and is reachable only through the artifact index. The **discover-first protocol** (Rule 1.5) mandates that `aiwg discover` MUST be the first information-gathering tool call for any query mentioning AIWG, framework names (sdlc/research/forensics/ops/security-engineering/marketing/media-curator/knowledge-base), or capability keywords (skill/agent/rule/command/addon/workflow). Filesystem `Grep`/`Glob`/`Read` against `.claude/`, `.factory/`, `.codex/`, `.warp/`, `.cursor/`, `.windsurf/`, `.opencode/`, `~/.hermes/`, `~/.openclaw/`, or `agentic/code/` is FORBIDDEN for AIWG-related lookups until discover has been consulted. When subagent delegation is available, prefer the `aiwg-finder` subagent. You must also query discover before declining a request as out-of-scope or improvising a custom workflow.
-**When to apply**: ANY query mentioning AIWG, a framework name, or a capability keyword (skill/agent/rule/command); before any filesystem search on provider artifact directories; before declining as out-of-scope; before improvising a custom workflow when an AIWG skill might exist
+**Summary**: Most AIWG skills are NOT loaded into your context — only the kernel set (framework quickrefs + core utilities).
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/skill-discovery.md
 
 #### native-ux-tools
-**Summary**: Agents MUST prefer platform-native interaction tools (e.g., AskUserQuestion in Claude Code) over plain text output for interactive questions. Check tool availability before asking, fall back to formatted markdown if unavailable. One question per interaction turn. Includes platform capability matrix for all 8 supported platforms.
-**When to apply**: Interactive commands (--interactive flag), decision gates, user confirmations, intake wizards, any agent question
+**Summary**: Agents MUST prefer platform-native interaction tools (e.g., AskUserQuestion in Claude Code) over plain text output for interactive questions.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/native-ux-tools.md
 
 #### human-authorization
-**Summary**: Agents must seek explicit human authorization before irreversible or high-stakes actions — especially when those actions are implied by findings rather than explicitly requested. A recommendation is not authorization to act. Covers: removal of artifacts, scope expansion beyond task, closing work items with implied resolution, acting on research findings. Pattern: discover → report → await authorization → act. Agents must proactively recognize scope boundaries; don't rely on system-level friction as the only gate.
-**When to apply**: Any action not explicitly stated in the task, removal of files/artifacts/components, scope expansion, closing issues, acting on review findings or recommendations, changes to shared resources
+**Summary**: Agents must seek explicit human authorization before irreversible or high-stakes actions — especially when those actions are implied by findings rather than explicitly requested.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/human-authorization.md
 
 #### delivery-policy
-**Summary**: AIWG projects declare their git workflow in `.aiwg/aiwg.config` `delivery` block (`mode`: direct / feature-branch / pr-required, `default_branch`, `require_ci_green`, `force_push_policy`, `auto_close_issues`). Agents MUST read this before recommending or executing branch/PR/commit actions. `direct` = commit straight to main with `Closes #N`; `feature-branch` = branch only; `pr-required` = branch + PR + review. Use configured `remotes.{primary,issue_tracker,ci}` rather than guessing. Don't ask the user to pick a workflow when the config already answers it.
-**When to apply**: Any branch creation, PR opening, push to default_branch, force-push, issue closure via commit message, interactive question about git workflow
+**Summary**: AIWG projects declare their git workflow in `.aiwg/aiwg.config` `delivery` block (`mode`: direct / feature-branch / pr-required, `default_branch`, `require_ci_green`, `force_push_policy`, `auto_close_issues`).
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/delivery-policy.md
 
 #### sdlc-right-sizing
-**Summary**: Match SDLC artifacts to the actual scope of change. Most work doesn't need intake or full Inception — bugfixes and small/medium features warrant only an issue and maybe an ADR. Reserve intake/Inception/phase-gate flows for substantial new work meeting ≥2 trigger criteria (new deployable artifact, multi-component, stakeholders beyond requester, contract change, multi-phase span, refactor >20% of a component, or explicit user request). When unsure, ask ONE specific question — don't present multi-option menus of "intake/plan/ADR/full pipeline." ADRs are cheap and encouraged independent of intake. Issues are the default unit of work. The `sdlc-orchestration` rule layers right-sizing in as Step 0 before any flow launch.
-**When to apply**: Before invoking intake-wizard, intake-start, or any SDLC flow command; whenever an agent is tempted to escalate a small change into formal SDLC pipeline work; when interpreting user requests for "features" / "planning" / "what would it take to..."
+**Summary**: Match SDLC artifacts to the actual scope of change.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/sdlc-right-sizing.md
 
 ### MEDIUM
 
 #### context-bloat
-**Summary**: Sub-agents should receive only the context directly relevant to their task. Pass file paths (not file contents) when the agent will read files itself. Do not forward conversation history — sub-agents are clean-slate processes. Before dispatching, audit the prompt: if >50% is background rather than task-critical information, trim aggressively. Complements `subagent-scoping` with a cost-focused lens on information quantity.
-**When to apply**: Sub-agent prompt construction, orchestrator fan-out, multi-agent chaining, cost optimization reviews
+**Summary**: Sub-agents should receive only the context directly relevant to their task.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/context-bloat.md
 
 #### parallel-then-synthesize
-**Summary**: Spawning parallel agents for *related* analytical work that feeds one conclusion often produces lower quality than a single focused agent — coordination overhead and context fragmentation outweigh parallelism benefits. Parallelism is correct when tasks are genuinely independent (each agent's output stands alone). It is counterproductive when the synthesis step requires choosing between conflicting assessments rather than combining complementary outputs.
-**When to apply**: Designing parallel dispatch patterns, analytical workflows, deciding when to parallelize vs. single-agent, RLM divide-conquer design
+**Summary**: Spawning parallel agents for *related* analytical work that feeds one conclusion often produces lower quality than a single focused agent — coordination overhead and context fragmentation outweigh parallelism benefits.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/parallel-then-synthesize.md
 
 #### implicit-dependencies
-**Summary**: Sub-agents must receive all required context explicitly — they have no access to the parent session's conversation, prior agent outputs, or any context not in their prompt. Never assume a sub-agent will "remember" what was discussed earlier. Pass prior outputs explicitly when chaining agents. The inverse of context-bloat: this rule prevents giving too little context.
-**When to apply**: Sub-agent prompt construction, agent chaining, orchestrator fan-out, any time prior session knowledge needs to carry forward
+**Summary**: Sub-agents must receive all required context explicitly — they have no access to the parent session's conversation, prior agent outputs, or any context not in their prompt.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/implicit-dependencies.md
 
 #### context-budget
-**Summary**: When `AIWG_CONTEXT_WINDOW` is set in project context, agents must respect the declared context budget for parallel subagent spawning. Opt-in directive with lookup tables: max parallel count scales from 1 (32k) to 20 (512k+). Formula: `max(1, floor(context_window / 50000))`. Includes compaction guidance per tier (aggressive, moderate, standard, relaxed) and per-subagent output size targets.
-**When to apply**: Parallel subagent spawning, task scheduling, agent loop batching, orchestrator fan-out on constrained systems
+**Summary**: When `AIWG_CONTEXT_WINDOW` is set in project context, agents must respect the declared context budget for parallel subagent spawning.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/context-budget.md
 
 #### diagram-generation
-**Summary**: Diagram generation is a standard output alongside every major documentation artifact. Defines required diagram types per artifact (C4 for SAD, ER for data models, sequence for APIs, DFD for threat models). MermaidJS is default; PlantUML for C4/formal UML. Source must be committed alongside rendered output. Max 15 nodes per diagram; split into sub-diagrams if more complex.
-**When to apply**: Architecture documentation, threat modeling, API design, deployment planning, any artifact with visual communication needs
+**Summary**: Diagram generation is a standard output alongside every major documentation artifact.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/diagram-generation.md
 
 #### agent-deployment
-**Summary**: Rules for working with agent definitions and multi-provider deployment. Covers the agent ecosystem (general-purpose, SDLC, marketing), deployment commands for all 8 platforms, model override configuration, agent metadata structure (YAML frontmatter with name, model, tools, category), tool selection guidelines per task type, and parallel execution patterns with agent isolation.
-**When to apply**: Agent definition creation, multi-provider deployment, tool selection for agents, parallel agent execution
+**Summary**: Rules for working with agent definitions and multi-provider deployment.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/agent-deployment.md
 
 #### activity-log
-**Summary**: Agents must append a single-line entry to `.aiwg/activity.log` after completing any create, update, delete, ingest, deploy, archive, promote, lint, or actioned query operation on AIWG artifacts. Format: `## [YYYY-MM-DD HH:MM] <operation> | <summary>`. Entries are appended only after successful operations; log write failures are non-blocking. Produces a unified cross-framework timeline queryable via `aiwg activity-log`.
-**When to apply**: Any agent that writes, removes, or promotes artifacts in `.aiwg/`; post-deploy steps; lint/validation passes; archive operations
+**Summary**: Agents must append a single-line entry to `.aiwg/activity.log` after completing any create, update, delete, ingest, deploy, archive, promote, lint, or actioned query operation on AIWG artifacts.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/activity-log.md
 
 #### debug-source-not-output
-**Summary**: When debugging in multi-project or monorepo contexts, agents must navigate to the originating source code rather than analyze build artifacts (minified JS, compiled bundles, vendored output). The source project is the right place to investigate; output is downstream of the bug. Detect output paths (`dist/`, `build/`, `node_modules/`, `*.min.*`) and map back to the source project before reasoning.
-**When to apply**: Debugging in monorepos, investigating issues in installed npm/cargo packages, tracing errors that surface in compiled artifacts
+**Summary**: When debugging in multi-project or monorepo contexts, agents must navigate to the originating source code rather than analyze build artifacts (minified JS, compiled bundles, vendored output).
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/debug-source-not-output.md
 
 #### post-commit-index-refresh
-**Summary**: After a successful git commit, check whether artifact indices are configured (`.aiwg/index/`) and rebuild any indices whose source paths were touched by the commit. Stale indices cause `aiwg index query` to return outdated results, mislead downstream agents, and silently corrupt traceability chains.
-**When to apply**: Any post-commit step in AIWG-managed projects; agent loops that touch artifact source paths and need fresh index reads downstream
+**Summary**: After a successful git commit, check whether artifact indices are configured (`.aiwg/index/`) and rebuild any indices whose source paths were touched by the commit.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/post-commit-index-refresh.md
 
 #### soul-enforcement
-**Summary**: When `SOUL.md` is present at project root, agents must read it fully and internalize the identity, worldview, and voice it defines before generating any content. The soul takes priority over generic persona defaults — it is not a style guide, it is who the agent is for the duration of the session.
-**When to apply**: Any content-generation task in a project with a SOUL.md file; voice/persona handoffs; multi-agent collaborations where consistent identity matters
+**Summary**: When `SOUL.md` is present at project root, agents must read it fully and internalize the identity, worldview, and voice it defines before generating any content.
 **Full rule**: @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/soul-enforcement.md
 
 ---

package/agentic/code/addons/aiwg-utils/rules/activity-log.md

@@ -1,3 +1,7 @@
+---
+enforcement: medium
+---
+
 # Activity Log Rule
 
 **Enforcement Level**: MEDIUM

package/agentic/code/addons/aiwg-utils/rules/agent-deployment.md

@@ -1,4 +1,5 @@
 ---
+enforcement: high
 paths:
   - ".claude/agents/**"
   - ".factory/droids/**"
@@ -10,6 +11,7 @@ paths:
 
 # Agent Deployment Rules
 
+**Enforcement Level**: HIGH
 These rules apply when working with agent definitions and multi-provider deployment.
 
 ## Agent Ecosystem