Skip to main content

daimon 0.29.0: recording what was ruled out

· 3 min read
daimon maintainers
daimon maintainers
Daily-Nerd

A memory that only records what you decided is half a memory. The other half is what you ruled out, and why, so nobody spends another afternoon rediscovering it. 0.29.0 adds that half.

The refutation ledger​

daimon refute add records a scoped verdict against a subject, with evidence cited at the point of assertion. An agent's assertion stays a candidate until a human runs daimon refute ratify. daimon refute guard checks a proposed action against the active ledger before you repeat something already settled, and daimon refute overturn is how a verdict comes back off the books when the evidence changes.

Two design choices are worth stating plainly.

Nothing in the ledger is reaped on a schedule. A refutation is worth more with age, not less: the fact that an approach failed eight months ago is exactly what you want surfaced when someone proposes it again. So daimon refute search reads the complete ledger with no age decay, unlike checkpoint recall.

And the guard is advisory. It surfaces the prior verdict; it does not block the action. An agent can still proceed. What changes is that the record of what it was told exists either way, so a repeated mistake is now traceable to a decision rather than to ignorance.

The skills a host could not see​

The plugin ships two skills, daimon-briefing and daimon-end. They sat one directory below where the loader looks, so nothing failed and nothing warned. They were simply absent from the session's skill list.

0.29.0 puts them where hosts look, confirmed on a real install rather than inferred. The same release adds daimon why, the read side of an item's evidence, to the skill an agent actually reads. It had been documented for people and invisible to agents.

Also in this release​

Codex rollout stems now resolve to the spawned session id.

The CLI reference is regrouped by what you are trying to do rather than by subsystem.

A new claims page lists every number we publish about daimon itself, each with the command that measures the same thing on your own install. Those commands run locally and send nothing. Your numbers stay on your machine.

Getting it​

uv tool install daimon-briefing

Upgrading:

uv tool upgrade daimon-briefing

Plugin users need /plugin and a reload. The plugin cache is pinned per version, so the skills fix arrives with the release commit rather than with the PyPI publish.