Total Runs
Status: HealthyMock automation runs this week
Read-only command center for growth, content, AI, automation, and operations visibility.
Workflow runs, dry-runs, blocked actions, approvals, and external-write safety. This page is for review, not live control.
Automation is visible in read-only and dry-run mode. Blocked actions, approval gates, and audit status are surfaced before any future live readiness decision.
Automation warnings stay visible before run data so blocked actions and approval gates are not hidden.
Top-level automation health. External write executions must remain zero in MVP.
Mock automation runs this week
Dry-run coverage before future live mode
Blocked by safety or approval gates
Needs investigation before live readiness
Review-only approvals, no automatic execution
Attempts must be blocked in MVP
Must remain zero in MVP
3 of 3 mock runs have audit logs
External write safety is the release gate for any future live automation.
External writes are disabled in MVP. Automation can only run in read-only or dry-run mode while approval, audit, and safety gates mature.
Approvals are review-only in MVP. Pending approval never triggers automation execution.
| Requested action | Workflow | Risk | Approval | Requested by | Expires | Reason |
|---|---|---|---|---|---|---|
| Review blocked external write request | Meta Ads Recommendation Dry Run | Risk: High | Approval: Pending | Automation system, review-only | Review before any future live mode | External write attempt was blocked by MVP safety gate. Automation cannot self-approve or execute itself. |
Automation runs show dry-run, blocked, approval, external write, and audit status. No row-level execution controls are provided.
| Workflow | Run mode | Status | Trigger | Risk | Approval | External write | Audit log | Started | Duration |
|---|---|---|---|---|---|---|---|---|---|
| Meta Ads Recommendation Dry Run | Mode: Dry-run | Run: Blocked | ai recommendation | Risk: High | Approval: Pending | Write: Attempted and blocked | Audit: Present | 2026-06-25T08:30:00+07:00 | 1m |
| Content Refresh Suggestion | Mode: Read-only | Run: Success | scheduled mock | Risk: Low | Approval: Not required | Write: None | Audit: Present | 2026-06-25T08:40:00+07:00 | 1m |
| WooCommerce Product Signal Read | Mode: Read-only | Run: Success | read sync | Risk: Low | Approval: Not required | Write: None | Audit: Present | 2026-06-25T08:45:00+07:00 | 1m |
Workflow health is downgraded when runs are blocked, failed, or missing audit coverage.
| Workflow | Category | Health | Run mode | Last run | Next review |
|---|---|---|---|---|---|
| Meta Ads Recommendation Dry Run | growth | Status: Needs review | Mode: Dry-run | 2026-06-25T08:30:00+07:00 | Review restricted action guardrail |
| Content Refresh Suggestion | content | Status: Healthy | Mode: Read-only | 2026-06-25T08:40:00+07:00 | Continue read-only monitoring |
| WooCommerce Product Signal Read | growth | Status: Healthy | Mode: Read-only | 2026-06-25T08:45:00+07:00 | Continue read-only monitoring |
Audit logs make automation traceable from trigger to outcome before live mode is considered.
| Audit signal | Count | Status | Trust | Note |
|---|---|---|---|---|
| Runs with audit log | 3 | Status: Healthy | Trust: Trusted | Runs can be traced from trigger to outcome. |
| Partial audit logs | 0 | Status: Healthy | Trust: Trusted | Partial logs should be reviewed before live readiness. |
| Missing audit logs | 0 | Status: Healthy | Trust: Trusted | Missing audit logs block safe automation review. |
| High-risk runs missing audit log | 0 | Status: Healthy | Trust: Trusted | High-risk workflows must have complete audit coverage. |
Risks that block live automation readiness or require Founder/CTO review.
A workflow may be trying to cross the MVP safety boundary before approval and audit gates are ready.
Evidence: 1 run(s) attempted an external write and were blocked.
Mitigation: Review workflow guardrails and keep it in dry-run until the requested action is safe.
Owner: CTO / Automation ReviewerAny external write execution in MVP would create operational and business risk.
Evidence: 0 executed write(s), 0 unexpected execution(s).
Mitigation: Treat non-zero execution as a release blocker and open an incident review.
Owner: Founder / CTOAutomation readiness can be misread if pending approvals are treated as permission to continue.
Evidence: 2 approval item(s) are pending.
Mitigation: Review approvals manually and keep execution disabled in MVP.
Owner: Founder / Automation ReviewerAutomation cannot be safely debugged or promoted without traceable audit records.
Evidence: 0 run(s) lack complete audit status.
Mitigation: Require audit records before considering any workflow for controlled live mode.
Owner: CTOFailed or blocked workflows may hide broken assumptions in AI or integration logic.
Evidence: 1 failed run(s), 2 blocked action(s).
Mitigation: Review failed and blocked dry-runs before expanding automation scope.
Owner: Automation ReviewerSafe next steps for Founder, CTO, or Automation Reviewer. These are review actions only.
Meta Ads Recommendation Dry Run attempted a restricted write and was blocked.
Every automation run must be traceable before live readiness can be considered.
Meta Ads Recommendation Dry Run needs human approval review and must not self-approve.
Keep failure review path ready for the next failed dry-run.
Live mode should wait for approval gates, audit coverage, safety monitoring, and rollback planning.