What is the ETIS Engineering Platform?¶
Purpose¶
The ETIS Engineering Platform is a repository-centered engineering environment for building trustworthy intelligent systems.
It combines Engineering Stage guidance, reusable templates, completed examples, project workspace conventions, evidence-centered engineering practices, and governance expectations in one practical starter kit.
Why it exists¶
Modern intelligent systems fail when teams treat trust as something that can be added after the fact.
ETIS starts from a different assumption:
Trustworthiness must be engineered through decisions, evidence, review, operation, and stewardship.
The platform helps teams do that work consistently.
What the platform includes¶
Engineering Stages
ES-100 through ES-114 guide a team from orientation and vision through requirements, design, implementation, release, operations, monitoring, and stewardship.
Reusable Templates
Templates give teams starting structures for evidence artifacts without pretending that templates alone create trust.
Reference Examples
LMU/COICP examples show what completed engineering evidence can look like across the lifecycle.
Project Workspace
docs/project-workspace/ is the cloned-project working area where completed evidence, decisions, reviews, risks, and stewardship records belong.
Why the repository is structured this way¶
The Starter Kit is published with MkDocs, so docs/ is the documentation root. That means project evidence cannot be described as living directly under docs/ without confusing publication files with project-workspace files.
For a cloned Starter Kit project, the working evidence area is:
docs/project-workspace/
That separation keeps the platform readable, the templates reusable, the examples stable, and the project evidence clearly bounded.
What makes it different¶
ETIS is not only about AI policy, documentation, code quality, or governance checklists.
It connects those concerns into one engineering system.
Intent
↓
Requirements
↓
Architecture
↓
Design
↓
Implementation
↓
Verification
↓
Release
↓
Operation
↓
LearningEvery important step leaves evidence in the project workspace.
Who should use it?¶
| Audience | Use |
|---|---|
| Engineers | Build systems with traceable decisions and reviewable evidence. |
| Architects | Preserve design intent, constraints, guardrails, and governance concerns. |
| Instructors | Teach disciplined software engineering in the AI era. |
| Organizations | Adopt a practical operating model for trustworthy intelligent systems. |
| Reviewers | Evaluate whether claims are supported by evidence. |
When not to use it¶
Do not use the platform as a paperwork exercise.
If a team is only filling templates to satisfy appearance, it is missing the point. ETIS is valuable when the evidence changes engineering judgment, improves review, clarifies risk, or strengthens operation.
Do not confuse having artifacts with having evidence. Evidence must be completed, connected, reviewed, and useful.
The repository is not storage. It is the engineering memory of the system, and the project workspace is where that memory is written.