· USE ·
Approval flow
Liege's approval flow is the difference between "AI that helps" and "AI that acts on your behalf." Every action type falls into one of two buckets.
Auto-approved (read-only or safe)
- INBOX-MANAGER — triages mail, doesn't reply
- FOLLOW-UP-SPECIALIST — finds stale threads, doesn't send
- MEETING-PREP — reads calendar + email, drafts briefings
- COMPETITIVE-ANALYST — scrapes, doesn't post
Approval required (anything that sends)
- SOCIAL-MANAGER — posting to FB/IG
- EMAIL-DRAFTER — creating Gmail drafts (not sending; still approval-gated)
- INVOICE-COLLECTOR — drafting invoice follow-ups
- GBP-MANAGER — Google Business Profile posts
- ADS-MANAGER — Meta/Google ad publishing
Approve via Telegram
When an agent drops an action in the approval queue, your @YorkisEstevez_bot DMs you with ✅ / ❌ / ✏️ buttons. Tap from phone. Done.
Approve via Command Deck
Queue panel shows all AWAITING actions with inline OK / X buttons. One click.
Approve via CLI
cd skills/meta-orchestrator/trials
node fire.js <client> approve <task_id>
Configuring what needs approval
Edit clients/<slug>/config.json:
{
"approval": {
"require_approval_types": ["fb_post", "ig_post", "invoice_chase", "gmail_draft"],
"auto_approve_types": ["inbox_triage", "follow_up_track", "meeting_prep"]
}
}
Move types between the arrays as you trust each agent more (or less).