Skip to main content
If your job is to operate the platform rather than write agent code — gating risky changes, debugging cross-agent flows, managing access, integrating with your observability stack — this is your reading path.
This page is a curated reading path, not new material. Every link goes to an existing guide. Treat it as the “what to read in what order” map.

​
The problem this page solves

You have engineering teams shipping agents on DecimalAI. Your job is to make sure:
  • When a change is about to break production, it is caught in CI before it merges.
  • When something goes wrong across multiple agents, you can trace the cross-agent flow (multi-agent debugging).
  • The right people have access to the right agents (teams + RBAC).
  • The deployment satisfies your org’s security and compliance bar.
This reading path covers all four.

​
Reading path (in order)

1

Step 0 — new to DecimalAI? (2 minutes)

Before wiring anything up, get a feel for what DecimalAI does. Run the 2-minute demo:
The 2-Minute Demo walkthrough explains what the report is telling you. Prefer prose? Skim the Introduction first.
2

Understand the multi-agent debugging model

Multi-agent guide — how orchestrator → sub-agent handoffs get traced, how parent_trace_id links them, and what the dashboard shows for cross-agent flows.Read this even if your engineers don’t think they have a multi-agent system. Any agent that calls another agent (e.g. a router calling specialists) shows up here.
3

Gate merges with the regression check

Run the regression check in CI so a manifest change that affects production traces blocks the pull request instead of shipping silently. The check comments its verdict on the PR, so the signal reaches the author where they already are.
4

Set up teams and per-agent RBAC

Teams guide — workspaces, teams, per-agent role assignments, the audit log.The common shape: one workspace per business unit, one team per product, agents owned by the team that ships them. Platform team gets workspace-admin; product engineers get team-member.
5

Review the security model

Security page — encryption at rest / in transit, data residency, retention policies, and the redaction / PII handling model.Pay special attention to the redaction section if your agents see PII — DecimalAI’s default is to store full payloads; redaction is opt-in via SDK config.
6

Configure trace retention + budgets

Pricing page for the per-tier retention limits.Trace volume budgets are set per workspace. Set conservative budgets early — you can raise them; you can’t easily un-page someone who got an after-hours bill alert.

​
Operational dashboards you’ll live in

​
Integration patterns

Periodic JSONL export via the Datasets API into your own bucket. Schedule it as often as your dashboards need — daily and weekly aggregates are the common cadences.
Use the generic OTel integration on the SDK side. The SDK can dual-emit to DecimalAI and your existing OTel collector, so you get DecimalAI’s manifest-aware view and your APM’s flame-graph view without instrumenting twice.

​
When to talk to the engineers page instead

If your job is more about writing agent code — adding traces, configuring regression checks, debugging your own agent’s behavior — read DecimalAI for Engineers first.

​
What’s next

Multi-agent

Cross-agent trace linking and orchestrator patterns.

Teams

Workspaces, RBAC, audit log.

Security

Encryption, data handling, and how we treat your traces.