Skip to content

Define the supersede path for a re-delivered observation #46

Description

@rusholme

What the purpose requires

When the SOC re-delivers an observation already processed, the system
needs a stated answer for whether the new delivery supersedes the old,
and how — silence here leaves reprocessing behavior undefined.

What exists today

Nothing states whether a re-delivered observation supersedes the
previously processed one, or how that supersession would work.

The trigger that reopens this

The first time the SOC re-delivers an observation already processed by
RAPID and the pipeline's behavior in response is not a deliberate
choice.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    handoverHandover: outstanding at the 2026-09-13 documentation handover

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions