How Mercidia safeguards Pilot
Approval-controlled automation for teams that want the speed of rules without hiding the evidence or the rollback path.
Automation is earned, not assumed
Pilot stays unavailable until the workspace has source-verified outcome calibration. A connected credential or a recommendation alone is not proof that an automated rule is ready to act.
- Calibration uses recorded expected and realized outcomes with a minimum sample threshold.
- Provider availability and source health remain visible before an action can run.
- Unsupported channels fail closed instead of being reported as applied.
Every action has a boundary
Approved rules run inside explicit budget limits, daily caps, approval mode, and rollback criteria. High-impact state changes require the appropriate re-authentication and role permissions.
- Pilot records approval state, cap decisions, provider results, and audit events.
- A local campaign state is not updated until the live provider mutation succeeds.
- Reject, approve, and rollback paths preserve provider truth and sanitized audit history.
Review what happened
Pilot is part of the decision record, not a black-box executor. Operators can inspect the evidence, rule, limits, provider response, rollback state, and eventual outcome before trusting a future action.
See the evidence loop
Start with the fictional sample workspace, then connect your own sources when you are ready. Mercidia keeps observed values, assumptions, uncertainty, and decisions visible together.