Repository-Wide Assets¶
Purpose¶
The Repository-Wide Assets directory contains LMU/COICP evidence that does not belong to only one lifecycle stage.
The lifecycle directories tell the stage-by-stage story. Repository-wide assets connect that story: common terminology, repository conventions, cross-stage decisions, continuing risks, AI-use records, artifact indexing, and stakeholder responsibilities.
Why this exists¶
A real engineering repository needs more than lifecycle folders. It also needs shared records that help readers and reviewers understand how the whole project fits together.
| Scenario | Repository-Wide Thread | Shared Asset Impact |
|---|---|---|
| COICP-SYN-001 | Information Commons leak intake | glossary terms, artifact index, evidence references |
| COICP-SYN-118 | Damen Hall Facilities handoff | decision log, risk register, evidence lineage |
| COICP-SYN-204 | Mertz Hall Residence Life access | stakeholder directory, risk register, conventions |
| COICP-SYN-219 | Cudahy Science HVAC closure | artifact index, decision log, risk register |
| COICP-SYN-322 | Emergency-boundary rejection | glossary, risk register, decision log |
| COICP-SYN-407 | Mundelein Wi-Fi ownership extension | decision log, scope terms, artifact index |
Shared asset set¶
Repository Conventions
Project-wide naming, evidence, navigation, review, and lifecycle conventions.
02Glossary
Shared LMU/COICP terms, scenario identifiers, roles, and evidence language.
03Decision Log
Cross-stage decisions that shape the whole LMU/COICP lifecycle.
04Risk Register
Repository-wide risks that persist across stages and change as evidence matures.
05AI Usage Log
Material AI assistance records and human review expectations.
06Artifact Index
Index of major lifecycle artifacts, readiness records, and evidence packages.
07Stakeholder Directory
Project-wide stakeholder roles, review responsibilities, and evidence interests.
How to read this directory¶
Start here before entering Vision. Return here after Governance when you want to inspect the project as one repository rather than one stage at a time.
Repository-wide assets do not replace lifecycle evidence. They connect lifecycle evidence so decisions, risks, terms, AI-use records, artifacts, and stakeholders remain visible across the whole repository.