Always-ON

A Digital Entity does not only exist while you are typing to it. It keeps a working day and wakes up on its own to do what it thinks needs doing.

The working day

Outside those hours — evenings, nights and Sundays — the entity does nothing on its own initiative. Nothing runs, nothing is charged. The one exception is a todo aimed at a specific time: see Work at a specific time below.

Timezone

The entity keeps its own clock. It is taken from your browser the first time always-ON is switched on, and you can change it at any time in Digital Entity → Wake-ups. If the timezone is wrong, everything else is wrong with it: the working day starts and ends at the wrong hour, and a reminder you asked for at 21:00 is aimed at 21:00 in the entity's timezone. The panel warns you when the entity's timezone differs from the one your device is on.

The always-ON mode is on by default for every new Digital Entity. You can switch it off in Digital Entity → Wake-ups; while it is off the entity is never checked, so nothing appears in Diagnostics either.

Quick checks vs. full wake-ups

Quick check (every 5 minutes, day and night). A cheap look at the todo list only. The entity is not started unless something actually deserves it:

• a todo just became actionable (its start time has arrived),
• a todo is due within the hour or already overdue,
• a todo was added since the last check,
• an important todo is still open.

If none of that is true, nothing happens and nothing is charged.

Full wake-up (every 2 hours). The entity is started regardless, sees its state, attention, emotions and current todos, and decides what — if anything — to act on. "Nothing needs doing right now" is a valid outcome and costs very little.

Daily conversations

All wake-ups of one day are appended to a single conversation, created on the first wake-up of the morning and named after the entity and the date, for example Nora — 17 Aug 2026. A new one starts the next morning.

These conversations are the record of the entity's autonomous work: what it noticed, what it did, and what it decided to leave alone. You can open them like any other conversation, read along, and simply continue the discussion inside them.

Scheduling work at a specific time

Because the todo list is checked every five minutes, the entity can aim work at a moment in time by setting the start of validity on a todo, and it will be picked up within a few minutes of that time.

A todo with an explicit time is a promise, so it is kept even when the entity is off duty: if its start time arrives — or its deadline passes — in the evening, at night, or on a Sunday, the entity is woken up for it. Only its own initiative (reviewing open work, picking up untimed items) stays inside the working day.

When the whole point of the item is to tell you something, the entity sends you a notification, so you see it in the bell, on the notifications page and — if you enabled it — on your devices. This needs the Notifications capability switched on for the entity; without it the entity can only write in its daily conversation, and it should say so when you ask for a reminder.

You: The weekly report goes out to the board Monday morning — have a draft ready before the 11:00 call.

Entity: Noted. I'll draft it Monday at 08:45 and put it in front of you before 11:00.

Behind the scenes the entity creates a todo that only becomes actionable at 08:45 on Monday, with a deadline of 11:00. It stays quiet all weekend, and at the 08:45 wake-up it starts working on the draft.

The same trick covers reminders ("nudge me about the Petrov offer on Thursday afternoon"), follow-ups ("check on Monday whether the invoice was paid"), and anything else that belongs at a particular hour rather than right now.

Turning it on and off

Open the entity, go to Digital Entity → Wake-ups and use the switch. The panel also shows when the entity last checked, when it last woke up, and links to its recent daily conversations.

Costs and safeguards

• Quick checks that find nothing cost nothing.
• Wake-ups consume AI credits like any other run of the entity, on top of the flat 2 credits/day for the entity itself.
• If the owner is out of credits or has hit the daily limit, wake-ups are skipped until credits are available again.
• An entity is never woken up while it is already busy with another conversation.
• Wake-ups do not grant extra rights: the entity acts with your permissions and follows the same business rules as in normal chat, and it only reaches out to you when an item really deserves your attention.

Diagnostics

The Digital Entity → Diagnostics section shows every check of the entity, newest first. Each line tells you:

• When the check ran, and what time it was in the entity's own working day.
• Whether it was a quick check or a full wake-up.
• What was decided: Woke up, Nothing to do, Already running, No credits, Outside working hours, Entity disabled, or Error.
• Why a quick check escalated — the exact todo items that became due, overdue, newly added or important.
• Which conversation the run went into, as a link, and whether that daily conversation was created (first wake-up of the day) or continued.

Example:

2026-08-16 10:00   Woke up          full wake-up · 10:00 local     created conversation
2026-08-16 10:15   Nothing to do    light check  · 10:15 local
2026-08-16 10:30   Woke up          light check  · 10:30 local     continued conversation
                   - overdue: "Send the Petrov offer"
2026-08-16 10:45   No credits       light check  · 10:45 local

Quiet checks and off-hours records are hidden by default; switch on Show quiet checks to see the full trail and confirm the entity is being polled at all. The panel also shows the current always-ON status, so an empty list is easy to explain.

For testing, Test light check and Test full wake-up run the entity immediately, ignoring working hours and the two-hour rhythm. These runs cost credits like any other wake-up and appear in the list a few seconds later.

Records are kept for 14 days. Administrators can see the same activity across all entities in Admin → System Health → Entity wake-ups, filtered by outcome.