Documentation menu
Customer evaluation worksheet
Use this record in your own repository for one authorized sandbox. No secrets, real customer records or confidential memory payloads belong in this worksheet. The questions below are a measurement plan, not claims of existing customers.
Before the run
| Field | Record |
|---|---|
| Team engineering owner and test date | Agreed with the participating team |
| Authorization and scope | One sandbox, one workflow, allowed synthetic namespace |
| Framework/store/adapter versions | Exact tested versions |
| Intended deletion scope | Copies, retrieval paths, principals and consistency window |
| Baseline workflow | Existing manual tests, their coverage and estimated time |
| Success criteria | Team-defined useful outcome and acceptable integration effort |
| Cleanup and incident owner | Who can stop pending work and remove only test records |
During the run
Record start/end time for configuration, adapter work, first valid report, reproduction and retest. Keep original JSON/HTML reports and sanitized config fingerprints. Record every unsupported capability and missing positive control. Count a finding only if the team reproduces the observed behavior and decides that it matters to its intended deletion or isolation contract.
Close the evaluation
- Did the same test FAIL before the fix and PASS after it? Link both reports.
- Was the finding already covered by an existing test? What did Memtru add?
- How many engineering minutes did setup, interpretation and remediation take?
- Did the team keep the test in CI and run it again after the evaluation?
- Would the team use the CLI, dashboard or assisted evaluation again? Why?
- Did the team accept an actual paid scope? Record an agreement only if it exists.
- Were synthetic records/jobs removed and temporary credentials revoked?
One participating team is a first data point, not proof of broad demand. Do not publish a name, logo, quote, report or case study without explicit permission. Page views, example downloads, internal tests and synthetic accounts are not customer adoption or revenue.
Smallest external evaluation
One engineer runs one existing deletion/lifecycle scenario inside their own sandbox, reproduces any finding, reruns after a fix and completes this worksheet. They can start with the first application guide or request help. Compatibility and any fee are agreed before work starts; there is no guarantee that the test will discover a defect.