External signals & onboarding import
external-signals and onboarding-import are the ingress edges that feed Zephr's belief
circuit. external-signals consumes CI and external code/signal ingress (the observability edge);
onboarding-import boots a workspace from a cold-start corpus or a partner data set. Both are
clean-bill shipped capabilities — the map carries no fabricated claims for them. They depend on
surfaces (the hook/signal vocabulary) and memory (the write path they inject into); neither
re-specifies the memory lifecycle, which lives in Memory.
Capability status
| Capability | Tier | Status | Evidence |
|---|---|---|---|
external-signals | Observability edge | Shipped | CI and external code/signal ingress |
onboarding-import | Surfaces extension | Shipped | Cold-start corpus / partner import engine |
external-signals
external-signals ships the CI and external code/signal ingress surface. It is the edge the
autonomous-agents trigger (guard_agent_trigger) and Pulse signal producers attach to, and it
is the source of the ci_status signal referenced by scheduled agent definitions. It emits
structured signals into the event bus (event-bus) and records no belief directly — capture into
the belief base is owned by memory and universal-capture.
onboarding-import
onboarding-import ships the import engine for cold-start corpora and partner onboarding. It
populates a workspace's initial belief set without hand entry, routing parsed material through
the memory write path with the same review-state defaults as live capture (UNREVIEWED).
Availability
| Surface | Tier | Residency | Notes |
|---|---|---|---|
zephr signal connect|list (CLI) | — | local, cloud | Signal connection and listing |
| CI / external signal producers | — | cloud | Produce into external-signals / event-bus |
Onboarding import (zephr import / partner flow) | — | local, cloud | Cold-start corpus / partner data seeding |
Egress
| Surface | Public service class | Payload class | Boundary owner |
|---|---|---|---|
| External-signal webhook ingress | webhook-receiver | metadata + source-code | platform admission |
| Partner import egress | partner-api | metadata + source-code | onboarding-import |
Both edges are reviewed and labelled with closed payload classes rather than hostnames or tenant coordinates.
Limits and failures
external-signalsdoes not assert truth: a received signal enters the event bus as metadata and must passgovernanceandtrustreview before it can influence recall.onboarding-importseedsUNREVIEWEDbeliefs only; bulk import never bypasses the review state machine.
Related capabilities
event-bus (single publish surface for DispatchEvent envelopes), governance (signal-origin
constraints), and Data flows: capture (the observation→belief path these
edges feed).