Conclusion

This specification defines the normative behavior of Chef Courier interpreters. By adhering to the input contract, output model, failure semantics, security considerations, and discovery mechanisms defined herein, interpreter authors can build plugins that integrate seamlessly into the Courier ecosystem. Runners can enforce policies, extract outputs, and orchestrate complex jobs without knowledge of interpreter internals. Future extensions (for example, additional artifact types or form metadata standards) can be layered on top of this foundation without breaking existing implementations.