Skip to main content

​
Application Delivery Overview

​
Audience

This page is for developers, platform maintainers, and delivery teams shipping applications into AiOS.

​
Goal and Scope

This page explains:
  1. how all delivery inputs normalize into AppSpec
  2. the boundary and failure rules of Compose import
  3. how deployment lifecycle integrates with tasks, approval, and audit

​
Core Concepts

  • all delivery inputs normalize into AppSpec
  • Compose uses a restricted import strategy, not full compatibility
  • production deployments and rollbacks are approval-gated by default

​
Standard Workflow

  1. choose an input source (Git / Compose / Image)
  2. parse and normalize into AppSpec
  3. execute Render / Apply / HealthCheck
  4. write task, audit, and deployment records

​
Current Control-Plane API Freeze

The currently frozen /api/v1/compose/import surface is a preflight/reporting entrypoint, not the full delivery pipeline.

​
Planned CLI Examples (Not Yet Implemented)

The repository does not currently ship these CLI subcommands. The currently frozen and implemented surfaces are control-plane HTTP APIs such as /api/v1/compose/import.

​
Web UI Path

  • application creation wizard
  • Compose import report
  • deployment history and rollback entrypoints

​
Pitfalls / Risk Notes

  • build is blocked in Compose v1; do not assume automatic image builds exist.
  • production deployment and rollback are not special paths that bypass approval.