Glossary
The words Milita uses
Milita talks about Promises, Proofs and Changes rather than tests, suites and scripts. That isn’t branding — the words describe different things. Here is what each one means.
- Promise
- A business rule in your own words, the people it covers, where it applies, and the results that prove it worked. For example: “Discounts above 20% need Finance approval before a quote can be sent.” A Promise is what you ask Milita to protect.
- Proof
- Evidence that Milita completed a whole business process herself, in a fresh cloud session, as the people the Promise requires, with fresh test data and no help — and that every required business result held. Watching you work never produces a Proof.
- Change
- A difference from the last good Proof: what is different now, when it last worked, when it first failed, and what was recorded between those two proofs. A Change never asserts a cause.
- Kept Promise
- A Promise Milita has proved on her own at least once and is actively checking. Until that first clean Proof, it is a draft.
- Business result
- The outcome that proves a process worked — a record reaching a state, an action being refused, a value matching, a case landing in the right queue. Not a click, and not a finished script.
- Fresh cloud session
- An isolated environment created for a single run and discarded afterwards, with its own browser and its own test data. Nothing carries over between runs.
- The Bridge
- A small helper on the computer you teach from. It lets Milita watch one Salesforce browser window that you control, while you do the work. It cannot issue a verdict — only a clean cloud run produces Proof.
- Inconclusive
- A run where Milita could not establish the result — for example infrastructure trouble, or a control she was not sure of. Reported as inconclusive, never as a business failure.
- Release gate
- A request from your release pipeline asking Milita to prove the relevant Promises before a release proceeds, and to report the verdict back.
- Non-production only
- Milita connects only to Salesforce sandboxes and scratch orgs, never production.
- Evidence
- What a Proof is made of: what Milita did, as whom, where, the exact records and values, which results held, when, and whether cleanup completed. Served only through your own sign-in and deleted on a schedule.
- Anchor
- A control you have named for Milita when its own clues disagreed. If that screen later changes too much, the anchor expires and she asks again rather than guessing.
Put one Promise to the test.
Free forever for a single process, in a sandbox you control.