DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to ship execution governance inside Dev Containers with Docker

Include Decionis in a Dev Container so every developer's agent inherits the same authority boundary.

Who it is forEngineering manager standardizing AI-assisted development across a team's Dev Container setup.

The problemGovernance depends on every developer and agent implementing it separately, so it is often missing or inconsistent.

The outcomeThe team's Dev Container carries the same Decionis policy and approval path, so governance travels with the environment.

What you need first

  • A Docker environment, such as Docker Desktop, where you can run the Decionis components
  • An AI agent or MCP client that can send proposed actions to Decionis before running a tool
  • A written policy for which actions need PROCEED, HOLD, or BLOCK, since Decionis evaluates against versioned policy
  • Awareness that the README says components are released incrementally, so some listed features may not be available yet

Steps

  1. Add the Decionis components to your team's Dev Container configuration.
  2. Attach the team's versioned policy so it applies in every developer environment.
  3. Confirm that agents launched from the Dev Container send consequential actions to Decionis first.
  4. Test one HOLD path and one BLOCK path in a non-production environment.
  5. Share the Dev Container definition so new developers get the same boundary.

Prompt for your agent

Using the decionis/docker repository, start the team Dev Container and send a test action named npm publish to Decionis from inside it. Expected output: a verdict with the policy name that governs the container. Verify that the verdict is HOLD or BLOCK under the team policy and that no publish runs.

Caveat. The README lists Dev Container integration as a later focus area, so the exact setup steps are not yet documented in this repository.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page