Skip to main content
The Siglo ecosystem provides modular, production-ready integrations across observability, HTTP web frameworks, message brokers, persistent storage backends, generative AI, and developer tooling. The core runtime (@siglo/core) remains strictly zero-dependency; all ecosystem integrations are published as independent packages that depend only on standard interfaces (StorageAdapter, IdempotencyStore, Flow, ExecutionOptions).

Ecosystem Directory

Detailed standalone guides are available for each plugin, adapter, and developer CLI:

Architecture Overview


Cross-Cutting Architectural Contracts

All adapters adhere to unified operational contracts that ensure predictable runtime behavior across diverse infrastructure backends:

1. Ingress & Context Extraction Contract

Every HTTP and queue adapter unwraps parameters, extracts correlation identifiers, and attaches abort signals:
  • Correlation Tracking:
    • HTTP adapters inspect x-correlation-id and x-request-id, echoing X-Correlation-Id on responses.
    • SQS and BullMQ map job/message identifiers into workflow idempotency keys.
    • OpenTelemetry injects and extracts W3C traceparent headers across process boundaries.
  • Workflow Stack ID:
    • Successful executions inject X-Workflow-Stack-Id into outgoing headers, linking client requests directly to persistence and telemetry records.
  • Context Unwrapping (unwrapContext):
    • Strips internal engine state (keys prefixed with $) and evaluates getter functions, ensuring clean, JSON-serializable payloads for downstreams.

2. Error Status Code Normalization

All HTTP adapters (@siglo/express, @siglo/fastify, @siglo/hono, @siglo/notifications) share an identical error categorization contract:

Installation & Quick Start Matrix

Each package can be installed independently as needed: