Entity Todo List

The Todo list is where a Digital Entity keeps work it intends to do. Unlike Attention, which is a handful of things the entity is actively holding in mind, the Todo list is unlimited and durable: an item stays there until the work is done, deliberately cancelled, or its time runs out.

The three stores work together:

Store	Holds	Size
Memory	What the entity knows — facts, preferences, procedures, episodes, relationships	Unlimited
Attention	What is salient right now	Up to 5 items
Todo	What the entity intends to do	Unlimited

What goes into a Todo

Reminders, commitments, follow-ups and anything deferred to later. The rule the entity follows is simple: before it promises to do something later, it writes the Todo. Facts and history never belong here — those go into Memory.

Each item carries:

Text — what is to be done.
Importance — 0 to 1. It influences which items the entity sees first in later conversations.
Valid from — optional. The item is not actionable before this moment. Leave it empty for "actionable right away".
Valid to — optional. After this moment the item is no longer relevant. Leave it empty for "never expires".
Related person and originating conversation — so the entity can pick the thread back up in the right place.

Validity windows

now < valid from                  →  future — not yet actionable
valid from ≤ now ≤ valid to       →  actionable
now > valid to                    →  expired

Expiry is not completion. When a pending item passes its "valid to" time, an hourly background job marks it expired, and it stays in the list as a record that the window was missed.

Examples:

"Remind Ivan to send the proposal" — valid from tomorrow 09:00, valid to tomorrow 18:00, importance 0.8. The entity will not raise it today, will act on it during the day tomorrow, and it expires by itself in the evening.
"Check whether the supplier price list has been updated" — no validity window, importance 0.4. It simply waits until the entity gets to it.
"Chase the disputed invoice lines with Kalina" — valid to the end of the month, importance 0.9. It becomes urgent as the deadline nears.

What the entity sees

Injecting the whole list into every conversation would be wasteful, so each activation carries a working set of about 10 items. Selection blends several signals rather than a single one: whether an item is actionable now, how important it is, how recently it was created or became valid, how close its deadline is, and whether it relates to the person or conversation at hand. Items whose start time is still more than a day away stay out of the way until they get close.

The entity is always told how many items it is not seeing, and it can search the full list — including old, future and person-specific items — whenever something outside the working set may matter.

Managing the list yourself

Open the agent and go to Entity → Todo. You can filter between actionable, future, all pending and closed items, and you can mark an item completed, cancel it, or delete it outright. Only the owner of the entity sees and manages its Todo list.

Not included yet

Subtasks, dependencies, recurring todos, assigning work to someone other than the entity itself, and extra workflow states such as in progress are not part of this first version.