Effects and readback
Evaluate the observed result within a declared scope, and preserve unknown evidence.
A dispatched command is not proof that the intended change happened. Effect Conformance evaluates observations against obligations within an explicit scope. It consumes the canonical composition contracts and does not grant authority.
State what must change and what must survive
Section titled “State what must change and what must survive”A bounded operation may have positive obligations and forbidden effects. Readback must establish the declared result while checking preservation within the observed scope. The system does not turn a local observation into a global noninterference claim.
Preserve unknown outcomes
Section titled “Preserve unknown outcomes”Missing readback remains unknown. A successful subprocess exit, a render or a cached artifact does not automatically prove the native application accepted a change. Project Graph consumers preserve required failures and unknown coverage.
Use native evidence adapters
Section titled “Use native evidence adapters”The integration record describes Godot and Blender native evidence adapters and separate exact-revision certification runs. Their historical results apply to the environments and SHAs named in those records.
Contractual compatibility with another integration is distinct from an executed production consumer. Do not infer universal Figma, audio or video certification from an Effects library test.
Read Project Graph for persistent relationships and artifact handoff for transferring verified file-backed output.
Source: Effect Conformance integration, source references checked 7 October 2026. Its historical evidence keeps its original source identity and limitations.