Dægwork

Our household's jobs lived in a shared to-do app, a shared calendar and a sticky note on the fridge. Each one covered part of it, badly, and none of them knew about the others.

Once Armarium was running, task management was the obvious next gap. Dægwork (Old English dæg, "day", plus work) is its sibling: the same architecture, the same habits, the same small server, so running two apps costs barely more than running one.

Most task apps treat sharing as a switch: a list is shared, or it isn't. That's fine until tasks start depending on each other.

In Dægwork every task has one owner, who can share it, read-only or with edit rights, with a person or a group. The hard part was deciding what "no access" really means. It isn't enough that you can't open a task you weren't given. If a task you can see depends on one you can't, you shouldn't learn the hidden one exists, not even as a locked placeholder. Your task just shows as blocked. By what, you don't get to know.

That's much harder to build than a switch, and I chose it anyway. Access control is the one thing you can't quietly fix later, once people have trusted an app with private things.

Sub-tasks are for breaking something down. Dependencies are for saying "this has to happen before that". Most apps blur the two, so the order of things ends up tied to where they sit in a tree.

Dægwork keeps them apart. A dependency can link any two tasks, wherever they live, because real life doesn't respect your folders: you can't leave for the shop until the shopping list is done, whichever list either of them is on.

The Agenda view groups tasks by due date. The Board view lays them out in columns by status, and the statuses are yours to define. Both sit on the same filters and the same category tree, so switching view never loses your place. Dragging a card does what you'd expect in each: in Agenda it reschedules the task, on the Board it moves it along.

Adding a task works the same way. Pick what you're adding (a quick to-do, a link, a document reminder or a full task) and you only see the fields that kind of task needs, rather than one long form for everything.

The app came together quickly: three versions in three days in June, with Claude Code doing most of the typing. Accounts by email, an admin section, light and dark themes, and it installs as an app on phones, tablets and desktops, all reusing patterns Armarium had already proven.

What I haven't done is release it, and that's a choice. A rough edge in the interface is cheap to fix later. A sharing model that shows the wrong thing to the wrong person isn't, especially when the whole point is a household trusting each other with private tasks. So the plan changed from "ship something usable" to "don't ship until the access model can't get this wrong".

It'll be open source when it's ready, and I'm in no rush.