Breaking Changes

Breaking changes lists every change that removes or reverses something you may rely on, newest first, with what to do instead. New features and wording changes aren't listed here.

Each change is listed under the date it reached production. Each page a change affects carries a Changed stamp that links to the entry here.

26 October 2026

A table's domain comes from the domain tag on its node

On the Aspects screen, tables, endpoints and channels group by the context tag named domain:<name> on the node that uses them, or on the first node above it with one. The Domain field on a node, and the name of a domain_group or bounded_context node, no longer place them. Until the code plugin tags your boards, rows show under No domain.

To get domains back, run /sync with the updated code plugin, which tags each business-area node once, then /aspects. To move rows yourself, change the domain: tag under a node's Tags and run /aspects again.

Affects Aspects, Organization Settings and the code plugin.

Organizations start with seven context tags, and archetypes add none

Load Default Tags adds seven tags: owner:team, change:breaking, change:needs-adr, change:quick-win, risk:tech-debt, risk:security-review and blocked:external. The other provided tags are gone, except where your organization used one: those stay as your own tags, on the elements that carry them.

The provided archetypes no longer add tags such as maturity:stable or observability:standard to new nodes and edges, and those tags are gone from existing ones. Tags the code plugin invented from your code that nobody else used are gone too; the plugin now adds only domain tags. A code push that names a tag your organization doesn't have is reported, not created: create the tag in Organization settings first.

Affects Organization Settings, Archetypes and the code plugin.

25 October 2026

The hub's Diary and Entries cards are now one Changes card

On both hubs, the Diary card and the Diary entries card are one Changes card. It says what leads in one sentence, over the row of weeks, the filters and the ranked entries, each with View detail. It sits beside Architecture, under Fleet attention on the root hub and under the attention queue on an app hub. On an app hub, From other apps is one of its filters.

A hub you haven't arranged no longer shows Diary timeline and Diary entry; add them from Add widget. The Changes screen's Diary tab now draws its entries as a List, a Timeline or a Map, with Replay the weeks beside them, and opens each entry beside the view. A layout you saved keeps the cards it had, with Changes added on top in place of the two it replaces.

On the root hub, Recent activity (Activity under Add widget) is no longer on the default, and the System scorecard is. The Add widget card named Migrations is now Comparisons, and it runs under Fleet attention whenever a comparison is open.

Affects The Root Hub, App Boards & the Hub, Changes and Change Cards.

18 October 2026

The Team page lists members only for owners and admins

Editors and viewers no longer see the member list on the portal's Team page or in Organization settings → Access. The Team page shows them Your access instead. It lists their own role, and the owner and admins with their email addresses. Organization settings → Access shows them Your role and Who manages the organization. Only owners and admins see other members, pending invitations and suspended members. Names on work items, diaries and workspaces still show.

To change your role or to bring a colleague in, write to one of the owner or admins listed there.

Affects Permissions & Access Control and Workspaces & Organizations.

16 October 2026

Contributor and Read only are now Editor and Viewer

The two organization roles are renamed wherever a role is shown. Contributor reads Editor, and Read only reads Viewer. You see the new names on the Team page, the invite panel, Settings → Access, the lock on a control your role can't use, and the role-changed email. What each role can do is unchanged, and nobody's role changed.

The Viewer role is now assignable on every plan, Free included, and a viewer never holds a seat. Only the Admin role is a Team feature. Any member, viewers included, can sign in to the code plugin against an app board that already exists.

Affects Permissions & Access Control, Plans & Billing, For Every Role and Workspaces & Organizations.

12 October 2026

The Diary replaced the root hub's briefing and change cards

The root hub now leads with the diary's cards: Diary, Diary entries and Architecture. Each app hub has them under the attention queue, above Contract surface. It tells each week as the pieces of work that happened, flagged and breaking changes first. These cards are gone, and Add widget no longer offers them:

