Model at the right level
Move from context and container views to components, sequences, states, classes, and data models without changing tools.
- System and trust boundaries
- Services, APIs, events, and stores
- Sequence, state, class, and ER diagrams
Software engineering solution
See the whole software system.Keep the reasoning attached.
Model architecture from system context to implementation detail, connect decisions directly to the services and interfaces they affect, and give engineers a shared view that stays useful after the review ends.
- 56 semantic shapes
- UML + C4 workflows
- Mermaid round-trip
- Agent-ready
AURELIA-R1 · software architectureSource-rendered project
Rendered from the checked-in AURELIA-R1 software project used by the application.
ClientWeb applicationCustomer checkout
EdgeAPI gatewayAuth · routing · limits
DomainPayment serviceIdempotent charges
DataEvent streamPayment outcomes
@
ADR-014 linkedCheckout reliability
Architecture that survives implementation
From design conversation to durable system knowledge.
Struct keeps the visual model, technical rationale, ownership, and review path together so the architecture can evolve with the code.
Connect decisions precisely
Reference a diagram, service, connector, or another specification, then follow backlinks from the architecture to every relevant decision.
- Visual and Markdown specifications
- Node and connector references
- Markdown, HTML, and Word export
Fit the engineering workflow
Import Mermaid or PlantUML, let Codex or Cursor produce a validated draft, and keep the result fully editable on the canvas.
- Mermaid import and export
- Validated agent patches
- SVG, PNG, PDF, and project export
Software work in Struct
Model software structure and keep the decisions attached.
Struct supports system architecture and UML work as editable project data, with imports, specifications, reviews, and deterministic checks in the same workspace.
Choosing the level first? Use the practical C4 model diagram guide to plan context, container, component, dynamic, and deployment views.
- 0156 native software shapesServices, actors, boundaries, stores, queues, UML elements, and deployment primitives.
- 02Mermaid interoperabilityImport flowcharts, class, sequence, state, and ER diagrams into editable nodes and relationships.
- 03Linked SpecificationsReference exact nodes and relationships; backlinks keep diagram and rationale navigable.
- 04Project-aware agentCreate or edit the current diagram, update Specifications, and run architecture and visual checks.
A continuous workflow
Design, decide, review, and explain.
Give architecture work a clear path from the first model to the people who build and operate it.
Start with structure
Use a focused starter, import Mermaid, or generate a validated draft with an external coding agent.
Add engineering meaning
Record ownership, technology, status, interfaces, and architecture checks on the model itself.
Write the rationale beside the design
Create linked specifications and reference the exact node or relationship a decision governs.
Review without losing context
Collaborate live, share an expiring review, or present the flow as an animated walkthrough.