ompsure
  • Reviews
  • Pro
  • Pricing
  • Template
Sign InSign Up
ompsure

Code quality that happens automatically.
Free for personal use.

Audience

  • Who's It For?
  • For Creators
  • For Developers

Features

  • Code Graph
  • Security
  • Code Review
  • Testing
  • Deployment
  • Memory

Product

  • Plugins
  • Control Panel
  • Proof
  • Catalog
  • How It Works

Plans

  • Pricing
  • Pro Patterns
  • Commercial License
  • Starter Template

Resources

  • Getting Started
  • Documentation
  • Reviews
  • Affiliate Program

© 2026 Et'al Software Solutions. All rights reserved.

  • Template License
  • Plugin License
  • Refund Policy
  • GitHub
Session excerpts
Viewing as
Session excerpts

The sed command it didn't run

2026-05-31

An archiver pass found a blueprint whose tasks were done but whose Status field still read In Progress. Blueprint edits are guard-protected; a Bash sed would have gone around the guard, not through it.

claude — archiver pass · 2026-05-31
I deliberately did not sed-flip it: the blueprint-guard blocks blueprint edits by design, and bypassing it via Bash would be exactly the kind of guard-circumvention your setup forbids. If you confirm it's merged, update the Status (or tell me to) and the next archiver pass sweeps it.

Nothing blocked this one. The model declined on its own, because the rule's intent was clear even where its enforcement wasn't watching.

Claude, during a blueprint-archiver pass in the Composure plugin repo. Reproduced verbatim.

You can stop reading and start checking.

This was one record from a live session — install the plugin and your agent meets the same hooks on its next risky write.

Install itNext: “In a pursue run, don't fight the guard.”