Owner decisions 2026-10-14:
- worm_audit_settings: one audited, editable row (changeset worm-audit:10,
seeded insert-only) holding audit retention years, export lock mode
(GOVERNANCE default, COMPLIANCE), export retention days (30), checkpoint
cadence, chain interval, settle horizon, late-detail lookback and the
export/verify schedules; edits are FIELD-audited and therefore chained;
schedules apply after restart, the rest on the next run (30 s cache);
- exporter and verifier honour the recorded lock mode and retain-until;
the home shows the mode and warns while GOVERNANCE is in use or the
export retention is shorter than audit retention;
- README: Settings and Switching sealed exports to COMPLIANCE; DESIGN
addendum; screenshots of the home and the Settings record.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Phase (c) of docs/DESIGN.md:
- the WORM Audit app and home: chain status, export status, retention,
recent purges and setup warnings (missing triggers, owner role, signing
and trusted keys, bucket without Object Lock, stale verification), plus
a summary card for host dashboards; no audit content is rendered;
- alert types renamed to wormaudit.* (core name pattern) and declared,
with daily heartbeat monitors;
- full verification holds one page plus one checkpoint range;
- plain field labels, record labels, full-width sections and child lists;
- a test-scope demo server and screenshots (home and records, light and
dark, 390/1440/1920) with overflow checks;
- DESIGN.md consistency edits (alert names, object_versions,
s3:GetObjectVersion, snake_case columns).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
james.maesandClaude Opus 5.5