policyengine-code-organization

Code organization for PolicyEngine establishes naming conventions, folder structures, and file layouts tailored to state and federal programs. Start with a flat structure for smaller programs, then expand to modular or full hierarchical organization as complexity grows, using consistent variable prefixes and component placement to improve maintainability.

PolicyEngine naming conventions use standardized prefixes derived from official references, consistent suffixes for variable types, and component placement rules. These patterns ensure clarity across income calculations, eligibility rules, and deductions, making code reviews and refactoring more efficient.

Transition to modular structure as your PolicyEngine program grows beyond a single flat layout. Split income, eligibility, and deduction logic into separate directories when managing medium-sized programs like TANF to reduce cognitive load and scale maintainability.

Yes, PolicyEngine organization patterns adapt to state-specific terminology and program requirements. The folder and naming conventions scale from small federal programs to complex multi-state implementations while maintaining consistent structure and readability.

Flat structure keeps all files in one directory for simple programs; modular separates concerns by feature or domain; full structure adds nested layers for large, complex programs. PolicyEngine guidance helps you choose based on program size, team capacity, and long-term maintenance needs.