Your stack does that.

DFB / An operating design

Start fresh.
See the whole situation.

One fresh assessment on a timer replaces thousands of independent sessions trying to keep up. Between batches, retain knowledge: facts, relationships, commitments and receipts.

  1. 01

    Discover first

    Ask what changed, what is missing and which new sources matter. Gather actual bodies, reconcile relationships and prepare one interconnected context with coverage gaps.

  2. 02

    Reason holistically

    A capable frontier model takes the time needed. Use multiple passes when useful. Save one whole-batch plan before execution.

  3. 03

    Execute finite jobs

    The executive chooses purpose and scope. Helpers judge ordinary details. Each returns a receipt: attempt, result, evidence and remaining uncertainty.

↶ Next batch: receipts become knowledge.

Every batch stands on its own

End the executive session after its finite assignments. The next batch judges what is true now; it does not automatically resume an old plan. An unfinished commitment is a fact in the CRM, not a suspended business state. No parent session waits for a worker or a reply.

All work is batched

Only calls and texts have real-time conversation. They use permitted CRM knowledge published by completed batches. Missing facts and new work enter the next batch. Email is entirely batched. Urgent labels, legacy jobs and failed receipts cannot start an independent decision-making worker.

The assistant can naturally accept a cancellation and offer a reasonable estimate. It must not claim the change already happened. Wording fits the person and situation; no fixed script is required.

A deadline can move the clock, never the owner

When a request carries a real deadline that falls before the next scheduled batch could act on it, the next batch starts early. It is a full batch: discovery, one plan, finite jobs, receipts. It considers everything else pending, not just that request. A text at 5:10 cancelling a 5:30 appointment gets an early batch. A text marked urgent with no actual deadline waits for the normal cadence.

Discovery keeps it alive

A receipt for a new watch or note-taker can reveal a new knowledge stream. The reasoner follows the lead, investigates authorized access and records any genuine connection gap. Existing mail, calendar, incoming and outgoing texts, calls, meeting transcripts, CRM and receipts are starting points. A fixed checklist is not discovery.

Collectors can have different schedules. A message archive might refresh once a day while the executive runs every half hour. Each batch uses a source’s true as-of time and never claims to have read past it.

Done is the standard

An ordinary proposal is thought through and sent within standing authority. Drafting it or assigning it does not achieve that result. Each batch assesses outcomes and decides what needs attention now. Escalate when the principal’s judgment or new authority is genuinely needed.

The assistant administers its own evolving CRM. Save useful knowledge even when fields need to change. Learn general lessons from imperfect work and feedback. Growth matters more than tidy records; avoid named-person patches.

Choose models for their jobs

A fast conversational model for calls and texts. A capable reasoning model for batches. Lighter models for narrow helpers. The best voice model is not necessarily the best planner. DFB is the order of work and the ownership of decisions; it is unrelated to any provider’s batch API.

Where this is wrong

Full article and diagram → · AI-readable build brief →