bremda

Learn

Guide

A practical walkthrough of how Bremda maps work across responsibilities, pendings, pulses, and reminders.

1 · Understand the board

The board is four quadrants, not a backlog theatre. Each item knows how heavy it is and what happens if it slips.

Start by capturing one real commitment into Responsibilities and one loose thread into Pendings — keep it honest.

2 · Work with the assistant

Talk to Bremda to add items, reschedule nudges, and summarize what is still open. Keyboard-first users can rely on ⌘K when the shell is available.

The assistant proposes changes; you confirm anything that touches deadlines or external commitments.

3 · Automate with pulses

Pulses are standing instructions — weekly reviews, renewal checks, or inbox sweeps. Set them once and let Bremda watch for triggers.

Keep pulses narrow: one intent per pulse avoids noisy alerts.

4 · Lightweight reminders

Reminders are atomic nudges without a plan. Use them when you only need a ping, not a project graph.

Promote a reminder to a pending if it grows teeth — that moves it into the close-the-loop lane.