6 posts. Tags are topics; for the editorial split see Feature releases and Developer updates.
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 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 data-room collector shipped, ran after every sync, and filed nothing. One AND in a where-clause had pinned it to the sixty seconds around the run it followed — which made a documented constant unreachable and the dedupe code around it dead. vocion-core#463.
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.
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.