gold-standards

To enforce Kailash SDK development standards during code reviews, check for absolute imports, the 4-parameter connection pattern, explicit error handling, and proper secret management before approving PRs.

The Kailash SDK testing strategy requires Test-Driven Development alongside a 3-tier testing framework that mandates real infrastructure use for integration and end-to-end validation in Tiers 2 and 3.

Kailash workflows require the .build() method before execution to validate the workflow implementation, ensuring all custom nodes and 4-parameter connections are properly configured and compliant.

To handle secrets and parameters safely in custom Kailash nodes, use explicit error handling and secure parameter passing patterns to prevent exposure and maintain input validation across the workflow.

The 4-parameter connection pattern is a mandatory Kailash SDK standard for workflow design that enforces explicit and validated connections between nodes, preventing inconsistent data routing during execution.

Yes, absolute imports are a mandatory requirement for Kailash SDK custom node development, enforced as a gold standard to prevent module resolution issues and maintain code compliance.