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
One run of a kept Promise: Milita performs the whole business process herself, in a fresh cloud session, as the people the Promise requires, with fresh test data and no help, and records which required business results held. Nothing you say or do produces a Proof, and a debug is never one.
Certificate of ProofComing
The record of one Proof: the Promise, the verdict, every step as every person with its screenshot, and at its foot the run ID, each workflow run, when it ran and in which org. You download it as a PDF.
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 Proof or Debug and discarded afterwards, with its own browser and its own test data. Nothing carries over from one to the next. You can watch it from the conversation; Milita drives it, and nothing runs on your computer.
Inconclusive
A Proof 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.
Persona
A role a workflow runs as, such as Sales Rep or Finance. Per environment it resolves to a principal, a real non-admin Salesforce user. A Promise names which persona performs each part.
Capacity
How much proving your plan has left this period, shown in your account as a percentage remaining. Every Proof uses some. When it runs out, nothing breaks and nothing is deleted; Milita pauses new proofs until the next period.
Credit pack
A top-up for any paid plan: 500 credits for $50, 1,000 for $100 and 2,000 for $200, valid twelve months. Credits are the one number your account shows.
Environment
A connected Salesforce sandbox. Sandboxes only, non-admin users only, one org per environment.
Workflow
One reusable path, one sign-in, built in the Workflow Builder. A workflow has no persona of its own; each use of it inside a Promise sets the persona and inputs.
Debug and Activate
Debug runs what is on the canvas, saved or not, in the hosted browser you can watch. It is never Proof. Activate saves, verifies, and puts a workflow version live.
Regression
Every Promise started at once and followed as one record with one verdict. It starts only the roots and lets the chains bring the rest. Its page shows today's results above fourteen days of history.
Sandboxes only
Milita connects only to Salesforce sandboxes. Production orgs, Developer Edition orgs, scratch orgs and Trailhead Playgrounds are refused when you connect, with no exception.
Non-admin access only
Milita connects only with non-admin Salesforce users you control, one for each persona. A user with the System Administrator profile, or with Modify All Data, View All Data, Customize Application, Modify Metadata Through Metadata API Functions or Author Apex, is refused when you connect.
Evidence
What a Proof is made of: what Milita did, as whom, where, the exact records and values, which results held, when, whether cleanup completed, plus the video and step trace. 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.
And why.
| We say | Not | Why |
|---|---|---|
| Promise | test, test case, script, suite | You see business objects, not machinery. |
| Proof | test result, run result, green build | A Proof is evidence she verified it on her own. |
| Change | regression, failure, incident | A Change is a difference from the last good Proof. |
| Inconclusive | flaky, false positive | Honest outcomes. |
| Between the two proofs | root cause, caused by | No guessed causes. |
| Sandbox, non-admin user | dev org, scratch org, production, admin | Milita connects only to sandboxes, only with a non-admin user. |