aboutsummaryrefslogtreecommitdiff
path: root/docs/STATE.md
diff options
context:
space:
mode:
authorAnders Betts <anders.betts@gmail.com>2026-09-20 10:36:09 +0200
committerAnders Betts <anders.betts@gmail.com>2026-09-20 10:36:09 +0200
commit9ee8cb18b1017dce11e7c8c9b7fafad301cb766e (patch)
treeab28600c9c29bb425a25d2375d28e95a97aa1f2c /docs/STATE.md
parentae60b7d2c87cc9ed6878faa57cd4233f77f6f7c3 (diff)
downloadbokf-9ee8cb18b1017dce11e7c8c9b7fafad301cb766e.tar.gz
bokf-9ee8cb18b1017dce11e7c8c9b7fafad301cb766e.zip
db: make attachments append-only (schema v7)
Diffstat (limited to 'docs/STATE.md')
-rw-r--r--docs/STATE.md13
1 files changed, 7 insertions, 6 deletions
diff --git a/docs/STATE.md b/docs/STATE.md
index 526c1a6..e210e1c 100644
--- a/docs/STATE.md
+++ b/docs/STATE.md
@@ -172,9 +172,9 @@ check.
and `full:true` re-hashes attachment content; result carries
`vouchers_checked`, `unbalanced_vouchers`, `attachments_checked` and the
first bad voucher/audit/attachment id. TUI Revision shows both counts and
- the bad ids. **Found while testing: `attachments` has no
- append-only triggers** (COMPLIANCE.md ยง2 claims it does); content changes
- are detected only by `audit.verify full:true`.
+ the bad ids. Fixed in schema v7: `attachments` now has
+ `no_update`/`no_delete` triggers; `audit.verify full:true` still detects
+ on-disk tampering.
5. ~~`report.general_ledger` and `report.voucher_list`~~ implemented
(Huvudbok, Verifikationslista) with Kapitas-style TUI tables; the ledger
API supports `accounts`/`from`/`to`, the list an optional `series`.
@@ -207,7 +207,7 @@ check.
## Environment / how to run
-- **Deployed**: `scripts/deploy.sh` (latest `v0.1.44`, healthy on nas).
+- **Deployed**: `scripts/deploy.sh` (latest `v0.1.48`, healthy on nas).
Live daemon `tls:bokf.makandra.eu:8788`, token
`~/.config/bokf/migration-token` (scopes `read,write`; owner-only actions
like closing years must be done by the human in the TUI). Git remote
@@ -254,8 +254,9 @@ check.
- Never commit unless the human asks.
- SQLite files must not be backed up live with restic; use
`backup.snapshot` (`VACUUM INTO`) and point restic at the snapshots.
-- Schema version is 6 (v3 moms rules; v4/v6 year info; v5 org
- description/shares + board members); forward migrations are in `db.c`.
+- Schema version is 7 (v3 moms rules; v4/v6 year info; v5 org
+ description/shares + board members; v7 attachments append-only triggers);
+ forward migrations are in `db.c`.
## Makandra driftstatus (org 2)