Omniweft · Engineering note
Omniweft adds native object parenting
Retained CPU snapshots show preserve-world reparenting, descendant movement and complete rollback after a rejected cycle.
Source: https://louijiecompo.com/updates/omniweft-native-hierarchy/
PR #15 merged on 19 September 2026. The current example and handoff still contain candidate wording; the GitHub merge record establishes integration. The native contract supports preserve-world and preserve-local modes with generation-bearing parent links.
The project page now lets readers inspect five transactions from the retained Windows CPU fixture at runtime 9630e3bf8dd934d7b91b6f06d0e458272d5d6e1c. Diagrams plot saved world positions and display real receipts. The rejected cycle preserves complete snapshots and canonical bytes.
This is a review of existing output, not a new engine run. Native hierarchy remains unsupported over the Python SDK and policy profiles. Physical-GPU behavior, physics and persistence are outside this CPU proof. The earlier room captures keep their separate provenance.
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