projector-engine-integration-proof

You can validate compiler and runtime engine integration by executing end-to-end behavioral tests that target state machine transitions and gateway logic, ensuring the projector output natively triggers correct execution outcomes without manual JSON fixtures.

Unit tests pass but combined behavior fails due to silent contract drift, where mismatched data shapes between the compiler projector and runtime engine break production behavior. End-to-end integration testing validates this boundary to prevent silent failures.

Integration boundary testing verifies that a workflow projector's output is natively compatible with a runtime engine. It uses outcome-based assertions, like cursor existence, rather than brittle implementation details to ensure correct state machine execution.

Yes, validating compiler and engine integration requires a testable runtime engine shim and an in-memory definition store. These components allow you to assert real-world outcomes during state machine transitions and gateway logic execution.

Use outcome-based assertions when you need to prove a runtime engine correctly processes new projected output after updating workflow definition logic. This approach verifies business outcomes like cursor existence, avoiding brittle implementation details.