AI App Builder And GitHub Publisher

Status

Future architecture only. No GitHub publishing workflow is implemented in the current task.

Role

AI App Builder turns confirmed OS Artifacts into app specs and later code. GitHub Publisher is the future integration boundary that creates branches, opens pull requests, and links deploy previews after explicit user approval.

Proposed Flow

1. Alma generates or receives an OS Artifact.
2. User pins it to a workspace.
3. User chooses Promote to App.
4. AI creates an app spec with manifest, route, UI, data, and permission notes.
5. User approves repository or branch creation.
6. Builder writes files in a controlled scaffold.
7. Publisher opens a pull request.
8. CI and deploy preview run.
9. User confirms app registry installation.
10. Audit log records each step and rollback hint.

Default Branch Policy

The default path should be pull request. AI should not mutate production or main branch directly.

Controlled Scaffold

Generated app code should use existing package taxonomy:

• reusable official app candidates under packages/apps/system-apps
• shell-only control surfaces under apps/os-shell
• implementation-neutral protocol under @prox-os/app-contract
• static iframe templates under @prox-os/app-registry

Future Backend Services

Future apps/api-worker may coordinate:

• GitHub authorization checks
• app spec storage
• artifact storage
• audit sink
• permission policy engine
• publish job status

It should not expose secrets to model context.

Non-goals Now

• No repository creation.
• No branch creation.
• No file-writing backend worker.
• No pull request automation.
• No deploy preview integration.
• No app registry auto-install.