01 · State
Work in progress
Know which connected agent is handling which task—and whether it is working, waiting, blocked, or complete.
A visibility control plane for AI agents
Make agent work visible.
See what your connected agents are working on, what informed their recommendations, where they need you, and what actually changed.
OrcaMule is the plan for a provider-neutral control plane that keeps an agent's work, authority, and observed result together throughout its working life.
This page describes the plan for OrcaMule. Email triage is the first delivery; the wider examples show where the same control pattern could go later.
Inbox triage
Illustrative agent · Receipt confirmation
Working on
Review a request to confirm that a workshop brief arrived.
Based on
The sender asks only for confirmation and says no other action is needed.
Recommends
Prepare a brief acknowledgement. Do not add a deadline, commitment, meeting, or task.
Needs you
Approve the transformed input, then review the exact draft separately.
May change
Create one approved mailbox draft. Sending remains disabled.
Observed resultWaiting for your decision
Between request and result
Your agent may be working. But can you see the work?
Most agent experiences show the request and the result. The important middle can disappear: evidence, uncertainty, authority, intended action, and what actually happened.
Without a control view
Request
Agent
ResultWith OrcaMule
Request
Evidence
Recommendation
Human decision
Intended action
Observed result
This is not a promise to reveal private model reasoning. It is a view of inspectable evidence, explanations, boundaries, decisions, and outcomes.
What becomes visible
See enough to understand, intervene, and verify.
02 · Basis
Evidence and explanation
See the sources and declared rules behind a recommendation, including uncertainty and unsupported assumptions.
03 · Attention
Where you are needed
See the exact decision in front of you, why it matters, and what remains unchanged until you decide.
04 · Outcome
What actually happened
Compare the approved intention with the external result. A mismatch or unknown outcome stays visible.
One control plane · different work
Different agents. The same clear questions.
The work changes. OrcaMule's visibility pattern stays familiar, so a person does not have to learn a new black box for every agent.
First delivery · Planned
Email triage
Why is a reply recommended—and what exactly will be created?
Working onReceipt-confirmation request
Based onOne explicit request; no other action
Needs youApprove transformed input and exact draft
ResultMatching mailbox draft—or visibly unknown
Only the exact approved draft may be created. Sending stays disabled.
Future idea · Hypothesis
Bookkeeping preparation
Why was this purchase categorized—and which fields will change?
Working onMatch a receipt to one transaction
Based onMerchant, amount, date, and receipt detail
Needs youConfirm business purpose and category
ResultApproved staging fields shown before and after
No tax filing, tax advice, money movement, or automatic posting of ambiguity.
Future idea · Hypothesis
Media organization
Why were these files grouped—and which labels remain uncertain?
Working onGroup photos and videos into one event
Based onCapture date and owner-confirmed location
Needs youConfirm event name and people-related tags
ResultChanged, skipped, and uncertain files remain clear
Sensitive metadata and people identification require explicit privacy choices.
First delivery · accountable email triage
See one agent at work, from evidence to result.
Email is the first detailed proof of the visibility pattern—not the whole product. This fictional case stays deliberately narrow and fully reviewable.
01
The source stays attached
Subject: Workshop brief received
Hi Morgan, please confirm you received the workshop brief. No other action is needed. — Riley
What becomes visible
The request is a receipt confirmation. “No other action is needed” rules out scheduling, task creation, and other follow-up.
Illustrative message · no real person or mailbox
02
You see what may leave your side
Hi [RECIPIENT], please confirm you received the workshop brief. No other action is needed. — [SENDER]
Needs you: review the exact transformed text and projected cost before authorizing one model call.
What becomes visible
Names were replaced, but the transformed text remains sensitive. The exact disclosure is separate from any later mailbox action.
03
The recommendation shows its basis
Disposition: Suggest a reply
The explicit request supports a short acknowledgement. The evidence does not support adding a commitment, deadline, meeting, or task.
Choices: Accept · Edit · Reject · Defer · Escalate
What becomes visible
The recommendation, evidence, uncertainty, and exclusions are reviewable together. Nothing has changed in the mailbox.
04
You approve the exact change separately
Subject: Re: Workshop brief received
Hi Riley, I confirm that I received the workshop brief. Thank you.
Morgan
May change: create this exact mailbox draft only.
What becomes visible
Recipient, subject, and body are fixed at approval. Editing them requires a new authorization. Sending, labels, moves, tasks, CRM, and calendar changes remain disabled.
05
The result is checked, not assumed
- AttemptedCreate one draft
- ObservedSubject and body match
- ResultVerified · not sent
What becomes visible
The approved intent and mailbox observation stay connected. A mismatch or ambiguous response remains unknown and enters review instead of becoming success.
The OrcaMule view
The agent changes. The questions stay familiar.
A consistent view turns visibility into a product experience—not a different collection of logs for every agent.
Truth boundary: visibility applies to connected work and consequential transitions that pass through OrcaMule's controls. Opaque activity may be inventoried at reduced assurance, not represented as governed.
- 01AgentWhich declared agent and version is involved?
- 02Working onWhat task is it handling, and what state has it reached?
- 03Based onWhat source evidence, policy, or rule supports the recommendation?
- 04RecommendsWhat does it propose, and what uncertainty or exclusion matters?
- 05Needs youIs human attention or exact authorization required?
- 06May changeWhat precise effect is permitted—and what stays out of bounds?
- 07ResultWhat did the external system actually show?
Future applications · hypotheses
The same clear view can travel to different work.
These examples show possible later uses of OrcaMule's control pattern. They do not add agents to the accepted product roadmap.
Future idea · Hypothesis
Bookkeeping preparation
EvidenceNorthline Office Supply receipt · CAD 84.27 · matching card transaction.
RecommendsUse “Office supplies” and attach the receipt to a tax-preparation staging record.
Needs youConfirm business purpose, category, and the exact fields to update.
ResultShow category before and after, linked receipt, approving person, and any exception.
Boundary: no tax filing, tax advice, money movement, or automatic posting of ambiguous transactions.
Future idea · Hypothesis
Media organization
EvidenceTwelve photos and two videos share a capture date and owner-confirmed location.
RecommendsGroup them as one event and suggest descriptive tags.
Needs youConfirm the event name and any people-related or sensitive tags.
ResultShow changed, skipped, and uncertain files with the approving person.
Boundary: people identification and sensitive metadata require explicit privacy choices and human confirmation.
A future agent would still need its own product decision, evidence, qualified bindings, authority boundary, and delivery gate.
More than one run
Keep the agent in view as it changes.
OrcaMule's durable destination is a provider-neutral lifecycle control plane. The important state and evidence should remain connected throughout an agent's working life.
- 01Set up
- 02Qualify
- 03Deploy
- 04Operate
- 05Change
- 06Pause
- 07Retire
Continuity: a change of model, framework, tool, cloud, or connector should not erase which agent was authorized or what happened before and after the change.
Truth: provider neutrality and lifecycle operation are planned product constraints. They have not yet been demonstrated.
Founder perspective
Visibility is where human command begins.
Models and tools will change. The need to see which agent was involved, what informed it, where authority came from, what changed, and how the result was verified will not.
Contact
Where would you want more visibility into an agent's work?
- Describe a workflow where the important middle currently disappears.
- Name the decision or effect that should always come back to a person.
- Explain what evidence you would need before trusting the result.