Reviewer Workflow

Purpose

Human-in-the-loop workflow for WS1 documentation accuracy and evidence alignment review.

Operational execution is outside scope.

Review Scope

review_scope:
  - documentation_accuracy
  - evidence_alignment
  - governance_consistency
  - architectural_truthfulness

Determinations

determinations:
  - ACCEPTED FOR HUMAN REVIEW
  - RETURN FOR CORRECTION

Flow

Author
  -> Publish governance + evidence package
  -> Reviewer opens portal / PR / working tree
  -> Compare narrative vs evidence
  -> Complete attestation (markdown form or GitHub Issue)
  -> Governance owner validates
  -> ACCEPTED FOR HUMAN REVIEW or RETURN FOR CORRECTION

Package to Review

Governance

• Topology
• Evidence Reconciliation
• Final Handoff
• Reviewer Notification
• Cover Note
• Attestation

Evidence

• Boundary Summary
• Audit Report
• Manifest: evidence-manifest.yaml

Submission Paths

1. Complete and return second-reviewer-attestation-v50.md.
2. Or open a GitHub Issue using the WS1 Documentation Attestation issue template (.github/ISSUE_TEMPLATE/ws1-attestation.yml).

Questions Reviewers Must Answer

1. Does documentation distinguish intended target state, evidence-backed current state, operator-reported status, and pending approvals?
2. Does documentation avoid unsupported completion claims (retirement, FSMO, cutover, disposition)?
3. Does documentation accurately reflect current evidence posture?
4. Does documentation comply with EFAR-001 (evidence-first authorization)?

Non-Authorizations

Review does not authorize FSMO transfer, DC demotion, AKODA retirement, resource reclamation, cutover, manifests, receipts, ProgressLedger mutation, git commit/push as authorization, artifact promotion, or WS2 execution.