Atlas overview

Atlas is the Observability Platform product in the Lightning IT portfolio. Its conceptual verb is Observe: Atlas is the product boundary for turning approved operational signals into service and platform insight.

Atlas is one of the five sellable products. ModuLix is the reusable engineering and automation content foundation, not a sixth product. AIO and Wunderbox may emit operational signals, Workbench may validate observation changes, and Platform Governance & Evidence may evaluate evidence derived from authorized observations. These boundaries do not imply a bundle, supported integration, or commercial commitment.

Public documentation scope

The initial public Atlas documentation defines:

• signal, context, ownership, and quality concepts;
• a conceptual path from source to authorized observation;
• operating checks for collection quality, capacity, retention, and alerts;
• security handling for potentially sensitive telemetry; and
• a troubleshooting flow for missing, delayed, or misleading observations.

It does not assert a collector, protocol, storage engine, query language, dashboard technology, alert manager, retention duration, deployment topology, or supported integration. Those details require an implementation-specific, verified public release contract.

What observability can and cannot prove

An observation is evidence from a defined source, time window, and processing path. It can support a decision only when its provenance, freshness, completeness, and interpretation are understood. A dashboard status does not by itself prove service health, security-control effectiveness, or compliance.

Provenance and lifecycle

This document is bounded by the canonical product authority, LIT-PRD-90-Atlas version 12. That authority approves the https://docs.l-it.io/atlas/ route family and the initial https://docs.l-it.io/atlas/overview/ route. Review is required annually and after any material scope, claim, taxonomy, delivery-boundary, or route change.

Continue

• Concepts defines the public vocabulary.
• Architecture describes conceptual signal boundaries.
• Operations covers quality and service readiness.
• Security covers telemetry sensitivity and access.
• Troubleshooting covers signal-path diagnosis.