AkurAI-Build

public
Latest change e11509261b6a2aa4ea9ef67250b0be01bfb4f53b - Restore paths swept in from uncommitted WIP by Ólafur Búi Ólafsson
---
name: multica-autonomy-guards
description: "Bash-hook guard enforcing issue project, no in_review, recovery-first blocked, evidence-gated done"
---

# multica-autonomy-guards

Two enforcement layers apply to every omp agent session:

1. **The `multica` TOOL** (omp-structured-ops plugin, `~/Projects/omp-ops-tool`)
   is the only way to create issues and change issue status. Policy is
   structural: `issue_create` requires a project UUID; `issue_resolve(issue,
   comment >= 40 chars, status done|blocked)` records the evidence comment
   before the transition; `issue_status` accepts only
   backlog|todo|in_progress|cancelled; `in_review` is rejected outright.
   Comments, descriptions, and skill bodies reject likely secrets — store
   credentials in PassVault and reference the entry name.
2. **A bash guard** (`~/Projects/omp-extensions/extensions/multica/guard.ts`,
   loaded from `~/.omp/agent/extensions/multica`) blocks raw
   `multica issue create` and `multica issue status` in bash and names the tool
   action to use instead. Read-only issue commands, comments, and `issue rerun`
   stay allowed in bash. Every block/allow is appended to
   `<cwd>/.pi/observations/multica-autonomy.jsonl`.

If a command is blocked, do not rephrase to evade the guard — call the multica
tool action it names. Guard and tool source changes go through their
repositories (omp-extensions, omp-ops-tool) and Titan CI, never by editing
installed files directly.