EaJPmHpiicrqMRRPODCSzr • 268:8256

806 technologies control

https://www.figma.com/design/EaJPmHpiicrqMRRPODCSzr/806-Technologies---Control?node-id=268-8256&t=j297swZdsN4Ghnan-11

not-readyneeds-fixesrender: coded

Preflight

Frame needs design cleanup before demo generation or dev handoff.

Design gate fix-first

Blocked because score 68 is below the demo threshold 85; status is not-ready, but demo generation requires ready-to-go; 1 error issue(s) exceed the allowed maximum 0.

Demo verdict: blocked

Current blocking structure issues make the demo path unreliable right now.

Score

68/100

Checked

4/21/2026, 3:47:54 PM

Recommended action

Request fixes

Demo verdict

Blocked

Demo eligibility

Blocked by strict gate

Override history

Structural absolutes

Decorative absolutes

Fixed width blocks

Fixed height blocks

Design review lanes

Responsiveness1 issue

No wrapping Auto Layout groups detected.info

Fix: Add wrap or a mobile stacking rule to these multi-item rows before handoff.

Handoff risk2 issues

Scene export is missing layout definitions, so responsive and sizing checks are low-confidence.warning

Fix: Treat this frame as fix-first until the export includes layout metadata, or re-run against a fuller scene dump before trusting the score.

Targets

Homepage v2 [268:8256]
Homepage v2 > Rectangle 13 [268:8257]
Homepage v2 > office-workers-working-together-as-team 1 [268:8258]
Homepage v2 > Frame 1597881491 [268:8259]
Homepage v2 > Frame 1597881491 > Hero - v2 [268:8260]
Homepage v2 > Frame 1597881491 > Hero - v2 > office-workers-working-together-as-team 1 [268:8261]

Root frame name "Homepage v2" does not follow the design SOP version naming convention.error

Fix: Rename the frame to the SOP format, for example: Projectname_Homepage_V1, Projectname_Homepage_V2, Projectname_About Us_V1.1.

Targets

Homepage v2 [268:8256]

Score breakdown

Start 92 → end 68. Demo threshold 85; ready-to-go threshold 85.

Responsiveness

NO_WRAP_LAYOUTS-4

No wrapping groups were detected, which increases responsive layout risk.

Handoff risk

MISSING_LAYOUT_DEFINITIONS-8

The scene export omitted layout definitions even though 226 nodes reference layout metadata, which weakens confidence in responsiveness and sizing checks.

DESIGN_SOP_FRAME_NAMING-12

Root frame naming is off-SOP ("Homepage v2"). Expected Project_Page_V1 or Project_Page_V1.1 style versioning.

Issues

Scene export is missing layout definitions, so responsive and sizing checks are low-confidence.warning

Treat this frame as fix-first until the export includes layout metadata, or re-run against a fuller scene dump before trusting the score.

Evidence: Homepage v2 [268:8256], Homepage v2 > Rectangle 13 [268:8257], Homepage v2 > office-workers-working-together-as-team 1 [268:8258], Homepage v2 > Frame 1597881491 [268:8259], Homepage v2 > Frame 1597881491 > Hero - v2 [268:8260], Homepage v2 > Frame 1597881491 > Hero - v2 > office-workers-working-together-as-team 1 [268:8261]

Root frame name "Homepage v2" does not follow the design SOP version naming convention.error

Rename the frame to the SOP format, for example: Projectname_Homepage_V1, Projectname_Homepage_V2, Projectname_About Us_V1.1.

Evidence: Homepage v2 [268:8256]

No wrapping Auto Layout groups detected.info

Add wrap or a mobile stacking rule to these multi-item rows before handoff.

Actions

Strict gate first. Parser, scene cache, and operator actions should stay visible here, not hidden behind API trivia.

Scene cache present

/app/data/scenes/806-technologies-control-268-8256.txt

65,537 bytes • updated 4/21/2026, 3:47:54 PM

Fix-first mode

This frame should stay in correction mode until the blocking design issues are fixed.

Demo verdict: blocked

Current blocking structure issues make the demo path unreliable right now.

Reference export

Standard publish stays locked until the frame clears the strict readiness gate.

Discord handoff block

Copy this directly into Discord or a dev handoff thread.

