system-overview.md

System Overview

Dispatchlane is planned as a Postgres-centred backend for integration reliability.

Intended shape

The first production shape is a modular monolith with separate runtime roles:

• api for ingestion and operator APIs
• worker for outbound delivery execution
• maintenance for recovery and background housekeeping

Core responsibilities

Dispatchlane is intended to provide:

• durable webhook receipt
• source verification
• canonical event persistence
• deduplication
• delivery attempt tracking
• retry scheduling
• dead-letter handling
• replay
• operator inspection

Design direction

The architecture should favour:

• explicit state transitions
• immutable historical records
• auditability
• production-style observability
• operationally honest guarantees

The system should not pretend to provide exactly-once delivery. The initial delivery model is at-least-once with replay-safe persistence and strong operator visibility.