2026-06-13-kyle-grice-faculty-profile-2
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
- —
URL capture
- Submitted URL
- https://www.depaul.edu/faculty/kyle-a-grice
- Final URL
- https://www.depaul.edu/faculty/kyle-a-grice
- HTTP status
- 200
- Capture status
- —
- Retrieved
- 2026-06-13T18:53:41.707593+00:00
- Content type
- text/html
- Snapshot
source_snapshot/page.html- SHA-256
bcc12d0a3c47d05f…
Workflow
- Intake status
- submitted
- Review status
- in_review
- Refactor status
- proposed
- Priority
- normal
- Created at
- 2026-06-13T18:53:41.707143+00:00
- Git branch
- development
Uploaded files
No files in uploads/.
URL snapshots
source_snapshot/page.html(184595 bytes)
Candidate links (human review only)
52 extracted link(s). Not sources — do not auto-ingest.
# Candidate Links (human review only) > Hyperlinks extracted from the submitted URL snapshot. > **Not sources.** Do not auto-ingest, fetch, or refactor from these links. > A curator reviews this list and manually adds selected URLs as separate sources. - **Submitted URL:** https://www.depaul.edu/faculty/kyle-a-grice - **Snapshot file:** `source_snapshot/page.html` ## Extracted links | # | Link text | Resolved URL | |---|-----------|--------------| | 1 | _(no text)_ | https://www.depaul.edu/ | | 2 | Request Info | https://www.depaul.edu/admission/request-information | | 3 | Apply | https://www.depaul.edu/apply | | 4 | Faculty And Staff Di… | https://www.depaul.edu/faculty | | 5 | Website | https://sites.google.com/site/drkyleagrice/ | | 6 | Experimental and Theoretical Investigation of the Coordination of 8-Hydroxquinoline Inhibitors to Biomimetic Zinc Complexes and Histone Deacetylase 8 (HDAC8) (mdpi.com) | https://www.mdpi.com/2673-9321/4/3/24 | | 7 | Synthesis, characterization, computational studies, and reactivity of platinum(II) complexes of alkyl phosphite ligands - ScienceDirect | https://www.sciencedirect.com/science/article/pii/S0022328X2300205X | | 8 | Methane Generation from CO2 with a Molecular Rhenium Catalyst \| Inorganic Chemistry (acs.org) | https://pubs.acs.org/doi/full/10.1021/acs.inorgchem.0c02579 | | 9 | Dr. Grice’s full publication list can be found here. | https://scholar.google.com/citations?user=4_bNwbMAAAAJ&hl=en | | 10 | DePaul Discoveries | https://via.library.depaul.edu/depaul-disc/ | | 11 | IONiC | https://www.ionicviper.org/ | | 12 | 1 E. Jackson Blvd. Chicago, IL 60604 | https://maps.app.goo.gl/YMhJzc6ctzup86nA8 | | 13 | _(no text)_ | https://www.linkedin.com/school/depaul-university | | 14 | _(no text)_ | https://www.tiktok.com/@depaulu | | 15 | _(no text)_ | https://www.instagram.com/depaulu | | 16 | _(no text)_ | https://www.facebook.com/DePaulUniversity/ | | 17 | _(no text)_ | https://www.youtube.com/c/@DePaulUniversity1898 | | 18 | Current Students | https://www.depaul.edu/students | | 19 | Visitors | https://www.depaul.edu/admission/undergraduate-admission/visit-depaul-undergraduate | | 20 | Faculty and Staff | https://www.depaul.edu/for-faculty-and-staff | | 21 | Alumni | https://www.alumni.depaul.edu/ | | 22 | Parents and Families | https://parents.depaul.edu/s/1906/23-parents/home.aspx?gid=2&pgid=3188 | | 23 | Academic Calendar | https://academics.depaul.edu/calendar/Pages/default.aspx | | 24 | Academic Catalog | https://catalog.depaul.edu/ | | 25 | Academic Success | https://resources.depaul.edu/student-success/Pages/default.aspx | | 26 | BlueM@il | https://offices.depaul.edu/information-services/services/email/student-email/Pages/default.aspx | | 27 | Campus Connect | https://campusconnect.depaul.edu/ | | 28 | Desire2Learn (D2L) | https://d2l.depaul.edu | | 29 | Library | https://library.depaul.edu | | 30 | MyDePaul | https://offices.depaul.edu/depaul-central/student-resources/Pages/onedepaul.aspx | | 31 | Security | https://offices.depaul.edu/public-safety/safety/Pages/default.aspx | | 32 | Bookstore | https://depaul.bncollege.com/ | | 33 | Campus Maps | https://resources.depaul.edu/campus-maps/Pages/default.aspx | | 34 | Events | https://events.depaul.edu/ | | 35 | Directory | https://ekze.fa.us2.oraclecloud.com/hcmUI/faces/FndOverview?fnd=%3B%3B%3B%3Bfalse%3B256%3B%3B%3B&fndGlobalItemNodeId=PER_HCMPEOPLETOP_FUSE_DIRECTORY | | 36 | University News | https://www.depaul.edu/university-news | | 37 | Athletics | https://depaulbluedemons.com/ | | 38 | Leadership and Administration | https://www.depaul.edu/about/administration | | 39 | Employment at DePaul | https://www.depaul.edu/employment-at-depaul | | 40 | A-Z List of Websites | https://www.depaul.edu/utilities/a-z-websites | | 41 | Help Desk | https://offices.depaul.edu/information-services/support/Pages/default.aspx#:~:text=You%20can%20reach%20the%20Help%20Desk,at%20helpdesk%40depaul.edu%20or%20call%20%28312%29%20362-8765. | | 42 | Visit | https://www.depaul.edu/visit | | 43 | Give | https://giving.depaul.edu/s/1906/19-giving/landing.aspx?gid=2&pgid=514 | | 44 | Disclaimer | https://www.depaul.edu/disclaimer | | 45 | Contact Us | https://www.depaul.edu/contact-us | | 46 | Emergency Plan | https://emergencyplan.depaul.edu/Pages/default.aspx | | 47 | Consumer Info | https://www.depaul.edu/consumer-info | | 48 | IBHE Complaints | https://complaints.ibhe.org/ | | 49 | Privacy Statements | https://go.depaul.edu/privacy | | 50 | Accreditation and Licensure | https://www.depaul.edu/about/accreditation | | 51 | Request Support for Website Accessibility | https://www.depaul.edu/utilities/accessibility | | 52 | © 2001-2026 DePaul University | https://www.depaul.edu/copyright | ## Curator selection _Mark links to intake separately (new submission or added upload). Do not assume candidate links are evidence until captured and reviewed._ - [x] **Selected for follow-up intake** (captured 2026-06-13 → `source_snapshot/captured/`): - #5 Personal site (`personal-site.html`) - #6 MDPI HDAC8 paper (`mdpi-hdac8.html`, HTTP 403 audit) - #7 ScienceDirect platinum paper (`sciencedirect-platinum.html`, HTTP 403 audit) - #8 ACS rhenium paper (`acs-rhenium.html`, HTTP 403 audit; maps to PUB-009) - #9 Google Scholar (`google-scholar.html`) - #10 DePaul Discoveries (`depaul-discoveries.html`) - #11 IONiC (`ionicviper.html`) - [x] **Rejected (not relevant):** #1–4, #12–52 (DePaul navigation, social media, maps, footer links)
Cursor refactor prompt
Copy this into Cursor on development when the packet is reviewed.
# Cursor Refactor Prompt — 2026-06-13-kyle-grice-faculty-profile-2
> Copy the block below into Cursor on the `development` branch once this packet
> is `ready_for_refactor`. Prompt refreshed 2026-06-14 from
> `sources/inbox/_template/refactor_prompt.md` (documentation only; no refactor rerun).
>
> See `docs/source-packet-workflow.md` and `docs/source-evaluation-policy.md`.
---
```
You are refactoring the DePaul ORS Resource Map corpus on the `development` branch.
Source packet: sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/
You are a repository editor, not a chatbot. The objective is evidence-backed
repository refactoring — not extraction, scraping, or chatty summarization.
Before editing, read:
- sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/intake.yaml (or metadata.yaml if from the intake app)
- sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/curator_notes.md (or submitter_notes.md)
- sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/review_notes.md
- sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/evidence_checklist.md
- every captured file in this packet (uploads/, source_snapshot/, source_snapshot/captured/)
- docs/source-packet-workflow.md
- docs/source-evaluation-policy.md
- docs/reports/grant-ingestion-governance.md (when packet includes grants/awards)
- docs/main-evidence-verification-audit.md
- resource-map-index.md (ID governance and field standard)
- sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/candidate_links.md (review only — not sources)
- sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/source_snapshot/page.html
- every file under sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/source_snapshot/captured/
SOURCE EVALUATION AND EVIDENCE POLICY (required):
- Distinguish CAPTURED SOURCES (everything saved in this packet) from SOURCES
USED AS EVIDENCE (only those cited in evidence_checklist.md and the diff).
- Preserve provenance for all captures regardless of use.
- Record intake channel: intake_form (intake app) vs curator_added (maintainer
additions outside the form). Every curator_added source must list added_by,
added_at, and added_rationale in intake.yaml or metadata.yaml.
- capture_status: success | partial | failed (HTTP 403 = partial, never success).
- High-confidence sources include university profiles, lab/department sites,
grants, journal articles, DOI pages, Google Scholar, ORCID, Web of Science,
Scopus, ResearchGate (when clearly the scholar), professional society profiles,
official project sites, and faculty-maintained research websites.
- Those sources may support people, publications, collaborations, memberships,
service roles, expertise, research themes, and professional activities.
- Remain conservative for facility ownership, equipment ownership, facility access,
organizational authority, administrative responsibility, laboratory affiliation,
and operational control — require institutional or project evidence.
- Scholarly indexes (Google Scholar, ORCID, Web of Science, Scopus, ResearchGate)
are strong for publications, collaborations, and expertise; NOT sufficient alone
for facility or equipment claims.
- Lower confidence: news, press releases, blogs, marketing (corroborate first).
- Very low confidence: social media, forums, anonymous sites (not primary evidence).
- Publications: resolve and verify DOI (Crossref/ORCID); register citation + abstract in
publications.yaml; link by DOI — do not store full-text articles in packets.
- ORCID on people.yaml: verified (Crossref authorship) or probable (ORCID API);
see docs/source-evaluation-policy.md § ORCID registry — identity only, not facility claims.
- Service/editorial/society roles: do NOT add to resource pages unless tied to
facilities or hardware.
GRANT AND AWARD INGESTION (when packet includes grants, awards, or ORS listings):
- Read docs/reports/grant-ingestion-governance.md.
- Unresolved knowledge is still knowledge: evidence-backed awards MAY enter
data/grants.yaml even when PI is not in people.yaml.
- Treat three questions separately: (1) grant existence, (2) PI identity
resolution, (3) facility/resource linkage.
- person_identity_status: resolved | unresolved | ambiguous — never invent person_id.
- resource_links_status: resolved | unresolved | not_supported — facility edges
require explicit lab/facility naming in source.
- Add person_grant_links.yaml ONLY when person_id is resolved.
- Add grant_resource_links.yaml ONLY when resource link is resolved.
- Do NOT discard awards solely because PI is absent from people.yaml.
- Report counts: grants added (resolved PI vs unresolved PI), PGL added, GRL added,
deferred unresolved rows indexed in packet extracted/.
AUDIT-DRIVEN REFACTORS (if implementing docs/reports/*-audit.md findings):
- Follow docs/reports/audit-driven-refactor-policy.md.
- Audit findings are NOT evidence; every change needs in-repo or packet source.
- Prefer surfacing/linking existing YAML evidence over new factual claims.
- Incremental diffs; preserve readability; stop before commit unless instructed.
URL SOURCE (this packet):
- Submitted source URL: https://www.depaul.edu/faculty/kyle-a-grice
- Saved snapshot: sources/inbox/2026-06-13-kyle-grice-faculty-profile-2/source_snapshot/page.html
- Read candidate_links.md — hyperlinks extracted for HUMAN REVIEW ONLY.
- Do NOT fetch, follow, auto-ingest, or treat candidate links as evidence.
- Use ONLY saved source material in this packet unless a curator adds captures.
Task:
Propose evidence-backed edits to the EXISTING corpus that reflect the supported
claims in this packet's evidence_checklist.md. Target resources: CSH-016, PER-100, PUB-009 (resolve from evidence_checklist.md).
Strengthen the network of evidence-backed relationships — do not simply append
isolated facts. The Resource Map is a hypertext knowledge system.
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)
- data/grants.yaml, data/person_grant_links.yaml, data/grant_resource_links.yaml (when evidenced)
- 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 (or curator guidance in metadata.yaml).
--------------------------------------------------
HYPERTEXT AND RECIPROCITY REQUIREMENTS
--------------------------------------------------
For every proposed relationship involving people, facilities, laboratories,
equipment, grants, publications, outputs, departments, colleges, external
partners, or organizations:
1. Create human-readable hyperlinks wherever appropriate.
2. Prefer reciprocal links. If A links to B, evaluate whether B should also link back to A.
3. Report all new links created.
4. Report all reciprocal links created.
5. Report all links deliberately NOT created and explain why.
6. Every relationship must be associated with one or more explicit sources.
7. Every relationship should preserve provenance.
8. Do not create relationships based solely on topic similarity.
9. Do not infer facilities, equipment, ownership, collaboration, or organizational
relationships unless supported by evidence.
10. If a source mentions an entity not yet in the repository: do not silently discard it;
do not invent a page; list it as a candidate addition with supporting evidence.
11. When updating pages, prefer improving existing content over creating new content.
12. Preserve narrative readability.
13. Preserve existing evidence.
14. Strengthen evidence visibility where appropriate.
15. Prefer repository-wide consistency over local page optimization.
--------------------------------------------------
REFACTOR OUTPUT REQUIREMENTS
--------------------------------------------------
Provide all of the following before or alongside the Git diff:
A. Source evaluation summary:
1. Captured sources (every file in this packet; include capture_status for URL snapshots)
2. Sources used as evidence (map each to evidence_checklist.md claims)
3. Sources reviewed but not used
4. Reason not used (for each unused capture)
B. Proposed repository changes
C. New relationships identified
D. New hyperlinks created
E. Reciprocal hyperlinks created
F. Candidate entities not yet represented (include unresolved-PI grants: index in packet extracted/, propose grant rows when source is reliable)
G. Relationships considered but rejected
H. Evidence supporting every accepted relationship
I. Any provenance concerns
J. Any conflicts with existing repository content
K. Audit implementation summary (when applicable — see audit-driven-refactor-policy.md):
relationships surfaced, hyperlinks added, reciprocal links added, evidence used,
recommendations not implemented and why
Write the report to refactor_output.md in this packet unless instructed otherwise.
--------------------------------------------------
KNOWLEDGE INTEGRITY REQUIREMENTS
--------------------------------------------------
Strengthen: discoverability, provenance, hyperlink structure, reciprocal
relationships, evidence visibility, and consistency.
Avoid: hallucinated entities, unsupported relationships, speculative facility
assignments, speculative collaborations, and speculative equipment ownership.
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` (or workflow fields in `metadata.yaml`).
2. Reviewer checks the Git diff against `evidence_checklist.md` and `refactor_output.md` section A (captured vs used sources).
3. On approval, run `./sync_docs.sh` and `mkdocs build --strict`.
4. Only after a clean, tested build does work move toward `main`.