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
    • Evaluating and Operating Agents
      • Task Success Rate on a Held-Out Set
      • Cost and Latency per Task
      • Regression Suites for Agent Changes
      • Drift, Incident Review, and Shutoff Rules
  • Interview and Judgment10
  • AI Skills: Full Course Index
  • Working with AI Glossary
  • Working with AI Cheatsheet
Loading lesson

‹Evaluating and Operating Agents
  1. Topics
  2. AI Skills for VLSI Engineers
  3. Agentic Workflows for Chip Teams
  4. Evaluating and Operating Agents
  5. Task Success Rate on a Held-Out Set

Reference: Agentic Workflows for Chip Teams · Beginner to Intermediate

Task Success Rate on a Held-Out Set

Task success rate on a held-out set, with uncertainty and multi-step chain arithmetic.

On this page

    What counts as resolved

    Resolved means an independent check passes, not that the agent says it finished. A triage task is resolved when the failing test is identified and a rerun confirms the diagnosis.

    Each task needs its pass condition written before the agent runs. Post-hoc grading moves the goalposts and inflates the rate.

    Outcome

    Counts as

    Example

    Resolved

    Independent check passes.

    Named culprit test confirmed by rerun.

    Attempted

    Agent ran, check did not pass.

    Wrong culprit, or no answer in budget.

    Invalid

    Excluded from the rate, counted separately.

    Task setup was broken on arrival.

    A held-out set

    A held-out set is a fixed task list never used for prompt or tool tuning. Tuning against it teaches the agent the test, not the job.

    Record the prompt version, tool versions, and permission set with every run. Refresh the set when tasks leak into tuning material.

    • Fixed tasks with written pass conditions, frozen for a review period.

    • No tuning on it: prompts, examples, and tool retries are tuned elsewhere.

    • Versioned alongside the agent, so old and new scores stay comparable.

    Reading a rate

    A rate without uncertainty is a single anecdote. The calc block below works an EXAMPLE set of 50 tasks with 40 resolved.

    plaintext
    1
    2
    3
    4
    5
    6
    7
    held-out set: n = 50 tasks, resolved r = 40
    task success rate = r / n = 40 / 50 = 0.80
    standard uncertainty = sqrt(p (1 - p) / n) = sqrt(0.80 x 0.20 / 50)
      = sqrt(0.0032) = about 0.057
    about-95 interval = 0.80 +/- 1.96 x 0.057 = 0.80 +/- 0.11 = 0.69 to 0.91
    chain check: per-step 0.95 over 10 steps
      = 0.95^10 = 59873693923837890625 / 10^20 = 0.59873693923837890625 = about 0.60

    The program below recomputes the lesson numbers from EXAMPLE data. It uses plain lists, with no model involved.

    example.py
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    import sys
    
    outcomes = [True] * 40 + [False] * 10
    chain_num = 95 ** 10
    n = len(outcomes)
    resolved = sum(1 for o in outcomes if o)
    rate = resolved / n
    
    if n != 50:
        print("FAIL: expected 50 held-out tasks")
        sys.exit(1)
    if resolved != 40:
        print("FAIL: expected 40 resolved tasks")
        sys.exit(1)
    if abs(rate - 0.80) > 1e-12:
        print("FAIL: rate arithmetic off")
        sys.exit(1)
    if chain_num != 59873693923837890625:
        print("FAIL: chain arithmetic off")
        sys.exit(1)
    print("PASS: 40 of 50 held-out tasks resolved for rate 0.80 with 10-step chain 0.59873693923837890625")

    Common mistakes

    Common pitfall

    Tuning prompts against the held-out set, then reporting the same set as proof, is self-grading. Keep a tuning set and a held-out set, and report the held-out number.

    Interview

    Likely probes: what counts as resolved, and why rates need uncertainty.

    • Resolved means an independent check passes, never the agent self-report.

    • 40 of 50 is 0.80 with an about-95 interval near 0.69 to 0.91.

    • A 0.95 per-step rate over 10 steps is about 0.60 end to end.

    Check yourself A run reports 40 resolved of 50 held-out tasks. What is the rate, and what interval should accompany it?

    Rate 0.80, with an about-95 interval near 0.69 to 0.91 for this n.

    Check yourself Each of 10 steps succeeds with probability 0.95. What is the exact end-to-end rate?

    0.95^10, which is 0.59873693923837890625, about 0.60.

    Related topics

    • Cost and latency

    • Evaluating AI tools

    Previous

    157 / 173

    Next: Cost and Latency per Task

    Up next

    Up nextCost and Latency per Task

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Regression Suites for Agent Changes
    • Drift, Incident Review, and Shutoff Rules