Artifact To App Pipeline

Status

This is future architecture. It is not implemented in the current task.

The current Alma can create local mock artifacts and pin them in prototype state. It does not create repositories, write production code, open pull requests, deploy previews, or register generated apps automatically.

Goal

The long-term route is:

AI generates dashboard -> user confirms -> dashboard becomes OS Artifact ->
user promotes it to App -> Prox OS creates branch or repository -> writes UI
code -> opens PR and deploy preview -> registers app into App Registry

Stage 1: Generate Artifact

Alma creates a dashboard, table, timeline, checklist, summary, report preview, or workspace note inside Prox OS.

The first implementation should start with local artifacts and exportable specs. It should not start by writing repositories.

Stage 2: Pin To Workspace

The user pins the artifact to a workspace. Pinning should be reversible and visible in operation logs.

Stage 3: Promote To App

The user chooses to turn the artifact into a real app. This requires explicit confirmation because it changes the artifact from local workspace object into a software object.

Stage 4: Generate App Spec

AI creates:

• app manifest
• route plan
• UI spec
• data requirements
• permission requirements
• artifact output contract
• rollback notes

Stage 5: Create Git Branch Or Repository

Future GitHub integration can create a branch or repository only after explicit authorization. The default path should be branch and pull request, not direct main branch mutation.

Stage 6: Write Files

Future agent writes UI files into a controlled scaffold. The file plan should be reviewed before execution. Generated files must follow package boundaries and repository language rules.

Stage 7: Open Pull Request

Default publication path is a pull request. The PR should include:

• generated app spec
• files changed
• validation commands
• screenshots or previews when visual
• rollback notes

Stage 8: CI And Deploy Preview

Checks and preview run before acceptance. Failed checks should stop automatic registration.

Stage 9: Register In App Registry

The user confirms installation into Prox OS. Registry updates must preserve the app manifest contract and route group rules.

Stage 10: Audit And Rollback

Every step should be logged. Rollback should be available where possible:

• unpin artifact
• remove generated branch
• close PR
• unregister app
• restore previous workspace layout

Safety Rules

• AI should not directly write to production by default.
• User confirmation and permissions are required.
• API keys and secrets must never be exposed to model context.
• External writes require high-impact confirmation.
• First implementation should export specs before automatic repository creation.