GitHub Repository Ecosystem¶
Repository-centered engineering in practice
Engineering Trustworthy Intelligent Systems is built on a central principle:
Every important engineering activity leaves evidence.
The ETIS repository ecosystem exists to demonstrate how trustworthy engineering work can be organized, reviewed, governed, operated, and continuously improved through repository-centered practices.
The repositories associated with ETIS are intended to support readers, students, instructors, engineers, architects, technical leads, review boards, and organizations applying the framework.
Repository links will be published as they become available.
Repository Ecosystem Overview¶
The ETIS ecosystem is designed around four complementary repository families:
ETIS Publication Repository¶
The publication repository contains the book and website source materials.
Purpose:
- Maintain the ETIS publication system
- Support website generation and updates
- Preserve figures, appendices, and publication assets
- Track corrections and improvements
- Provide transparent publication history
Typical contents include:
- Markdown manuscripts
- MkDocs configuration
- Figure assets
- Branding assets
- Website resources
- Publication releases
- Issue tracking
- Change history
ETIS Student Starter Kit¶
The Student Starter Kit provides a complete repository structure for software engineering courses and project teams.
Its purpose is to help students learn repository-centered engineering without first inventing repository architecture.
Planned artifacts include:
- Requirements templates
- Use case templates
- User story templates
- Architecture Decision Records (ADRs)
- Planning artifacts
- Work Breakdown Structures (WBS)
- Review logs
- AI-use logs
- Test evidence records
- Release-readiness records
- Postmortem templates
- Runbook templates
- Governance records
The starter kit is intended for undergraduate, graduate, and professional education environments.
LMU / COICP Reference Repository¶
The Lakeside Metropolitan University (LMU) repository serves as the primary ETIS reference implementation.
The repository follows the evolution of the Campus Operations and Incident Coordination Platform (COICP) throughout the lifecycle presented in the book.
Unlike a finished project showcase, the LMU repository is intended to demonstrate engineering progression.
Readers should be able to observe:
- Requirements evolution
- Architectural decisions
- Planning activities
- Implementation evidence
- Review records
- Verification activities
- Release preparation
- Operational governance
- AI oversight
- Incident response
- Postmortem learning
- Continuous improvement
The repository acts as a practical example of how trustworthy engineering evidence accumulates over time.
Instructor Repository¶
A dedicated instructor repository is planned to support classroom adoption.
Potential materials include:
- Lecture slides
- Assignment packages
- Project launch materials
- Team exercises
- Review-board simulations
- Assessment rubrics
- Sample artifacts
- Teaching guides
- Course schedules
- Repository-centered engineering exercises
Instructor materials may be distributed separately from public resources.
Repository-Centered Engineering¶
The repositories are not supplements to ETIS.
They are part of the framework itself.
Within ETIS:
- repositories preserve engineering memory,
- reviews preserve accountability,
- evidence preserves trust,
- governance preserves control,
- operations preserve learning.
The repository becomes the durable system of record that connects decisions, artifacts, outcomes, and organizational knowledge across the full lifecycle of a system.
Future Releases¶
Future repository releases may include:
- downloadable templates,
- populated project examples,
- governance toolkits,
- review-board resources,
- AI governance examples,
- operational readiness packages,
- stewardship review materials,
- course support materials,
- certification preparation resources,
- framework updates.
As the ETIS ecosystem expands, repositories will continue to serve as the primary location for engineering evidence, reusable artifacts, and framework implementation guidance.