Skip to content

Article CMS Persistence Workflow

Purpose

This document defines the persistence rule for article-domain changes: article and article-collection changes are not complete until the resulting state exists behind article-bff.

Authority Model

  • article-bff is the retrieval and mutation gateway.
  • CMS is the underlying persistence layer.
  • This repo may describe desired content shape and collection usage, but it does not become the persistence layer.

Required Persistence Rule

When article-domain content changes:

  1. resolve the target object in the BFF
  2. validate the intended shape against the live contract
  3. persist through the appropriate BFF mutation
  4. re-read and verify the stored state

Guardrails

  • Do not declare fields authoritative unless they are actually persisted and returned by the live BFF.
  • Use BFF-returned slugs and keys as operational truth.
  • Treat app caches and generated JSON as delivery artifacts, not persistence evidence.

Assistant Obligation

For article-related change work, the assistant should:

  1. identify the affected article or collection object
  2. validate against the live BFF contract
  3. mutate through the BFF when the task includes persistence
  4. report any contract gap instead of inventing local fallback authority