1. Suitable Engineer Profile (Please confirm you match before applying)
This project is only suitable for individuals or teams who simultaneously have the following capabilities: backend engineering ability (automation / workflow / API / task scheduling / state machine); AI integration and engineering experience (not just calling APIs); Web 3D integration ability (Three.js / WebGL / Unity Web, etc.), and the ability to correctly connect the 3D layer as a guidance and presentation layer to the backend system; frontend–backend collaboration capability; acceptance of staged delivery + acceptance + escrow fund rules; ability to quote based on real engineering workload. We do not accept engineers who only do backend and do not understand 3D, only do 3D and do not understand system engineering, only build normal websites, quote by the hour, or refuse staged acceptance.
2. Project Description
We have already defined a strict and reasonable Engineering Implementation Plan. No changes by the engineer are required; the work is to be constructed and assembled on the fly.io platform. What we are building is not a normal website, but a comprehensive service platform centered on automation and AI. The final goal of the platform is to achieve long-term stable unattended operation with as little human involvement as possible. The platform will gradually implement the following capabilities: automatic promotion, automatic publishing, automatic decision-making, automatic prompting, automatic alerting, automatic upgrading, and module-level automatic backup. Our core principle is: any problem that can be solved by automation and AI should not require human participation.
It must be clearly stated that this is not a one-off website project, but a replicable automated platform prototype. Once the first platform runs stably according to the defined logic, structure, and functions, we will immediately launch the construction of another 5–8 professional platforms under the same logic, architecture, and module boundaries. All subsequent platforms will be built by replicating and extending the core architecture and module system of this project, not by redesigning from scratch. Therefore, the engineering goal of this project is not just to “build one platform,” but to create a reusable, replicable, and long-term expandable base platform core. This is also the fundamental reason why we must adopt strict acceptance, independent stages, escrow funds, and a no-acceptance-no-payment mechanism in the first two stages.
3. 3D Digital Humans as the Guidance and Presentation Layer Core (Not a Logic Driver)
The biggest difference between this platform and ordinary platforms is that we introduce 3D digital humans and AI as guidance and assistance capabilities, but all business logic, state control, automation workflows, and decision-making are completed in the backend. The 3D layer does not participate in any system driving. 3D digital humans will only be used for user reception and guidance, advertising and content display, and result explanation and interaction feedback. The goal is to improve user retention time, revisit rates, and overall conversion efficiency. For us, the 3D digital human is not a logic driver module, but the core component of the guidance and presentation layer. Therefore, this project must have real, production-grade Web 3D integration capability and be correctly connected with the backend state machine and workflow system, but the 3D layer itself does not undertake any business driving or state decision responsibilities.
4. The Role of AI in Backend Workflows
In the backend system, we will extensively use AI to handle workflow processing, content generation, promotion strategy execution, anomaly detection, prompting and alerting, system upgrading, and module backup. All automation logic, judgment logic, and execution logic are completed in the backend. AI is a part of the backend workflow system. The goal is not “semi-automation,” but a clear evolution toward a fully automated, unattended platform. This is an engineering direction, not a gimmick.
5. Engineering Implementation Approach (Three Stages)
5.1 Stage One: Prototype Stage
This stage is used to verify core feasibility, automation logic, backend state machine and workflows, AI integration methods, and the integration method of 3D digital humans as a guidance and presentation layer. The planned schedule is 12 days of development plus about 3 days of fixes, with a maximum of around 15 days. The prototype stage is an independent stage. If it does not pass acceptance, the escrow funds for this stage will not be released and the project may be terminated directly.
5.2 Stage Two: Trial-Run Version
This stage verifies stability, defects and boundary issues, automation reliability, and the stability of collaboration between the backend and the 3D guidance layer in a real environment. The planned schedule is about 15–20 days. This stage is also an independent stage. If it does not pass acceptance, the escrow funds for this stage will not be released and the project may be terminated directly.
5.3 Stage Three: Full Delivery
After the first two stages pass acceptance, the system will be gradually pushed toward stable unattended operation. From project start to final delivery, the target overall timeline is about 2 to 2.5 months. Ten percent (10%) of the third-stage payment will be withheld and paid three months after delivery. The engineer must provide three months of free maintenance and adjustment. After that, ongoing maintenance will be provided at USD 100 per month.
6. Quotation and Fund Rules (Must Be Accepted)
We do not provide any internal budget. Engineers must provide a fixed total price quotation (hourly billing is not accepted) based on actual engineering workload, technical complexity, number of modules, and the execution boundaries and materials provided. The quotation must clearly list: 1) total project price; 2) prototype stage price + prototype stage timeline; 3) trial-run stage price + trial-run stage timeline; 4) final delivery stage price + final delivery stage timeline; 5) total project timeline.
7. Escrow and Acceptance Rules
All project funds will be placed into platform escrow. Funds for each stage will be released only after that stage passes acceptance. If the prototype stage does not pass, no payment will be made. If the trial-run stage does not pass, no payment will be made. Only after the trial-run version passes acceptance will we enter the third stage.
8. Important Statement (For Filtering Unqualified Engineers)
We will evaluate your quotation and timeline to determine whether you are a pragmatic engineer who quotes based on real engineering workload, rather than someone who arbitrarily inflates prices or proposes unrealistic schedules. If the quotation is obviously inflated or the timeline is obviously unrealistic, we will terminate communication directly.
9. Closing
If you believe the above positioning, boundaries, stages, acceptance rules, and fund rules are reasonable, please provide: 1) total project price; 2) prototype stage price + timeline; 3) trial-run stage price + timeline; 4) final delivery stage price + timeline; 5) total project timeline. If the quotation or timeline is clearly unrealistic, we will terminate communication directly.
