Core Concepts

Understand the three primitives that power NxtOne: observation layer, behavioral map, and alignment loop.

NxtOne shifts the debugging paradigm from searching raw text logs and system metrics to queries over a structured database of software actions. Here are the key primitives that power this model:

1. The Observation Layer

Traditional tracing relies on manual span creation, which is error-prone and omits local method contexts. The NxtOne Observation Layer attaches at the runtime engine level, transparently to your business logic. It captures execution branches, return payloads, throw frames, and variable states automatically, with zero manual instrumentation code required.

2. The Behavioral Model

Every runtime event emitted is consolidated into a unified Behavioral Modelof your system's execution. The model captures:

• Topology: Your microservices, systems, and the pathways between them.
• Execution Flow: The sequence of method calls, HTTP handlers, and database interactions that make up each request.
• Contextual Data: Parameters, return values, and the propagation of data across services — safely serialized and scoped to your security perimeter.

3. Session Lifecycle & Application Code Mapping

A Session represents a single bounded execution context (such as an API request processing pipeline or a cron task run). As the session boots, NxtOne performs Application Code Mapping — securely linking execution to your repository so investigation screens surface the exact code context (variables, class methods, lines) alongside each live snapshot.