• At a glance and Briefing on the root hub: the Diary's entries say what changed, and a line under them says who depends on it. Pointing at an entry rings the boards it landed on in the board map.
• Change map on the root hub: its canvas, lenses and replay are now the Architecture card beside Diary entries.
• Architecture, the canvas preview: it is now the live canvas painted with the diary, on both hubs. Its Layers and Boards below counts are gone.
• Contract changes: the Diary's Contracts filter.
• Asked vs arrived: an entry's Asked for, and the System scorecard's Periods with no work item.
• Changed upstream on an app hub: the From other apps filter on the app hub's Diary entries card, which lists the changes in other apps that reach this one. get_hub_status with include: ['changes'] still lists them for an app board.
• People and agents and Most changed (the card that listed services by their commits, renamed) are tabs on the Changes screen now, with the same period control.

On the Changes screen, the list of periods and All recorded are gone. The Diary tab lists the entries of every week the period control reaches, and selecting a week on the row of weeks lists only that week. An opened entry names who did that piece of work. The sentence per person and the services each person touched are gone, and /changes no longer writes a sentence for the whole period or for each person.

A flag's row on the attention queue and on Fleet attention reads Open change, not Open period, and opens the entry. The Monday briefing names diary entries and links each one.

Affects The Root Hub, Changes, Change Cards, App Boards & the Hub and Automations.

get_hub_briefing is now get_change_diary

The MCP tool get_hub_briefing is gone. Call get_change_diary instead: it returns a week's diary entries on the root board or an app board, and takes at or periodId to pick the week.

list_change_periods rows name the headlines of a period's pieces of work in place of a summary. get_change_period returns the pieces of work, and its people no longer carry a summary or the services they touched. get_hub_status period rows no longer carry summary.

Affects MCP Tools.

The architect plugin is now the workspace plugin

The plugin that works across your whole workspace over MCP access installs as pmap-workspace, and its commands run as /pmap-workspace:<command>. The command that sets up an empty workspace is /setup; every other command keeps its name.

pmap-workspace is a new plugin, so you install it; updating pmap-architect doesn't bring it. An update to pmap-architect brings a last release that only points to the new plugin. Each session starts with a line naming pmap-workspace, and /pmap-architect:start, /pmap-architect:help and /pmap-architect:update print the same notice and stop. It has no other commands and gets no further updates.

To move, install pmap-workspace from the marketplace you already have, then uninstall pmap-architect:

claude plugin install pmap-workspace@provenmap
claude plugin uninstall pmap-architect@provenmap

codex plugin add pmap-workspace@provenmap
codex plugin remove pmap-architect@provenmap

If you installed from the early-access marketplace, use @provenmap-ea in place of @provenmap.

Your sign-in carries over. The stored token and your host's provenmap MCP entry are unchanged, so there's no new /login. Tokens are still generated and revoked under Workspace agent access on the root hub.

Affects The Workspace Plugin, Getting Started — Plugin or Chat, MCP Access and Boundary Rules.

Architect access is now Workspace agent access

Each hub's access button names its scope:

• Workspace agent access on the root hub was Architect access. It opens the workspace's MCP access tokens (Use a key → Generate token) and the plugin connections bound to its app boards.
• App agent access on an app board hub was Agent access. It connects a coding agent to that one board through the code plugin's /login.

The Workspace settings section that holds both the tokens and the plugin connections was Architect access and is Agent access. Tokens, scopes, plugin connections and who can open each button are unchanged.

Affects MCP Access, App Boards & the Hub, Signing In & Credentials, Workspace Settings, Workspaces & Organizations, The Workspace Plugin and Connecting Sources. Both getting-started paths are affected too: Plugin or Chat and Hands-On.

10 October 2026

What changed moved from pushes to change periods

A push session's footprint no longer lists the commits, who was involved, the services touched or the change rules' answers. Its What changed section names the change period the push landed in, and the period holds all of that. /sync and /aspects no longer record it; /changes reads it from git, once per week or month.

