Skip to content

As Decided v0.24.0 - Sentry

Choose a tag to compare

View all tags
@tcballard tcballard released this 27 Jul 21:44
v0.24.0
846cc7b

As Decided can now check whether code follows the decisions that govern it.

Until now, As Decided could validate the decision corpus and tell an agent which decisions applied—but a pull request could still contradict those decisions and pass. v0.24.0 adds Sentry, a deterministic code-side enforcement layer.

decided sentry .
decided gate . --code

Sentry checks machine-readable constraints declared by decisions against either a pull-request diff or the full source tree:

  • forbid a pattern in selected paths
  • require a pattern in selected paths
  • forbid imports across boundaries
  • emit deterministic SARIF for code scanning

No embeddings. No model call. No LLM judge. The same source and decisions produce the same verdict offline.

This does not pretend every engineering decision can be reduced to a rule. As Decided now reports enforcement coverage explicitly, so teams can see which live decisions are machine-enforceable and which still require human review.

Also in this release:

  • Herald rendering is now native Rust, removing its Python runtime.
  • Native archives ship decided and decided-mcp for Linux, Apple Silicon macOS, and Windows.
  • decided gate --code composes corpus integrity and source enforcement into one gate.

The corresponding Sentry and native Herald GitHub Actions are prepared in asdecided/ci#7.

Assets 5
Loading