TíoDay

This page explains TíoDay in TomaTío 1.9.8: a private page per person that their artificial intelligence (AI) apps keep current, and how one is set up.

A TíoDay shows what is yours to do (tasks), what is in progress (inflight), what got done (done), the decisions you made (decisions) and comments on any of them (comments). It is an HTML (HyperText Markup Language) page that shows this data from its page store. Your TíoDay is pinned at the top of your signed-in home page, under Yours.

How your AIs keep it

When you have a TíoDay, the brain tells every AI you connect to keep it current: record finished work, mark long work as in progress and clear it when it lands, add a task when it needs you, record your decisions, and answer comments meant for it.

They use these tools, which appear only on a connection that may keep a TíoDay:

• Read my TíoDay: open tasks, work in progress, the day's done items and decisions, and the last week of comments.
• Add or update a task for me, which can also mark it done.
• Record what got done, with a work stream and a title.
• Mark work in flight, or clear it.
• Record a decision.
• Reply to a comment on my TíoDay.

Every change is kept in the page store's history, so it can be undone. Done items, decisions, comments and finished tasks are also saved as memories in the TíoDay's scope, so AIs that can read that scope find them.

Point an AI at an item

Every item has a reference: t: for a task, d: for a done item, c: for a decision or f: for work in progress, then its key, for example t:approve-brief. Give the reference to an AI and it finds the item.

Who may read and change it

The lead agent, curators and people who manage the brain may change it, and you may read your own. When you connect as yourself without choosing an agent, your AI writes as your default agent.

Set one up

There is no button for this yet:

1. A curator creates an HTML page whose lead is the person's default agent, in a scope that fits who may see it, and uploads a page that shows these collections.
2. The curator turns on its page store with the collections tasks, inflight, done, decisions, comments and meta.
3. A server admin pins it to the person with WP-CLI (the WordPress command line):

wp post meta update <artifact-id> ab_home_owner <user-id>

If a person has more than one, the most recently changed HTML page counts. Archived ones do not.