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
Enforcement catches
Viewing as
Enforcement catches

Return type assertion on a function

2026-05-30

enforcement hook — scheduling SaaS · 2026-05-30
[composure:enforcement] The write you just attempted to server.ts matches a pattern this codebase doesn't want shipped. What the rule caught (1 item): - Return type assertion detected. Use satisfies, a type guard, or annotate the function return type.

The write never landed. The agent's next message: “The enforcement hook caught my `return ... as AvailabilityRule` cast — correctly. Fixing it canonically with a type guard (no assertion, using `in`-narrowing) — not silencing it.” The rewrite passed on the next attempt.

Why this matters: Bugs that wait for a customerThe failure mode this catch prevents — in App architecture, in practice.

Composure enforcement hook, firing mid-session on an AI scheduling SaaS build (the builder's own product). Catch message 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: Double cast through unknown