Specify
Define the requested outcome, repository or system boundary, constraints, acceptance criteria, risk, and required evidence.
Software Factory is the ILAIOS capability direction for converting software goals into governed engineering work rather than treating code generation as an unrestricted one-shot request.
ILAIOS tracks capability maturity separately from release state. This page describes the canonical product workflow and does not claim every Software Factory function is generally available today.
Define the requested outcome, repository or system boundary, constraints, acceptance criteria, risk, and required evidence.
Decompose work into bounded engineering jobs with dependencies, ownership, permissions, and a validation plan.
Use source, symbol, dependency, configuration, and runtime context where available instead of making blind edits.
Engineering capabilities modify only authorized files and systems; architecture and security boundaries remain authoritative.
Run applicable deterministic tests, lint/type/static checks, code review, and security checks before acceptance.
Material work is not accepted solely because its author or executing agent reports success. Required independent verification remains risk-driven.
Version artifacts, capture build/test/security evidence, prepare rollback or recovery semantics, and keep environment progression explicit.
Deliver source/build/deployment preparation with traceable evidence; failures follow bounded diagnose, repair, retest, retry, or rollback paths.