Documentation
¶
Overview ¶
Package componentregistry provides component registration for SemStreams framework. This package registers both protocol-level and semantic-level components.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func Register ¶
Register registers all SemStreams framework components with the provided registry. This includes protocol-layer, semantic-layer, and example domain components:
Protocol Layer (network/data agnostic):
- UDP input (network protocol)
- WebSocket input (federation)
- JSONGeneric processor (Plain JSON wrapper)
- JSONFilter processor (field-based filtering)
- JSONMap processor (field transformation)
- ObjectStore storage (NATS JetStream)
- File output (file system)
- HTTP POST output (webhooks)
- WebSocket output (broadcasting)
- HTTP gateway (bidirectional HTTP ↔ NATS request/reply)
Semantic Layer - Graph Components (modular architecture):
Core (all tiers): - graph-ingest (entity/triple CRUD, hierarchy inference) - graph-index (OUTGOING, INCOMING, ALIAS, PREDICATE indexes) - graph-gateway (GraphQL + MCP HTTP servers) Statistical/Semantic tier: - graph-embedding (vector embedding generation) - graph-clustering (community detection, structural analysis, anomaly detection, LLM enhancement) Optional indexes: - graph-index-spatial (geospatial indexing) - graph-index-temporal (time-based indexing)
Semantic Layer - Rule Processing:
- Rule processor (rule-based transformations)
Agentic Layer - LLM-powered autonomous agents:
- agentic-model (OpenAI-compatible LLM endpoint caller)
- agentic-tools (tool execution dispatcher)
- agentic-loop (state machine orchestrator with trajectory capture)
- reactive-workflow (reactive rules engine for KV watch and subject-triggered workflows)
AGNTCY Integration Layer - Internet of Agents interoperability:
- oasf-generator (generates OASF records from agent capabilities)
- directory-bridge (registers agents with AGNTCY directories)
- slim-bridge (receives messages from SLIM groups via MLS)
- a2a-adapter (receives A2A task requests from external agents)
- otel-exporter (exports agent telemetry to OpenTelemetry collectors)
Domain Layer (example processors):
- IoT sensor processor (JSON sensor data → Graphable SensorReading)
- Document processor (document processing)
Note: Domain-specific components (MAVLink, robotics, etc.) are registered in separate modules like streamkit-robotics.
Types ¶
This section is empty.