8 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.
Per-product reference sets: synthetic inputs written the way a request actually arrives, real shipped commits as the gold standard, a standards page the seat reads and a dataset it never sees. The first set's baseline was 2 of 16 — and why that is the right number to start from.
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.
Vocion's agents now carry typed, scoped memory — preferences, knowledge and procedures, filed per workspace, agent, user, mission or workflow. Every rule is a file a person can read and reword, approval is still the only way one is written, and approved rules finally reach the model instead of waiting to be noticed. Release notes 2026-09-16.
A workspace's voice used to be a paragraph in a prompt that nothing checked. It is now a typed rule set your workspace authors, enforced by a synchronous lint at every seam a draft can come through — the drafting model, the proposal, and the rewrite. A banned phrase costs the model one corrective retry and then fails loudly. And a phrase a reviewer cuts becomes a proposed rule. Release notes 2026-09-16 — vocion-core#370.
One table behind a LangGraph BaseStore, scope carried in the key, a read-only filesystem mount, and a middleware that puts approved rules on the system message. Plus the migration renumbering the release train forced, and an honest account of the one write path the gate does not structurally cover. Release notes 2026-09-16.
When a human edits, approves, or rejects a draft, that decision can become a rule the agent reads next time — but only after a person approves it.
v2.24.0 closes the API gap — fourteen new /api/v1 endpoints give review, feedback and learnings full parity with the dashboard, and admins can now mint API tokens without shell access.