Board board
foundational
A set of tasks, each in one of three lanes.
-
Title
titletext, one linerequired Encrypted
$ cm quill add tasks
Or, as an administrator, open Administration → Quills in the app and choose Tasks. Either way your cloud shows you everything below and waits for your yes.
The kinds of data it works with. Records belong to the people who write them, not to the quill: removing it leaves every one where it is.
boardA set of tasks, each in one of three lanes.
title
text, one linerequired
Encrypted
taskOne thing to do, on a board, in a lane. Its body is Markdown; subtasks are - [ ] lines.
board
link to Boardrequired · deleted with its board
Indexed
title
text, one linerequired
Encrypted
body
Markdown
Encrypted
lane
one of To Do, Doing, Done
Indexed
due
date
Indexed
done_at
date and timeset when lane becomes Done
Indexed
Indexed fields are kept plain, so your cloud can sort and filter by them. Encrypted fields are encrypted before they reach the disk.
Each is a tab, drawn by your cloud itself on every surface:
cm taskssweep_donefirst_board · “your name's tasks”None. Everything it does is declared in quill.toml and run by your cloud itself.
A Quill for Cloudmorrow: boards, and three lanes on each — To Do, Doing, Done — because that is what a board is for.
- [ ] lines) live.| Datamodels | uses the foundational board and task (domain Tasks) |
| Screens | one board, on the phone, the web app, the terminal, cm tasks, and to your assistant |
| Jobs | sweep_done: deletes tasks that have been done for seven days |
| Datasets | first_board: one board for each person, the first time they open Tasks |
| Services, webhooks, APIs | none |
It contains no code: everything above is declared in quill.toml.
See CLAUDE.md. In short: cm quill check, then cm quill dev.
AGPL-3.0-or-later.