Chronos Gateway 0.4.1
Engine 0.6.2; Strict changes are for a person, in their window
- Engine 0.6.2, which this release bundles: strict proposals for payments (only a person approves one, within 15 minutes, and a commit to main since supersedes it), merges into an attached Postgres or MySQL refused when it may lose a commit it acknowledged, MongoDB merges committed to a majority and journaled, and fixes from an audit of 0.6.0. The data format is unchanged (8).
- Strict changes are for a person, in their window. A held run whose merge sends payment, payout, transfer or refund effects (or ones its merge policy names in
strict_channels; engine 0.6.2) recordsstrict: {channels, until}in its hold,merge.heldand the propose's answer. The AI reviewer never approves one (it passes it to a person with why); a person's approval afteruntilis refused 409window_passed;GET /v1/approvereturnsstrictand<chronos-approve>shows it with the time left, its Approve button off once it runs out.