Release notes — 2026-09-15

There was a second release on 2026-09-15. This post covers the morning. Release notes — 2026-09-15 (afternoon) covers what shipped after it: Review folding into Needs you, the app's first notification surface, the navigation sweep, a chat composer that never locks, team report v2, and the live artifact that supersedes the canvas described below.

The release branch both posts describe landed on main overnight, inside Vocion 2.82 — which also carries scoped memory, the extractor and crawler work, and two new manifesto principles. Six further versions shipped that day, in Vocion 2.88.

Vocion core is at v2.69.0. This is the first post in the releases feed. Posts now come in two categories: feature releases for what changed for someone using Vocion, and developer updates for the architecture, APIs, schema and operations behind it. The one-page bulleted version of everything below is /releases. The intent from here: one post per user-facing change, with the pull request it came from, the outcome it serves, and a screenshot or short video from a local workspace on fictional data. The deploy moved the instance's pin from 4ccbe03b to v2.69.0 — 109 commits.

Merged to `main` (everything in this release)

Feature	Post	Source
Needs-you inbox and the `ask` primitive	Decisions from your phone	#325
Outbound mail and the daily team report	Vocion can mail you now	#324
One conversation surface on every page	The dock	`336fddd9`
Agents recommend a decision; adoption measures agreement	Recommend a decision	#321
A decision proposes a learning candidate	Learning candidates	#318
Extraction pipeline: processors in the sync, feed-aware web connector, sources API	Extraction leaves the agent loop	#319
A workspace spends its own key on paid tools	Own keys	#316
Slack surface, phase 1	Mention an agent	#251
Review queue: retryable failures, true filters, Regenerate, claim-before-resume	Review queue	`36083e10`, `0d056246`, `82354c3b`, `4aa06a6d`, `aeb5c956`
Product Design Manifesto	The bar	#322
Team report: outcome contracts per team and member	Team report	#326 · `775c5e10`
Model upgrade test; GPT-6 Astra, GPT-5.6 and Claude 5 pricing	Model upgrade test	#323 · `297f420a`
Slack: the bot introduces itself on invite; agent personas	in Slack surface	#253 · `c46580ee`
Vocion mark and favicon as the default brand	—	#327 · `55756348`

Each post opens with its status line; the two written while their PRs were in review (team report, model upgrade test) were updated the same day when the PRs merged.

Developer updates in this release

The same changes, written for someone reading the code rather than using the product.

Subject	Post	Source
The `AgentEvent` union, the SSE route, resumable streams	What streams through the conversation surface	#332, #329
No agent picker: a workspace lead and a derived delegation roster	One agent per workspace	#332
The `artifact` table, `render_*` tools, and an org-checked route	Artifacts as data	#333
`decision_alignment`, the six-rung ladder, promotion thresholds	Earned autonomy	#338
Verify-before-parse webhook, threading, unknown senders	A mailbox per workspace	#334
Why a cookie-scoped `/dashboard` URL breaks a mailed link	Workspace-aware links	#336
List, Detail and Ledger as the three dashboard archetypes	A pattern library	#339
Dump-before-migrate, a post-migration schema check, a daily pin-bump PR, workspace dry-runs in CI, a rollback runbook	Deploying without losing the schema	deployment-side; the migration conventions and CI gate are in `vocion-core`

The rail train, shipped

Nine of the posts above describe the rail, canvas, email, routing, autonomy, patterns and review work. That train merged onto release/2026-09-15-rail (7db4f7f6) and deployed on 2026-09-15, with migrations 0094–0099 applied. The individual pull requests are landing on main behind it at CI's pace, so for a short window a path a post cites may be on the release branch before it is on main. Each post's status line says which state it was written in.

One of them ships dark: the per-workspace mailbox is in the build but off until a deployment sets VOCION_EMAIL_SURFACE.

Feature	Post	Source
Proposals described for a person, grouped per record	The inbox reads like a list of decisions	#335
The review page: context title, folded Up-next, sticky actions	The review page, rebuilt	#337
Rendered output as tiles on a page beside the chat — superseded the same afternoon, see One live artifact beside the conversation	A canvas beside the conversation	#333
Page and selection context; Do this on a recommendation	Ask about this brief	#329

Also in this deploy

Smaller commits in the same range, each linked: workspace reads stay inside the configured workspace directory (bcffe834) and playbook resource reads inside the playbook's own folder (3b14cc90); a mission run records why a task failed, not just the summary line (1037beaa); enrolment writes approved sends into the nurture ladder's slots first (202c5d1d); MQL intake is read live from HubSpot (bb2806dd); the e2e suite uses one database handle per process (deb9895f). The full list is git log 4ccbe03b..v2.69.0 in the public repo.

How to read these

Each post opens with status (merged or in review), states the outcome the change serves, explains how it works with paths into the public repo, and ends with what changed for an operator. Screenshots are from a local workspace on fictional data; nothing in them is a customer's.

Where this lives in the repo

Core: vocion/vocion-core at tag v2.69.0; the merged PRs and commits are linked in the tables above.
This release process: the workforce's feature-release skill (private repo) writes one post per user-facing change after every merge; the feeds are /blog/feature-releases and /blog/developer-updates, summarised on /releases and available as RSS. The old /blog/tag/release URL redirects to the feature-releases index.

Merged to main (everything in this release)