Refinement¶

Refinement is how Mozaiks changes an app after the first build.

Initial generation creates the app. Refinement keeps it alive and editable. When a user asks for a change, Mozaiks classifies the request and then chooses the smallest safe next step.

The Four Change Classes¶

Mozaiks classifies every refinement request as one of four classes:

• patch - a small, localized fix
• design - a visual or structural change without a new capability
• feature - a new capability within the same product direction
• core - a concept-level pivot

What Each Class Means¶

• patch usually means a scoped code edit against the affected files only
• design usually means regenerating page or layout surfaces while keeping the backend intact
• feature usually means re-entering a workflow sequence with updated planning context
• core usually means restarting from concept and value planning

Why This Matters¶

The point of refinement is to avoid doing more work than the change requires. Mozaiks preserves the current build state, targets the relevant surfaces, and keeps the rest of the app stable.

For the full runtime behavior, see Refinement Control Plane.