Preview and deliver

Preview is where generated artifacts become an executable candidate. Delivery is the explicit choice of how that candidate leaves modelARch and who operates it.

Preview is evidence

A preview should run the actual generated application or a faithful build of the same artifacts. It is not only a design mock.

Use it to verify:

• startup, health, and readiness;
• central actor journeys;
• access boundaries and rejection behavior;
• empty, loading, and error states;
• data entry and lifecycle transitions;
• integration configuration status;
• responsive behavior;
• basic performance at representative data sizes.

Preview data is disposable unless the environment explicitly says otherwise. Never infer production migration safety from a small ephemeral database alone.

Candidate isolation

The preview candidate should not receive production traffic, share production secrets, or mutate production data. Its job is to provide evidence about a specific model revision and generator version.

If the candidate fails, the active release remains unchanged. Fix the owning authority—model, generator, configuration contract, or infrastructure—and create a new candidate.

Delivery channels

modelARch supports different ownership outcomes:

• Download/export: receive a portable package for inspection or independent operation.
• Source handoff: publish generated artifacts into a source-control workflow you own.
• Managed deployment: let the release orchestrator build, verify, and promote the candidate on managed infrastructure.

Availability may depend on target and workspace configuration. Each channel should identify exactly what is handed off: model revision, generated source, evolution bundle, environment manifest, and evidence.

Before delivery

Use this checklist:

• the model revision is immutable and identified;
• blocking validation findings are zero;
• generated source compiles and tests pass;
• required environment variables are declared but secret values are absent from artifacts;
• migration plan and compatibility assumptions are reviewed;
• health, readiness, and smoke checks pass;
• rollback compatibility is known;
• the destination and ownership boundary are explicit.

After delivery

Managed delivery records which release receives traffic. Exported delivery transfers operations to you. In both cases, the model revision remains the explanation of product intent. If exported code is later edited as the primary source, that copy becomes an explicit fork, not silently “still regenerative.”

See Delivery channels and Managed deployment for operational detail.