Xero beta adds architecture decision records

Xero private beta now keeps an architecture decision record with each proposed serverless design. The record captures the workload goal, the AWS services selected, the relevant constraints, and the trade-offs considered while the proposal was created.

The purpose is simple: an architecture diagram is useful, but a team also needs to know why a boundary, event path, or data choice exists before it becomes infrastructure code. The decision record gives reviewers a starting point for that conversation and gives future contributors context they can keep with the project.

What is included

For supported proposals, the beta now groups the following together:

• the system goal and constraints supplied by the team;
• the proposed service and data flow;
• alternatives and notable trade-offs;
• an editable TypeScript and AWS CDK starting point;
• the next implementation questions that still need human ownership.

Nothing deploys as part of creating a proposal. Teams can review, edit, export, or discard the result before choosing an explicit deployment workflow.

During the beta

We are using feedback to improve how clearly Xero explains its recommendations, especially for event-driven boundaries, identity, and migration sequencing. If your team is planning a new service or revisiting an architecture before a build, request access and describe the decision you need to make.