LMU/COICP Reference Implementation¶
Completed Example
Lakeside Metropolitan University / Campus Operations and Incident Coordination Platform
LMU/COICP is the ETIS reference implementation. It demonstrates how a modern engineering team applies repository-centered, evidence-centered, AI-assisted software engineering to a realistic institutional operations platform.
What is LMU/COICP?¶
Lakeside Metropolitan University is the fictional institution used throughout ETIS.
COICP, the Campus Operations and Incident Coordination Platform, is the reference system used to demonstrate how engineering evidence evolves across a complete lifecycle. The platform supports coordinated awareness, triage, communication, escalation, and operational follow-through for selected campus operations scenarios.
The example is intentionally realistic. It includes institutional stakeholders, operational constraints, AI-assisted engineering workflows, evidence expectations, governance obligations, release discipline, and long-term stewardship concerns.
How to read this repository¶
The LMU/COICP example is designed to be read like a professional engineering repository.
Start with Repository-Wide Assets to understand the conventions, glossary, decision log, risk register, AI-use log, artifact index, and stakeholder directory that tie the lifecycle together. Then proceed through the Engineering Stages from Vision through Governance.
Repository-Wide Assets
→ Vision
→ Requirements
→ Planning
→ Architecture
→ Design
→ Implementation
→ Integration
→ Testing
→ Release
→ Operations
→ Deployment
→ Monitoring
→ Stewardship
→ Governance
→ Repository-Wide Assets
Lifecycle map¶
Repository-Wide Assets
Shared conventions, terminology, decisions, risks, AI-use records, artifact index, and stakeholders.
ES-101Vision
Problem framing, purpose, stakeholders, outcomes, scope, assumptions, and success criteria.
ES-102Requirements
Functional needs, quality attributes, constraints, acceptance criteria, and traceability.
ES-103Planning
Work breakdown, ownership, delivery approach, assumptions, dependencies, and risks.
ES-104Architecture
System structure, boundaries, decisions, integration points, and architectural controls.
ES-105Design
Detailed behavior, interfaces, data flows, user experience, and operational design choices.
ES-106 / ES-107Implementation
Repository readiness, AI-assisted development, implementation records, evidence, and summaries.
ES-108Integration
Code review, pull request review, guardrail review, traceability review, and integration evidence.
ES-109Testing
Verification strategy, test evidence, defect handling, risk coverage, and release confidence.
ES-110Release
Readiness evidence, acceptance records, open risks, rollback planning, and approval rationale.
ES-111Operations
Operational readiness, support model, monitoring plan, incident response, and transition evidence.
ES-112Deployment
Environment readiness, rollout controls, access/data transition, validation, and deployment evidence.
ES-113Monitoring
Signals, logs, incidents, access/data monitoring, guardrail monitoring, and trust monitoring.
ES-114Stewardship
Post-release learning, feedback synthesis, improvement backlog, lessons, and next-cycle recommendations.
GOVGovernance
AI governance, release governance, risk and exception handling, evidence governance, and stewardship oversight.
What to look for¶
Traceability
Requirements connect to architecture, design, tests, release evidence, operational controls, and governance decisions.
Professional realism
The artifacts include constraints, uncertainties, ownership, review points, risk treatment, and evidence boundaries.
Lifecycle continuity
The project does not end at release. Operations, deployment, monitoring, stewardship, and governance remain part of the engineering system.
Begin with repository-wide assets.
Start with the shared evidence that makes the LMU/COICP repository readable, traceable, and reviewable across stages.
Open Repository-Wide Assets →