Tuple Tech
AI LayerPart of Stratos

AI Agents

Four specialized agents built for real engineering environments — each one understands your environment, not just your prompts.

  • Infra Agent — cloud automation, drift detection, and IaC
  • DV Agent — design verification, test generation, and coverage
  • PV Agent — physical verification triage, traced to the source
  • SVA Agent — assertion generation, analysis, and failure debug
Request a DemoView Stratos Platform
Infra AgentDV AgentPV AgentSVA Agent
Infra Agent

Infrastructure that provisions, detects drift, and self-corrects

Infra Agent connects to your cloud environment and acts as an autonomous infrastructure operator. It detects configuration drift, generates remediation plans, provisions resources from natural language, and keeps an auditable change log — across AWS, GCP, and Azure.

  • Automated infrastructure provisioning from natural language
  • Drift detection and autonomous remediation
  • IaC generation and review (Terraform, Pulumi)
  • Multi-cloud resource orchestration (AWS, GCP, Azure)
  • Policy enforcement and compliance guardrails
  • Auditable change history and rollback support
Infra Agent · Drift Detectionprod-cluster · ap-south-1
$ stratos infra scan --env production
⚠ Drift detected — 3 resources out of sync with IaC state
aws_security_group.api-gateway ingress rule added
aws_autoscaling_group.workers desired_capacity: 4 → 6
aws_iam_role.deploy-role policy attached manually
Generating remediation plan…
infra agent — Remediation plan ready. 2 changes require approval (security group, IAM policy). Auto-applying autoscaling correction. Estimated apply time 45s. Run `stratos infra apply --plan 7c3a` to proceed.
dv_agent.log
coverage.rpt
VS Code Extension
DV Agent · Design Verification
youCoverage is stuck at 78% on block MEM_CTRL. What's missing?
dvScanning coverage report and testbench constraints…
dv agent — 3 uncovered FSM states in mem_ctrl_arb: IDLE→STALL→RETRY path not exercised. Suggested: add directed test for back-pressure + retry sequence. Estimated coverage lift: +9%. Testbench snippet ready to insert.
youGenerate the testbench snippet.
dv agent — Snippet generated for IDLE→STALL→RETRY. Inserted at line 247 of mem_ctrl_tb.sv. Re-run sim to confirm coverage closure.
DV Agent

Test generation and simulation — without the manual effort

DV Agent understands your testbench, coverage reports, and design specs. It generates tests for uncovered paths, runs simulations, and automates regression management — so your team closes coverage faster without manual effort.

VS Code Extension

DV Agent is available directly inside VS Code. Inline suggestions, diff-aware context, and chat — without leaving your editor. IP stays on-prem with self-hosted inference.

  • Test generation for uncovered paths, FSM states, and corner cases
  • Simulation run management and regression automation
  • Coverage analysis and gap identification across functional and code coverage
  • Directed test authoring from coverage holes — no manual testbench edits
  • Spec-aware context from your runbooks and design docs
  • Formal verification setup and result interpretation
PV Agent

Physical verification triage — traced to the source

PV Agent triages DRC, LVS, and ERC failures — identifies root causes, traces violations back to the responsible commit, and surfaces fix suggestions with full runbook context. Sign-off moves faster when every error already has an answer.

IP stays on-prem

PV Agent supports self-hosted LLM inference — your design data never leaves your environment. Required for tape-out sensitive and export-controlled designs.

  • DRC, LVS, and ERC triage with root-cause identification
  • Fix suggestions with cross-project runbook context
  • Commit-aware: traces violations back to the responsible change
  • Batch violation analysis across full chip or block level
  • Self-hosted or cloud LLM inference — IP stays on-prem
  • VS Code extension for inline access during sign-off
pv_agent.log
drc_summary.rpt
VS Code Extension
PV Agent · Physical Verification
youPV run failed on VCO_LDO — what triggered it?
pvParsing DRC log and cross-referencing recent commits…
pv agent — Metal-3 spacing violation near bias resistor array (4 instances, rule M3_SP_MIN). Introduced in last commit by @mpark. Fix: increase spacing by 0.04µm on nets VN_BIAS[2:0]. Same pattern resolved in BGR_CORE — runbook #441 linked.
youAre there similar violations elsewhere in the block?
pv agent — Scanning full block for M3_SP_MIN pattern… 2 additional instances found in VCO_CORE near net VBG_REF. Same fix applies. All 6 violations can be resolved in one edit pass — diff ready.
SVA Agent

SystemVerilog Assertions — generated, analyzed, and debugged

SVA Agent understands your RTL design intent and generates assertion-based verification collateral automatically — from property generation to coverage analysis and failure debug. Reduce hand-written assertion effort and close SVA coverage faster.

  • Automatic SVA property generation from RTL and spec context
  • Coverage analysis — identifies which assertions are firing, dormant, or vacuous
  • Failure triage — traces assertion violations back to the originating design change
  • Waveform-aware debug: correlates assertion failures with signal activity
  • Works with formal verification tools and simulation regressions
  • Self-hosted or cloud LLM inference — IP stays on-prem
sva_agent.log
assertions.sv
SVA Agent · SystemVerilog Assertions
youGenerate assertions for the AXI handshake in axi_slave.sv
svaParsing RTL and extracting handshake protocol intent…
sva agent — Generated 6 assertions for AXI4 handshake: VALID/READY stability, no X-propagation on data, and address alignment. 2 properties flagged as potentially vacuous — recommend formal prove run to confirm. Assertions inserted at line 84 of axi_slave.sv.
youOne assertion is failing in sim — VALID_STABLE_ASSERT
sva agent — VALID_STABLE_ASSERT fires at time 4820ns. AWVALID deasserted before AWREADY — violates AXI4 spec §A3.2.1. Introduced in commit c9f2a by @rlee (pipeline stall fix). Suggested fix: add hold condition in axi_master.sv line 211.

Put AI to work in your environment

See how all four agents work together inside your existing infrastructure and EDA workflows.

Book a Demo