Notice Board transactional write-lock / queue safety layer

Action

Not set.

Status

pending

Capture notes

• Cron self-audit recommendation A: build a write-lock / transaction wrapper before adding more Notice Board automation.
• Goal: prevent overlapping WhatsApp captures, Claude Code research-page commits, and cron link-triage jobs from interleaving brain.json, inbox.md, generated HTML, and git commits.
• Expected benefit: safer concurrent captures/research/cron work; risk is low-to-medium because stale locks and failed runs need careful handling.

Explore

Intent: Goal: prevent overlapping WhatsApp captures, Claude Code research-page commits, and cron link-triage jobs from interleaving brain.json, inbox.md, generated HTML, and git commits.

Next action: Pick the first implementation slice from the linked recommendation page.

Outcome

Implemented transactional Notice Board write safety: mutating CLI commands now serialize through .notice-board.lock, read fresh state inside the lock, validate staged brain.json, and atomically replace brain.json plus staged inbox audit.

Legacy artifacts

• note Cron self-audit recommendation captured
• doc Implementation options and recommendation
• note Three-channel concurrency walkthrough added