01
Analysis
Read campaign evidence.
Execution Control
Know exactly what will change in Meta.
An Execution Plan names the account entity, reads its current value, shows the proposed value, and records every gate between approval and the final result.
Meta execution starts disabled. An administrator must enable the write path before an approved operator can run a plan.
01
Read the live value
02
Approve the exact diff
03
Record the outcome
Authority boundaries
Not every product object is allowed to do the same thing.
The workflow makes the transition from observation to proposal to account mutation visible.
02
Recommendation
Propose a candidate action.
03
Experiment
Define the learning plan.
04
Execution Plan
Describe and approve the Meta change.
Review the plan
Current value. Proposed value. Readiness state.
AdFlow reads the live Meta value immediately before execution. If the account changed after review, the plan is blocked as stale.
Demo planCampaign status
Paused to Active
01Current valueLive check passed
02Budget guardrailPassed
03ApprovalRequired
04ConfirmationPending
05ExecutionDisabled
- Global and scoped kill switches
- Protected entity checks
- Budget and performance guardrails
- Idempotent execution state
- Object-level results
- Retry and rollback plans
- Launch verification
Handle the outcome
A partial failure remains visible and recoverable.
Each object records its own outcome. Failed objects can enter a new retry plan; reversible successes can enter a separate rollback plan for review.
Partial result
Every object keeps its own outcome.
Retry plan
Only failed objects move into the next attempt.
Rollback plan
Reversible changes return as a new review item.
Deployment boundary
Understand where the product, data, and credentials live.
The public demo runs on Vercel with sample data only. The local product can connect to Meta and an optional AI provider when an operator configures it.
Hosted demo
Sample data with temporary demo state.
Meta Graph API
Not connected in the public demo.
OpenAI or Gemini
Not connected in the public demo.
The hosted demo contains no live Meta or AI credentials. It starts view-only, requires a password to unlock workspace editing, and keeps every live Meta write disabled.