62 built-in abstract business patterns, each self-contained with business parameter mapping and code templates.

These patterns cover the most common ERP development scenarios including master data, document flow, approval processes, and reporting.

1)    Each pattern has clear applicable scenario descriptions to help users choose the most suitable pattern.

2)    Pattern parameterization: each pattern adapts to different business needs through parameters without modifying template code.

3)    Pattern composition: complex business can combine multiple patterns, with auto-handling of dependencies and conflicts.

4)    Pattern extension: enterprises can register their own patterns as templates for reuse.

5)    Pattern versioning: patterns have version numbers, with backward compatibility for previously generated code.

Structured requirement input: not free text, but structured six questions plus pattern selection.

The six questions cover six key dimensions of business requirements, ensuring unambiguous requirements for reliable code generation.

Phase 0 input → Phase 1 semantic matching → Phase 2 AST to code file rendering.

The three-phase pipeline transforms structured requirements into runnable code with clear inputs and outputs at each stage.

1)    Phase 0 input: structured requirements entered via six questions plus pattern selection, generating spec files.

2)    Phase 1 matching: semantic matching of specs against 62 business patterns to select the best pattern.

3)    Phase 2 AST rendering: generates AST tree from matched pattern and parameters, renders to code files.

4)    Generated code includes Python models, XML views, CSV permissions, demo data, ready to install.

5)    Traceable rendering: each code file's generation is traceable to the corresponding requirement spec.

Generated code follows Odoo development conventions including naming, structure, and security.

Built-in quality checks ensure generated code passes syntax and convention checks automatically.

1)    Naming conventions: field names, model names, view names follow Odoo conventions.

2)    Code structure: model inheritance, view inheritance, permission definitions follow standard structure.

3)    Security permissions: auto-generates ir.model.access.csv ensuring complete permission configuration.

4)    Demo data: auto-generates demo data for testing and demonstration.

5)    Syntax check: generated code automatically passes Python syntax and XML format checks.