Declare, document and test this boundary.
← Back homeDEVELOPERS / CHANGELOG
Keep Capacity releases traceable.
A changed contract must not silently break solutions that depend on its old behavior.
CAPACITY / CHANGELOG
01Version intent
02Compatibility impact
03Evidence by release
04EVIDENCE
Three things a Capacity needs
A specific contract before a Solution can rely on it.
Declare, document and test this boundary.
Declare, document and test this boundary.
CONCRETE EXAMPLE
If a scene detector changes timestamps from seconds to milliseconds, declare the breaking change and retest recipes.
NEXT / PROVIDER
Make your capability usable by builders
Conceptual guidance for Capacity creators. No public production SDK/API is offered by this website.
info@kabin.cloudBack to homepage