/nw-review-output-format

name: nw-review-output-format
description: YAML output format and approval criteria for platform design reviews. Load when generating review feedback.
user-invocable: false
disable-model-invocation: true

Platform Review Output Format

YAML Structure

review_id: "platform_rev_{timestamp}"
reviewer: "nw-platform-architect-reviewer (Forge)"
artifact_reviewed: "{path to platform design documents}"
review_date: "{ISO 8601 timestamp}"
authorized_scope: "{selected operational/design promise and authority locator}"

external_validity_check:
  deployment_path_complete:
    status: "{PASS/FAIL/UNKNOWN/NOT_APPLICABLE}"
    reason: "{applicable obligation or authorized exclusion; not mere absence}"
    evidence: "{authority/observation locator and designed versus observed limit}"
  observability_enabled:
    status: "{PASS/FAIL/UNKNOWN/NOT_APPLICABLE}"
    reason: "{applicable obligation or authorized exclusion; not mere absence}"
    evidence: "{authority/observation locator and designed versus observed limit}"
  rollback_capability:
    status: "{PASS/FAIL/UNKNOWN/NOT_APPLICABLE}"
    reason: "{applicable obligation or authorized exclusion; not mere absence}"
    evidence: "{authority/observation locator and designed versus observed limit}"
  security_gates_present:
    status: "{PASS/FAIL/UNKNOWN/NOT_APPLICABLE}"
    reason: "{applicable obligation or authorized exclusion; not mere absence}"
    evidence: "{authority/observation locator and designed versus observed limit}"
  overall_status: "{PASS/FAIL/BLOCKER/INDETERMINATE}"
  blocking_issues:
    - "{issue description if any}"

strengths:
  - category: "{pipeline/infrastructure/deployment/observability/security}"
    description: "{what is done well}"
    evidence: "{specific example from design}"

issues_identified:
  - id: 1
    category: "{pipeline/infrastructure/deployment/observability/security}"
    dimension: "{critique dimension name}"
    severity: "{blocker/critical/high/medium/low}"
    description: "{clear description}"
    impact: "{consequence if not addressed}"
    recommendation: "{specific, actionable fix}"
    evidence: "{where in the design this was found}"

dora_metrics_assessment:
  deployment_frequency_enabled: "{yes/no/partial}"
  lead_time_achievable: "{yes/no/partial}"
  change_failure_rate_trackable: "{yes/no/partial}"
  time_to_restore_measurable: "{yes/no/partial}"
  assessment_notes: "{specific observations}"

priority_validation:
  largest_bottleneck_addressed: "{YES/NO/UNCLEAR}"
  simple_alternatives_documented: "{ADEQUATE/INADEQUATE/MISSING}"
  constraint_prioritization: "{CORRECT/INVERTED/NOT_ANALYZED}"
  verdict: "{PASS/FAIL}"

recommendations:
  immediate:
    - "{must fix before approval}"
  short_term:
    - "{should fix soon}"
  long_term:
    - "{consider for future improvement}"

approval_status: "{approved/rejected_pending_revisions/conditionally_approved}"
conditions_for_approval:
  - "{condition if conditionally_approved}"

Approval Criteria

Apply approval only to the stated authorized scope. `NOT_APPLICABLE` requires authority and a concrete reason; no-rollout alone does not waive an applicable deployment/recovery design promise. A missing required rollout check is `FAIL` when its violation is observed, or `UNKNOWN` when evidence is unresolved, never `NOT_APPLICABLE`. An unresolved load-bearing check leaves overall validity `INDETERMINATE` and approval `rejected_pending_revisions` with the evidence gap named; it is not proof of a defect. `PASS` for a design plan is not observed production readiness. Scope these same distinctions in DORA/priority notes.

**Approved**: No blocker or critical issues. High issues acknowledged with timeline.

**Conditionally approved**: No blockers. Critical issues have mitigation plan. High issues documented for follow-up.

**Rejected (pending revisions)**: Any blocker present | multiple critical issues without mitigation | external validity check failed.