Automated Compliance Library Management

Overview

Compliance content changes constantly: new frameworks arrive, controls get revised, and requirement language gets rewritten. Before Library Management, every content change rode a full application deploy, so a one-line copy fix and a new control template had the same release cost. The release model was tolerable with a few frameworks, but it broke down as the library grew.

I designed and built the content management layer that separated framework content from code releases. Product managers and compliance specialists can stage routine content changes, while validation and publishing move through a managed path instead of a full application deploy.

What I built

The architecture separated authoring, publishing, and validation. A versioned content store records every published update as a revision. A publishing flow lets non-engineering stakeholders stage changes while validation gates what reaches production. Seeding and validation tooling built on Pydantic v2 catches schema and content-shape errors before the content reaches customers.

The Pydantic ingestion tool became the workhorse of the content path. Content experts can update a CSV, and the tool ingests the sheet into the target environment, validates the rows, and keeps development and production content aligned. I also rewrote the Automated Compliance README around this flow so the content path was documented instead of passed around through informal onboarding.

The framework-versioning work was the stretch goal. I built it to support fast migrations between content versions. The design came out more flexible than the use cases on the table, which is a miss I called out when reviewing the project. The content layer held up, but the product-facing migration flow landed later than I planned.

Collaboration

I worked with product on the publishing UX and with the compliance content team on the content model that the new validation path had to enforce.

Outcome

• Routine compliance-content changes moved from code-release coupling to a lightweight validation-and-publish flow.
• Product and compliance teams can stage validated content updates through a managed review path before publishing.
• Published content changes are traceable through revision records and rollback targets.

The content layer held up, but part of the versioning design reached beyond the use cases in front of us. I now try to cover the cases on the table first, then let the next real case earn the abstraction.