Code Factory is HEPO's tooling for defining and generating module and capability artifacts. It brings together manifests, model and interface definitions, configuration, and supported generation commands. Implementers use it to produce repeatable platform structures and examine the result through an authoring surface.

The aim is to reduce repeated construction work. The generated output still needs to satisfy the business requirement and pass the relevant integration and release checks.

Start with the definition

A new capability needs a clear record model, fields, permitted operations, presentation, and any specialised rules. The factory's definition and manifest surfaces organise those concerns so supported generators can use them consistently.

Module definitions, capability definitions, models, forms, rules, widgets, features, and dashboard configuration each describe part of that structure. Their relationships matter: a form depends on the intended model and operations, while a displayed capability needs the appropriate registration and navigation.

Follow the generation path

The authoring surface can invoke supported commands without manually entering them in a development terminal. Generation still runs through an installed toolchain and supported environment. Custom business behaviour, deployment, and verification may require engineering work; a completed generator command is not a production acceptance result.

Choose generation when configuration is insufficient

Common Canvas arranges existing views. Shared Module renders supported data surfaces from configuration. Code Factory works at the artifact level when a module or capability needs further structure.

That preserves the original progression from views to data surfaces to modules. The organisation owns the requirement and definitions; the platform supplies reusable patterns and tooling. The choice depends on what the required behaviour actually needs.

Review what the generated capability inherits

Shared patterns provide a route into common interfaces, process registration, and relationships. Permissions, validation, audit coverage, and data handling must still be checked in the generated and integrated result. The generator cannot establish the correctness of a business rule solely from its presence in a definition.

Implementers walk the organisation's technical team through a representative capability, including a preview, the resulting artifacts, a validation failure, and the release checks. Consultants and business owners confirm that the completed behaviour serves the intended work.

Scalability places this extension path in the wider growth model.

System Layer | Platform overview