Skip to content

Keeper Operational Planning Doctrine

Keeper operational planning exists to help a human decide what to do next.

Doctrine

  • Planning fields extend canonical Keeper tasks; they do not create a second task system.
  • Console views are manual planning surfaces over canonical task data.
  • Inline edits and drag ordering must call canonical Keeper APIs.
  • Review mode records human review metadata only when the user saves a task.
  • Focus mode is a view over today_focus, blockers, and task state.
  • Recurrence rules are stored for future use only; this pass does not generate recurring tasks.
  • Dependencies and blockers explain sequencing. They do not trigger autonomous task mutation.

Human Control

Keeper may suggest, rank, group, and summarize. It must not silently schedule, reschedule, complete, archive, or create work in the background.

Fail-Closed Rules

  • Unknown planning fields are not written by the console.
  • Calendar writes are absent.
  • Background planners are absent.
  • Direct database access from Keeper Console is forbidden.
  • Proposal artifacts are evidence, not approval.