Objectives and tasks

Objectives, bounded worker runs and approval requests represent different parts of work.

Work lifecycle

Objectives describe ongoing outcomes. Tasks and runs represent work toward them. HUD observations do not start a new worker run.

When a deferred action is needed, the queue records its producer and proposed call. Accepting a request starts that action; it does not automatically complete its larger objective.

Outcome evidence

Distinguish proposed, accepted, executing and resolved work. Inspect failures and external receipts before reporting completion.

Implementation sources

Repository paths below describe the implementation. They do not certify a running deployment or a configured external account.

  • src/mushegh/brain/worker.py
  • src/mushegh/brain/approvals.py
  • src/mushegh/brain/tools/tasks.py

Subsystem directory · HUD guide · Verification and known limits