A trader describes a futures strategy in plain English, the engine replays it over history, and every figure can be traced and reproduced. Start here for what is decided, what is still open, and where everything lives.
LRBO3 is the holding-company name of a new Chicago brokerage; the final company name is not decided. They plan a mobile-first brokerage for futures, perpetuals, prediction markets, options and digital assets, set apart by AI features. They will be regulated, so every AI step has to be explainable to a regulator.
Existing tools such as AskFutures ask confusing questions and return results for a different strategy than the one asked. The client wants to beat them on getting the ask right, and to prove an auditable agent framework on a small product before building more on it.
The AI only translates the ask into a strategy. No number on screen comes from the model.
What was decided before kick-off, who decided it and where it is recorded. 16 entries come from the client's written brief.
Scope, breakdown and hours. The client's Phase 1 brief and the intro call transcript are attached to it. Developers and designers can review the estimation as cards on the Povio board (LATB), the next card to the right.
The work breakdown as cards, imported from the estimate on 17 Nov. Hours only. No assignees or scheduled starts yet.
The clickable prototype shown to the client on 13 Nov. The chat is scripted and has no LLM behind it, so typed text is ignored.
Nothing here is decided. Internal questions are for the 18 Nov kick-off; client questions go to the client kick-off.
| Line | Hours | Basis |
|---|---|---|
| Hours spent | not known | No Manage project exists yet, so nothing is logged against LRBO3. Prototype and sales hours are not counted. |
| Hours projected: build | 240 | Estimate, task-based: Engineer 124, QA 38, PM 31, SA 31, DevOps 16. Not yet logged. |
| Hours projected: prompt optimization | 120 | Estimate, time and materials: 12 weeks at 8 h Engineer and 2 h QA per week. Not yet logged. |
| Hours projected: UI design | no number | Offered as an add-on; no hours in the estimate. Left out of the total. |
| Projected total | 360 | Equal to the estimate baseline of 360 h. Design comes on top once it has a number. |