Schema and API contract are answered from the period's changed files, such as migrations, OpenAPI files and controllers, instead of from an /aspects push in the period. Every recorded period now answers them. The hub's change cards count change periods, not syncs.

Run /changes in each app's repo to record its history, and let /analyze --scheduled keep the current period up to date. Update the code plugin to its latest version.

Affects App Boards & the Hub, Changes and Change Cards.

/adopt is now /aspects

The code plugin's command that extracts aspects is /aspects. Its flags and workflow are unchanged: --aspect <kind>, --db, --api, --mode replace|merge, --dry-run and --no-verify, and with no kind flag it asks which kinds to extract.

Running /adopt prints that the command is now /aspects and stops; it extracts nothing. Run /aspects with the same arguments; the message also says /adopt will be removed in a future release. The app's empty states and playbook steps name /aspects.

Affects The Code Plugin and Aspects.

6 October 2026

get_board_tree lists one level at a time

get_board_tree returns the board you name and the layer boards directly beneath it, up to 100 per call. A call on root no longer returns every layer board in the workspace, so a workspace with hundreds of boards stays one short read.

Each layer board in the result carries childCount. To read deeper, call get_board_tree again with that board's slug, or pass depth: 2 for two levels in one call. When the result's more is above 0, pass offset for the next page. Update the workspace plugin to its latest version: its /hub and /start read the tree this way.

Affects MCP Tools.

4 October 2026

Proposals stop at the depth cap

/analyze no longer proposes boards deeper than analysis.plan.maxDepth, or drill-downs the analysis suggested with fewer than analysis.plan.unitFloor significant files. Accepting a board past the cap with an older --plan-accept key stops with an error that names the cap. Each proposal accepted past the cap used to propose the next layer down, so the list never emptied, even with every planned board built.

To go deeper in one place, run /analyze --deeper <folder>. To let the plan propose deeper everywhere, raise analysis.plan.maxDepth. To decline a proposal, dismiss it with --plan-dismiss <key> or from the Next area question in /analyze.

Affects The Code Plugin.

30 September 2026

Remove work items no longer complete themselves

A sync completes an Open or Assigned structural work item when its changes already exist in code. A work item with a Remove answer is the exception. A sync can't tell a removed element from a renamed one, so a rename completed the work item although nothing was removed.

A Remove work item now stays open and shows ≠ Drifted once its element is gone. Check the code, then complete it yourself, or leave it to the developer who holds it. Other structural answers still complete themselves, and a sync still confirms a completed Remove with ✓ Confirmed.

Affects Work Items.

Agents no longer publish boards

The publish_board tool is gone from MCP access. Publish from Publish: publishing makes a board readable outside the workspace, so you choose who can see it. A playbook's publish step is now yours: the agent asks you to publish, and the step ticks when you do.

An agent that calls publish_board gets an error that the tool doesn't exist. Update the workspace plugin to its latest version so it stops asking for it.

Affects MCP Access, MCP Tools and Playbooks.

24 September 2026

The connect plugin is retired

Grounding a board in a document repo moved from the connect plugin (pmap-connect) into the code plugin, as its /ground command. /ground mirrors an architect-authored board into a document repo, links the board's nodes to the PRDs, RFCs and ADRs that back them, and reports drift.

If you have pmap-connect installed:

1. Install pmap-code from the same marketplace (/plugin install pmap-code@provenmap on Claude Code; pick it from /plugins on Codex) and restart your host.
2. Run /ground in the document repo. It reads the .provenmap/ state the connect plugin wrote (the binding, the mirrored board and the evidence links) as is, so nothing needs migrating.
3. Uninstall pmap-connect. Its last release ships three commands (/start, /help, /update) that print this notice, and it gets no further updates.

The binding credential is unchanged.

Affects The Code Plugin. The connect plugin's own page is gone; its address redirects to the code plugin.