Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • Getting Started with AI for VLSI Engineers5
  • Just Enough AI: Models and Context15
  • Prompting13
  • Trust and Verification14
  • Using AI for Engineering Work17
  • Engineering Walkthroughs7
  • Practical Foundations for AI Workflows4
  • Engineering Data5
  • Retrieval-Augmented Generation6
  • Agents and Tool Use18
  • Agent Design8
  • MCP and Skills6
  • Multi-Agent Design6
  • Practical Capstone6
  • Tokens, Cost and Latency12
  • Agentic Workflows for Chip Teams18
    • Regression Triage Agent
    • Lint-and-Fix Loops
    • Guardrails and Human in the Loop
      • Permission Tiers and Least Privilege
      • Sandboxing and Approval Gates
      • Rate, Cost Limits and Audit Logs
      • Secret Handling
      • Prompt Injection from Files and Logs
    • Evaluating and Operating Agents
  • Interview and Judgment10
  • AI Skills: Full Course Index
  • Working with AI Glossary
  • Working with AI Cheatsheet
Loading lesson

‹Guardrails and Human in the Loop
  1. Topics
  2. AI Skills for VLSI Engineers
  3. Agentic Workflows for Chip Teams
  4. Guardrails and Human in the Loop
  5. Rate, Cost Limits and Audit Logs

Reference: Agentic Workflows for Chip Teams · Beginner to Intermediate

Rate, Cost Limits and Audit Logs

Rate and cost limits with worked arithmetic, plus audit logs that record every action.

On this page

    Rate and cost limits

    Limits bound how much an agent may attempt. Rate limits cap actions per hour or day, and cost limits cap billed units per run.

    Both are EXAMPLE parameters set before the run. The checker refuses new actions once a cap is reached.

    Limit

    EXAMPLE setting

    What it stops

    Steps per run

    At most 30 tool calls

    Loops that never converge.

    Jobs per day

    At most 20 simulation jobs

    Queue flooding across a team.

    Billed units per run

    At most 8 cost units

    An expensive retry spiral.

    Worked cost arithmetic

    Cost follows one formula with stated EXAMPLE prices. Substitute the run counts to get the run total in cost units.

    plaintext
    1
    2
    3
    4
    5
    6
    7
    8
    EXAMPLE parameters: 1M input tokens cost 3 units, 1M output tokens cost 12 units
    formula: cost = input_tokens / 1M x input_price + output_tokens / 1M x output_price
    per step: 40000 input tokens, 8000 output tokens
    input part = 40000 / 1000000 x 3 = 0.04 x 3 = 0.12 units
    output part = 8000 / 1000000 x 12 = 0.008 x 12 = 0.096 units
    per-step total = 0.12 + 0.096 = 0.216 units
    30-step run total = 30 x 0.216 = 6.48 units
    check against EXAMPLE cap of 8 units: 6.48 < 8, so the run fits
    plaintext
    1
    2
    3
    4
    EXAMPLE daily budget: 20 simulation jobs per team per day
    each triage run uses 2 jobs
    runs per day = 20 / 2 = 10 runs
    a proposed 11th run needs a wider budget or waits for the next day

    Audit logs

    The log records every proposed action, its verdict, and any approval. It is append-only and written by the checker, not the agent.

    Each entry names who, what, and when. A minimal entry holds time, run id, action, target, verdict, and approver.

    Field

    Example value

    Use

    Time

    2026-05-01 09:14 UTC

    Orders events during review.

    Run

    triage-042

    Groups one run's actions.

    Action

    repo write rtl/alu.sv

    Names the tier and target.

    Verdict

    allow, needs-approval, deny

    Shows the checker outcome.

    Approver

    named reviewer or none

    Links each gate to a person.

    Common mistakes

    Common pitfall

    Logging only approvals hides the probing before them. Denied and gated attempts matter most, since they show what the agent kept trying.

    Interview

    Likely probes: budget math and log completeness.

    • Cost is input plus output parts from the stated EXAMPLE prices.

    • The 30-step EXAMPLE run costs 6.48 units, inside an 8-unit cap.

    • Logs are checker-written, append-only, and cover denials too.

    Check yourself The EXAMPLE run above costs 6.48 units against an 8-unit cap. How many more identical steps fit?

    Each step costs 0.216 units, and 8 minus 6.48 is 1.52. Seven steps cost 1.512 and fit; eight cost 1.728 and do not.

    Check yourself A log shows allows but no denials. What is the likely gap?

    Denied proposals are missing. The agent writes drafts while the checker writes verdicts, so a complete log shows every verdict.

    Related topics

    • Sandboxing and approval gates

    • Evaluating and operating agents

    Previous

    154 / 173

    Next: Secret Handling

    Up next

    Up nextSecret Handling

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Permission Tiers and Least Privilege
    • Prompt Injection from Files and Logs