Product Requirements Document

Agentic AI Development Stack & CSS Strategy (Battalion Build)

Version: 1.0
Date: 2026-06-24

1. Executive Context & System Overview

Dual Nature of "MX Build"

Architectural precision is required to distinguish between two technically distinct but unified systems in this environment:

Mission Directive

The core objective is to transition Battalion Build to an open-source, agentic development architecture. This system will automate construction financial workflows, grounded in proven business impact.

Business Justification: Field deployments (e.g., Epic Wood Work) have demonstrated that this architecture can reject over $10,000 in unauthorized or incorrect transactions within a single month, protecting corporate liquidity before funds exit the account.

Target Audience & Operational Environment

2. The Agentic AI Development Stack

Primary Development Agent (Claude Code)

Claude Code is the lead orchestrator for application modeling. It interacts with the model via mxcli to scaffold the environment and perform headless modifications.

Agentic Configuration Files

Architectural compliance requires the following mandatory configuration files:

Mandatory Skill Pattern: Agents must utilize the "standard HVAC tax logic" pattern for all mechanical trade financial modules.

The Modeling Language (MDL)

Mendix Definition Language (MDL) serves as the textual interface for Claude Code. This allows the agent to edit visual microflows, pages, and domain models directly as text, bypassing the Studio Pro graphical interface to enable high-velocity iteration.

Operational AI Integration (Gemini)

Gemini powers front-end operational features (e.g., real-time user-facing assistants), keeping operational AI separate from the development-focused modeling handled by Claude Code.

3. Open-Source CI/CD Architecture (GitHub Actions)

Transition Framework

We are migrating from Tekton-based Kubernetes pipelines to a streamlined GitHub Actions architecture to centralize agentic deployment workflows.

Headless Compilation via MxBuild

MxBuild must be executed via command line with the following flags for the GitHub Actions runner:

Environment Virtualization

The CI/CD pipeline utilizes Dev Containers for isolation. Prerequisites:

Diagnostic Mapping

The following exit codes are the only valid schemas for the MxBuild compiler. All other codes must be treated as system exceptions.

4. CSS and UI Styling Strategy: Mendix Atlas UI

Atlas UI Framework Integration

Agents must interact with the Mendix Atlas UI framework to maintain visual standardization across the Battalion Build ecosystem.

Styling Protocols for AI Agents

Visual Constraints

Structural integrity of the Layout Grid must be maintained. The sum of individual column weights ($W_i$) within a single row must exactly equal 12:

$\sum_{i=1}^{n} W_i = 12$

5. Construction-Specific Financial Logic & Workflows

Financial Automation Engine

The agent must implement the "Proposal-to-Payment" lifecycle across five phases:

Gross Margin Protected Calculations

AI agents must implement domain model logic to protect Project Gross Margin ($M_g$) using the following formula:

$M_g = \frac{R_p - (C_m + C_l + C_s)}{R_p}$

Spend Control Integration

The agent must configure AI-powered transaction classification. Incoming MX Build Card expenses must be matched directly against project cost codes to prevent unauthorized overhead leakage.

6. Technical Guardrails & Performance Optimization

Microflow & Loop Efficiency

Architectural "Don'ts" for agentic logic:

Domain Model Optimization

7. Implementation Roadmap & Diagnostic Protocols

Scaffolding Phase

Environment initialization begins with mxcli init. This scaffolds the local workspace and populates the .devcontainer and AI context files.

Troubleshooting Environment Obstacles

Validation Benchmarks

The Best Practice Recommender is the final automated gate. No agent-generated modification shall be merged until it passes a scan for architectural anti-patterns and performance risks.