ADR-0001: relayr, its own repository and package¶

Status: Accepted Date: 2026-09-29 Deciders: Alex Nodeland

Records decision D1 of stackr RFC-0002, the combined system.

Context¶

artifactr and reflexr are independent siblings: neither imports the other, and the adapters between them belong to the system that combines them (reflexr ADR-0003). That system is an application built from stackr's template (artifactr ADR-0032). The adapters carry invariants that are easy to get wrong: ids derived for idempotency, loop control, and allowlists that are the only check on some commands. Every application that wrote its own would meet the same hard parts.

Decision¶

• The bridge is a new sibling repository and package, relayr, depending on artifactr and reflexr through their public APIs only.
• It holds the two adapters, the bridged event types, and the ledger with its in-memory and SQL adapters; later, the rule artifact type and the install rule, the proposal-outcome evaluator, and the telemetry links and tags.
• stackr's template wires it in through a bridge question in its both variant, pinned by revision like the libraries.
• The name is relayr: it relays events and commands between the two libraries, and fits the family's names. bridgr and linkr were considered; "link" already means trace and span links in this design.

Options considered¶

Consequences¶

• Easier: the invariants are written, tested and fixed once, and the libraries stay independent.
• Harder: one more package to release and pin, and relayr moves with both libraries' public APIs.