Muhammad Atashi
Client / company system · governed AI content operationsCLIENT-SANITIZED

Content Automation Pipeline

The system coordinates asynchronous content work across multi-provider LLM execution, PostgreSQL/pgvector, Redis/Celery, editorial state, WordPress delivery, and operational monitoring. Publication is fenced to the exact approved article revision so stale or revoked content cannot silently inherit prior approval.

Owns
Fences publishing to the exact approved revision
Status
Production-ready and deployed · no GA traffic or uplift claim
Stack
Next.js · FastAPI · Celery · PostgreSQL · WordPress · Search Console
Public Reference

Client / company work — ownership of company IP is not claimed

Company identity may remain withheld; displayed data is synthetic/sanitized; production/GA claims stay evidence-bound.

Hard problem

Publishing authority belongs to an approved revision, not to whatever content happens to be current.

Question · How do we let AI move content quickly without letting stale or unapproved state cross the publishing boundary?

APPLIES TO

Content Teams · Marketing Operations · SEO Teams · Publishers · High-volume structured content organizations

PROOF

Revision-bound publishing · RAG + multi-provider execution · controlled canary and rollback

CAPABILITIES

13 declared in the project record

  • Workspace context
  • Research pipeline
  • Grounded content planning
  • Multi-provider LLM gateway
  • Durable task orchestration
  • Quality evaluation
  • Deterministic SEO intelligence
  • Human editorial review
  • Multilingual EN/FA/AR interfaces
  • Idempotent publishing
  • Cost accounting
  • Operational monitoring
  • Versioned content lineage

Revision-bound operations

Publishing authority follows the approved revision.

REVISION LINEAGE

Approval belongs to a revision, not to a topic forever.

  1. 01

    Research

    audience · brand · topic intelligence

  2. 02

    Context

    approved knowledge + first-party data

  3. 03

    Plan

    intent · outline · evidence · keywords

  4. 04

    Generate

    multi-provider workflow

  5. 05

    Evaluate

    quality + deterministic SEO

  6. 06Gate

    Review

    human release authority

  7. 07Gate

    Publish

    idempotent adapters

  8. 08

    Observe

    cost · jobs · outcomes

PROMOTION BOUNDARY

SEO lift, traffic lift, conversion lift, and throughput savings are not claimed.

Engineering decisions

The constraints that matter.

01

Generation is one stage, not the product

Reliable content operations require research, retrieval, planning, evaluation, review, publication, feedback, and recovery around model output.

02

Approval belongs to an exact revision

A newer edit must not silently inherit the release authority granted to an older article state.

03

Publishing rechecks authority at worker time

Queued work can become stale after approval; the worker must fence revoked or superseded revisions before the external write.

04

Operational feedback stays separate from release authority

Search Console and SEO signals can inform the next iteration without autonomously rewriting or promoting content.

Measurement contract

What would make the preferred answer fail?

EVALUATION METHOD

A content workflow is reliable only when the exact approved revision—and no stale successor—can cross the publishing boundary.

Revision-bound review fixtures, stale/revoked approval tests, durable queue execution, provider-failure injection, publish verification, backup/restore checks, and canary/rollback gates.

01

Revision binding

approval identity matches published revision
02

Stale publish block

superseded/revoked content fenced
03

Durable execution

queued work survives worker failure
04

Publish verification

idempotent write + downstream confirmation
05

Recovery

backup/restore and rollback path
06

Release gate

controlled staging/canary readiness

Validation

What the evidence actually supports.

Claims stay scoped

Focused P0 tests

VERIFIED

63 passed

Recorded repository validation; not a current production-traffic result.

Focused P1/P2 tests

VERIFIED

7 passed

Focused unit validation; not a substitute for full supported launch acceptance.

Static release gate

VERIFIED

PASS

Environment-sensitive warnings were tracked separately in the source reports.

Migration graph

VERIFIED

10 Alembic revisions · single head 20260801_001

Schema topology evidence, not live migration proof against production data.

SEO Intelligence v2.0

VERIFIED

uses_llm=false · performs_network_requests=false · rewrites_content=false · publishes_content=false

Deterministic advisory layer; it does not autonomously modify or publish content.

Promotion boundary

SUPPORTED

Production-ready and deployed

SEO lift, traffic lift, conversion lift, and throughput savings are not claimed.

Boundaries

— Client/company ownership is not claimed— No proprietary customer content in the public showcase— No unsupported SEO, traffic, conversion, or revenue uplift claim
← Selected systemsNext · Persian Conversational Commerce