2026-06-13-kyle-grice-faculty-profile

Submission

Title

Kyle Grice faculty profile

Submitter

Eric Landahl (elandahl@depaul.edu)

Unit

Physics

Submitted

2026-06-13

Description

—

Source

Type

faculty_profile

Origin

DePaul public

Source date

—

URL

https://www.depaul.edu/faculty/kyle-a-grice

Visibility

public

Storage permission

yes

Sensitivity

—

Workflow

Intake status

submitted

Review status

not_reviewed

Refactor status

not_started

Priority

normal

Created at

2026-06-13T18:51:18.284347+00:00

Git branch

development

Uploaded files

No files in uploads/.

Cursor refactor prompt

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

# Cursor Refactor Prompt — 2026-06-13-kyle-grice-faculty-profile

> Copy the block below into Cursor on the `development` branch once this packet
> has been reviewed. It drives an evidence-backed refactor of the existing
> Resource Map corpus. This prompt does NOT run extraction or scraping — Cursor
> reads the repository context and proposes diffs for human review.

---

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

Source packet: sources/inbox/2026-06-13-kyle-grice-faculty-profile/

Please do the following:
- Review this source packet (metadata.yaml, submitter_notes.md, review_notes.md,
  evidence_checklist.md, and every file under uploads/).
- Inspect the current Resource Map repository to understand existing IDs,
  conventions, prose, and data YAML before proposing anything.
- Propose evidence-backed updates to the EXISTING corpus that reflect the
  supported claims in this packet. Suggested targets: (resolve from packet).
- Preserve narrative quality and the established voice of the corpus.

Hard guardrails (do not violate):
- Do not invent claims. Every change must trace to evidence present in this packet.
- Do not infer facilities or relationships unless directly evidenced
  (shared unit is not collaboration; affiliation is not facility use;
  keyword match is not proof).
- Produce a normal Git diff of proposed file edits only.
- Stop for human review before any commit. Do not commit, push, or merge.
- Do not edit anything under docs/ (it is a generated mirror).
- Do not run sync_docs.sh, mkdocs, or graph exports.

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

---

## After the refactor

1. A human reviews the Git diff against `evidence_checklist.md`.
2. On approval, run `./sync_docs.sh` then `.venv/bin/mkdocs build --strict`.
3. Commit to `development`; only merge to `main` after a clean, tested build.