2026-08-20-hpcc-operational-status
Submission
- Title
- —
- Submitter
- — (n/a)
- Unit
- —
- Submitted
- —
- Description
- —
Source
- Type
- —
- Origin
- —
- Source date
- —
- URL
- —
- Visibility
- —
- Storage permission
- no
- Sensitivity
- —
Workflow
- Intake status
- —
- Review status
- —
- Refactor status
- —
- Priority
- —
- Created at
- —
- Git branch
- —
Uploaded files
No files in uploads/.
URL snapshots
source_snapshot/hpcc-cs-depaul-edu.html(6466 bytes)
Cursor refactor prompt
Copy this into Cursor on development when the packet is reviewed.
# Refactor prompt — HPCC operational status This packet has already been applied in the Phase A schema pass. Keep this file as the provenance prompt that drove the CDM-014 operational record. Expected corpus edits (done): - `data/resource_operational.yaml` — CDM-014 `impaired`, public section on - `data/resource_verification.yaml` — add 2026-08-20 capture + packet to evidence; keep `needs_review` - `resources/CDM/CDM-014.md` — regenerated Operational status via `apply_operational.py` - Do not edit `data/resource_access.yaml` (stay yellow)