ifcos-syntax-fileio

To safely read and write IFC files using IfcOpenShell, explicitly select the schema and version, then wrap modifications in transaction begin/end pairs to ensure rollback safety and prevent corrupted undo history.

IFC file output fails schema validation when the schema is missing or mismatched. You must explicitly select the schema/version during creation and verify the `model.schema` property after opening to avoid using entities that do not match the target schema.

The best way to create a production-ready IFC file is using `ifcopenshell.api.project.create_file()`, which generates properly populated IFC headers. You should reserve `ifcopenshell.file(schema=...)` only for prototyping and testing workflows.

To implement undo and redo support for IFC model edits, wrap your modifications in transaction begin/end pairings. This deterministic multi-step transaction control avoids corrupted undo history and ensures predictable rollback behavior on failure.

Yes, you can serialize and export IFC models to STEP, XML, or ZIP formats. The Skill supports loading existing IFC, IFCZIP, and IFCXML inputs, and writing the modified results back to disk or as a string for downstream pipelines.

You should not use blank file creation methods like `ifcopenshell.file(schema=...)` for production IFC writing because it lacks proper header population. Using it for real projects risks generating invalid or incomplete IFC outputs.