Zephr Docs

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

CapabilityTierStatusEvidence
external-signalsObservability edgeShippedCI and external code/signal ingress
onboarding-importSurfaces extensionShippedCold-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

SurfaceTierResidencyNotes
zephr signal connect|list (CLI)—local, cloudSignal connection and listing
CI / external signal producers—cloudProduce into external-signals / event-bus
Onboarding import (zephr import / partner flow)—local, cloudCold-start corpus / partner data seeding

Egress

SurfacePublic service classPayload classBoundary owner
External-signal webhook ingresswebhook-receivermetadata + source-codeplatform admission
Partner import egresspartner-apimetadata + source-codeonboarding-import

Both edges are reviewed and labelled with closed payload classes rather than hostnames or tenant coordinates.

Limits and failures

  • external-signals does not assert truth: a received signal enters the event bus as metadata and must pass governance and trust review before it can influence recall.
  • onboarding-import seeds UNREVIEWED beliefs only; bulk import never bypasses the review state machine.

event-bus (single publish surface for DispatchEvent envelopes), governance (signal-origin constraints), and Data flows: capture (the observation→belief path these edges feed).