Output intake rules
Codified rules from outputs discovery batch 1 and seed pass (May 2026). These govern what enters the resource-map outputs layer and what may appear in graph exports.
Related: outputs-layer-plan.md · output-data-intake-template.md · outputs-quality-review.md
Registry baseline (after batch 2, 2026-06-01): 18 outputs · 16 person–output links (15 graph-included) · 12 output–resource links (all graph-included). See full-refresh-report.md.
Purpose
The outputs layer documents non-publication creative, technical, and professional artifacts that evidence DePaul facilities, labs, production infrastructure, fabrication, games, exhibitions, software, datasets, or deployed systems tied to map entities. Center leadership, program affiliation, or topical fit alone is insufficient for person–output or output–resource edges.
Core principles
Person–output links
Person–output links require explicit evidence that the person worked on, led, curated, directed, designed, developed, produced, advised, or otherwise contributed to the specific output.
- A person’s leadership of a center, lab, or program is not enough by itself to create a person–output link.
- One or two included outputs per person per batch is the default cap.
- External museums, festivals, showcases, and portfolios may be valid output contexts, but the DePaul person connection must be explicit on the output page, press release, or official faculty/lab bio for that artifact.
Output–resource links
Output–resource links require explicit evidence connecting the output to the resource.
- Resource leadership is not enough to infer output authorship or facility use.
- Target: sparse, high-confidence edges — same bar as publication-intake-rules.md publication–resource links.
- Default for a new output: person–output link only when role is named;
resource_link_allowed: falseuntil production/facility text is reviewed.
What is not sufficient
| Inference | Rule |
|---|---|
| Center / lab directorship alone | Not sufficient for person–output. Example: POL-008 Wagner → OUT-008 (Plant digital twin; SPARK page does not name Wagner). |
| General affiliation alone | Not sufficient for person–output or output–resource. |
| Nearby project page without naming the person | Not sufficient for person–output. |
| Grant leadership without output page naming the person | Not sufficient for person–output. |
| Topical similarity | Not sufficient for output–resource. |
| Same school or center | Not sufficient for output–resource. |
| Co-credit / co-production | Not a collaboration edge. Person–output records documented roles; it does not create person–person or cross-unit collaboration edges. |
| Generic project relevance | Not sufficient for include_in_graph: true on any edge. |
Hub resources (monitor, do not infer)
SPARK (UNI-003), Cinespace (CDM-016), HexLab (CDM-022), IRL (CDM-001), and similar nodes can be real hubs when evidence is explicit. Monitor hub growth for weak inferred edges — do not add a fourth UNI-003 output–resource edge without new explicit SPARK facility text (batch 1 lesson).
Graph inclusion vs registry retention
| Situation | Action |
|---|---|
| Explicit person role + strong resource-map relevance | Output + person–output with include_in_graph: true |
| Explicit output–resource text | Output–resource with include_in_graph: true |
| Output artifact documented; person not named on output page | Retain output (and output–resource if facility text is explicit); set person–output include_in_graph: false (e.g., OUT-008 + ORL-006 kept; POL-008 excluded) |
| Weak or external-only context (documentary, museum exhibit) | Person–output may stay in graph at medium confidence when role is explicit; no output–resource link |
| Unclear identity or evidence | confidence: low, needs_review in notes; include_in_graph: false until resolved |
| Clearly wrong record | Prefer needs_review or include_in_graph: false over deletion unless duplicate or fabricated |
Output records may remain in the registry even when person–output links are excluded from the graph.
Hard exclusion rules for person-output links
Do not create person–output links when the only support is:
- Center directorship alone — person directs SPARK, Jarvis, HexLab, etc.; the output page does not name them for this artifact.
- General affiliation alone — faculty in CDM, Theatre School, or a mapped center without output-specific role text.
- A nearby project page unless the person is named — same lab, grant, or program URL does not prove contribution to this output.
- Grant leadership unless the output page connects the person to that output — Steans/URC PI status does not link every related showcase to the PI.
Required: Do not create a person–output link unless an official DePaul page, production page, press release, or faculty/lab bio explicitly names the person’s role on this specific output.
When in doubt, set person_link_allowed: false, retain the output if the artifact itself is documented, and record reason_person_link_not_added in the intake template.
Hard exclusion rules for output-resource links
Do not create output–resource links when the only support is:
- Topical similarity alone — output theme matches a lab’s research area but does not name the lab, stage, instrument, or facility.
- The person’s affiliation alone — output director is affiliated with HexLab; page does not say the work was developed in HexLab.
- The resource being in the same school or center — CDM affiliation does not link every CDM output to every CDM resource.
- Resource leadership — lab director’s portfolio does not prove every listed work used that lab without explicit text.
Required: Do not create an output–resource link unless a page explicitly says the output used, was produced by, was hosted by, was developed in, or was supported by the resource (quoted in evidence_text).
When in doubt, leave resource_link_allowed: false and document reason_resource_link_not_added.
Allowed output–resource evidence
Acceptable evidence types (with quoted or linked text in evidence_text):
| Evidence type | Example from batch 1 / seed |
|---|---|
| Production page names facility or stage | ORL-001–005: Project Bluelight + people.yaml Cinespace (CDM-016) stage text |
| Official lab page lists output or portfolio of that lab | ORL-009: HexLab site → itch.io portfolio (CDM-022) |
| DePaul news or SPARK project page names facility for this work | ORL-007–008: SPARK 8th floor dashboards, digital twin at SPARK Center (UNI-003) |
| Partner/project page hosted at named center | ORL-008: SPARK housing partner project text |
| Course showcase or handbook names shop/studio used | Future: IRL capstone with CDM-001 acknowledgment |
Profile pages: A lab profile may support an output–resource link only when it names this specific output or quotes facility use for this work — not when it only lists generic capabilities.
Person–output intake criteria
Include a person–output link when all apply:
- Hard-tech or resource-map utility — output documents mapped facility use, production infrastructure, games/XR, exhibitions with map relevance, or technical capability (see outputs-layer-plan.md §3).
- DePaul person — matches a
people.yamlrecord. - Explicit role on this output — named on output page, press release, production credit block, or official bio for this artifact.
- Conservative per-person cap — 1–2 includes per person per batch unless quality review expands.
Exclude or defer (candidate_status: maybe | exclude) when:
- Person not named on the specific output (defer person link; output may still be included).
- Professional credits only without DePaul facility signal (e.g., external theatre lighting — defer to named TTS production).
- Bulk harvest without per-record review.
- Personal portfolios not linked from official DePaul sources.
Batch workflow (batch 1 pattern)
| Step | Action |
|---|---|
| 1 | Select 8–10 people from cohort plan; document search in discovery batch report |
| 2 | Search official DePaul profile / project / lab page first |
| 3 | Fill output-data-intake-template.md per candidate |
| 4 | Set candidate_status: include | maybe | exclude |
| 5 | Add outputs.yaml + person_output_links.yaml for includes with explicit person roles |
| 6 | Add output_resource_links.yaml only when allowed evidence exists |
| 7 | Set hub_risk_note when linking to UNI-003, CDM-016, or other high-degree resources |
| 8 | Run quality review pass; downgrade overclaimed edges (prefer include_in_graph: false) |
| 9 | Run python3 scripts/refresh_all.py |
Expect ~1 affiliation-inferred person link per batch at current coverage; quality review should catch and exclude from graph (batch 1: POL-008).
Lessons from outputs batch 1
| Lesson | Detail |
|---|---|
| Bluelight / Cinespace | ORL-001–005 are strong because output–resource evidence is explicit on Project Bluelight + Cinespace text. |
| SPARK projects | ORL-006–008 strong when SPARK page or DePaul press names facility connection; person link still needs person named on that output. |
| Plant digital twin | OUT-008 + ORL-006 valid; POL-008 excluded — evaluate person–output and output–resource separately. |
| Person must be named | Wagner on Beyond the Loan (press) vs not on Plant page — same director, different evidence. |
| Hub monitoring | UNI-003 (3 edges) and CDM-016 (5 edges) are justified but should be monitored. |
Downgraded in quality review: POL-008 (include_in_graph: false — center directorship only).
Validation checks (automated)
scripts/refresh_all.py reports outputs layer counts and review notes when implemented. Regenerate after any YAML change:
python3 scripts/refresh_all.py
Regenerate counts: python3 scripts/refresh_all.py