harness-multitool

0031 — Custom callbacks are project handlers

Context

ADR 0015 made a custom callback handler a plugin crate linked into the multitool binary. No such crate was ever built (journal#101). A project that wants its own callback type, such as deploy_done, should not have to rebuild the harness.

Decision

A custom callback belongs to the project: .harness/callbacks/<name>/ holds a config.toml and a handler.

The handler

The daemon stands at the start, as for every callback

A custom callback comes to a conversation's URL with a uuid and a type, like a default one. The daemon keeps a registry, conversation → type → handler, in hash tables, so a callback finds its handler in O(1). Standard types stay native.

The handler stands between the daemon and the conversation

Trust

Rejected

This page's source