In the chat
How Valor handles the chats he is in: one session speaks in each chat and hands the work to agents behind it.
Chats
How a chat session handles messages
The session reads the chat, memory, task status and the repository itself. Then it hands work on:
- a quick lookup to a subagent;
- anything on the web to the web agent;
- anything to deliver to a task.
A task reports back to the session that started it, and only the session posts in the chat.
When Tom, who built Valor and runs Yudame, is still talking an idea through, the session starts nothing. It asks what only he can settle, one question per message.
Source: skills/sdlc/converse.md · tools/chat_tasks.py
Rooms
Team chats and engineering chats
Team chats
Valor waits to be mentioned, and no engineering work starts there. He can still search the web or file a GitHub issue.
Engineering chats
Every message reaches the session, and engineering work starts there.
Each chat's purpose is written down and included in every turn's prompt.
A message Valor reads gets 👀 at once. When the turn finishes, the emoji changes to show the outcome.
Source: docs/bridges/telegram.md · core/reactions.py
Attention
What reaches Tom
Each time Tom acts on a task, the ledger (the append-only record of everything Valor does) gets a row, counted beside the money spent. Tom receives four kinds of message:
- A question, only when the answer changes the outcome.
- A delivery, saying what was verified and what wasn't.
- A report for each merge or send.
- An agenda when the condition a business decision was waiting on has been met.
Documents come as phone-readable PDFs.
Source: docs/mission.md, The attention log · persona/delivery.md
Routines
Routines
The macOS service manager, launchd, decides when a routine runs. The kernel, the deterministic code that runs every task, provides everything else, so each run has a ceiling on what it may do, a meter and a ledger, and can be stopped.
| verify | runs a project's suite and starts a fix task for each new group of failing tests |
| expiry | lists for Tom the guards past their ninety-day expiry; deletes nothing itself |
| conditions | puts a business decision whose watched condition was met on the next agenda |
Source: docs/routines.md · routines/