5 posts. Tags are topics; for the editorial split see Feature releases and Developer updates.
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.
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.
The red team's first live run returned nothing parseable twice, and the agent read the document by hand instead and said so. The cause was a length budget, not a reasoning failure — and the fix was to stop asking a model for JSON in prose and declare a tool it has to call. vocion-core#457.
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.