Clean Code Rules
Purpose
This page defines the AIC standard for clean code rules.
The standard is designed for secure, maintainable and repeatable delivery across high-assurance, enterprise and government-facing projects.
AIC Position
AIC teams MUST apply this guidance unless a project-specific exception is approved and recorded.
The default position is:
use supported .NET platforms
keep design simple and explicit
automate checks where possible
retain evidence for material decisions
protect customer data and AIC IP
test behaviours rather than implementation details
design for secure operation and handover
Required Practices
Define ownership for this area at project start.
Record material decisions in an ADR or project decision log.
Include relevant checks in the pull request process.
Include relevant checks in CI where automation is practical.
Include security and operational considerations before release.
Review exceptions during delivery governance.
Implementation Guidance
When applying this standard, teams should consider:
the customer environment
classification and data sensitivity
expected service life
operational support model
integration dependencies
testing strategy
release and rollback model
maintainability by future teams
reuse potential for AIC accelerators
evidence required for assurance
Quality Gate
Before release or handover, confirm:
the approach is documented
the implementation follows AIC architecture boundaries
automated tests cover expected behaviours
error and edge cases are handled
security impact is understood
logging and diagnostics are adequate
deployment impact is understood
exceptions are recorded
Evidence
Retain evidence such as:
code review record
automated test results
analyzer or inspection reports
architecture decision records
screenshots or API examples where relevant
release notes
security review notes
operational runbook updates
Checklist
Was this helpful?