From written plan to assigned work in Aivonic Workspace

From written plan to assigned work in Aivonic Workspace

A plan written in a note is a promise with no one attached to it. It becomes work only when each line that implies an action is turned into a board card carrying three things: a single owner, a due date, and a link back to the project it serves. Miss any one of those and the card can sit on the board looking busy while nobody moves it.

Inside Aivonic Workspace the plan stays in notes, where it can be argued over and revised. The breakdown happens on the board. A plan line that says to draft a document and then get sign-off is one sentence in the plan and two cards on the board, because drafting and approving usually belong to different people. Each card links back to the project, so anyone opening it can trace why it exists and read the reasoning behind it without asking.

The slow part is the translation itself, which is why it often gets skipped. An AI Hire has read and write access to the same notes and boards the team uses, so it can read the plan and draft the cards, proposing owners and dates. A human then confirms, edits or rejects each one. The confirmation step matters: a card assigned by software that nobody agreed to is just another way of having no owner.

The handoff usually leaks in three places. First, cards created without an owner, or assigned to "the team", which in practice means no one. Second, plans that never leave the document, where agreed actions live only as sentences in a note nobody reopens. Third, duplicate tracking in a second tool, where the same task exists twice, the two copies drift apart, and people stop trusting either one.

Why should an approval be a state change instead of a message?

An approval given in a message thread is a sentence, not a signal. Someone replies with a casual go-ahead under a draft, and now three things have to happen before anything moves. The person doing the next step has to see the message. They have to decide whether that casual reply means approved or only means the approver skimmed the draft. And they have to go somewhere else and act on it. Each of those is a place for the approval to stall, and the most common stall is the simplest: the approver replied, but the owner of the next step was not in that thread.

When the approval is a change of state on the board card itself, those three steps collapse into one. The approver moves the card from awaiting sign-off to approved, or sets its status, on the same card that holds the work. Nothing needs interpreting, because a status has no tone. Anyone watching that board sees the change where they already look. That includes an AI Hire. Because it works in the same boards as the team, the transition can be its cue to pick up the step that was waiting, such as sending the approved quote, publishing the cleared page or opening the follow-up card. The approval releases work instead of announcing it.

The card also keeps the record a thread scatters: who approved, when, and against which version of the work. Weeks later nobody has to search chat history to reconstruct a decision.

The cost is deciding which steps actually need sign-off. If every card carries an approval gate, approvers face a queue of trivial requests and start clearing them without reading, and the gate becomes a rubber stamp. Someone has to name the few steps where a second pair of eyes changes the outcome, and leave the rest ungated.

How do you find a document without hunting for it?

Finding a document is slow because most retrieval is recall, not search. You know the file exists, but you cannot remember its title, its folder, or who saved it, so you type guesses into a search box and scan the results. Search only works when you already hold the right keyword. Linking works from whatever you do remember: the client, the project, the task that produced the file.

In a workspace where documents, notes, CRM records and boards share one knowledge graph, each document can be tied to the things it belongs to. A signed scope document linked to its project, to the customer's CRM contact and to the board card that delivered it can be reached from any of those three starting points. Someone on a call with the customer opens the contact and the scope is one click away. Someone reviewing the project finds it from the project. No one needs the filename. The cost of this comes at filing time: a document saved with no links is as lost as one buried in a folder tree, so the link has to be made when the file is created, not later.

The encrypted vault holds a different category: credentials, contracts with personal data, financial records, anything whose exposure causes harm rather than inconvenience. The test is simple. If the wrong person reading it would be a problem, it goes in the vault. Ordinary documents stay in the linked workspace, where being found is the point.

That split matters more once AI Hires work alongside the team. An AI teammate that can read the workspace benefits from the same links people do and can pull context from a project or contact quickly. It also reads everything placed in its reach. The vault decision becomes the access decision. A password pasted into an ordinary note can be read by any person or agent with access to that note.

What does Maya do when you message her over WhatsApp?

Maya is an AI Hire: a named AI teammate hired into the workspace, with read and write access to the same boards, notes and documents the team uses. The WhatsApp channel is simply another way to reach her when you are away from your desk.

When a message arrives, Maya treats it as a request against the workspace, not as a conversation to answer from general knowledge. If you ask which cards on a project are blocked and who owns each one, she opens the project board, filters for the blocked cards, and reads the linked notes and documents to confirm what each block is actually about. She then replies in the same WhatsApp thread with a short list: each card, its owner and its due date. If you also ask for a follow-up task on anything overdue, she creates it on the board, assigns it to the card's existing owner, and says in her reply that she has done so.

This replaces two things. The first is the human relay, where someone messages a colleague, the colleague stops their own work, opens the board, reads it, and types a summary back. The second is the copy-paste loop, where information is pasted into one place and the answer has to be carried back into the tool by hand. Maya reads the source and writes the change herself, so nothing is retyped.

The answer is only as current as the board. If an owner has resolved an issue but never updated the card, Maya reports the card as it stands, which is still blocked. The fix is a team habit: the board is the record, so it gets updated when the work changes.

She also stops at a boundary. Reading, summarising and creating internal tasks are fine to automate. Emailing an outside party, changing a purchase order or committing money should wait for a person to confirm before Maya acts. Deciding where that line sits for your team is the setup work worth doing in the first week.

Where does the day break, and what should you measure?

Three failures show up first, and none of them announce themselves.

The first is writing to stale state. An AI Hire reads a card, spends time drafting, then writes back over a field a person changed in between. The edit is valid against what it read and wrong against what exists now. The second is over-broad permissions. Granting write access to the whole workspace because scoping it took effort means one misread instruction can touch boards, documents and records far outside the task. The third is silent duplication. A request is phrased twice, or retried after a timeout, and two near-identical tasks appear. Each one looks legitimate on its own, so nobody notices until two people do the same work.

The countermeasure is a habit, not a feature: verify before write. Immediately before changing anything, the agent re-reads the target and checks whether a matching task already exists. If the state has moved, it stops and reports instead of overwriting. Query first, then act, and treat an unknown state as a reason to ask rather than a reason to proceed. It costs an extra read per write, and that read is cheaper than one cleanup.

Four numbers tell you whether it is working, and you can track them yourself:

• Tasks created versus tasks closed. A widening gap means the agent is generating work faster than the team finishes it, and duplicates often hide there.
• Time from request to approval. If it grows, the gates are clogging.
• How often a search fails and someone asks a person instead. That is your measure of linking gaps.
• How often humans correct an AI Hire's edits. A falling rate earns wider access. A rising rate means narrowing it.

Start this week with one project. Turn its plan into owned, dated, linked cards. Put one real approval on a card as a status change. Link every new document to a project and a contact as you file it. Move anything sensitive into the vault. Then give one AI Hire a narrow, read-mostly job and watch those four numbers for a few days before you widen its access.