Skip to content

Manual attribution and an explicit re-match action #27

Description

@jbagsik

Parent

#21

What to build

An operator can correct an attribution by hand and can deliberately re-run matching on selected
documents — and neither of those can undo the other.

Both halves are needed because the review outcomes only pay off if the loop closes. Documents park in
review precisely so master data gets completed; if nothing is ever re-evaluated, they stay parked
forever. Conversely, if a re-run can silently overwrite a human decision, reviewing is pointless.

Re-matching stays explicit. Confirmed and validated documents are never re-evaluated by the
automatic path, and nothing re-attributes documents in the background — an attribution must not change
without someone asking for it.

Acceptance criteria

  • An operator can set the attribution on a document by hand from the admin surface.
  • A manually set attribution is recorded with a manual source, distinguishable from an automatic
    one.
  • An operator can trigger re-matching for a selected document; it resets to the pre-confirmation
    state and re-evaluates.
  • Re-matching leaves a manually sourced attribution untouched.
  • The automatic path still refuses to re-evaluate a confirmed or validated document.
  • Nothing re-matches on a schedule or as a side effect of unrelated processing.
  • A document parked in review is picked up correctly by a re-run after the missing master data is
    completed.
  • Covered through the validation entry point plus the re-match action, asserting the resulting
    attribution and status.

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentSpec is ready for an agent to implement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions