12 posts. Tags are topics; for the editorial split see Feature releases and Developer updates.
The software-factory plugin: a request becomes work a person approves from one card, a contract a headless worker executes in its own checkout, evidence QA checks against the contract, and a release the asker hears about. Three pages, four seats, gates at every handoff. vocion-core#655, #658, #672, #683, #695.
One room per engagement — a deal, a project — holding everything ingested about it and everything written from it: the sources filed with a weight and a score, the rules the agent reads first, the notes, the timeline, the open items on Review. A collector files clear matches after every sync and asks about plausible ones. What it is, who it is for, and the line that turns it on.
The client document written from its data room — proposals, scope documents, partnership updates — as print-ready sheets in the house framework that render-verify before a person sees them, are read as the sceptical buyer before the export will print them, and teach the writer a rule from every correction. What it is, who it is for, the line that turns it on, and what has changed since it shipped.
One line turns on a workspace's long-term memory: the voice, the standing rules, who is who, the decisions that hold — as markdown artifacts the agents write above a confidence bar, a researcher answers from, a debrief keeps current after every finished piece of work, and a curator consolidates on Fridays. What it is, who it is for, and what has changed since it shipped.
The collector files fresh material into the room it belongs to, with its score and the evidence behind it, and a Remove that undoes it for good. It had never once worked in production — until today.
The red team stops being a habit the writer has to remember. export_document_pdf now refuses to print a client-facing document with a blocking finding on its current version — and reads the document itself if nobody has.
The Proposals plugin gains a red team, a twelve-sheet spine and its own learning step: the writer critiques the document the way the person receiving it will, and every correction becomes a rule the next proposal starts with.
A client document cannot be exported until it has been read as the buyer. One Marketplace with two tabs is where you add capability; Teams is where you see what you already have. The Review queue calls a proposed action what it is — a recommendation. And the data-room collector files things, which it had never once done in production.
Two verbs, two places: Teams and Agents show the capability you already have, Marketplace is where you add more. And a Review item is now a recommendation — because a proposal is a document a client reads, not a decision on your queue.
The client-engagement workflow — one room per engagement, the document written from it — moves out of a sample workspace into two plugins with their own agents, missions and measures, and the sample workspace becomes one line plus a brand.
Vocion 2.117 ships workspace plugins — a wiki, data rooms and proposals as directories of agents, skills, pages, missions and measures that a workspace enables with one line, that the chat recommends when a conversation calls for them, and that start improving themselves the moment they are on.
What nine weeks of a founder's hand-run wiki taught us about long-term context for agents — and how Vocion's wiki plugin is built so the agents write it, people undo it, and nobody pastes into it.