Skip to content
Recursive agents / control flow

Recursive reasoning. Finite execution. Verifiable output.

ELITZE uses an explicit LangGraph state machine for evidence loading, deterministic analysis, optional model triage, recursive consistency checking, and persistence. The loop has a hard two-review maximum; model output can never enlarge its own authority.

Control plane

Built for evidence-first security operations

Unavailable integrations are labeled not configured. Missing evidence is described as not verified or not measurable.

Bounded recursion

Maximum two passes

At most two NIM review passes are allowed in a run. Empty source windows stop with UNMEASURABLE; retries never synthesize observations.

Evidence allowlist

Immutable boundary

The model can reference only the finding IDs supplied for that run. Original severity and source references stay controlled by deterministic code.

Tool governance

Least privilege

A recursive answer is never an execution grant. Sensitive tools and response steps still require ELITZE authorization, scoped identity, and applicable approvals.

Enterprise helpdesk pattern

Human-controlled

A secure IT-helpdesk agent should answer from approved knowledge, link its sources, request clarification for ambiguous requests, and require approval before changing accounts, access or infrastructure.

Recursive vendor boundary

Explicit unknown

A named Recursive context-layer product is not assumed connected. No endpoint or API behavior is fabricated; direct connector support remains NOT_CONFIGURED pending documented API and customer credentials.

Audit-ready outcome

Traceable

Each LangGraph run records the tenant, requesting actor, evidence counts, model configuration state, review notes, evidence gaps and associated findings.

Related capabilities

ELITZE does not claim a clean posture when telemetry is absent. Live source records, authorization scope, execution state, and verification evidence remain separately visible.