MerivaneBook a demo

Evidence captured when it happened.Not reconstructed later.

Each executed step leaves a screenshot, a sha-256 hash, and a UTC time stamp. Entries go to an append-only, hash-chained audit trail. AI steps and human steps are attributed by name.

Book a demoWhere it sits in the chain
One chain, end to end
  1. Approved requirement
  2. Test scripts
  3. This pageAutonomous execution
  4. This pageYou take over
  5. Defects logged
  6. Signed OQ / PQ report
Capture

Each step leaves a screenshot, a hash, and a time.

Every executed step writes one evidence entry: a screenshot, a sha-256 hash, and a UTC time stamp.

  • Captured at execution timeNot reconstructed after the run.
  • Verified against system stateEach expected result is checked on screen, not assumed.
  • AttributedAI steps and human steps carry the name of who acted.
OQ-2214 · Evidence log6 of 96 steps shown
StepActionResultEvidence
1Log in as QA-02Pass9f3c…a71e14:31:02 UTC
2Open batch record BR-2219Pass4b0e…c2d914:31:19 UTC
3Enter sample result 4.2 mgPassd71a…08f414:31:44 UTC
4Approve record · Priya N.Passe2c8…5b1314:33:10 UTC
5Verify audit entryPass77ad…f90c14:33:41 UTC
6Print certificateFail · DEF-0311c5f…3e6a14:34:05 UTC
Hash chain

Change one byte and the chain breaks.

Each entry in the audit trail carries the hash of the entry before it. A verification pass checks the chain end to end.

  • Append-onlyEntries are never edited or removed.
  • Each entry links to the lastEvery entry includes the previous entry's hash.
  • Independently verifiableThe chain can be checked outside Merivane with standard tooling.
OQ-2214 · Hash chain6 of 96 entries shown
Step 1prev 0000…0000
hash 9f3c…a71e
Step 2prev 9f3c…a71e
hash 4b0e…c2d9
Step 3prev 4b0e…c2d9
hash d71a…08f4
Step 4prev d71a…08f4
hash e2c8…5b13
Step 5prev e2c8…5b13
hash 77ad…f90c
Step 6prev 77ad…f90c
hash 1c5f…3e6a
Verifying 96 entries …
Data integrity

ALCOA+ is a property of the capture, not a checklist.

Each attribute is met by how evidence is captured, not by a form filled in after the fact.

ALCOA+9 attributes
Auditor access

Give the auditor a read-only seat.

An auditor can review the trail without touching it. Access comes through your SSO.

  • Read-only, via SSOThe auditor role cannot edit a record.
  • Export packageEvidence, hashes, and the verification report, exportable.
  • Retention set by youThe retention period is yours to set.
Auditor seatRead-only
Auditor · read-only14 runs visible · no export of credentials
Evidence formats

Screenshot (PNG), audit trail entry (JSON), verification report (PDF), evidence package (ZIP).

Where evidence comes from, and where it goes

Before and after the audit trail.

BeforeAutonomous executionThe run that produces the evidence, step by step.AfterDefect managementA failed step becomes a locked defect, with the evidence attached.AfterE-signatures and complianceEvidence and signatures are bound to identity, meaning, and time.

Questions about evidence and the audit trail.

If your question is not here, ask us. We reply within one working day.

Can evidence be edited?

No. The trail is append-only. A correction is a new entry that points at the old one.

Where is it stored?

In a single-tenant environment, in the region you choose.

Can an auditor verify without Merivane?

This is under review.

How long is it kept?

This is under review.

Now onboarding validation pilot partners

See a full run on one of your systems.

Bring one approved requirement. We show you the chain end to end, on a system you already use, in under an hour.

Book a demo
Reply timeOne working day
FormatLive run, 45 minutes