Components
A component has a stable ID, name, section (frontend, backend, database, APIs, authentication, storage, AI, external, infrastructure, deployment, security), technology, status, inputs, outputs, dependencies, owner agent and linked requirements. See the architecture page for the Atlas Field Service demo inventory.
System Map
- Views: System, Frontend, Backend, Database, AI, APIs, Infrastructure.
- Zoom, pan, search, filter and group.
- Selecting a node highlights its dependencies and dependents and fills the inspector.
- Layout is a longest-path layered graph so the same project always draws the same way.
Data Flow
Nodes represent users, interfaces, application logic, AI, services, databases, external systems and results. Edges record:
- The data that moves.
- Classification: public, internal, personal, credential or project content.
- Whether the channel is encrypted.
That classification is what the Security Agent audits. A high-severity finding in the demo project (AUD-001) is a routing-agent prompt that still includes customer names — visible because the edge is classified as personal.
Decision records
Architecture Decision Records (ADR-001…) keep the reasoning next to the result: decision, reason, alternatives, consequences and status, linked to the components they affect.
Application layers
The Windows application itself is specified as UI → domain → application services → AI → visualization → infrastructure → security. The public website shares the visual language of that UI but does not include those layers. Details: application architecture.
Something missing? Send feedback.