2026-06-13-grice-lab-pilot

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/.

Cursor refactor prompt

Copy this into Cursor on development when the packet is reviewed.

# Cursor Refactor Prompt

> Copy the block below into Cursor (on the `development` branch) once this packet is
> `ready_for_refactor`. It drives an evidence-backed refactor of the existing corpus.
> Fill in the bracketed placeholders first. Do not run extraction or scraping.

---

```
You are refactoring the DePaul ORS Resource Map corpus on the `development` branch.

Source packet: sources/inbox/[PACKET_ID]/

Before editing, read:
- sources/inbox/[PACKET_ID]/intake.yaml
- sources/inbox/[PACKET_ID]/curator_notes.md
- sources/inbox/[PACKET_ID]/evidence_checklist.md
- the captured source files in this packet
- docs/source-packet-workflow.md
- docs/main-evidence-verification-audit.md
- resource-map-index.md (ID governance and field standard)

Task:
Propose evidence-backed edits to the EXISTING corpus that reflect the supported
claims in this packet's evidence_checklist.md. Target resources: [TARGET IDS or "resolve from packet"].

Rules:
- Edit source-of-truth files only:
  - resources/<PREFIX>/<ID>.md  (prose: Description, Documented Relationships, Notes)
  - data/resource_access.yaml, data/resource_verification.yaml, data/resource_equipment.yaml
  - data/people.yaml (each association needs evidence_file + evidence_text)
  - documented-link YAML (e.g. data/course_resource_links.yaml)
- Do NOT edit anything under docs/ — it is a generated mirror (sync_docs.sh regenerates it).
- Do NOT run sync_docs.sh, mkdocs, or graph export. Stop at proposed file edits.
- Every change must cite a source present in this packet. No claim without evidence.
- Never invent URLs, emails, dates, confidence scores, or person IDs.
- Preserve existing resource IDs; assign new IDs sequentially per resource-map-index.md; never reuse.
- Keep access evidence in resource_access.yaml and verification evidence in resource_verification.yaml.
- When evidence is incomplete, set verification status to needs_review (do not inflate confidence).
- Respect display vs graph separation (include_in_public_site / include_in_graph) and the
  "what the system refuses to assume" rules (shared unit ≠ collaboration, affiliation ≠ use,
  keyword match ≠ proof).
- Honor the `do_not` list in intake.yaml.

Output:
1. A short plan listing each proposed edit and the packet evidence item it satisfies.
2. The concrete file edits as diffs.
3. Any claims you could NOT support, marked for the human reviewer.

After you finish, a human will review the Git diff, then run:
  ./sync_docs.sh && .venv/bin/mkdocs build --strict
```

---

## After the refactor

1. Update `intake.yaml` `status:` to `refactored`, then `in_review`.
2. Reviewer checks the Git diff against `evidence_checklist.md`.
3. On approval, run `./sync_docs.sh` and `mkdocs build --strict`.
4. Only after a clean, tested build does work move toward `main`.