Is Mycel good for human AI coordination? Yes, when what you mean by coordination is building a shared knowledge base your team and an AI assistant both work from, giving people explicit control over what the AI can change, showing exactly which documents the assistant read for every answer, and requiring approval before the assistant writes anything into connected apps. Mycel is not good for human AI coordination if you need video meetings with transcription, real-time screen co-piloting, or an agent that takes actions on its own.
The product is the memory a small business runs on: a shared vault of plain-markdown folders your team works in, with an AI assistant that answers questions from those folders. Each answer surfaces which vault documents it read, and a reply that read nothing from the vault is marked that way. The assistant never runs tasks for you; anything it would change inside a connected Martello app waits in Approvals first. Team chat lives inside the business workspace, and typing @assistant in any channel or direct message pulls an answer from the vault into the thread, with approval required before any suggested task or note gets filed.
Key Takeaways
- Mycel's assistant answers questions from the business vault and shows which documents it read for every answer, so the team sees where information came from and can verify it.
- Anything the assistant would file into a connected app or the vault waits for a person to approve it first, keeping humans in control of what actually gets written or changed.
- Business workspaces include team chat with channels and direct messages, and typing @assistant in a message gets an answer in the thread from the vault.
- The vault exports as markdown at any time with full metadata, giving the business ownership and portability of its knowledge.
- Mycel does not run automations or tasks on its own, does not record meetings, and does not build agents or workflows.
What Human AI Coordination Actually Means in Practice
Human AI coordination describes any system where people and AI tools share work on the same outcome, with handoffs, approvals, or shared context between them. The term covers a wide range of setups, from an AI drafting an email a person reviews before sending, to a scheduling assistant that books meetings only after a human confirms the slot, to a warehouse robot that stops and alerts a supervisor when it encounters an unexpected obstacle.
The common thread is control and transparency. Coordination requires that people understand what the AI did, why it did it, and have a clear point where they decide whether the AI's work moves forward. Systems that lack those qualities are automation, not coordination.
For a small business, the practical question is narrower: can your team and an AI assistant work from the same knowledge, does the assistant show its work, and do people retain final say over what gets written, sent, or filed? That is the version of human AI coordination Mycel is built for.
How Mycel Structures Coordination Between People and AI
Mycel puts coordination into three mechanisms: the vault as shared context, citations that show what the assistant read, and approvals that gate any change the assistant suggests.
The Vault as Shared Context
The vault is a collection of plain-markdown folders the whole team can read and edit. Every business decision, process note, customer insight, and brand guideline lives there. When someone asks the assistant a question in Ask or types @assistant in team chat, the assistant reads from those folders to answer.
The vault is not hidden from the team or locked inside the AI. Anyone with access to the folder can open the document, see its history, edit it, or restore an earlier version. The assistant and the team are working from the same material.
Connected Martello apps can file what the business learns into the vault. Relay and TradesBackbone handle customer records and keep them in their own systems, but they can write summaries, insights, or decisions into vault folders the owner shares with them. ReputeLift's AI reads the business vault to draft review responses. SynthPrism's assistant reads the vault for brand voice and business facts when generating marketing copy.
Each of those apps reads only the folders the owner shares with it. A folder can be kept to everyone in the business, to team members but not viewers, or to owners and admins only. That means the owner controls what context each AI can see.
Citations That Show the Assistant's Work
Every answer from Mycel's assistant displays which vault documents it read to produce the reply. If the assistant answered a question without reading anything from the vault, that reply is marked that way.
This is not a guarantee of correctness, and Mycel does not claim the assistant cannot be wrong. But it does mean the person reading the answer can check the source documents, see whether the assistant interpreted them accurately, and decide whether the answer is useful. That transparency is what makes the interaction coordination rather than blind delegation.
When someone types @assistant in a team chat message, the assistant replies in the thread and the same citation behavior applies. The team sees which folders informed the answer, and anyone in the channel can verify it.
Approvals That Gate Changes
Anything the assistant would write into the vault or a connected Martello app waits in the Approvals section until a person reviews and confirms it.
The assistant may offer to file a decision note after answering a question in team chat, or suggest adding a task. Neither happens until someone in the business approves it. The same applies to anything the assistant would change inside TradesBackbone, Relay, ReputeLift, or SynthPrism. The change sits in Approvals, shows what it would do, and does nothing until a person with the right role confirms it.
Approvals is the explicit coordination layer. The AI suggests, the person decides, and the system enforces that boundary.
When Mycel's Coordination Model Fits the Work
The Mycel approach to human AI coordination works when the bottleneck is scattered knowledge, unclear answers to recurring questions, and the risk that an AI assistant will write something inaccurate into a business system without anyone noticing.
Consider a hypothetical painting contractor with six field teams. Crew leads ask questions in the team chat throughout the day: what primer spec for exterior cedar in coastal climates, what the standard change-order language says about material cost adjustments, whether a specific insurance certificate meets the commercial contract requirement. The operations manager has answered each of these before, often multiple times, and the answers are somewhere in old message threads or email.
With Mycel, those answers live in vault folders labeled by topic: product specs, contract templates, compliance requirements. When a crew lead types @assistant followed by the question in the #field channel, the assistant reads the relevant folders and replies in the thread, showing which documents it pulled from. The crew lead sees the answer and the source in the same place, and can ask a follow-up or flag a gap. If the assistant offers to file the answer as a permanent note in the vault, that suggestion waits in Approvals until the operations manager confirms it.
The coordination here is between the crew leads who need the answer, the assistant that retrieves it, the operations manager who verifies it, and the vault that holds the canonical version everyone works from.
Mycel is less useful when coordination means something else: real-time joint editing with AI suggestions inline, voice-to-voice conversation with an assistant during a field visit, or an AI that monitors a dashboard and takes action when a threshold is crossed. Those are valid coordination models, but they require capabilities Mycel does not offer.
The Role of Team Chat in AI Coordination
Team chat in Mycel's business workspaces includes channels and direct messages between people in the business. Every business workspace has a #general channel, and the owner can create additional channels for topics, projects, or teams.
Typing @assistant in any message gets an answer from the business vault in the thread. The assistant may offer to file a decision note or add a task, which does nothing until a person approves it. That approval happens in the Approvals section, not inline in the chat.
This structure keeps the assistant available in the conversation without interrupting it. The team discusses a decision in a channel, someone asks the assistant for the documented policy, the assistant replies with the answer and its sources, and the conversation continues. If the discussion surfaces a new decision, the assistant can offer to file it, and the owner or admin approves it later.
Team chat is not a separate tool the business has to adopt alongside Mycel. It is part of the workspace, so the vault, the assistant, and the team conversation share the same context. That integration is what makes @assistant in chat a coordination mechanism rather than a search feature bolted onto messaging.
What Today Does for Cross-App Coordination
Home opens on Today, a list of what is waiting on a person across the connected Martello apps. Each item shows which app it came from, why it surfaced, how long it has waited, and a link straight to it.
Today aggregates the coordination surface. Instead of checking TradesBackbone for unsigned proposals, Relay for customer inquiries, ReputeLift for review drafts, and the vault for approvals waiting in Mycel, the owner opens Today and sees all of it in one list.
This is coordination between the person and multiple systems. Each system still owns its own data—customer records stay in Relay and TradesBackbone, not in Mycel—but Today pulls the pending items into a single view so the owner knows where attention is needed.
The link from each item goes directly to the source. If a proposal is waiting for signature in TradesBackbone, the link opens that proposal in TradesBackbone. If a review response draft is waiting for approval in ReputeLift, the link opens it there. Mycel does not copy the work into its own interface; it surfaces it and sends the person to the tool that owns it.
Vault Ownership and Portability
The whole vault exports as markdown at any time. Each exported file carries its created and updated dates and metadata in a frontmatter header. The export is the current version of each document, not its version history.
This export is part of coordination, not a backup feature. If the business decides Mycel is not the right tool, the knowledge the team built in the vault leaves with them as portable markdown files. If the business wants to analyze vault contents with a different tool, the export provides the raw material. If regulatory or contractual requirements demand an archive, the export delivers it.
AI coordination systems that lock knowledge inside a proprietary format or API create dependency. Mycel's plain-markdown vault and one-click export put the business in control of its own memory.
Coordination Across Roles and Folder Permissions
A business workspace in Mycel has four roles: Owner, Admin, Member, and Viewer. A folder can be kept to everyone, to team members but not viewers, or to owners and admins only.
These permissions shape what the AI can read and what each person can see. If the owner keeps the pricing strategy folder to owners and admins only, members and viewers cannot open it, and the assistant will not read it when answering a question from someone without access. If a crew lead asks the assistant about discount thresholds, the assistant replies based only on the folders that crew lead can see.
This is coordination through access control. The owner decides what context each person and each connected app's AI can work from, and the system enforces it. Transparency about what the assistant read matters only if the person reading the answer is allowed to see those documents in the first place.
Document history tracks who changed what and when, with restore. If the assistant files a note the owner later decides was inaccurate, the owner can undo it. If a team member edits a process doc, everyone can see the change and who made it. History is not a coordination mechanism on its own, but it supports coordination by making past decisions visible and reversible.
The Limits of Mycel's Coordination Model
Mycel does not coordinate video meetings, does not transcribe calls, does not record what was said in a conversation outside the vault or team chat, and does not build agents that take actions on behalf of the business. It does not run automations or tasks for you, and it does not connect to a library of third-party services.
If your coordination need is an AI assistant that listens to a sales call, takes notes, and drafts a follow-up email while you drive to the next appointment, Mycel is not built for that. If you need an agent that monitors inventory levels and automatically reorders supplies when stock is low, that is not what Mycel does.
The product coordinates around knowledge: writing it down, finding it, showing where an answer came from, and gating what gets changed. If the work fits that model, Mycel's coordination tools are explicit and transparent. If the work requires a different form of AI involvement, look elsewhere.
How Mycel's Pricing Reflects Coordination Needs
Coordination between people and AI usually requires more than one person. Mycel's pricing tiers reflect that.
The Free plan is $0 for one person, with vault, filing, search, and 50 AI credits a month. It includes the assistant and basic coordination tools, but no team roles, no private folders, and no connected apps.
Personal is $50/month or $500/year for one person, with 1,500 AI credits a month, Email in, and Omi included. Personal Plus is $89/month or $890/year for one person, with everything in Personal plus every available add-on and more AI credits.
Team roles, private folders, and team chat belong to a business workspace. The Business plan is $119 per seat per month for up to 20 seats, or $1,190 per seat per year. It includes everything in Personal per seat, plus connecting TradesBackbone, Relay, ReputeLift, and SynthPrism, Today, team roles, private folders, document history with restore, automations, and every add-on.
Enterprise past 20 seats is custom.
For a small business where coordination means the team and the AI assistant work from shared folders with approval gates, the Business plan provides the workspace structure, connected apps, and role-based access that coordination requires.
Real Coordination Versus AI Hype
Much of the language around human AI coordination in 2026 describes aspiration, not shipping product. Claims that an AI "never hallucinates," "always cites its source," or "cannot be wrong" should be read skeptically. Mycel does not make those claims. The assistant shows which documents it read, and a reply that read nothing is marked that way, but that does not mean the assistant's interpretation is always accurate or complete.
Coordination is not about perfect AI. It is about structures that let people verify, correct, and control what the AI does. Mycel provides those structures: shared context in the vault, citations that show the assistant's work, approvals that gate changes, and export that keeps the business in control of its knowledge.
If a tool claims its AI coordinates with humans but does not show which sources it read, does not require approval before taking action, or does not let you export and leave, that is automation with a coordination label. Read the feature list carefully.
Frequently Asked Questions
Does Mycel's assistant require approval before every answer it gives?
No. The assistant answers questions from the vault without approval, and every answer shows which documents it read. Approval is required only when the assistant would write something into the vault, file a task, or make a change inside a connected Martello app. Answers are transparent but not gated; changes are gated.
Can the assistant read documents outside the vault?
No. The assistant reads only from the folders in the business vault, and only the folders the person asking the question has permission to see. If the answer requires information not in the vault, the assistant will say it found nothing, and a person can add the missing document.
What happens if someone approves something the assistant filed and it turns out to be wrong?
Every document in the vault keeps a history of who changed what and when, with restore. If the assistant filed a note that was inaccurate, the owner or admin can undo the change. The same applies to anything a team member writes: the history is visible, and earlier versions can be restored.
Does Mycel coordinate work between people without involving the AI?
Yes. Team chat includes channels and direct messages between people in the business, and the vault is a shared workspace the team edits directly. The AI assistant is available when someone types @assistant in a message, but the coordination tools—shared folders, team chat, role-based access, document history—work independently of the assistant.
Can Mycel's assistant take actions inside Relay or TradesBackbone without approval?
No. Anything the assistant would change inside a connected Martello app waits in Approvals first. Customer records stay in Relay and TradesBackbone, and the AI in those apps reads only the vault folders the owner shares with them. Mycel's assistant does not write directly into another app; changes wait for a person to confirm them.
Is Mycel useful for a solo business owner with no team?
Yes, for the Personal or Personal Plus plans, which are built for one person. The owner gets the vault, the assistant, and coordination tools like Email in and Omi, but no team roles, no private folders, and no connected apps. Coordination in that context is between the owner and the assistant, with the vault as shared memory. Business workspaces with team chat and connected apps require the Business plan.
Making Human AI Coordination Concrete
Human AI coordination is not a feature to check off. It is a set of structures that determine whether people stay in control of what an AI does, can verify its work, and retain ownership of the knowledge the business builds.
Mycel puts those structures in place: the vault as shared context, citations that show what the assistant read, approvals that gate changes, team chat that brings the assistant into the conversation, Today that aggregates what is waiting across apps, role-based access that controls what each person and AI can see, document history that makes changes visible and reversible, and export that keeps the business in control of its memory.
If your coordination need fits that model—team knowledge, approvals, transparency—Mycel is built for it. If your need is real-time co-piloting, meeting transcription, or agents that act on their own, it is not. The product is young, from a small team, and it does what it says it does. Start with how Mycel works if you want to see the vault, assistant, and connected apps in detail.
Human AI coordination works when the structures are explicit, the boundaries are clear, and the people using the system understand what the AI can and cannot do. Mycel makes those structures visible and keeps them under the team's control.