QA evidence capture · built for the AI era

The QA platform for teams and agents.

Purpose-built for testing software and proving it works. Designed for the AI era.

Built for teams that get audited
FedRAMP · CMMC · 21 CFR Part 11 · IEC 62304
A signed microfilm
MICROFILM History › TKT-1417
TKT-1417 Build 2.3.1 Signed

Form 1090-EZ submission verification

Briefing Microfilm
Attestation
Mia Nakamura · QA Engineer
May 13, 2026 · 16:42 UTC
7a3f29c1b8e94f1a06d24fc8a3b58e91
TC-417 User can submit Form 1090-EZ with all required fields populated Pass
Validation errors triggered correctly on empty submit.
Walkthrough — confirmation receipt displayed.
TC-418 Form submission fails when fiscal year out of range Fail
"Picker showing 2024 as max — we're in 2026."

A signed record. Actor, content, and time, bound at the moment of capture.

Why Microfilm

Evidence you build once — and never reconstruct.

01

Capture as you work

Screen, voice, and screenshots recorded against the exact thing you're testing — not stitched together afterward.

02

Proof that holds up

Every verdict is signed and append-only. The record can’t be quietly edited later, and you can prove it — the day an auditor asks, you export instead of reconstruct.

03

Context that ships itself

Failures arrive in dev tickets and agent context already explained. Nobody opens a thread to ask what happened.

The workflow

From the work in front of you to audit-ready proof.

The QA workbench
MICROFILM Active recording · 04:12
Active · 5
  • TKT-1417 0m
    Form 1090-EZ submission verification
    3/8
  • TKT-1422 12m
    Auth token refresh on expiry
    Ready to attest · 6/6
  • TKT-1419 1h
    Export audit package as PDF
    In progress · 2/5
  • TKT-1408 1d
    Bulk import CSV validation
    Stale · 1/7
  • TKT-1390 3d
    Role-based field redaction
    Attested · 9/9
TKT-1417 Recording recording · 04:12

Form 1090-EZ submission verification

3 of 8 verified
Checks · 8
Test Case · TC-417
User can submit Form 1090-EZ with all required fields populated
Pass
Expected result
Submission succeeds and a confirmation receipt is displayed.
Evidence
00:42
Walkthrough — confirmation receipt shown
Shot — populated form fields
Shot Video Voice Quick note… Pass Fail Blocked
Acceptance Criterion
Empty submit surfaces inline validation on each required field.
Not run
Assertion · MCP-412
POST /forms/1090ez returns 422 when fiscal year is out of range.
Fail
3 of 8 checks verified · 5 remaining Attest & file to Records

The tester's workbench: the Active queue on the left, the open ticket on the right with its checks, expected results, bound evidence, and multi-modal capture (Shot / Video / Voice / note).

  1. 01
    Capture

    One tool, one tab.

    A lightweight app sits beside your browser. Your assigned tests, the acceptance criteria, the linked ticket, and prior notes all live next to the work — so you’re not touring Jira, then git, then Slack to figure out what you’re verifying. Narrate as you go; it records the screen, what you see, and what you say, together.

  2. 02
    Sign

    A verdict, not a screenshot in a thread.

    Mark each check pass, fail, or blocked, and sign it. The evidence behind every verdict is bound to it. When you’re done, attest the session and file it — one freeze step turns the work into a record.

  3. 03
    Hand off

    Failures land where the fix happens.

    A failed check posts a structured comment to the linked Jira or Linear ticket: what was tested, what you saw, and a deep link to the capture. Your coding agents — Claude Code, Cursor, whatever you run — read the same context through a native MCP server. The fix loop starts with the full story already in hand.

  4. 04
    Trace

    The matrix builds itself.

    Requirements → acceptance criteria → test cases → evidence → signatures, linked as the work happens. When something regresses, the history is one query away: when it last passed, who ran it, what they saw. When an audit comes, you export — you don’t reconstruct.

Trust

Built around evidence, from the database up.

See how we handle your data

Your captures are isolated to your tenant, hosted in US regions, and never used to train any model. You set retention. SSO/SAML, SCIM, role-based access, and signed access logs come standard.

Tenant-isolated US-hosted No model training You set retention SSO / SAML SCIM Role-based access Signed access logs

Start building your evidence trail.

Create a workspace for your team, or download the free capture app and record your first session.