meta-optimize

# Meta-Optimize: Outer-Loop Harness Optimization for ARIS Analyze accumulated usage logs and propose optimizations for: **$ARGUMENTS** ## Privilege boundary — this skill is a READ-ONLY PRODUCER meta-optimize **proposes**; it does not **land**. The mutation of the skill corpus is the exclusive job of a separate, human-invoked skill: [`/meta-apply`](../meta-apply/SKILL.md). This split is structural, not advisory — it is why a missed instruction cannot let this loop apply its own patch (the self-acquittal failure mode): - **No `Write`/`Edit` tool.** This skill cannot edit a SKILL.md / shared-reference / any corpus file with the frictionless mutators. Its only outputs are the REPORT and staged patch files, written under `.aris/meta/` (a scratch area, never the corpus). - **No apply step.** There is no in-skill "apply the patch" path (see Step 6). The producer ends by *staging* approved patches for `/meta-apply`; a human must then invoke `/meta-apply` to land them. That human action is the landing gate. - **`Bash` writes to the corpus are filtered, not impossible — be honest about the layers.** What IS fully closed: the *accidental / in-flow* self-acquittal — this skill has no `Write`/`Edit` and no apply step, so an honest run cannot slip into editing the corpus. Defense-in-depth: install the [`corpus_write_guard`](../../templates/claude-hooks/corpus_write_guard.json) PreToolUse hook (like `meta_logging.json`), which DENIES the common Bash shell-writes (`>`, ...