perspective-validationlisted

## Intent Produce a **PVC report** (Perspective Validation Checklist) that scores the target against key non-type failure modes (human factors, governance, economics, adversarial security, loop stability, data governance, and legitimacy) with concrete evidence references and remediation actions. **Success criteria:** - A valid PVC report is written to `docs/reviews/pvc/` and passes `python skills/perspective-validation/scripts/validate_pvc.py` - Each non-N/A score is justified with at least one evidence reference - Any FAIL/PARTIAL includes a concrete remediation action (P0/P1/P2) **References:** - `CHECKLIST.md` - `pvc_report_template.yaml` ## Inputs | Parameter | Required | Type | Description | |-----------|----------|------|-------------| | `target` | Yes | string | What to review (file/dir path, workflow name, or PR/change description) | | `risk_tier` | No | enum | `low \| medium \| high` (defaults to `medium` if unclear) | | `domain` | No | string | Domain context (e.g., `general`, `manufacturing`, `healthcare`) | | `deployment` | No | string | Deployment context (e.g., `local-dev`, `customer-facing`, `safety-critical`) | ## Procedure 1) **Scope the review**: Confirm `target`, `domain`, `deployment`, and `risk_tier` - If the target is a PR or branch diff, identify changed files and whether they touch critical paths (`schemas/`, `hooks/`, `skills/`, `grounded_agency/`, `tools/`, `spec/`) 2) **Collect evidence**: Read the minimum set of files needed to justify s