Architecture
Architecture is a branch-aware diagram workspace for designing infrastructure and keeping the design aligned with code. Diagrams live in .infracodebase/*.json in the connected repository, so a saved diagram follows the same review and history model as the rest of the project.
Architecture depends on Work and appears when both features are enabled for your enterprise.
Open a diagram
Use the branch picker to open the workspace branch, one of your Work branches, or another remote branch. Architecture opens an active architecture branch first when one exists, then the workspace branch or repository default branch.
A repository can contain more than one diagram. Use the diagram picker to switch between them or create a new one.
Design on the canvas
Open the resource palette to search icons by provider and category. Drag resources onto the canvas, place resources inside containers, and connect related nodes. Select a resource or connection to rename it or change its properties.
The canvas supports undo and redo, connection endpoint changes, and deletion. The layout score highlights overlaps, crossings, spacing, and other visual problems. Moving an item changes the presentation without changing what the architecture means.
Save to Git
Edits stay in your browser until you choose Save. Saving commits the selected diagram file to the branch with your user identity. The save dialog suggests a commit message based on the architectural changes, and you can edit it before committing.
Architecture never writes directly to the repository's default branch. Saving from the default branch creates a feature branch. If the branch moved after you opened it, the save is refused so your changes do not overwrite newer work. Your local draft remains available.
You can edit a Work branch when you have access to its conversation and no run is active on it. The next Work request continues from your saved diagram commit.
Synchronize diagrams and code
Choose Sync with code and select a direction.
- Update code to match the diagram asks Work to implement the saved design.
- Update the diagram from code asks Work to inspect the repository and revise the diagram.
The sync uses the same feature branch, Work conversation, and open review request. Starting from another repository branch creates an architecture conversation based on that branch. Only one architecture sync can run at a time in a workspace.
The sync badge compares the saved architecture with the version last handled by Work. Resource changes, connections, labels, and container membership require another sync. Layout, size, style, and attachment-side changes do not.
Open the active status button to follow the run in Work. When a Work result changes a diagram, its View diagram action returns to the matching branch and version in Architecture.
Continue an existing feature branch
Architecture and Work share a feature branch, but only one conversation can change that branch at a time. This keeps each conversation's checkout, verification result, and review request aligned with the same branch state.
When the current conversation is idle and no change request is still open, a new Architecture sync can continue from the branch's latest commit. The new conversation gets its own history and becomes the branch's writer. The earlier conversation keeps its messages and results, but it can no longer change or publish that branch.
Architecture refuses the handover while the current conversation is running, waiting for an answer, publishing, or attached to an open or unconfirmed change request. Finish that work or save the diagram to a new branch before starting another sync.
Read-only states
A diagram is read-only when you only have view access, when it belongs to another private Work conversation, when Work is active on that branch, or when the file contains data that cannot safely be shown in the editor. The branch and diagram can still be inspected when your permissions allow it.