ES-100 — Start Here¶
You are here¶
You are at the entrance to the ETIS Engineering Platform.
This stage does not ask you to design, build, test, deploy, or govern a system yet. It prepares you to do those things deliberately.
Most engineering problems do not begin with code. They begin with uncertainty:
- What problem are we solving?
- Where should engineering evidence live?
- Which decisions have already been made?
- What should happen next?
- What does “done” mean?
- How should AI assistance be used without surrendering engineering judgment?
ES-100 reduces that uncertainty before real project work begins.
Why this stage exists¶
Traditional starter repositories often provide a README, a few folders, and a set of templates. That is not enough for serious engineering work.
A trustworthy intelligent system requires more than files. It requires a disciplined engineering environment where:
- work is organized,
- decisions are traceable,
- evidence is preserved,
- reviews are intentional,
- AI assistance is controlled,
- and engineers can tell where they are in the lifecycle.
The ETIS Starter Kit is therefore not merely a document package. It is an engineering platform.
ES-100 teaches you how to use that platform.
The engineering question¶
Every Engineering Stage answers one engineering question.
How is engineering work organized within the ETIS Engineering Platform?
That is the only question this stage is responsible for answering.
You are not expected to master ETIS here. You are expected to understand how the platform works well enough to begin ES-101 without confusion.
What you will learn¶
By the end of ES-100, you should be able to:
- explain the purpose of the ETIS Engineering Platform;
- describe how engineering work is divided into stages;
- navigate the Starter Kit repository;
- distinguish engineering artifacts from engineering evidence;
- understand why Repository-Centered Engineering matters;
- understand why Evidence-Centered Engineering matters;
- use the platform without waiting for tribal knowledge;
- complete the readiness gate and continue to ES-101.
What you will not do yet¶
ES-100 intentionally avoids premature complexity.
You will not yet:
- define the system vision;
- write requirements;
- estimate work;
- design architecture;
- create implementation plans;
- configure CI/CD;
- create operational runbooks;
- write governance evidence;
- approve AI delegation.
Those activities belong to later stages.
This stage exists so you can reach those later stages with orientation, confidence, and discipline.
Required reading order¶
Follow this order the first time through ES-100:
- This README — understand the purpose of the stage.
- Navigation — learn how to move through the platform.
- First Day Guide — complete the practical onboarding path.
- Engineering Journey — understand the lifecycle.
- Engineering Principles — learn the platform doctrine.
- Stage Map — see the full ES-100 through ES-114 progression.
- Glossary — review the shared language.
- Readiness Gate — verify that you are ready to continue.
- Stage Manifest — review the structured stage contract.
Experienced engineers may skim, but should still complete the readiness gate.
Core idea¶
ETIS organizes engineering work around evidence.
A conversation with an AI assistant is not evidence. A decision discussed in a meeting is not evidence. A design that lives only in someone’s memory is not evidence.
Evidence is something durable, reviewable, and located in the repository.
Examples include:
- a vision brief;
- a requirements decision record;
- an architecture decision record;
- a risk assessment;
- a test result;
- a release readiness record;
- a postmortem;
- an AI-use log.
The repository becomes the memory of the engineering effort.
Repository-centered engineering¶
Repository-Centered Engineering means the repository is not merely where code is stored.
It is where the engineering system lives.
The repository contains:
- source code;
- engineering artifacts;
- decision records;
- governance evidence;
- review materials;
- test evidence;
- operational records;
- release evidence;
- stewardship history.
When important engineering work happens, the repository should eventually reflect it.
Evidence-centered engineering¶
Evidence-Centered Engineering means important engineering claims should be supported by artifacts that can be inspected.
A team should not merely claim that requirements were reviewed. The repository should contain the review evidence.
A team should not merely claim that risks were considered. The repository should contain risk analysis.
A team should not merely claim that AI assistance was controlled. The repository should contain AI-use evidence and verification records.
Trustworthy systems are not built on confidence alone. They are built on disciplined evidence.
AI assistance in this platform¶
AI can help engineers move faster, but AI does not replace engineering responsibility.
AI proposes; engineers verify.
The model is not the system. The prompt is not the process. The generated answer is not the evidence.
AI can help draft, summarize, compare, critique, test, and explore alternatives.
In this platform, AI-generated work is acceptable only when engineers understand, review, adapt, and verify it.
What ES-100 produces¶
ES-100 produces readiness, not project deliverables.
After this stage, you should have:
- read the orientation materials;
- understood the platform structure;
- located key resources;
- understood how stages work;
- understood where evidence belongs;
- completed the readiness gate;
- identified ES-101 as the next stage.
The expected output is not a document. The expected output is an engineer who knows how to begin.
Do not treat the Starter Kit as a folder of templates to fill out mechanically.
The templates support engineering judgment. They do not replace it.
A completed template without real thought is paperwork. A concise artifact that captures a real decision, tradeoff, review, or piece of evidence is engineering.
A good engineering platform reduces cognitive load without reducing rigor.
ES-100 should make the work feel clearer, not easier in a superficial way. The rigor remains. The confusion is removed.