What is Intent Architect?

​

The Problem Intent Architect Solves

• Repetitive boilerplate code that takes time to write and maintain
• Inconsistencies across the codebase as teams grow
• Technical debt accumulating from copy-paste coding
• Synchronization issues between documentation, models, and code
• Knowledge silos where patterns exist only in senior developers’ minds
• Slow onboarding for new team members learning the codebase

​

How Intent Architect Works

​

Key Concepts

​

Models, Not Scaffolding

• Code is regenerated to reflect changes
• New patterns are automatically applied
• Relationships are maintained consistently
• Validation and constraints are enforced

​

Modules: Packaged Patterns

• Templates: Code generation templates for specific artifacts
• Factory Extensions: Hooks into the generation pipeline
• Modelers: Visual designer extensions
• Metadata: Stereotypes and additional modeling capabilities

<!-- Example: Intent.Application.MediatR module spec -->
<package>
  <id>Intent.Application.MediatR</id>
  <version>4.5.4</version>
  <summary>Provides the MediatR middleware</summary>
  <templates>
    <template id="Intent.Application.MediatR.CommandHandler">
      <role>Application.Command.Handler</role>
    </template>
    <template id="Intent.Application.MediatR.QueryHandler">
      <role>Application.Query.Handler</role>
    </template>
  </templates>
  <dependencies>
    <dependency id="Intent.Common.CSharp" version="3.9.4" />
    <dependency id="Intent.Modelers.Services.CQRS" version="4.1.1" />
  </dependencies>
</package>

​

The Software Factory

1. Reads your models from visual designers
2. Loads installed modules and their templates
3. Executes templates against your models
4. Manages generated files and preserves custom code
5. Integrates with your version control system

​

Code Management

• Generated regions: Completely managed by Intent Architect
• Protected regions: For your custom code that won’t be overwritten
• Partial classes: Extend generated classes without modification
• Extension methods: Add functionality without touching generated code

// Generated by Intent Architect
public partial class Customer
{
    public Guid Id { get; set; }
    
    public string Name { get; set; }
    
    public string Email { get; set; }
}

// Your custom code in a separate file
public partial class Customer
{
    public string GetDisplayName()
    {
        return $"{Name} ({Email})";
    }
}

​

Architecture Patterns Supported

​

Clean Architecture

​

CQRS (Command Query Responsibility Segregation)

// Command - represents an action
public class CreateOrderCommand : IRequest<Guid>
{
    public Guid CustomerId { get; set; }
    public List<OrderItemDto> Items { get; set; }
}

// Command Handler - executes the action
public class CreateOrderCommandHandler : IRequestHandler<CreateOrderCommand, Guid>
{
    private readonly IRepository<Order> _orderRepository;
    
    public async Task<Guid> Handle(CreateOrderCommand request, CancellationToken cancellationToken)
    {
        // Business logic here
    }
}

// Query - retrieves data
public class GetOrderByIdQuery : IRequest<OrderDto>
{
    public Guid OrderId { get; set; }
}

// Query Handler - retrieves the data
public class GetOrderByIdQueryHandler : IRequestHandler<GetOrderByIdQuery, OrderDto>
{
    // Query logic here
}

​

Domain-Driven Design (DDD)

• Entities with identity
• Value Objects without identity
• Aggregates as consistency boundaries
• Domain Events for communication
• Domain Services for complex operations
• Repositories for aggregate persistence

​

Event-Driven Architecture

• Message Publishing: Intent.Eventing.MassTransit, Intent.Eventing.AzureServiceBus
• Message Handling: Automatic subscriber generation
• Saga Orchestration: Long-running business processes
• Outbox Pattern: Reliable message delivery

​

Benefits

​

What Intent Architect Is Not

• Not a black box: All generated code is visible, readable, and maintainable
• Not prescriptive: Choose your architecture, patterns, and technologies
• Not a framework: Uses standard .NET libraries and frameworks
• Not a vendor lock-in: Generated code has no runtime dependency on Intent Architect

​

Integration with Development Workflow

• Version Control: Generated code commits to Git like any other code
• Visual Studio / Rider: Edit generated and custom code side-by-side
• CI/CD: Build pipelines work unchanged
• Team Collaboration: Models can be shared and merged
• Code Reviews: Review generated code changes in pull requests

​

Real-World Usage

• Enterprise web applications
• Microservices architectures
• Event-driven systems
• Serverless applications
• Mobile backends
• IoT platforms
• Financial services applications
• Healthcare systems

​

Next Steps

​

Learn More

• Official Intent Architect Website
• Intent Architect Documentation
• Support & Community