# AcmeOS: Governed AI Workbench

Answer a customer question using permitted company sources, then require approval before acting.

Type: Permission-aware AI workbench

Availability: Public source package

Evidence: Source code · Screenshots · Visual preview

## The work

A useful answer needs to respect role access, and a draft must remain separate from permission to send it.

A React workbench and Python backend with role-filtered sources, citations, owner approvals, local dry-run outbox artifacts, and event receipts.

## Where it stands

The company and customer are fictional. Role selection is a demonstration control, not authentication; production identity, multitenancy, and live email sending are out of scope.

## Take a look

Browse the public source, documentation, and included examples.

- [Explore the repository](https://github.com/joshdbloodworth/acmeos-governed-workbench)
- [Watch the recorded workflow](https://github.com/joshdbloodworth/acmeos-governed-workbench/blob/main/docs/assets/acmeos-walkthrough.mp4)

![AcmeOS fictional customer response with owner approval, withheld sources, and a completed local dry run](https://joshuabloodworth.com/archive-artifacts/acmeos.webp)

Original public demo capture. The fictional company workflow writes to a local outbox after owner approval; nothing is sent externally.

[Portfolio project page](https://joshuabloodworth.com/projects/acmeos-governed-workbench.html)