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
    • Hallucination and Failure Modes
      • Invented APIs, Flags and Signal Names
      • Plausible but Wrong Numbers
      • Overconfident Tone and Sycophancy
      • Instruction Drift in Long Sessions
      • Subtle Bugs That Compile
    • Verifying AI Output
    • Evaluating AI Tools for Your Team
  • 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
  • Interview and Judgment10
  • AI Skills: Full Course Index
  • Working with AI Glossary
  • Working with AI Cheatsheet
Loading lesson

‹Hallucination and Failure Modes
  1. Topics
  2. AI Skills for VLSI Engineers
  3. Trust and Verification
  4. Hallucination and Failure Modes
  5. Invented APIs, Flags and Signal Names

Verification and Safe Use · Beginner to Intermediate

Invented APIs, Flags and Signal Names

Invented tool flags, API calls and signal names, with checks against the real reference.

On this page

    Fluent but invented names

    A model predicts likely text, so it can emit names that never existed. The invented name sits beside genuine ones and matches their style.

    Common targets are tool flags, library calls, standard section numbers and signal names in a described block. Each looks ordinary, which is why reading alone cannot catch them.

    Invented name

    Why it passes a quick read

    What the reference shows

    --auto-fix beside --lint and --strict

    Same prefix style as the genuine flags

    No such flag is listed.

    uart_tx_done beside uart_tx_busy

    Follows the block naming pattern

    The block exposes uart_tx_busy only.

    fifo_full_sync in an async FIFO

    Combines two real words

    No such port exists on the module.

    An engineering example

    An assistant suggests four flags for a lint run. Three are genuine and one is invented, and the audit program below sorts them against a known-good list.

    example.py
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    import sys
    
    KNOWN_FLAGS = ["--lint", "--strict", "--output"]
    SUGGESTED = ["--lint", "--auto-fix", "--strict", "--output"]
    
    def main():
        unknown = [f for f in SUGGESTED if f not in KNOWN_FLAGS]
        if len(SUGGESTED) != 4:
            print("FAIL: wanted 4 suggestions, saw " + str(len(SUGGESTED)))
            sys.exit(1)
        if unknown != ["--auto-fix"]:
            print("FAIL: unknown set is " + ",".join(unknown))
            sys.exit(1)
        print("PASS: 4 suggested flags checked, 1 unknown name located")
    
    main()

    The program stands in for the checking habit with a fake suggestion list. Four suggested names go in, and one unknown name is located.

    How to detect it

    Look up every name in the real reference before use. The schematic transcript below shows the shape of the failure and its verdict.

    plaintext
    1
    2
    3
    4
    schematic transcript - fake reply written for this lesson, not from any real system
    assistant: run the pass with --lint --auto-fix --strict --output
    check: --lint, --strict and --output are listed; --auto-fix is absent
    result: 1 of 4 suggested names is invented, so the command is held back
    • Check each name, not just the ones that look odd: invented names are built to look ordinary.

    • Paste the exact name into the reference search: near matches do not count.

    • Confirm versions and variants too: a genuine flag on one tool may be absent on another.

    Common mistakes

    Common pitfall

    Trusting a name because it appears twice in one reply. Repetition is a style habit, so both copies can be invented together.

    Interview

    Likely probes: the audit habit and the verdict rule.

    • Every name goes through the reference, genuine-looking or not.

    • An unlisted name is set aside, never run on guesswork.

    • Signal names are checked against the module port list, not the description prose.

    Check yourself A suggested command mixes three known flags with one unknown name. Which part is trusted?

    The three known flags, after the reference confirms each. The unknown name is set aside until a reference shows it.

    Check yourself Why check every name instead of only the ones that look odd?

    Invented names are built to look ordinary. Spot checks miss them, so each name goes through the reference.

    Related topics

    • Verifying AI output

    • Prompt debugging

    Previous

    34 / 173

    Next: Plausible but Wrong Numbers

    Up next

    Up nextPlausible but Wrong Numbers

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Overconfident Tone and Sycophancy
    • Instruction Drift in Long Sessions
    • Subtle Bugs That Compile