← Complete project index

Apps & Control Planes / Built / deployed

Content Studio

Self-hosted content operations platform for drafting, review, approval, scheduling, workspace isolation, audit history and durable AI generation workflows.

STATUSBuilt / deployed
AREAApps & Control Planes
STACK5 documented technologies
INTEGRATIONS6 connected / bounded services
01

OVERVIEW

What I built.

Self-hosted content operations platform for drafting, review, approval, scheduling, workspace isolation, audit history and durable AI generation workflows.

01

Built a self-hosted content operations platform around workspaces, roles, profiles, generation, review, approval and scheduling.

02

Added durable AI-generation workflows with provider gating, typed output and fail-closed behavior when no eligible model provider exists.

03

Kept auto-approval and publishing disabled by default so human review remains an explicit boundary.

02

SYSTEM ARCHITECTURE

How the system is divided.

01
Architecture boundary

Browser -> application/API -> PostgreSQL workspace/content state.

02
Architecture boundary

DBOS checkpoints generation workflows; Pydantic AI structures provider output.

03
Architecture boundary

Approved content hands off to a separate publisher service instead of coupling generation and external posting.

03

NETWORK / DATA FLOW

What talks to what.

04

TECHNOLOGY STACK

The technical surface.

01Python
02PostgreSQL
03DBOS
04Pydantic AI
05Docker
05

IMPLEMENTATION

How it works in practice.

  1. 01

    Browser -> application/API -> PostgreSQL workspace/content state.

  2. 02

    DBOS checkpoints generation workflows; Pydantic AI structures provider output.

  3. 03

    Approved content hands off to a separate publisher service instead of coupling generation and external posting.

06

TESTING & VALIDATION

How I know it works.

TEST 01

Authentication/CSRF behavior

TEST 02

Workspace isolation

TEST 03

Draft→review→schedule state transitions

TEST 04

Provider-gating/fail-closed generation

TEST 05

DBOS durable checkpoint behavior

TEST 06

Publisher dispatch kept disarmed by default

07

EXTERNAL SERVICES & DEPENDENCIES

What sits outside the core.

COREContent Studio
08

ENGINEERING EVIDENCE

Artifacts behind the claims.

01Workspace/role model
02Content calendar
03Generation workflow
04Provider budget/cooldown state
05Audit history
06Delivery worker
09

BOUNDARIES / CONSTRAINTS

What the project does not pretend to solve.

No placeholder content when all AI providers are unavailable

AUTO_APPROVE is false by default

External publishing is a separate service and explicit gate

10

RESULT / CURRENT STATE

What this produced.

A durable editorial control plane where AI generation, human approval and publishing are separate operational stages.