module-guardrails

The policy engine every automated value-moving action must pass: hard denies, caps, a kill switch, and an append-only audit chain.

With cargo

cargo add cratefield-module-guardrails

What it is

module-guardrails.

The policy engine every automated value-moving action must pass (issue #763). A job that would move a venture’s or a user’s funds — send a transaction, sign a permit, approve a spender, swap — describes itself as a Request and gets one of two answers: an opaque Approval that only the engine can mint, or a typed Denied carrying every reason. Default deny everywhere, and fail closed on any port error. Hard denies, allowlists, required simulation, micro-USD caps, a kill switch and the audit chain are the policy; a policy alone cannot make an on-chain contract safe, and this crate does not claim it can.

From the crate’s own README.

Ports

WalletSigner

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 2 versions recorded, newest first. Every published version is on crates.io.

  1. 0.1.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core, cratefield-testing
  2. 0.1.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core

    Added

    • First release, 0.1.0: the policy engine every automated value-moving action must pass. It checks hard denies, recipient and contract allowlists, required simulation and micro-USD caps, and it has a kill switch and an audit trail. It denies by default and fails closed (#763).

One of 76 crates in the harness, all of them MIT and all of them in one repository.