Architecture·production

IAM.Solution / AGL

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

Landing Application
IAM.Solution / AGL interface
Current public IAM.Solution / AGL surface. The screenshot was verified when the documentation was published.

Key capabilities

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

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.