What you build

A modelARch project produces more than source files. Its outputs form an evidence chain from product decision to runnable release.

The Evolutionary Model

The primary artifact is the structured product model. It includes the product’s domain, actors, behavior, access rules, experience, design intent, integrations, add-ons, and infrastructure choices.

The model is versioned. Each accepted change creates a new revision related to its parent so generation can reason about evolution instead of treating every build as a disconnected first build.

Portable product contracts

modelARch emits human- and machine-readable views of the model:

• MODEL.md explains the business system: vocabulary, objects, behavior, rules, actors, access, and rationale.
• DESIGN.md describes the visual and experiential contract: brand, typography, tokens, layout, and relevant design decisions.
• Gherkin features express executable examples and rejection behavior derived from modeled actions and rules.

These files are projections, not new authoring authorities. If they are wrong, correct the model and regenerate them.

Generated backend

Depending on the selected target, the backend projection can include:

• domain entities, value objects, errors, and lifecycle rules;
• command and query handlers;
• repositories and persistence mappings;
• API routes and transport schemas;
• authentication and configured modules;
• integration adapters and callbacks;
• migrations, health checks, and runtime configuration contracts;
• automated tests.

The implementation follows a separated domain/application/infrastructure/API structure so generated responsibilities remain inspectable.

Generated experience

The React projection can include:

• actor-specific application surfaces;
• routes and navigation derived from the experience model;
• list, detail, dashboard, workflow, and specialized view patterns;
• forms and contextual actions connected to backend contracts;
• design tokens, typography, density, and component decisions;
• empty, loading, error, and permission states.

The intended invariant is preview fidelity: the preview and exported UI must consume the same decisions rather than maintain independent approximations.

Evolution and delivery artifacts

For supported evolution paths, generation also produces:

• a physical schema manifest;
• a migration chain from the parent revision;
• an evolution bundle used by the next revision;
• configuration requirements without secret values;
• build and validation evidence.

Managed delivery adds an immutable release record and deployment state. Export and source handoff provide an explicit path to own and operate the result elsewhere.

What is not generated

modelARch does not generate live customer data, secret values, current infrastructure state, or external-provider availability. It generates the contracts and adapters those authorities need.

See Generator targets, Add-ons, and Infrastructure for concrete support.