# Worlds Documentation

## Docs

- [3.0.0](https://docs.worlds.io/3-0-0.md)
- [3.1.0](https://docs.worlds.io/3-1-0.md)
- [3.1.1](https://docs.worlds.io/3-1-1.md)
- [3.2.1](https://docs.worlds.io/3-2-1.md)
- [3.3.1](https://docs.worlds.io/3-3-1.md)
- [3.4.0](https://docs.worlds.io/3-4-0.md)
- [Composing Checks](https://docs.worlds.io/concepts/check-chaining.md): How to combine check types to build any detection use case
- [Detection Pipeline](https://docs.worlds.io/concepts/detection-pipeline.md): How detection data flows from cameras through the state machine to your workflows
- [Signals](https://docs.worlds.io/concepts/signals.md): Understanding track and zone signals from the state machine
- [Tracks & Zones](https://docs.worlds.io/concepts/tracks-and-zones.md): Understanding the core data structures in Worlds detection workflows
- [Architecture Overview](https://docs.worlds.io/getting-started/overview.md): How the Worlds detection pipeline connects to your workflows
- [Prerequisites](https://docs.worlds.io/getting-started/prerequisites.md): What you need before building Worlds workflows
- [Batch Track State Workflow](https://docs.worlds.io/guides/batch-track-state.md): Build a workflow that processes complete track summaries after tracks expire
- [Choosing Your Workflow Pattern](https://docs.worlds.io/guides/choosing-your-workflow.md): A decision guide for selecting the right trigger mode, signal type, and check nodes for your use case
- [Streaming Track State Workflow](https://docs.worlds.io/guides/streaming-track-state.md): Build a workflow that reacts to real-time track updates with check-based event management
- [Streaming Zone State Workflow](https://docs.worlds.io/guides/streaming-zone-state.md): Build a workflow that monitors aggregate zone activity in real time
- [Worlds Workflow Builder](https://docs.worlds.io/index.md): Build automated detection workflows using Worlds custom nodes for the Workflow Builder
- [Worlds Actions](https://docs.worlds.io/nodes/actions.md): General-purpose action node for AI operations, image processing, email, and data queries
- [Check Types Overview](https://docs.worlds.io/nodes/check-types-overview.md): The three composable check types that form the foundation of every Worlds workflow
- [Debug](https://docs.worlds.io/nodes/debug.md): Debug and manage event state in the state machine's Redis store
- [Detection Webhook Trigger](https://docs.worlds.io/nodes/detection-webhook-trigger.md): Receive real-time track and zone state from the Worlds detection pipeline
- [Event Manager](https://docs.worlds.io/nodes/event-manager.md): Create, update, and close events in the Worlds platform
- [Event Orchestrator](https://docs.worlds.io/nodes/event-orchestrator.md): Intelligent event lifecycle routing based on check results
- [Replay Trigger](https://docs.worlds.io/nodes/replay-trigger.md): Replay historical track detections for testing workflows without live camera feeds
- [Type I: Track in Zone](https://docs.worlds.io/nodes/type-1-track-in-zone.md): Check if a track's interaction with configured zones meets threshold conditions
- [Type II: Zone Sequence](https://docs.worlds.io/nodes/type-2-zone-sequence.md): Check if a track visited zones in a specific order
- [Type III: Track Interaction](https://docs.worlds.io/nodes/type-3-track-interaction.md): Check if a track interacted with other tracks matching tag and threshold criteria
- [Zone Activity Check](https://docs.worlds.io/nodes/zone-activity-check.md): Evaluate zone-level conditions like track count, dwell time, and intersection
- [State Machine API](https://docs.worlds.io/state-machine/api-reference.md): REST API reference for the state machine service
- [State Machine Overview](https://docs.worlds.io/state-machine/overview.md): The Go service that bridges the Worlds detection stream and your workflows

## OpenAPI Specs

- [openapi](https://docs.worlds.io/api-reference/openapi.json)