Visual-World-First Software
References, absolute locks, production envelopes, and evidence-bearing visual implementation
Software projects usually treat visual direction as a late presentation layer: a moodboard, a design pass, or a set of images that developers reinterpret into components. In AI-assisted production, that separation becomes especially destructive. Models generate plausible but inconsistent interfaces, characters, shots, and products; visual intent is scattered across prompts; approved references lose authority; each regeneration becomes a new interpretation.
Visual-World-First Software (VWFF) treats the visual world as an architecture artifact. References, absolute locks, influence, asset roles, continuity, layout, camera, material, typography, responsive crops, production state, and verification become typed project objects. A Visual Direction Compiler converts those objects into a frozen Production Envelope or shot/build packet. The envelope is inspectable before execution. A separate explicit action authorizes generation or implementation. Returned assets are reviewed against the envelope, attached to exact lineage, and accepted or revised.
The approach includes a preservation ladder for locked mockups: live reconstruction when faithful, hybrid reconstruction when necessary, and image-backed/sliced assets when code would weaken visual fidelity. The winning output is not the purest CSS. It is the best working system that preserves the approved visual contract.
Current evidence state
IMPLEMENTED
This label describes the strongest public-safe state of the specific paper claims. Open the paper's claim ledger for claim-level distinctions and limitations.
Publication
- Full paper:
/papers/p19-vwff-visual-direction-compiler - Claim ledger:
content/papers/p19-vwff-visual-direction-compiler/claim-ledger.json - Source manifest:
content/papers/p19-vwff-visual-direction-compiler/source-manifest.json - Diagrams: 4
- Approximate body length: 1,493 words
Demonstrations
d14-workpage-generator
Benchmarks
b09-workpage-os
Public boundary
The research entry publishes a public-safe architecture and evidence record. It does not grant implementation rights or expose restricted claim-ready material.