Changelog

This page is the record of what changed in Zuse Bifrost and when, newest first. Each entry names the day a change reached the product, says in a sentence what a person or an agent can do that they could not do before, and links to the pages of this guide that describe it in full. Read it when the product has moved under you, or when a page you know has grown a section you have not seen.

October 29, 2026Copy Anchor Link

• The board. The running sprint's work, or any scope of the backlog, in a column per status: a card dragged into another column runs the same move as the backlog, a card dragged up or down takes a new place in the project's order, a column the project caps turns red and takes no more once full, the swimlanes lay the cards out by epic, person or kind, and the quick filters narrow them. Agents read the board through their own tool, items are ranked over the API, and work_item.ranked joins the family. See Board, Backlog and Project settings.
• Sprints. A sprint is planned with its dates, goal and capacity, takes its scope from the backlog, starts when the team's commitment approval carries, runs with its points on the page, and closes with its velocity recorded and the unfinished work carried to the backlog or the next sprint. The backlog gained a sprint field and a sprint filter, agents read sprints through their own tools, and the sprint.* events go out to webhook endpoints. See Sprints, Backlog and Approvals.
• Generated documents. A business requirements document or a software requirements specification is rendered from the record, drafted by Heimdall, approved to final and shared with the client, with every copy kept. See Generated documents, BRD, SRS and Documents shared with you.
• Baselines and change requests. A baseline freezes a set of approved records, the client signs off on scope, and a change request is the one way a frozen record changes, with Heimdall's impact analysis and the council's change-impact sitting. See Baselines, Change requests, Signing off scope and Impact analysis.
• Heimdall's panel. The panel says what Heimdall is doing while it works, grew wider, lights its aura from the edges of the window, follows the record it writes to its page, and folds the answer's cards. The council now deliberates: every voice researches its lens, reads the record, answers the others and refines the plan before Heimdall rules. See The Heimdall panel, The council and Start a project with Heimdall.

October 28, 2026Copy Anchor Link

• Approvals. The approval engine landed with its policies, requests, signed decisions and clocks, the approval bar on every approvable record, the policy editor in the project settings and the approvals inbox, over the REST API and the MCP server as well. See Approvals, Approving requirements and Project settings.
• A project from a conversation. Heimdall starts a project from a paragraph, writing the registry and the planning record as it goes, with record cards in the thread and the council sitting in it; agents gained the tools that write the registry, the record, the review queue and the research notes. See Start a project with Heimdall and the tools reference.
• Heimdall suggests. The project overview gained the suggestions rail, the weekly improvement sweep checks the record for what is missing, and research runs read the project's domain. See Project overview, The improvement sweep and Research.
• The council. Named voices with their own lenses sit on bounded moments, each sitting kept with its turns and findings and a verdict after one rebuttal round, with a Council tab in the panel and the voices seated per project in its settings. See The council.
• Brief import. A pasted brief, an upload or a knowledge entry is read into a review queue where every suggestion lights up the passage it came from, with an editor and a merge picker; nothing is written until a person accepts it. See Brief import and Heimdall reads a brief.
• Quality reviews. Heimdall scores a story, a requirement or a rule, shows its findings in the flyout with Review now and Ask Heimdall, and badges the rows with the score. See Quality review and Quality review with Heimdall.
• Inline assists. Ask Heimdall sits beside every long field of the planning editors for one metered rewrite, and a version saved after an inline draft is marked as drafted by Heimdall and accepted by the person. See Inline assist and Revisions and versions.
• Versions for the registry. Glossary terms, data entities, personas and stakeholders keep every version and show them in their flyouts. See Glossary, Data dictionary, Personas and Stakeholders.
• Around every artefact. Attachments on a private disk with a files panel, labels as a project's own vocabulary on the backlog, comments with mentions and watchers under every record, and links between artefacts read from either side. See Attachments, Labels, Comments and mentions and Traceability.
• The rest of the planning record. Decisions with the options weighed, the RAID log with its risk matrix, use cases with their flows and steps, and business rules of six kinds with condition, action, exceptions and worked examples. See Decisions, RAID log, Use cases and Business rules.
• The brand. The application and this guide draw their marks and icons from the Zuse Bifrost logo.

October 27, 2026Copy Anchor Link

• Requirements. Functional and non-functional requirements on their own sequences, versioned, on their page and over the REST API and the MCP server. See Functional requirements and Non-functional requirements.
• The backlog. Work items of six kinds with acceptance criteria, versioned, with their lifecycle, hand-over and versions. See Backlog and Acceptance criteria.
• Versions and epics. Every save of a revisable artefact writes a restorable version with its diff, author, origin and reason; epics are numbered from the tracker sequence with their lifecycle and history. See Epics and Revisions and versions.
• The intake wizard. A project starts from a client, a name and a paragraph, walks components, environments, stakeholders and personas with presets, and resumes from the sidebar until it is finished. See Intake wizard.
• The registry. Project settings with workspace defaults and a danger zone, repositories, design references, the dictionary of glossary terms and data entities, stakeholders and personas, and components and environments with health checks and change freezes. See Project settings, Repositories, Design references, Glossary, Data dictionary, Stakeholders, Personas, Components and Environments.
• The project shell. The project selector, the sidebar menus, the overview page, the project registry and the clients page. See Project overview, Registry and Clients.
• Names and voice. The product is called Zuse Bifrost and its assistant Heimdall everywhere people read them, and the application's prose took on a light Norse voice with the nouns kept plain. See the introduction.
• Heimdall with a budget. The assistant runs behind AI metering with monthly budgets per team and the AI settings page. See The Heimdall panel, Usage and budgets and AI settings.

October 26, 2026Copy Anchor Link

• Machine surfaces. The REST API with its OpenAPI document, the MCP server with OAuth, discovery documents, a consent screen, the first tools and the catalogue resources, and the agent-readiness documents served from the application. See the REST API, the MCP server and Agent readiness.
• Events and webhooks. Domain events announce every change and outbound webhooks deliver them, signed, with retries. See Webhooks and events and Webhook endpoints.
• Activity and notifications. The activity log and timeline, the notifications centre, alert destinations per class, and Telegram linking. See Activity log, Notifications and Telegram.
• The workspace. Teams, members, invitations, roles and groups, with API tokens and webhook settings. See Teams, Members and guests, Roles, Groups and API tokens.
• Accounts. Invite-only sign-in with two-factor authentication and passkeys, and the account settings pages. See Account, Sign in, Two-factor authentication and Passkeys.