Omniweft · Engineering note
Omniweft builds a room within checked permissions
A scripted Python client assembles five blocks, rejects a forbidden edit and rearranges the room. The portfolio now includes retained Windows GPU frames from the merged showcase.
Source: https://louijiecompo.com/updates/omniweft-room-showcase/
PR #13 merged on 18 September 2026. It follows the fixed-step provider, scoped permission and resource-budget slices, and the integrated Windows SDK compatibility correction. Some upstream documents still contain candidate wording; the GitHub merge record establishes the current integration state.
The room contains five cubes representing a floor, two walls, a table and a stool. A rejected plan stages a valid table move before a forbidden stool move, testing that the entire batch leaves the previous state intact. A corrected batch commits revision 4.
The project page presents original color readback bytes from runtime de3d52e8a4937a1eae59c3a41b22f791fdd00149, encoded losslessly as PNG with hash and decoded-pixel verification. This is a review and reuse of public retained evidence, not a fresh native-engine execution.
The provider is scripted and offline. Linux physical-GPU validation, physics, persistence and richer world editing remain outside this result. Earlier notes retain their historical source snapshots.
Follow the evidence
Read source evidence ↗ (opens in a new tab)
Related reading
- Retrying AI Workers Without Duplicating Actions
- From Python Agent to Vulkan Frame: Designing a Bounded Control Path
Follow writing and engineering notes
Add this feed to your RSS reader to follow new articles and engineering notes. No signup or tracking on this site.
Follow via RSS