Revision review

Review decisions ties a decision to a social profile and its source revision. The Independent Reviewer records Approved, Returned or Rejected after seeing the source material, with the decision time, reason and evidence reference. This keeps a review of an earlier profile version from being mistaken for approval of a later correction.

State history records status changes with actor, time, source revision, operation key and reason. Operation runs and operation steps hold execution provenance. Read these records together when a team member asks why a profile reached Analyzed or Published. The history should answer what changed and who acted; the review decision should answer who judged the evidence.

• Submission. The Profile Owner identifies the revision and gathers supporting facts and documents.
• Decision. The Independent Reviewer records the outcome for that same revision.
• History. Status transitions and operation steps preserve the sequence around the decision.

Choose reviewers who are distinct from the people preparing the observations. Agree what evidence is needed for Approved and when Returned is more useful than Rejected. A returned case may need a new snapshot or corrected fact; a rejected case may reflect a source that cannot support the claim. The reason should be specific enough for the owner to act.

Decide how a correction creates a successor revision. The prior revision number, its decision and its operation result reference should remain readable. The team should also agree who can move a reviewed profile through the later lifecycle states and whether open follow-up actions block publication.

Take a profile with a snapshot, post facts and an evidence document. Have the Profile Owner submit its current revision for review. The Independent Reviewer opens the source links and records a Returned decision with a reason if one fact is unsupported. The coordinator assigns a follow-up action and the owner corrects the source context. Record the later revision and its own review decision.

Ask a third person to reconstruct what the reviewer saw the first time. They should find the earlier decision and its revision number separately from the corrected profile’s new decision. Then let the reviewer approve the new revision and inspect the state history before the Analytics Lead considers publication.

• Revision Decision Inbox — Find pending decisions tied to profile revisions and named reviewers.
• Run Exceptions — Inspect failed or reconciliation-needed operations before relying on results.
• Profiles by Status — See which properties are validated, analyzed or published.

See revision review for the human decision and metric analysis for the later result inspection.