Connector contract: events in, actions out, lookups #1979

Closed
opened 2026-11-14 14:42:47 +00:00 by sam · 1 comment
Owner

Every system Archie hears from or acts on is a connector extension. A connector declares its event types (with typed fields), its actions (with input schemas and reversibility), and its lookups (such as ownership). Core contains no vendor-specific code for any of them.

Done when: a connector extension can be installed that provides events, actions and a lookup, and a workflow can use all three without core changes.

Spec: principle 3, R6, R17.

Every system Archie hears from or acts on is a connector extension. A connector declares its event types (with typed fields), its actions (with input schemas and reversibility), and its lookups (such as ownership). Core contains no vendor-specific code for any of them. Done when: a connector extension can be installed that provides events, actions and a lookup, and a workflow can use all three without core changes. Spec: principle 3, R6, R17.
sam added the featurehigh labels 2026-11-14 14:42:47 +00:00
sam added a new dependency 2026-11-14 14:42:58 +00:00
sam added a new dependency 2026-11-14 14:43:01 +00:00
sam added a new dependency 2026-11-14 14:43:01 +00:00
sam added a new dependency 2026-11-14 14:43:01 +00:00
sam added a new dependency 2026-11-14 16:02:46 +00:00
Author
Owner

Done. The connector contract declares events (typed schemas), actions (input schema, declared effect, per-action Resolve, idempotency keys, executed digest, unknown outcomes), lookups, deliveries (messages and records, never offered to an agent) and listening (a stream from a connection the connector holds, resumed from a stored cursor). On staging, extensions installed without core changes provide each: Alertmanager events, host lookups, Semaphore template actions, a Prometheus MCP server's lookups, and Telegram deliveries and answer events. The investigate workflow uses events, lookups and actions together.

Done. The connector contract declares events (typed schemas), actions (input schema, declared effect, per-action Resolve, idempotency keys, executed digest, unknown outcomes), lookups, deliveries (messages and records, never offered to an agent) and listening (a stream from a connection the connector holds, resumed from a stored cursor). On staging, extensions installed without core changes provide each: Alertmanager events, host lookups, Semaphore template actions, a Prometheus MCP server's lookups, and Telegram deliveries and answer events. The investigate workflow uses events, lookups and actions together.
sam closed this issue 2026-11-15 17:29:59 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1979