VeriLLM
Full walkthroughPart 7Lesson 48

Show Tampered Transcript Rejected

Tampering, Detection Probability, and Verifier Cost

+5 XPLesson 48 of 57
LEARNING OBJECTIVE

Build Show Tampered Transcript Rejected as one small, testable piece of Tampering, Detection Probability, and Verifier Cost.

By the end, you will know what this function owns, why the larger system needs it, how its mathematics works, and how to prove your code is correct.

01 · CONCEPT

Understand the idea first

Show Tampered Transcript Rejected has one clear responsibility. Think of it as a small tool on a workbench: it should accept a well-defined input, perform exactly one job, and return an output the next step can trust. Keeping this boundary small is what lets a large VeriLLM system remain understandable.

Why this step exists

This step exists because tamper with transcripts, derive the detection probability under k audits and a corruption fraction, and quantify verifier cost as a fraction of full re-execution. Later lessons assume this behavior already works, so correctness here removes uncertainty from everything downstream.

02 · INTUITION

Build a mental picture

Imagine data moving through a row of small, labelled boxes. This lesson builds exactly one box. The label tells us what may enter, the implementation tells us what happens inside, and the return value tells the next box what it may safely expect.

Inputshow tampered transcript rejectedCheckIntegrate
One dependable stepSmall verified contracts compose into the complete project.
INPUTDocumented values, shapes and types
SHOW_TAMPERED_TRANSCRIPT_REJECTEDOne focused transformation
OUTPUTA predictable, testable result
03 · MATHEMATICS

Derive it carefully

The symbols below express the core relationship used in this part of the project. MathJax renders the equation so fractions, matrices, superscripts, and alignment remain readable.

  1. 1

    Name every input and write down its shape, dtype, and legal range.

  2. 2

    Express the transformation independently of the surrounding project.

  3. 3

    Check the smallest normal case, an edge case, and an invalid case.

  4. 4

    Only after those checks pass, connect the function to the next lesson.

Do not memorize the symbols. Ask what each symbol represents in code, what shape it has, and which axis is reduced.

04 · IMPLEMENTATION

Turn the idea into code

Start with the contract, implement the smallest correct behavior, and use tests before optimizing. Reveal the reference only after making a real attempt.

def show_tampered_transcript_rejected(*args, **kwargs):
    """Implement Show Tampered Transcript Rejected."""
    # TODO: follow the contracts and checks on this page.
    raise NotImplementedError
05 · VERIFY

Prove it works

Normal case

Use the smallest representative input and compare exact values.

Edge case

Try empty, full, boundary, masked, or single-item input.

Purity check

Confirm whether inputs should stay unchanged and repeated calls are independent.

Common mistakes

  • Changing the input in place when later code expects it to remain unchanged.
  • Returning the right values with the wrong shape or dtype.
  • Testing only the happy path and missing empty, full, masked, or boundary inputs.
KNOWLEDGE CHECK

What should you verify first for Show Tampered Transcript Rejected?

READY TO CONTINUE?Mark this lesson complete