Use the configured conduct Gate
The configured Gate projects the selected receipt’s sealed conduct decision; it does not decide whether you should ship.
Use this when
Use this when CI or Console should read the same Gate decision already sealed with a concluded run receipt.Before you start
Choose the Store and receipt. Conduct Gate needs no caller-defined criteria or policy version. Keep a modeled-money threshold separate and customer-owned.Before a secret-bearing CI job, download Meguro CI kit v2 from the public marketing site, verify its pinned SHA-256, unpack it as byo-ci-test/, review it, and commit that directory. CI runs the vendored files; it never downloads executable code after secrets are supplied.
curl -fsS -o meguro-ci-kit-v2.tar.gz https://meguro.io/downloads/meguro-ci-kit-v2.tar.gz
curl -fsS -o meguro-ci-kit-v2.tar.gz.sha256 https://meguro.io/downloads/meguro-ci-kit-v2.tar.gz.sha256
printf '%s %s\n' '37ca683e4373b8f25ac04723e1f67853f7a6e123ac46a233634cb277921f5de4' 'meguro-ci-kit-v2.tar.gz' | cmp - meguro-ci-kit-v2.tar.gz.sha256
shasum -a 256 -c meguro-ci-kit-v2.tar.gz.sha256
tar -xzf meguro-ci-kit-v2.tar.gz
git add byo-ci-test/Steps
- Select one Store and its concluded receipt.
- Read or evaluate the configured Gate; the response carries policy
meguro.release-gate-policy.v2and the receipt’s own go/no-go sentence. - Fail CI when the Gate is no-go. If your business rule also requires nonnegative net contribution, add a separate command that checks the receipt’s modeled value.
- Retain the receipt and Gate evaluation together so the decision remains traceable.