Loading…
Shadow Mode
See what Decionis would have blocked — before you flip a single switch.
Same install everywhere we ship: GitHub Action, LangChain (Python & JS), Azure API Management, Slack, Shopify. The gate observes, records a signed Decision Dossier, and never changes caller behaviour — until you decide to enforce. One-line change to flip, reversible without uninstalling.
1
Pick the surface that touches your most-asked workflow
You don't have to wire every surface — start with the one whose audit you'd be asked about first. Tabs below swap the install snippet to that surface verbatim.
2
Install GitHub Action in shadow
Drops into any workflow YAML in one line. Verdicts surface on the PR + the run summary.
yaml
# .github/workflows/deploy.yml
- uses: decionis/govern@v1
with:
api-key: ${{ secrets.DECIONIS_API_KEY }}
org-id: ${{ secrets.DECIONIS_ORG_ID }}
workflow-key: github_deploy_approval
mode: shadow # ← every verdict recorded; step never fails
comment-pr: 'true' # ← post verdict + verify URL on the PR
3
Watch the would-have-blocked numbers
Every gated call produces a signed Decision Dossier. Nothing changes for callers.
Each PR carries a Decionis comment with the verdict, dossier id, and verify URL. The same dossier is in your Decionis audit log (filter by workflow_key=github_deploy_approval).
- Per-dossierEvery call → one verifiable proof artifact at
/verify/decision-dossiers/<id>. - Per-weekVerdict distribution and a Decionis Score on /decionis-score — exportable as an executive PDF or AI-Act packet.
- Per-decisionForwardable Decision Dossier links — Slack / Teams / LinkedIn unfurl with the verdict OG card.
4
Flip GitHub Action to enforce
One-line change. Reversible without uninstalling.
yaml
# .github/workflows/deploy.yml
- uses: decionis/govern@v1
with:
api-key: ${{ secrets.DECIONIS_API_KEY }}
org-id: ${{ secrets.DECIONIS_ORG_ID }}
workflow-key: github_deploy_approval
- mode: shadow
+ mode: enforce # ← step fails on a block verdict
comment-pr: 'true'
Same dossier id, same verify URL, same audit log — the only difference is that blocked verdicts now actually hold the action. If a real workflow regresses, swap back to shadow: the rollback is the same one-line edit, in reverse.
Once you've been in shadow a few days
The numbers you collected become the case for enforcement.
Every dossier ID you record in shadow opens to a public verification page and unfurls with the OG verdict card in Slack / Teams / LinkedIn. Use them in the rollout review packet — the same signed artifact is the proof your CFO, your security reviewer, and your customer's auditor all want.
Thresholds
Which actions auto-clear, escalate, or block.
Owners
Who receives gray-zone actions and override reviews.
False positives
Which verdicts need policy tuning before enforcement.
Rollback
The one-line change that returns the workflow to shadow.