01
Product goal & references
Define the application outcome, users, platform target, constraints, references and acceptance criteria.
ILAIOS App Factory
From product idea to a bounded application outcome, with release authority kept explicit.
App Factory is no longer only a review-plan concept: repository evidence includes a bounded Windows-first finished-product path. That does not make Android/iOS, production signing or Store publication complete.
App Factory target lifecycle
Turn product ideas into store-ready targets without claiming Store publication before proof.
The supplied visual describes the target product lifecycle. “Store Ready” is a release-readiness target, not evidence that signing, submission, certification or live installation has already occurred.
Target lifecycle: prompt + references → product/UX spec → architecture → build → test & verify → platform packaging → Store readiness. Current mobile/Store completion remains evidence-gated.
Current reality + target truth
Windows evidence is current reality. Mobile Store release remains target work.
This separation prevents the target architecture from being presented as production completion.
02
Product & UX specification
Turn the goal into bounded user flows, screen structure, interaction direction, data needs and reviewable requirements.
03
Architecture & scope
Resolve the minimum architecture, protected roots, permissions, data/auth boundaries and build/test plan before implementation.
04
Governed implementation
Implementation proceeds only inside admitted scope. Existing Core, policy, approval, tool and evidence authorities remain unchanged.
05
Build, test & verify
Run the required format/analyze/test/build/package checks and retain exact source-to-artifact evidence for the bounded platform path.
06
Windows-first finished product
The current repository evidence includes a bounded generated Flutter Windows application that was built, packaged and smoke-tested with content-addressed evidence.
07
Mobile & Store gates
Android/iOS execution, production signing, App Store/Play Store submission, certification and live install remain separate evidence-gated release work.
08
Delivery & acceptance record
Record test results, artifact identity, approvals and delivery evidence for each completed platform scope; do not mark unproven publication or installation as complete.
Release boundary
Build evidence does not silently grant signing, Store submission or publication authority.
Those actions require their own credentials, approvals, exact artifact identity, platform checks and external evidence.