v1.8 Changelog

Released: October 2026

The "V/TO" release: an organization has one company vision shared by all its teams, each team's traction shows its Rocks and long-term issues live, and issues are short-term or long-term.

Highlights

• One company vision: Core Values, Core Focus, 10-Year Target, Marketing Strategy, and 3-Year Picture belong to the organization -- every team's V/TO shows the same vision
• Team traction, live: the 1-Year Plan per team, the quarter's Rocks and the long-term issues straight from their modules -- nothing is typed twice
• Long-term issues: the Issues page has Short-term and Long-term tabs; the weekly meeting works the short-term ones, the V/TO lists the long-term ones

Features

Company Vision

• The Vision column of every team's V/TO shows the organization's vision, with the note "The vision of <organization>, shared by all teams."
• Organization Owners and Admins, Implementers, and the Admins and Owners of a leadership team edit it. Everyone else in the organization reads it ("… The leadership team edits it."). Not while the organization is suspended.
• The 3-Year Picture moved to the Vision side, where EOS puts it.
• The People Analyzer takes its core values from the company vision.
• GET /api/v1/orgs/{orgId}/vision reads it (every organization member), PATCH /api/v1/orgs/{orgId}/vision with { "field", "value" } sets one field.

Team Traction

• 1-Year Plan -- written by the team's Admins and Owners, as before.
• Quarterly Rocks -- the Rocks of the current quarter (in your time zone) with owner and status, live from Rocks: the organization's company Rocks on the leadership team's V/TO, the team's department Rocks on the others. All Rocks opens the Rocks page.
• Issues List -- the team's open long-term issues, live. Long-term issues opens the Long-term tab of the Issues page.
• Archive -- the rocks and issues lists written by hand before this release are kept in a read-only card, shown only when there is something in it. Team Admins and Owners move what still matters into Rocks or Issues, then click Clear archive.
• The 3-Year Picture and the 1-Year Plan can be plain text or labelled entries (revenue, profit, measurables or goals).
• There is no Create V/TO button anymore: every team has a V/TO, and the first save stores the team's part.

Short-term and Long-term Issues

• The Issues page has the tabs Short-term (worked in IDS at the weekly L10 meeting) and Long-term (on the V/TO, worked in quarterly and annual planning), each with the number of open issues. The tab is in the address (?tab=short-term, ?tab=long-term).
• The issue menu has Move to long-term / Move to short-term; the issue dialog has a Long-term issue checkbox, ticked already on the Long-term tab. Whoever may edit issues may move them.
• The IDS step of the L10 meeting lists only the short-term open issues.
• The REST API Issue has longTerm; POST /teams/{teamId}/issues and PATCH /issues/{id} accept it, and GET /teams/{teamId}/issues?longTerm=true|false filters by it.

AI Assistants (MCP)

• Server version 1.7.0: reading a team's V/TO returns the new shape -- the company vision, the 1-year plan, the quarter's Rocks and long-term issues live, and the archive.
• Listing issues filters by short-term or long-term; creating and updating issues can set it.

See V/TO and Issues.

Changes

• Breaking API change: GET /api/v1/teams/{teamId}/vision returns a new shape: { teamId, companyVision, oneYearPlan, quarter, goals, longTermIssues, archive, updatedAt }. It no longer returns 404 for a team without a V/TO -- the fields are empty instead. The change was made while the API was available only on the dev environment. See V/TO in the REST API.
• PATCH /api/v1/teams/{teamId}/vision accepts only the team's fields: oneYearPlan (text or object), and quarterlyRocks / issuesList with an empty value only, which clears the archive. Anything else for these two, and every company field, returns 422. POST /api/v1/teams/{teamId}/vision still creates the team's record if it is missing (201).
• Existing issues are short-term.

Upgrade Notes

• One database migration runs automatically on start. It copies each organization's vision from its leadership team's V/TO -- or, if that one is empty, from the most recently updated V/TO with vision content -- into the new company vision, keeps the old rocks and issues texts as each team's archive, adds the short-term/long-term flag to issues, and removes the vision fields from the team V/TO.
• If two teams of one organization hold different vision texts, the migration stops with an error instead of losing data ("Organization … has different visions in several teams"), and the app does not start. Make the visions of those teams equal, or clear the vision of all but one of them, then start the app again.