Preflight report for 806 technologies control
Target
- Figma: https://www.figma.com/design/EaJPmHpiicrqMRRPODCSzr/806-Technologies---Control?node-id=268-8256&t=j297swZdsN4Ghnan-11
- File key: EaJPmHpiicrqMRRPODCSzr
- Node id: 268:8256
- MCP lane: healthy, real preflight ran
- Checked at: 2026-04-21T15:47:54Z
Design gate
- Status: fix first
- Score: 68/100
- Recommended action: fix first
- Summary: Frame needs design cleanup before demo generation or dev handoff.
Demo gate
- Verdict: blocked
- Note: Current blocking structure issues make the demo path unreliable right now.
Decision
- Blocked because score 68 is below the demo threshold 85; status is not-ready, but demo generation requires ready-to-go; 1 error issue(s) exceed the allowed maximum 0.
Top fixes
1. Rename the frame to the SOP format, for example: Projectname_Homepage_V1, Projectname_Homepage_V2, Projectname_About Us_V1.1.
2. Treat this frame as fix-first until the export includes layout metadata, or re-run against a fuller scene dump before trusting the score.
3. Add wrap or a mobile stacking rule to these multi-item rows before handoff.
Detailed findings
- [WARNING] Scene export is missing layout definitions, so responsive and sizing checks are low-confidence.
  Fix: Treat this frame as fix-first until the export includes layout metadata, or re-run against a fuller scene dump before trusting the score.
  Evidence: Homepage v2 [268:8256] | Homepage v2 > Rectangle 13 [268:8257]
- [ERROR] Root frame name "Homepage v2" does not follow the design SOP version naming convention.
  Fix: Rename the frame to the SOP format, for example: Projectname_Homepage_V1, Projectname_Homepage_V2, Projectname_About Us_V1.1.
  Evidence: Homepage v2 [268:8256]
- [INFO] No wrapping Auto Layout groups detected.
  Fix: Add wrap or a mobile stacking rule to these multi-item rows before handoff.
Score deductions
- MISSING_LAYOUT_DEFINITIONS: -8 (warning) The scene export omitted layout definitions even though 226 nodes reference layout metadata, which weakens confidence in responsiveness and sizing checks.
- DESIGN_SOP_FRAME_NAMING: -12 (error) Root frame naming is off-SOP ("Homepage v2"). Expected Project_Page_V1 or Project_Page_V1.1 style versioning.
- NO_WRAP_LAYOUTS: -4 (info) No wrapping groups were detected, which increases responsive layout risk.
Artifacts
- Detail page: https://demo.wickedlab.io/demos/806-technologies-control-268-8256
- Scene markdown: /data/openclaw/workspace-personal-assistant/reports/figma/eajpmhpiicrqmrrpodcszr-268-8256.md
- Scene raw json: /data/openclaw/workspace-personal-assistant/reports/figma/eajpmhpiicrqmrrpodcszr-268-8256.json
- Preflight markdown: /data/openclaw/workspace-personal-assistant/reports/figma/eajpmhpiicrqmrrpodcszr-268-8256-preflight.md
- Preflight json: /data/openclaw/workspace-personal-assistant/reports/figma/eajpmhpiicrqmrrpodcszr-268-8256-preflight.json
Next: fix the listed issues in Figma, then say recheck.

Links

Reference export

/diagnostic/806-technologies-control-268-8256

Generated preview

Not generated yet.

/generic/806-technologies-control-268-8256

/ai-preview/806-technologies-control-268-8256

/compare/806-technologies-control-268-8256

Published

Not published yet.

Artifacts

/data/openclaw/workspace-personal-assistant/reports/figma/eajpmhpiicrqmrrpodcszr-268-8256.md

/data/openclaw/workspace-personal-assistant/reports/figma/eajpmhpiicrqmrrpodcszr-268-8256.json

Scene cache

/app/data/scenes/806-technologies-control-268-8256.txt

Present • updated 4/21/2026, 3:47:54 PM

Discord flow

Target commands: check https://www.figma.com/design/EaJPmHpiicrqMRRPODCSzr/806-Technologies---Control?node-id=268-8256&t=j297swZdsN4Ghnan-11, recheck, go, publish, status.

Current rule: go/generate should open the standard preview route for a registered demo. If no dedicated implementation exists yet, preview uses the exact-frame path. Publish still requires the stricter gate and a dedicated implementation.