The adapter's manifest mode names each document's verified cache artifact
instead of merging the federation and writing the split Scene IR itself.
This module hydrates those artifacts and reproduces, byte for byte, the
structure, geometry, and property column bytes and the adapter report that
the monolithic adapter path would have written: the same merge rules
(extract_federation), the same key and value column merges
(merge_property_indexes, merge_property_value_columns), the same
packing (write_scene), and Python's canonical JSON. No structure file is
written; its digest is streamed.
Every artifact check that fails is a fallback signal, never an error: the
caller re-runs the monolithic adapter path instead. Only inconsistencies in
the manifest itself, and the limits the adapter would also refuse, throw.
In-compiler IFC federation assembly (ADR-0019 slice 3b).
The adapter's manifest mode names each document's verified cache artifact instead of merging the federation and writing the split Scene IR itself. This module hydrates those artifacts and reproduces, byte for byte, the structure, geometry, and property column bytes and the adapter report that the monolithic adapter path would have written: the same merge rules (
extract_federation), the same key and value column merges (merge_property_indexes,merge_property_value_columns), the same packing (write_scene), and Python's canonical JSON. No structure file is written; its digest is streamed.Every artifact check that fails is a fallback signal, never an error: the caller re-runs the monolithic adapter path instead. Only inconsistencies in the manifest itself, and the limits the adapter would also refuse, throw.