Skip to content

Backlog: consider atomic chapter Work + parent relation creation #804

Description

@ja573

Status

BACKLOG / NOT APPROVED FOR IMPLEMENTATION

Context

Current chapter creation is a two-step process: create the chapter Work, then create its parent WorkRelation. If relation creation fails after Work creation succeeds, an orphan chapter Work can remain.

The CTO has explicitly chosen not to broaden the current incident remediation into this backend change unless it proves strictly necessary.

Potential future objective

Evaluate a transactional/domain-level operation that creates a chapter Work and its initial parent relation atomically, so the system cannot leave an orphan solely because the second step fails.

Non-goals for current incident work

  • Do not implement this as part of the wrong-parent investigation.
  • Do not change chapter deletion behavior.
  • Do not alter the approved single-parent rule task.
  • Do not change GraphQL contracts or database behavior merely because this issue exists.

Trigger for revisiting

Revisit only if:

  • incident reproduction shows atomicity is required to prevent the observed corruption; or
  • orphan chapter records become an independently evidenced operational problem; or
  • a future API/domain redesign provides an appropriate bounded opportunity.

Any implementation requires its own approved specification, tests, rollout/rollback and independent review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions