--- status: accepted --- # The engine is built from a reference that is never modified The solution architecture agent works, and is still being developed: four of its iterations have open steps. We decide that the Execution engine is built in this repository from that agent as a **Reference**, and that no file of the Reference is changed in doing so. - A module is brought across by `scripts/bring.py`: copied, with its imports renamed and nothing else changed. - `REFERENCE.lock.json` records, for every file brought, the Reference's commit and the hash of the file as it stood there. - A module is changed here only after it has been brought, in a later step, so the change is a diff against what was brought. - The Reference is never run by this repository's tests, and the tests read none of its files. Accepted by the owner on 2026-10-13. ## Considered Options - **Separate the engine inside the Reference, then take it from there:** rejected by the owner. It refactors working code that has other work open on it. - **Depend on the Reference as a package:** rejected. Its engine cannot be imported without its subject. ## Consequences - There are two Execution engines: the Reference's own and this one. A fix made in one reaches the other only if someone carries it. The recorded hashes say which brought files the Reference has since changed. - Moving the Reference onto this engine is a separate decision and is not planned. - A test that a brought module depended on the Reference's own Skills, bundle or roles for is rewritten against stand-ins here, or waits for the step that brings what it needs.