Architecture·production

IAM.Solution / AGL

Architecture as Code with AGL DSL, diagrams, generation and MCP tools.

Landing Application

Key capabilities

  • Enterprise, Solution, System and Software levels
  • AGL DSL and architecture artifact generation
  • CLI, Web and MCP integrations for IDEs and agents

Step-by-step guides

Use cases

Start with the outcome: open a guide, prepare prerequisites, follow the steps and verify the success signals.

01 Create an architecture project and render an AGL diagramThe textual model validates and reproducibly generates a diagram.
Audience
Architect
Outcome
The textual model validates and reproducibly generates a diagram.

Before you start

  • Workspace
  • Architecture scope
  • Identifier convention

Steps

  1. Create a projectSelect Enterprise/Solution/System/Software level and repository path.
  2. Add an AGL modelDefine actors, systems, containers/components and relations with stable ids.
  3. Run validationFix unresolved references, duplicate ids and invalid dependencies.
  4. Generate a viewSelect viewpoint/layout, review labels and keep the source beside the artifact.
Verify the result

Regeneration from the commit produces the same structure without manual diagram edits.

If it does not work

If layout is unstable, pin viewpoint/ordering instead of editing only the export.

02 Review architecture and export artifactsComments link to model elements and exports carry current version/provenance.
Audience
Architecture board
Outcome
Comments link to model elements and exports carry current version/provenance.

Before you start

  • Validated AGL project
  • Reviewers and decision criteria
  • Target export formats

Steps

  1. Create a review snapshotPin commit/model version and the review views.
  2. Collect commentsAttach feedback to element ids/relations, not image coordinates.
  3. Update the modelApply decisions in AGL and ADR, then rerun validation.
  4. Export artifactsGenerate SVG/PNG/PDF plus a manifest with commit/version.
Verify the result

Export and manifest reference the same validated commit and view set.

If it does not work

If exports differ, clear generation cache and verify the pinned renderer version.

Application sections

Open detailed manual

Every application screen has a separate page with controls, safe example values, CLI/API alternatives and status-specific recovery steps.

Open detailed manual →

Role in the ecosystem

IAM.Solution implements Architecture-as-Code on top of AGL: the architecture is stored as the text model is validated and produces consistent representations. The approach connects the enterprise, solution, system and software levels without manual discrepancies between diagrams and documentation.

Workflow

  1. Describe elements, connections and views in the AGL DSL.
  2. Run parse/validation and eliminate model errors.
  3. Generate diagrams and document views.
  4. Discuss the change through diff of the source text.
  5. Use CLI, Web or MCP in the selected engineering process.

Contracts and instruments

The web application is suitable for viewing and editing, the CLI is suitable for local automation and CI, API - for integration, MCP - for architectural agents. Generated artifacts are considered derivative: the source of truth remains versioned AGL model.

Governance

Validation checks the syntax, references, and rules of the model before publication. Changes undergo the usual review with the author and history. Generative assistant may offer structure, but does not circumvent architectural limitations and does not publishes changes without explicit acceptance.

Communication with IAM

Model calls can be routed via IAM.Router, inspect via IAM.Secure and provide tools agents via IAM.Core.