Why tsutome, and why now
A policy is not kept by being written
Write "deleted within 30 days of the answer" into a policy, and nobody remembers it thirty days later. Someone has to raise a task, keep the date in mind and close it when it is done. Where that manual step is missed, the policy and what actually happens drift apart.
A tick does not make it done
"Done" in a task tracker records that someone pressed the button. Whether the data was really deleted has to be checked some other way. A duty in tsutome closes only when the event that says the deletion happened is on the record.
People decide, agents do
Looking at what is due, telling the owner, doing the work and recording it can be left to an agent. Adopting a rule, approving an action and setting a duty aside are a person's, and each is recorded with who did it.
How it works, in three minutes
Take a policy that says an inquiry is deleted within 30 days of the day it is answered.
Write a rule, and have a person adopt it
The article of the policy becomes a Markdown file with its terms at the top. An agent may draft it, but it gives rise to nothing until a person adopts it with
tsutome adopt. Adoption puts the rule's terms and the file's digest on the record.An event is recorded, and a duty arises
When
data.answeredis recorded for inquiry q1, a duty arises:data.deletedmust follow for q1 within 30 days. Nobody raises a task. The duty is not stored; it is computed each time the record is read.An agent looks, and tells the owner
Seven days before the deadline the duty comes up. An agent calls
tsutome agendaon a schedule, tells support, the owner, and gets the deletion approved. If the deadline passes, legal is told.The deed is recorded, and the duty closes
Once it is approved and the deletion is done,
data.deletedis recorded and the duty closes: done if in time, done_late if not.tsutome auditreports what was done without approval and what ran past its deadline.
A rule is a file a person can read
Its terms at the top, the words of the policy below. Someone in legal can read and review it, and a change shows as a diff.
---
id: delete-after-answer
title: Delete inquiries 30 days after they are answered
source: Personal data policy, article 12.1
when: data.answered
expect: data.deleted
within: 30d
notice: 7d
owner: support
escalate: legal
approval: required
where:
form: contact
---
Inquiries are deleted within 30 days of the day they are answered.
When data.answered is recorded for an item, data.deleted must follow for the same item within 30 days. Seven days before, the duty comes up and support is told; if the deadline passes, legal is. A person approves before the deletion.
when, expect | The event that starts the clock, and the one that must follow |
|---|---|
within | The deadline: 30d, 12h, 45m |
notice | How long before the deadline the duty comes up. Left out: from the start |
owner, escalate | Who must act, and who is told when the deadline has passed. Roles, not people's names |
per | The keys that name the thing: one duty per distinct combination. device, advisory gives a duty per device and advisory |
approval | required: a person approves first, and done without it is a finding |
where | Only events whose values equal these start the clock |
Done without approval, or an agent that stopped: it shows later
The rules, the approvals and what was done are all in one append-only record. Anyone holding the record computes the same duties.
Approval is held against what was done
When an approval is recorded, the digest of the plan that was approved stays with it. tsutome audit reports what was done without the approval its rule requires, or not as the approved plan said, with the line of the record where it shows.
An agent that stops looking shows
Each time an agent looks at what is due, the look is recorded. An agent that has stopped shows as a record that goes quiet.
What was due yesterday cannot be quietly changed today
Changing a rule file changes nothing until it is adopted again, and a duty already under way keeps the version it started under. The record is a deedlog chain, so it can be signed, cosigned by witnesses and verified by anyone.
Tsutome is not a gate. It cannot stop an agent from acting without approval; it shows it afterwards. To prevent it, put a policy gate between the agent and its tools. And the record is what was reported: where it matters, have something other than the agent write it, such as an MCP proxy or the system's own audit log.
What goes on the record, and what does not
Not recorded
- Personal data. The record holds names of events and identifiers only
- The text of an approved plan, or of the reason for an exception (its digest is recorded)
- Guessable identifiers. A ticket number can go in as an HMAC
Recorded
- The terms of each adopted rule, and the digest of its file
- The events that start a duty, and the ones that meet it
- Who was told, who approved, who granted an exception
- That an agent looked at what is due
This record and the rule files are all the state there is. No database and no server.
Compared with a task tracker
| A typical task tracker (tickets) | tsutome | |
|---|---|---|
| Who creates a task | A person. Forget to raise it and it does not exist | Nobody. It arises from a rule and an event |
| What closes it | Someone pressing "done" | The expected event appearing on the record |
| The deadline | Editable afterwards | Follows from the rule and the event that started it. To change it, adopt the rule again |
| Where the state lives | In the tool's database | Nowhere. It is computed from the record each time |
| The link to the policy | In someone's head, or another document | The rule file holds the words of the policy and where they come from |
| Approval | A comment or a change of status | Who approved, and which plan, on the record. Done without it is a finding |
| Checking from outside | Trust the tool's administrator | Anyone holding the record computes the same result |
| Where the cost is | A monthly fee per user | The software is free (Apache-2.0). Design and integration are yours, or ask for help |
What it takes
By role: what each one holds and what each one does. There is no new server to run.
Whoever sets the rules (legal, an administrator)
- Turn an article of the policy into a Markdown file with its terms. An agent may draft it
- Check it with tsutome check, and adopt it with tsutome adopt
- Be told when a deadline has passed. Granting an exception is also this role's
The owner (the role a duty falls to)
- Be told by the agent
- Where a rule requires approval, read the plan and approve before the work is done
- Approval can be taken in whatever the organization already uses: chat, a workflow tool
The agent
- Call tsutome_agenda on a schedule (Claude or ChatGPT scheduled runs, cron)
- Tell the owner, get approval, and do the work with the tools of the system concerned
- Record what it did. It may ask for an exception, but a person grants it
What the current version does
It does
- Checking, adopting and retiring rule files, and noticing a change not yet adopted
- Computing duties: waiting, due, overdue, done, done late, excepted, withdrawn
- Recording who was told, approvals and exceptions, and auditing them (tsutome audit)
- A command line, an MCP server and a library (Node.js)
- The record as a deedlog chain, which dlog signs, has cosigned and verifies
It does not
- Run agents. Use the agent's own scheduling
- Send notifications or ask for approvals. Use what the organization already has
- Call the systems where the work is done. Use their tools
- Stop an action taken without approval. It shows it afterwards
For developers
npm install -g tsutome
tsutome check rules/delete-after-answer.md
tsutome adopt rules/delete-after-answer.md --by legal --name example.com/duties
tsutome record data.answered -m item=q1 -m form=contact --by support
tsutome agenda
tsutome approve DUTY --by support --plan plan.txt
tsutome record data.deleted -m item=q1 --by agent
tsutome audit
- Install
npm install -g tsutome. Node.js 20 or later. The record istsutome.jsonland the rules are inrules/; change them with--chainand--rules(TSUTOME_CHAIN,TSUTOME_RULES).- Commands
check / adopt / retire / rules / record / duties / duty / agenda / told / approve / except / unexcept / audit / verify.auditexits with status 1 when there are findings, so it fits in CI or cron.- MCP server
tsutome-mcp:tsutome_agenda,tsutome_record,tsutome_told,tsutome_draft_rule,tsutome_request_exceptionand more.tsutome_approve, which records a person's approval, is offered only when the server is started withTSUTOME_APPROVER.- States of a duty
waitinguntil itsnotice, thendue, andoverduepast the deadline. When the expected event is recorded,doneordone_late. Set aside by a person,excepted; its rule retired,withdrawn.- A rule adopted later
- It applies to what was already there, and the clock starts at adoption. Changing a rule file changes nothing until it is adopted again.
- The record
- A deedlog chain (JSON Lines). Tsutome appends to it;
dlogsigns checkpoints, has witnesses cosign them and verifies. An identifier can go in as an HMAC with--hmac item=Q-0001. - License
- Apache-2.0. GitHub and npm.
- Related
- The record itself is deedlog. shinten keeps form input encrypted on every server, and kangoh runs a shared reward program without a customer database. They are sister projects built on the same principle: hold no more than you need.
Talk to us
Ask us about turning a policy into rules, fitting tsutome into your agents and the systems you have, and designing how approvals are taken. The software is free to use. What costs money is help with design and integration.
What you send is used only to answer your enquiry, and is not stored on this site. See our privacy policy.
