Forge template
Settlement desk
Dual control, a hard cap, and a rail that can fail. Amounts are demo units. Not a stablecoin and not a bank.
Start from a reviewed template, not a random repository.
Adapters in this template
- Role access
Running in a demo
Each desk has named roles. A restricted field is hidden from the role that should not see it.
- Approval workflow
Running in a demo
A second person must approve a synthetic payment above the desk limit.
- Dual control
Running in a demo
Above the limit, the approver's action is not enough. A controller must take the second step.
- Hard cap
Running in a demo
A synthetic amount above the hard cap cannot be submitted. The cap is demo units.
- Rail simulator
Running in a demo
The desk can mark the simulated rail down and fail or retry a payment. It is not a stablecoin and it does not move value.
- Reconciliation
Running in a demo
Operations marks a settling payment reconciled when the simulated rail is up.
- Invoice request
Running in a demo
Seeded rows are invoices with demo-unit amounts. A supplier sees status, not the internal note.
- Audit log
Running in a demo
Each transition appends an event the auditor can read. The digest is a label, not a cryptographic hash.
- State machine
Running in a demo
A record only moves along the transitions defined for its desk.
- Synthetic records
Running in a demo
Every desk starts from invented organisations, invoices, and assets. Reset restores that seed.
- Demo fence
Running in a demo
Every running desk states that it is synthetic, local, and not for production.
Not in the box
- Private repository
- Push or pull request to an upstream project
- GitHub Codespaces
- Dev Container
- Docker Compose file
- Ephemeral preview URL
- SBOM
- Pinned commit
- OpenSSF score
- Secret scan
- Vulnerability scan
- Source-derived code pack
