Requirements traceability

The evidence layer for teams and agents.

Move fast. Stay on course.

Microfilm holds teams and agents to their requirements—every test maps to a requirement, every result shows its work.

Start sealing evidence — free See how it works
A signed evidence record
MICROFILM Portal › Reel TKT-1417
TKT-1417 Build 2.3.1 Signed

Form 1090-EZ submission verification

Work item Evidence
Signature · KMS ES256
claude-code · agent
May 13, 2026 · 16:42 UTC · chained to reel
7a3f29c1b8e94f1a06d24fc8a3b58e91
TC-417 User can submit Form 1090-EZ with all required fields populated Pass
Assertion: validation errors raised on empty submit.
Response 200 — confirmation receipt rendered.
TC-418 Form submission fails when fiscal year out of range Fail
Returned 200; expected 422 for out-of-range fiscal year.

One signed record. Actor, content, and time, bound and chained the moment the agent writes it.

How you connect

One line in your agent. No app to install.

Microfilm runs as a remote MCP server. Connecting takes a single command — here's the setup for each client. 

$claude mcp add --transport http microfilm https://mcp.microfilm.dev/mcp
  1. 01

    Connect

    Add Microfilm to your agent.

  2. 02

    Authorize

    Log in once. Your agent is paired.

  3. 03

    Capture

    Your agent records signed evidence as it tests. Everything lands in your portal.

What your agent produces
MICROFILM mcp · record_event signed
agent › microfilm.record_event
{
procedure: "checkout-flow",
work_item: "TC-417",
result: "pass"
}
← signed · reel #1417 · ES256
  chained to a3f9…58e91 · verifiable offline

Each test your agent runs becomes one signed record like this — captured at the moment of work, not reconstructed from a log.

Why Microfilm

The more your agents test, the more you need proof they did.

01

Agents do the testing now

AI coding agents write most of the test code and run most of the tests. They’re good at running tests and bad at holding themselves to a spec. Throughput stopped being the hard part.

02

The bottleneck is proof

A green checkmark in a terminal isn’t evidence. What’s missing is a structured, verifiable record of what actually ran — and agents don’t produce that on their own.

03

Microfilm is the evidence layer

It’s the structured enforcement and evidence layer agents write to. Signed, chained, verifiable offline — so testing produces a record, not just output.

How it works

Capture → Sign → Hand off → Trace.

Agent → MCP server
MICROFILM mcp · record_event connected
agent › microfilm.record_event
{
procedure: "checkout-flow",
work_item: "TC-417",
result: "pass"
}
← signed · reel #1417 · ES256
  chained to a3f9…58e91 · verifiable offline

The agent writes a test event to the MCP server; Microfilm signs it, chains it into the reel, and returns a record anyone can verify — no desktop app, no extension, no screen recorder.

  1. 01
    Capture

    The agent writes evidence as it tests.

    Your AI coding agent records each test event — the procedure it ran, the work item, the result — to the Microfilm MCP server as it works. The agent is the user. There’s no app to open and nothing to record by hand.

  2. 02
    Sign

    Every event is signed and chained.

    Each event gets a real, KMS-backed signature (ES256) and chains into a tamper-evident reel. Any record verifies offline — anyone can confirm what happened without trusting Microfilm.

  3. 03
    Hand off

    Evidence lands in the portal.

    Signed records flow into the web portal — searchable, scrollable, filterable, and ready to share as a record anyone can verify.

  4. 04
    Trace

    Traceability is just another view.

    Requirements traceability and sharing are lenses on the same signed evidence, not a separate product. Follow any requirement to the records that prove it was tested.

Trust

Built around evidence, from the signature up.

See how we handle your data

Every event is signed with a KMS-backed key and chained into a tamper-evident reel, so any record verifies offline. Your evidence is isolated to your tenant, hosted in US regions, and never used to train any model. You set retention.

KMS-backed ES256 Chained reels Verifiable offline Tenant-isolated US-hosted No model training You set retention Signed access logs

Write your first signed record.

Point your coding agent at the Microfilm MCP server. Your team searches, traces, and shares everything it captures in the portal.

Start sealing evidence — free See how it works