ETIS Repository Ecosystem¶
Repository-centered engineering in practice
The ETIS GitHub ecosystem demonstrates one of the central ETIS principles:
Everything important leaves evidence.
Repositories are not supplements to ETIS.
They are part of the framework itself.
The ETIS repository ecosystem connects engineering decisions, evidence, reviews, governance, operations, and organizational learning across the entire lifecycle of trustworthy intelligent systems.
Why Repositories Matter¶
Within ETIS, repositories are more than code storage locations.
Repositories become systems of record that preserve:
- engineering intent
- assumptions
- requirements
- architectural decisions
- AI usage
- reviews
- test evidence
- release decisions
- operational learning
- incidents
- stewardship knowledge
The repository is where engineering memory lives.
Repository Ecosystem Overview¶
The ETIS ecosystem is organized around several complementary repository models.
ETIS Flagship Reference Implementations¶
The ETIS ecosystem includes two flagship reference implementations.
These repositories bridge ETIS education and future professional adoption.
They demonstrate how ETIS moves from doctrine into real engineering environments.
ETIS COMP330 Reference Implementation¶
The COMP330 reference implementation demonstrates how ETIS operates within a university software engineering course.
The repository will showcase:
- repository-centered engineering
- responsible AI usage
- project lifecycle management
- team-based engineering
- release readiness
- engineering accountability
- evidence-centered learning
Its objective is not to teach students how to complete assignments.
Its objective is to help students practice professional engineering behaviors.
Status: Under development as part of the ETIS educational ecosystem.
ETIS LMU Reference Enterprise¶
The Lakeside Metropolitan University (LMU) reference repository demonstrates ETIS across the complete intelligent systems lifecycle.
Unlike a static example repository, LMU evolves throughout the ETIS framework itself.
Readers will eventually be able to observe how engineering evidence accumulates chapter by chapter.
The repository will demonstrate:
- requirements evolution
- architecture development
- AI governance
- implementation decisions
- reviews and verification
- release readiness
- observability
- incident response
- operational trust
- stewardship
LMU is intentionally designed as an evolving enterprise rather than a finished system.
Status: Under development as a living ETIS reference implementation.
ETIS Publication Repository¶
The publication repository is the authoritative source for the ETIS public ecosystem.
It supports:
- book publication
- website generation
- figures and visual assets
- appendices
- downloads
- educational products
- publication releases
- issue tracking
- continuous improvement
Typical contents include:
- Markdown manuscripts
- MkDocs configuration
- publication assets
- figures and diagrams
- branding resources
- downloadable products
- release history
ETIS Educational Ecosystem Repositories¶
Educational products extend ETIS into classroom and institutional environments.
Educational repositories may support:
- instructor products
- student products
- flagship implementations
- institutional adoption
- educational stewardship
These repositories preserve educational continuity over time.
ETIS Student Starter Kit Repository¶
The Student Starter Kit provides a professional engineering environment rather than a software platform.
Students learn repository-centered engineering without first inventing repository architecture.
The repository separates responsibilities clearly:
docs/ Think
src/ Build
tests/ Verify
data/ Support
scripts/ Automate
Students learn that evidence is as important as implementation.
Inside the LMU / COICP Repository¶
The Lakeside Metropolitan University (LMU) repository serves as the flagship ETIS reference implementation.
The Campus Operations and Incident Coordination Platform (COICP) demonstrates engineering evolution over time.
Readers should be able to observe:
- requirements evolution
- architectural decisions
- planning activities
- implementation evidence
- reviews
- AI governance
- release readiness
- operational governance
- incidents
- postmortems
- stewardship learning
The objective is not to showcase a finished project.
The objective is to demonstrate how engineering evidence accumulates over time.
Repository-Centered Engineering¶
Repository-centered engineering is one of the foundational ETIS concepts.
Repositories preserve:
| Activity | What Is Preserved |
|---|---|
| Requirements | Intent |
| Architecture | Decisions |
| Reviews | Accountability |
| AI Use | Transparency |
| Testing | Verification |
| Releases | Judgment |
| Operations | Reality |
| Postmortems | Learning |
| Stewardship | Continuity |
Repositories connect the entire engineering lifecycle.
Future Repository Assets¶
Future repository assets may include:
- starter repositories
- populated reference implementations
- template libraries
- evidence packages
- governance examples
- review-board resources
- operational toolkits
Repository products will be intentionally curated.
Not every internal artifact will become a public resource.
Related Resources¶
Repository Doctrine¶
Several ETIS principles govern repository-centered engineering:
- Everything important leaves evidence.
- AI proposes; engineers verify.
- Governance is architecture.
- Context is control.
- The model is not the system.
- A demo is not operational proof.
- Educational memory is educational infrastructure.
- Tools change. Engineering behaviors endure.
Bottom Line¶
The ETIS GitHub ecosystem demonstrates how trustworthy engineering work can be organized, reviewed, governed, operated, and continuously improved over time.
The repository is not where engineering ends.
The repository is where engineering continuity begins.