Verification Pipeline

If the feature works, you get the proof.

Mulu does not stop at generated code. It opens the app, runs the flow, checks the result, records the session, and shows you evidence before you ship.

Try Mulu See the codebase map

Screenshot placeholder: verification run view showing a browser timeline, passing checkpoints, a clean console, and a recorded proof clip ready to review.

How it works

Build it. Verify it. Ship with proof.

The same pipeline covers build mode, debug mode, and everything in between.

Screenshot placeholder: recorded verification run with step-by-step browser actions, status chips, and a video artifact showing the feature passing end to end.

Recorded browser testing

After Mulu builds a feature, it opens the app and runs the actual flow. Click, type, submit, scroll — then records proof so you review evidence, not claims. If the flow is broken, the run shows exactly where.

Screenshot placeholder: codebase map panel showing the files, routes, and tests selected for the verification run before any browser actions start.

Context-backed runs

Verification is only useful if it knows what matters. Mulu maps the codebase first, ranks the relevant files, and guides the browser run from that knowledge — not blind replay.

Screenshot placeholder: debug timeline showing reproduction, code fix, rerun of the recorded browser flow, and a final fixed status with proof attached.

Debug mode proves the fix

When Mulu debugs a broken feature, the same pipeline reruns after the fix lands. Bug fixing no longer ends on "I think it's fixed." The same standard applies: rerun, inspect, record.

Screenshot placeholder: verification detail panel showing video, executed steps, screenshots, and console output attached to a completed feature task.

Artifacts, not a shrug

A passing run can include the browser recording, executed steps, screenshots, and console output. The evidence is attached to the work — not buried in a log you have to dig up separately.

Common questions

What does the verification pipeline actually do?

It builds the feature, opens the runnable app, executes the relevant flow, inspects the result, and records the session. The goal is evidence that the feature works, not just a successful code generation step.

Is this only for web apps?

No. The pipeline is designed for runnable product work, including browser flows and desktop app flows. The key idea is the same: exercise the real interface and capture proof of the result.

Does debug mode use the same tools as build mode?

Yes. After a fix lands, debug mode now reruns the same verification workflow instead of stopping at a guess. Manual confirmation is only needed when the tools cannot prove enough on their own.

Do I need a separate test harness?

No. The verification pipeline is part of the product workflow. You do not need to spin up a separate automation stack just to get recorded browser verification and proof artifacts.

What if the tool run can't prove the feature?

Mulu falls back to the strongest available proof. If a path cannot be fully automated, it can ask for manual confirmation — but only after tool-based verification has gone as far as it can.

Build it. Verify it. Then ship it.

Verification is a product feature in Mulu, not extra work you have to remember to do.

Try Mulu