War Loops: frontend reconstruction

A War Loops workflow that captures a real page, builds a static Pencil mirror and moving Forge version, then repairs the weakest fidelity signals.

Use when

Use War Loops when an authorized interface must be rebuilt from a URL or image and judged on appearance, motion, and responsive behavior.

The loop

Point War Loops at an authorized URL or image. Capture it with a genuine browser and record the layout, styles, content, motion, and responsive behavior. Build a static Pencil mirror and a moving Forge version. Compare both with the source at desktop, tablet, and mobile sizes; repair only the weakest fidelity signals. Stop when every gate passes, progress stalls, or capture is blocked. Finish with the builds, spec, renders, scores, and remaining gaps.

Steps

• Capture the source with a genuine browser and extract its design spec, motion, and target viewports.
• Build the static Pencil mirror and moving Forge version from the verified spec.
• Judge both across static design, experiential motion, and responsive reflow.
• Repair the weakest signals without rebuilding what already matches, then repeat to a terminal fidelity decision.

Verification

The builds match the source across all three fidelity axes. Static appearance, experiential motion, and responsive reflow pass their gates, or the run reports stagnation or a blocked capture.

Why it works

War Loops separates a page's still appearance from how it moves and reflows. Its surgical critic targets the weakest measured signals without churning areas that already match.