Glossary

The terms you'll meet across DXDT. Follow the links for the full story.

Actioned savings — Identified savings on findings your team marked resolved. See Pulse.

Blast radius — The set of entities affected if a given entity fails, answered from the graph: "what depends on this replica?"

Dependency — A relationship between two entities in the graph (e.g. payments-api depends on sql-replica-ew1). Dependencies power blast-radius answers and plan review.

Domain — The area a finding belongs to: FinOps, security, SRE, or topology. Findings can be filtered by domain.

Entity — A node in the graph: a service, database, load balancer, cluster, or other resource DXDT has mapped.

Finding — A discovered cost, reliability, or security issue produced by Pulse, with a severity, evidence, and a lifecycle status (open → acknowledged → in_progress → resolved / dismissed).

Graph, the — DXDT's continuously maintained map of your infrastructure: entities and their dependencies. Powers blast-radius answers, incident context, and plan review; visible on the Memory page.

Identified savings — The estimated monthly savings on a grounded finding, summed over unique resources so overlapping findings never double-count. See Pulse.

Incident — A tracked operational event (SEV1–SEV4) with a commander and a permanent timeline. See War rooms & incidents.

Institutional memory — Everything your team has taught DXDT, stored with attribution and injected into every future agent run. See Institutional memory.

Integration — A connection installed from the in-app Marketplace (cloud providers, monitoring, ticketing). Integrations define what DXDT can see; every claim DXDT makes is grounded in integration data.

Investigation mode — The chat sidebar's Deep Investigation toggle: switches a turn from conversational chat to a more thorough, multi-step investigation.

Morning Report — The once-daily digest of what happened overnight, plus exactly one decision to take, delivered to Slack or email. See Morning Report.

Personal access token (PAT) — A dxdt_... bearer credential for the CLI and API, pinned to the minting user and tenant, with read or read_write scope. See Authentication.

Plan review — DXDT's change gate: submit a Terraform plan and get cited risk annotations grounded in your live environment. Read-only, guaranteed. See Plan review.

Pulse agent — One of the autonomous domain investigators (cost, security posture, threats, topology, and more) that scans your connected infrastructure on a schedule and writes findings and recommendations.

Quiet night — A Morning Report with nothing to report: no new findings, no incidents. DXDT says so explicitly.

Realized savings — Savings confirmed against your actual cloud bill. Never estimated: if you don't see a realized figure, DXDT won't invent one.

Recommendation — The suggested action attached to a finding, with estimated monthly savings where applicable. Carries its own status (pending → in_progress → completed / dismissed).

Replay — A reconstructed war room (title starts with [Replay]) interleaving a past incident's timeline with what DXDT would have contributed. Marked on every entry; never mixes into your real history.

Session — One durable conversation with the chat agent. Turns run server-side, so a dropped connection never kills an investigation.

Severity — The urgency ranking. Findings run critical … info; incidents run SEV1–SEV4; triage events run CRITICAL–INFO.

Taught fact — A single durable statement your team taught DXDT, stored with who taught it and when, and cited whenever it shapes an answer.

Tenant — Your organization. Every session, finding, incident, and token is tenant-bound; the API never returns another tenant's data.

Triage event — An alert ingested from a monitoring source (Datadog, PagerDuty, CloudWatch, and others) into DXDT's triage pipeline, where it is assessed — investigate, enrich, or auto-close — and routed onward.

Triage rule — A rule you define (source filter + match conditions → forced action) that overrides automatic triage decisions for matching events.

War room — The live collaboration surface on an incident: the shared timeline, the responders, and the DXDT agent working alongside them. Optionally mirrored to a dedicated Slack channel.