App · in development
Spicilège
Intentions: for each saved item, why it was kept, proposed by a local model and measured.
Dispatches
From the workshop log
Site · built, not yet online
arsis.dev
Three mockups, then a new direction: the site becomes the workshop’s window.
App · in development
Rhizomes
The redesign goes on, on a new desktop base.
App · in development
Spicilège
A local model proposes bookmarks for notebooks; tags that evolve; a choice of app icon.
Open source · open source soon
LLMarium
Models in memory, each with what launched it; heading for an open-source release.
Game · in development
Futon Fighters
The couch-game collection gets its name, Futon Fighters, and a new icon.
Game · in development
Tales of Chinatown
Four drawn banners chosen for the store page; the game gets its page on this site.
App · prototype, moving fast
Squatcat
Calendar and routine: an eight-week programme, sessions played step by step, summaries.
The week in numbers
Measured, as of 14 Oct 2026.
- Projects touched in the last 7 days
- 9 of 14
- Changes in the last 7 days
- 273
- Changes in the last 30 days
- 1,094
Busiest of the twelve weeks: 517 changes.
Finds
-
Directory ·
mkdir (opens in a new tab)mkdir.directory
-
Site ·
Overbrowsing (opens in a new tab)overbrowsing.com
-
Site ·
Material-Archiv (opens in a new tab)materialarchiv.ch
Latest workshop note
correction ·
A second model reviewed Syntype and found four blocking issues: a survival task that mostly predicted harvest, modelled tree heights, a growth task solved by “next year equals this year”, and species reduced to their epithet. Public correction the same evening.
Activity board
Twelve weeks on the bench
Changes per week in each project’s Git history, as of 14 Oct 2026. Busiest first, by the last 30 days.
| Project | 11 weeks ago | 10 weeks ago | 9 weeks ago | 8 weeks ago | 7 weeks ago | 6 weeks ago | 5 weeks ago | 4 weeks ago | 3 weeks ago | 2 weeks ago | 1 week ago | now | 30 days | Last |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Daymon Next up | 0 | 3 changes | 0 | 0 | 0 | 2 changes | 17 changes | 0 | 0 | 222 changes | 28 changes | 15 changes | 265 changes in 30 days | |
| Tales of Chinatown On the fire | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 95 changes | 157 changes | 252 changes in 30 days | |
| LoopHuntr Next up | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 change | 181 changes | 0 | 1 change | 183 changes in 30 days | |
| Spicilège On the fire | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 23 changes | 69 changes | 28 changes | 3 changes | 11 changes | 134 changes in 30 days | |
| NamerKit Next up | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 66 changes | 30 changes | 0 | 96 changes in 30 days | |
| Futon Fighters On the fire | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 24 changes | 24 changes | 48 changes in 30 days | |
| ron-ron | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 39 changes | 39 changes in 30 days | |
| Slyfari Side projects | 3 changes | 0 | 0 | 0 | 0 | 0 | 2 changes | 0 | 0 | 16 changes | 7 changes | 0 | 23 changes in 30 days | |
| Rhizomes On the fire | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 10 changes | 8 changes | 18 changes in 30 days | |
| Appothèque Open source | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 11 changes | 0 | 11 changes in 30 days | |
| arsis.dev On the fire | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 10 changes | 10 changes in 30 days | |
| LLMarium Open source | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 change | 8 changes | 9 changes in 30 days | |
| Syntype On the shelf | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 changes | 0 | 0 | 4 changes in 30 days | |
| tralala Side projects | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 changes | 0 | 2 changes in 30 days |
Changes in a week
- none
- 1–4
- 5–19
- 20–69
- 70 or more
Columns run from 11 weeks ago (left) to now (right). The number in a square is the exact count; colours only group them. “Last” is the date of the latest change. 14 projects measured.
Feature · Daymon ·
Multi-signal attribution in Daymon
The hardest problem in automatic time tracking isn’t capturing activity — it’s attributing it to the right project. When you switch between a browser tab, a terminal, and an IDE in the span of 30 seconds, which project owns that time?
Daymon solves this with a multi-signal attribution system. Each activity window gets scored against project rules (path patterns, URL patterns, app names, title regex), and the highest-scoring project wins. When signals are ambiguous, the system falls back to file modification context — if you just saved a file in project A, the next 60 seconds of browser activity probably belongs to project A too.
The implementation uses pre-compiled regex patterns stored in a RuleMatcher, with configurable priority levels. Rules can be imported/exported as JSON, and templates exist for common project types (React app, Rust crate, Python package, etc.).
The tricky part was reassignment: when you realize attribution was wrong for a past session, the timeline view now supports drag-to-reassign with full propagation of the rule change to prevent the same misattribution in the future.