- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
This paper focuses on LEGO model generation, aiming to generate LEGO models and corresponding step-by-step assembly instructions from natural language requests. The proposed DailyBrick organizes the LEGO generation task into structured stages with intermediate outputs and feedback. It utilizes a Planner–Designer–Critic workflow to enable iterative refinement of the generated results. The experimental results demonstrate the effectiveness of DailyBrick.
Critical strengths
- The task of generating LEGO models and corresponding step-by-step assembly instructions from natural language requests is interesting.
- The design of the Planner–Designer–Critic workflow is reasonable.
- The experimental results demonstrate the effectiveness of the proposed DailyBrick.
Critical weaknesses
- As mentioned in Lines 97–106, decomposing long-context generation into structured stages and performing iterative refinement is a common practice in agent workflows. I am curious about whether DailyBrick introduces any task-specific designs for LEGO generation.
- In Table 4, adding the Meta-Reviewer improves performance. However, I wonder whether this improvement stems from the design of the Meta-Reviewer or simply from having an additional round of corrective refinement. I suggest adding a comparison between the Meta-Reviewer and a baseline with one additional round of correction and retry. Such a comparison would provide stronger evidence for the effectiveness of the Meta-Reviewer.
Questions for authors
What task-specific designs does DailyBrick introduce for LEGO generation?
3 comments
offical Response to Reviewer hVcZ
Weakness 2: Meta-Reviewer versus an additional correction round
Reviewer Comment:
In Table 4, adding the Meta-Reviewer improves performance. However, I wonder whether this improvement stems from the design of the Meta-Reviewer or simply from having an additional round of corrective refinement. I suggest adding a comparison between the Meta-Reviewer and a baseline with one additional round of correction and retry. Such a comparison would provide stronger evidence for the effectiveness of the Meta-Reviewer.
Response:
Thank you for this suggestion. We agree that the cumulative comparison in Table 4 does not rule out the possibility that part of the gain comes from an additional opportunity to revise. We compare an ordinary correction round with Meta-Reviewer-guided targeted repair, using the same configuration. With the same allowed correction opportunities and resource ceilings, Meta-Reviewer-guided repair achieves better performance on final acceptance, compared with providing another round of correction.
Table R1. Meta-Reviewer and additional correction-round ablation.
| DailyBrick | Valid (%) | Stable (%) | CLIP | DINOv2 | P_inv | VQAScore | PE | SigLIP2 | Replay exact (%) | All-prefix pass | Failure pos. | Accept | Tokens/case |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| w/ an additional round | 100.0 | 99.86 | 0.339 | 0.899 | 0.049 | 0.724 | 0.360 | 0.722 | 94.8 | 0.945 | 0.956 | 0.694 | 8.167k |
| w/ Meta-Reviewer | 100.0 | 100.0 | 0.340 | 0.906 | 0.049 | 0.736 | 0.362 | 0.724 | 100.0 | 1.000 | 0.960 | 0.834 | 7.760k |
Question: What task-specific designs does DailyBrick introduce?
Reviewer Comment:
What task-specific designs does DailyBrick introduce for LEGO generation?
Response:
Thank you. The task-specific design of DailyBrick concerns translating a language request into brick placements with explicit support and connection information, while producing instructions for the same construction sequence. Accordingly, the structural blueprint specifies support layout and brick connections before the design is expressed as an assembly program (Sec. 3.1). To make these construction decisions executable, SDK calls specify brick identity, colour, pose, connector, support dependency, and insertion direction. Partial assembly skills compose these calls into reusable subpart procedures with defined interfaces and preconditions (Sec. 3.2).
To keep the generated model and instructions aligned, both are derived from the same compiled placement trace (Sec. 3). Verification also follows the construction sequence: before each placement, verify replay reconstructs the accepted partial assembly and available attachment sites, then checks pose validity, connector compatibility, and subpart assembly connections. If a placement is rejected, the Self Meta-Reviewer uses the failed action, violated constraint, last accepted state, and recorded generation dependencies to select candidate revision targets; the revised program undergoes complete replay (Sec. 3.3). Thus, the adaptation to LEGO lies in the construction information represented, the operations exposed, and the constraints checked, rather than in stage decomposition or iterative refinement alone.
Thanks for the responses. They have addressed my concerns, and I will keep my positive score.
offical Response to Reviewer hVcZ
General Comment
Thank you for your thoughtful review. We appreciate your recognition of the importance of jointly generating LEGO models and assembly instructions, and your positive assessment of the PDC workflow. Your comments help us clarify how the design is tailored to LEGO construction and how the Meta-Reviewer should be evaluated against an additional correction opportunity.
Weakness 1: Task-specific designs beyond common agent workflows
Reviewer Comment:
Response:
Thank you for raising this point. While DailyBrick builds on these general principles, its design emphasis is on adapting them to the specific requirements of LEGO construction, through task-specific intermediate representations, executable brick operations, and verification and repair mechanisms for jointly generating brick models and their assembly instructions. The distinction therefore lies not in staging or refinement alone, but in how these mechanisms address the constraints of the LEGO task, as detailed below.
1. A language description specifies an object, but not its brick-level support and connection structure. For example, asking for a house does not specify how its walls support the roof or how the subassemblies attach. These choices are coupled: visually plausible subparts do not necessarily form a compatible brick assembly. This motivates separating semantic design from structural planning before generating placements. Our structural blueprint explicitly represents support layout and brick connections, while partial assembly skills give subparts defined interfaces and preconditions rather than treating them as independent shapes (Secs. 3.1-3.2).
2. Visual proximity is not sufficient for a legal LEGO connection. Two parts can appear to touch while their connectors are incompatible or incorrectly oriented. Part identity, pose, connection choice, and placement dependencies therefore cannot be left as an informal geometric description. This motivates the brick-level SDK, whose operations explicitly specify brick ID, pose, connector, support dependency, and insertion direction. The purpose is to expose the construction decisions needed for executable placements, rather than simply providing a generic code-generation tool (Sec. 3.2).
3. A final arrangement does not determine a valid construction order or a faithful instruction sequence. A proposed placement may depend on a supporting part or attachment site that has not yet been introduced. Checking only the completed model cannot establish whether that step was valid when it occurred. This motivates replay over successive partial assemblies and their available attachment sites. Moreover, independently written instructions could describe a different order or placement from the generated model. We therefore derive both the model and instruction views from the same compiled placement trace, coupling instruction generation to the construction process being checked (Secs. 3 and 3.3).
4. The location of a rejected brick is not necessarily the location of the underlying error. An incompatible attachment may reflect an earlier blueprint decision, a subassembly interface, or its expansion into SDK operations, rather than only the latest placement. This motivates retaining dependencies across these levels and using the violated construction constraint to identify candidate revision targets. The Self Meta-Reviewer can therefore direct revision toward the relevant construction decision instead of treating every failure as a request to regenerate the last output. A revised program must still undergo complete replay (Sec. 3.3).
Thus, the task-specific contribution is not the use of staged generation or iterative refinement in isolation, but their realization through brick-level construction representations, executable connection-aware operations, a shared model–instruction trace, and replay-grounded revision targets.