Grounded execution
Learn how Flopinio supports concrete review, draft, preparation, and staged-action workflows while keeping approvals, runtime visibility, and human control explicit.
- Before you start
- Active Flopinio workspace
- Execution-enabled access for assistant and runtime actions
- Who can use this
- Public
On this page
Explore workflow diagram
Workflow diagram
Grounded execution
Operating loop diagram. The text on this page has the exact steps and permissions.
Overview
Grounded execution is Flopinio's shipped execution-help layer for connected client work. It supports concrete review, draft, preparation, and staged-action workflows inside the same workspace that already holds requests, projects, notes, tasks, time, invoices, and payments.
Shipped workflows
- External Inbox review with source context, AI summary, urgency, owner, evidence links, and options to create a request or task.
- Request triage and review.
- Task, note, and project review.
- Async single and batch AI reviews with ready/failure workspace notifications.
- Assistant ask and draft flows.
- Invoice preparation and follow-through from tracked time to sent invoices, payments, reminders, and invoice history.
- Workspace-preset automation recommendations built on ordinary automation rules.
- Recurring workflow generation for template-backed service cycles.
- Staged MCP actions for compatible external AI clients.
Human-control boundary
Grounded execution helps produce summaries, drafts, suggested fields, generated records, agent runs, and approvals. People review triage suggestions, apply drafts, resolve required approvals, send invoices (or opt in to auto-send for a recurring invoice schedule), record payments, and choose whether to accept recommended automations. MCP writes require manual review by default. A token explicitly permitted to self-approve may approve its own eligible writes for the same user and organization; both paths preserve approval and execution history.
What this page does not claim
- No autonomy claim: Flopinio does not market hidden autonomous record mutation as the 1.0 product.
- No self-running magic claim: MCP access is still beta, token-scoped, and approval-aware even when workspace members issue their own tokens from Settings.
- No generalized AI planning claim: the shipped product supports specific execution workflows, not a universal autonomous planner.
- No expanded-portal claim: the authenticated project-only portal is shipped, while anonymous links, invoice evidence, generic messaging, and broader client editing remain future work. The macOS Desktop Recorder is built, but its verified download is not currently available. Also future: public browser extension rollout, Workrooms, assistant streaming/tracing, and advanced RBAC.
Next steps
Read MCP Connector, How To Use AI Request Triage Without Losing Control, and How Flopinio Prepares Invoice Drafts With Auditable AI.