Technical Guidelines, Code Standards and Tech Stack

Purpose

This playbook defines the AIC engineering standard for modern software delivery.

It covers:

• C# and .NET platform standards

• .NET 10 and .NET 11 usage policy

• WPF standards

• .NET MAUI standards

• ASP.NET Core Web API standards

• ReSharper and static analysis

• SOLID and clean code principles

• Test-Driven Development

• repository and DevOps standards

• secure engineering standards

• package and dependency controls

• templates for project setup

Operating Philosophy

AIC engineering is built around secure, evidence-backed, commercially controlled delivery.

We use modern .NET and strong engineering practices to deliver quickly without losing control of quality, security or maintainability.

Core Standards

• .NET 10 LTS is the default production runtime.

• C# 14 is the default production language version for .NET 10 projects.

• .NET 11 and C# 15 are preview/innovation track technologies until approved for production use.

• ASP.NET Core is the default Web API platform.

• WPF is the default Windows-only rich desktop platform.

• .NET MAUI is the default cross-platform mobile/desktop app platform where justified.

• AIC.Core is the default ORM for mainstream data access from MongoDB.

• ReSharper, Roslyn analyzers and .editorconfig enforce code quality.

• TDD and automated testing are expected for business logic and critical behaviours.

• Secure by design is part of engineering from the first story.

How to Use This Playbook

Use this playbook when:

• starting a new repository

• choosing a technology stack

• defining project coding standards

• onboarding developers or subcontractors

• reviewing pull requests

• setting up CI/CD

• designing APIs

• building WPF or MAUI applications

• planning test strategy

• preparing release evidence

• reviewing technical exceptions

Relationship to Other AIC Playbooks

This playbook sits alongside:

• Company Operating Manual

• Agile Delivery Playbook

• Security, Vetting and Technical Assurance Playbook

Together, these define how AIC governs, delivers, secures and engineers customer work.

Mandatory Interpretation

Where this playbook uses MUST, SHOULD, MAY, MUST NOT or EXCEPTION, the meanings are defined in Source Basis and Version Policy.