Note not found.
TODO: Update agency SOPs and conventions for board auto-sync
Problem
PR #166 (pal-e-docs) shipped board auto-sync:
POST /boards/{slug}/sync + update_note hook. Boards are now self-maintaining. But the agency operating model doesn't know about it yet. SOPs, conventions, and agent personalities still assume manual board maintenance.What Needs Updating
- agent-workflow SOP — Add board sync to post-merge workflow. Betty Sue should call
/syncon relevant board after merges. - sop-post-merge-docs (skill-update-docs) — Step 5 still talks about manually moving board items. Should reference the auto-sync hook and explicit sync endpoint.
- agent-betty-sue personality — Add board sync awareness. Betty Sue should call sync at session start for active project boards, not manually create/move items.
- convention-block-first-access — Consider adding board state to session startup injection (currently injects plan TOCs only).
- SessionStart hook — Consider adding
POST /boards/{slug}/synccalls for active project boards at session start. Ensures boards are current before any work begins.
Why Now
Board sync is live and verified across all 9 project boards (2026-03-14). Without SOP updates, agents will continue manually maintaining boards — wasting tokens on work the platform now handles automatically. The whole point of shipping 5b-1 was to eliminate this friction.
Related
phase-pal-e-docs-auto-population— Phase 5b (parent feature)plan-pal-e-agency— parent plan- PR #166 (pal-e-docs) — the feature that enables this
agent-workflow— primary SOP to updateskill-update-docs— post-merge skill to update