Skip to content

Article Lifecycle And Renaming Policy

Objective

Define how article identity changes should be handled when article authority lives behind article-bff.

Lifecycle Principle

  • article identity is operationally anchored by BFF-returned keys and slugs
  • rename decisions must preserve downstream routing and collection integrity
  • local intent notes may propose a rename, but the persisted BFF result is authoritative

Rename Procedure

  1. Resolve the target article in the BFF.
  2. Decide whether the change is an in-place title/slug update or a replacement article strategy.
  3. Apply the update through the article BFF.
  4. Re-read the returned canonical slug and key.
  5. Update any collection memberships or site references that depend on the returned identity.

Rule

Do not treat speculative or pre-write slugs as operational truth after rename work. Use the slug returned by the BFF.