work-ledger-sync

A universal work ledger tracks work across sessions by applying three mandatory ledger touches: session start, milestone updates, and session end. It utilizes Supabase MCP to insert and update entries in the public.work_ledger, ensuring real-time status transitions, timestamping, and notes for comprehensive tracking.

A universal work ledger is a real-time record of all work across planning, execution, review, and dispatch phases. It prevents untracked work and miscommunication by requiring entries at session start, milestones, and session end, creating a single source of truth for teams.

Yes, the work ledger sync requires Supabase MCP to apply proper status transitions, timestamping, and notes when inserting or updating the public.work_ledger. This ensures entries are accurately reflected as work progresses and milestones occur.

You log ad-hoc tasks and cross-repo work to a Supabase ledger by documenting the context and events of each session. The ledger supports appending notes and updating statuses for ad-hoc tasks, ensuring all activities are captured in the universal work ledger.

Yes, the work ledger includes guardrails designed to prevent stale or duplicate entries. These guardrails operate alongside the Supabase MCP inserts and updates to ensure the public.work_ledger maintains accurate, real-time records without redundant data.