Modules

Overview

The EAC module system provides independently buildable, testable units with explicit contracts, dependency management, and file ownership.

Key concepts:

• Modules - Independently buildable units with explicit identity and dependencies
• Components - Typed components within modules (go, typescript, dockerfile, etc.)
• Dependencies - Explicit declaration enables topological build ordering
• File Ownership - Each file claimed by exactly one module via glob patterns

Module definition (.eac/repository.yml):

modules:
  - moniker: core
    name: EAC Core Libraries
    depends_on: [logging]
    components:
      - type: go
        root: go/core

All modules are registered in .eac/repository.yml with dependencies, component types, and file ownership patterns.

Module Organization

28 modules organized into focused groups:

Core Framework

See: core.md, clibase.md

CLI Tools

See: eac.md, eac-ext.md, eac-mcp-server.md, clie-eac-bundle.md

Commands

The commands module contains 7 command components:

• base - Command infrastructure and shared utilities
• build - Build automation commands
• lint - Code quality and linting
• repository - Repository management
• scan - Security scanning
• test - Test execution
• update - Update and maintenance

Location: go/commands/

See: commands.md

Adapters

The adapters module contains 17 adapter components:

Test Frameworks: gotest, godog, mocha, pytest, behave, reqnroll, cucumber

Package Managers: npm, pip, nuget, dotnet

Infrastructure: docker, gh, ai, eac

Utilities: tui

Location: go/adapters/

See: adapters.md

Contracts

Contract schemas define interfaces between modules and external tools:

Location: contracts/

See: contracts.md

OCI Tools

Containerized development tools (12 container images):

Location: containers/

See: oci-tools.md

Supporting Modules

Key Features

Component Types

Modules contain typed components that determine build behavior:

• go - Go packages with build/test support
• typescript - TypeScript/JavaScript with npm builds
• dockerfile - Multi-platform container builds
• book - MkDocs documentation sites
• pwsh / bash - Script validation
• gherkin / structurizr - Specifications and architecture

See: Component Types Reference

Dependency Management

Modules declare dependencies via depends_on in .eac/repository.yml. Build system uses topological sort to determine build order and supports incremental builds based on change detection.

Commands:

eac show dependencies          # View dependency graph
eac validate dependencies      # Validate no cycles
eac get changed-modules-ci     # Detect changed modules

See: Architecture: Modules

File Ownership

Each file is claimed by exactly one module via glob patterns:

components:
  - type: go
    root: go/core
    patterns:
      source: ["**/*.go"]
      tests: ["**/*_test.go"]

Commands:

eac show files                 # Show file ownership
eac validate module-files      # Validate no conflicts

Module Lifecycle

1. Discovery - Load from .eac/repository.yml
2. Build - Topological build based on dependencies
3. Test - Execute test suites with tag filtering
4. Validation - Schema and dependency validation
5. Release - Version tagging and changelog generation

See: Architecture: Modules for detailed lifecycle documentation.

Architecture Diagrams

Each module includes C4 architecture diagrams in Structurizr DSL format:

eac serve design               # View all diagrams in browser
eac serve design --module core # View specific module

Design files: specs/{module}/.design/workspace.dsl

See: Viewing Architecture Diagrams

Related Documentation

• Architecture: Modules - Detailed module system architecture
• Architecture: Component Types - Component type specifications
• Architecture: Contracts - Contract system and schemas
• Commands Reference - CLI commands for working with modules
• Repository Layout - Directory structure and organization

Tutorials | How-to Guides | Explanation | Reference

You are here: Reference — information-oriented technical descriptions of the system.