Flow: HTTP Service Packaging
This doc contains the step-by-step flow. For inputs, tools, outputs, and safety, see /.system/skills/ssot/repo/scaffolding/devops-packaging-service/SKILL.md.
Step-by-Step Flow (AI + Human)
Step 1: Collect Parameters (AI -> Human)
AI asks human for:
- Service name for the image
- Which module to package
- Service port
- Optional: base image, registry URL
Human checkpoint: Confirm parameters before proceeding.
Step 2: Validate Inputs (AI)
AI validates:
- Module exists and has source code
- Service name follows naming conventions
- Port is valid
Step 3: Preview Changes (AI)
AI runs orchestrator with --dry-run:
python scripts/devops/scaffold/devops_packaging_service.py --service-name "<service_name>" --module-id "<module_id>" --port 8080 --dry-run
AI presents planned_changes to human.
Human checkpoint: Review and approve planned changes.
Step 4: Execute Scaffold (AI)
AI runs orchestrator without --dry-run:
python scripts/devops/scaffold/devops_packaging_service.py --service-name "<service_name>" --module-id "<module_id>" --port 8080
Step 5: Review Generated Files (AI + Human)
AI presents generated files for review:
- Dockerfile
- Build script
- Packaging configuration
Human checkpoint: Review generated files and customize if needed.
Step 6: Record in Workdocs (AI)
AI records scaffold execution in /ops/packaging/workdocs/:
- Service name and module
- Configuration decisions
- Follow-up tasks (build, push, deploy)
Converted and distributed by TomeVault — claim your Tome and manage your conversions.