'%20d='M64%205c-3%2018-15%2026-13%2043-9-5-13-13-13-22C20%2043%2015%2062%2022%2082c7%2022%2023%2037%2042%2041%2022-4%2039-21%2043-43%203-17-3-32-18-45%202%2011%200%2018-6%2025C84%2036%2075%2019%2064%205Z'%20/%3e%3cpath%20fill='url(%23heat)'%20d='M64%2045c-2%2015-14%2022-13%2038-5-4-8-9-9-15-7%2010-8%2020-4%2030%205%2012%2014%2020%2026%2023%2013-3%2023-12%2027-25%203-11%200-20-8-29%200%207-2%2012-6%2016%201-16-5-27-13-38Z'%20/%3e%3c!--%20The%20glasses%20render%20as%20two%20stacked%20stroke%20groups:%20a%20pale%20warm%20casing%20under%20a%20dark%20warm-charcoal%20stroke.%20The%20casing%20keeps%20the%20dark%20strokes%20legible%20where%20they%20leave%20the%20flame%20body%20(temple%20tips,%20lower%20rims)%20on%20dark%20backgrounds,%20and%20reads%20as%20a%20rim%20light%20against%20the%20flame%20on%20light%20ones.%20--%3e%3cg%20fill='none'%20stroke='%23ffe3ae'%20stroke-opacity='0.85'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='14'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='14'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='14'/%3e%3cpath%20stroke-width='13'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3cg%20fill='none'%20stroke='%2333221b'%20stroke-linecap='round'%20stroke-linejoin='round'%3e%3cpath%20stroke-width='8'%20d='M7%2063c12-4%2027-5%2043-1M78%2062c16-4%2031-3%2043%201'/%3e%3crect%20x='12'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3crect%20x='70'%20y='58'%20width='46'%20height='35'%20rx='13'%20stroke-width='8'/%3e%3cpath%20stroke-width='7'%20d='M57%2066c5-4%209-4%2014%200'/%3e%3c/g%3e%3c/svg%3e){kind=small}
@happyvertical/smrt-approvals
A decision gate: revision-bound, single-use approvals with quorum, expiry, tenant policy, and an append-only event ledger.
What it gives you
A decision gate: revision-bound, single-use approvals with quorum, expiry, tenant policy, and an append-only event ledger.
- 01A package defines an approval kind; a requester opens a request bound to one revision of one subject
- 02Only human principals of the same tenant holding the kind’s permission decide, once each; agents and services may request and consume
- 03Not a workflow engine: no stages, no executor, no compensation
Request, decide, consume
ApprovalRequest is one gate on one subject revision. ApprovalEvent is the append-only ledger and the source of truth. ApprovalPolicy lets a tenant tighten a kind with a higher quorum, a shorter expiry, or one more permission; it can never loosen the defaults. An approved request is consumed exactly once against the revision the consumer is about to act on.
Concurrency has one winner
Every transition is one guarded conditional UPDATE plus one event insert in the same transaction. Concurrent double approval or double consumption has exactly one winner; the loser is refused and writes nothing. Each transition returns transitioned, already_applied for an idempotent requestKey replay, or refused with a typed reason.
Only the service writes
A request or event built directly is refused at the model layer. Events cannot be updated or deleted. Optional self-approval needs an explicit selfApprovalPermission on the kind and is recorded on the event.
Package UI
No UI layer to carry
This package stays focused on models, runtime behavior, or tooling. Build its interface with smrt-ui, or use a related domain package that exposes a /svelte entry point.
Intentionally headless
Package previews
No playground module yet
This package does not currently export a ./playground module. Its component names and import path remain available in the Components tab.
Intentionally not registered
Generated interface
REST
The exact route set comes from each model's @smrt({ api }) policy
and the application manifest—not from a second controller definition.
The generated REST and MCP surface is list and get only, and there is no generated CLI. Writes go through ApprovalService.
Generated interface
MCP
AI tools are generated from the methods you explicitly include. Their inputs are validated against the same model metadata used by REST and CLI.
The generated REST and MCP surface is list and get only, and there is no generated CLI. Writes go through ApprovalService.
Browser-native agent interface
WebMCP
The generated web definitions carry the same tool names, descriptions, and JSON Schema
inputs as MCP. smrt-web registers them with document.modelContext.
The generated REST and MCP surface is list and get only, and there is no generated CLI. Writes go through ApprovalService.
Generated interface
CLI
The app CLI turns manifest resources into predictable operator commands while keeping package-specific actions close to their models.
The generated REST and MCP surface is list and get only, and there is no generated CLI. Writes go through ApprovalService.