Technical Workflows

Validated technical workflows share one contract:

POST /v1/history/{session_id}/actions/{action}

The route requires an existing Technical Session and one supported action identifier. It accepts no request body and does not execute code, deployments, security scans, migrations, incident actions, or other external changes. It prepares and persists validated guidance.

Workflow catalog

Action	Purpose	Analysis used
`architecture_review`	Review component boundaries and architecture context.	Architecture
`implementation_plan`	Prepare a canonical implementation package.	Architecture, code
`code_review`	Review supplied code context and security concerns.	Code, security
`deployment_readiness`	Evaluate release and production readiness.	Infrastructure, operational, security
`validation_checklist`	Prepare checks for supplied technical work.	Code, infrastructure
`scenario_validation`	Evaluate a proposed scenario and operational effects.	Architecture, operational
`technical_decision_review`	Review a technical decision or ADR context.	Architecture, infrastructure
`infrastructure_review`	Review infrastructure or Terraform context.	Infrastructure, security
`troubleshooting`	Prepare a bounded troubleshooting analysis.	Code, infrastructure, operational
`migration_guide`	Prepare migration or upgrade guidance.	Architecture, code, infrastructure
`runbook`	Prepare operational runbook guidance.	Operational, infrastructure
`operational_review`	Review monitoring, recovery, ownership, and operations.	Operational
`production_review`	Review production context and readiness.	Operational, infrastructure, security
`incident_review`	Review incident or postmortem context.	Operational, security
`security_review`	Review supplied security context conservatively.	Security

Run a workflow

curl --request POST \
  "$IVORLEAF_API_BASE_URL/v1/history/$SESSION_ID/actions/deployment_readiness" \
  --header "Authorization: Bearer $IVORLEAF_API_KEY"

All workflows use the Technical Session's saved objective and evidence. The source-derived packet includes technical analysis, recommendations, risks, validation summary, sources, a revision_id, and an artifact. implementation_plan returns the canonical implementation-package structure instead.

Review and blocking

Workflow validation_summary.human_review_recommended is derived from the canonical package's validation.human_review_required. Inspect it before allowing downstream automation. Prepared artifacts are guidance; this endpoint does not apply changes to external systems.

See Generate Artifacts and Validation Responses.