Navigation¶
Purpose¶
This page explains how to move through ES-100 and the larger ETIS Engineering Platform.
Navigation is part of the engineering experience. If engineers cannot determine where they are, what they have completed, and what comes next, the platform has failed before engineering work begins.
The ES-100 path¶
Complete ES-100 in this order:
README
↓
navigation.md
↓
first_day_guide.md
↓
engineering_journey.md
↓
engineering_principles.md
↓
stage_map.md
↓
glossary.md
↓
readiness_gate.md
↓
stage_manifest.md
↓
ES-101
This order is intentional.
It moves from orientation, to action, to lifecycle understanding, to principles, to terminology, to readiness.
How every stage works¶
Every Engineering Stage follows the same basic pattern:
- Orient — understand where you are.
- Focus — understand the engineering question.
- Act — perform the stage activities.
- Produce evidence — store the results in the repository.
- Review readiness — confirm that the stage is complete.
- Advance — continue to the next stage.
The goal is predictable engineering movement.
You should never wonder whether a stage is finished. The readiness gate tells you.
Page-level navigation convention¶
Every ES-100 page provides:
- the current stage;
- the current page;
- the previous page;
- the next page;
- related resources where useful;
- a clear final action.
No page should end without telling you what to do next.
Repository navigation convention¶
The Starter Kit separates different kinds of work.
A typical project may contain areas such as:
/docs
/vision
/requirements
/planning
/architecture
/design
/implementation
/testing
/release_evidence
/operations
/governance
/stewardship
/engineering
/ES-100
/ES-101
/ES-102
...
/ES-114
/templates
/vision
/requirements
/architecture
/evidence
/governance
/examples
/lmu-coicp
The exact repository may evolve, but the principle remains stable:
Engineering artifacts should live where future engineers can find, review, and reuse them.
How to know where something belongs¶
Use this rule:
- If it explains the platform, it belongs under
engineering/. - If it is a reusable blank structure, it belongs under
template-library/. - If it is a completed illustration, it belongs under
examples/. - If it records project-specific engineering work, it belongs under
docs/. - If it supports publication, it belongs under the documentation site structure.
- If it is source code, it belongs in the project implementation area.
When in doubt, place engineering evidence where it will be easiest for reviewers to inspect later.
Navigation and evidence¶
Navigation is not only about convenience. It supports evidence.
A reviewer should be able to move from:
Stage → Activity → Artifact → Evidence → Readiness Gate → Next Stage
That movement is what makes the engineering process traceable.
Common pitfall¶
Do not create new folders simply because a topic feels important.
A repository with too many ad hoc locations becomes harder to govern. Prefer established locations and clear naming conventions.
Engineering insight¶
Good repository navigation is a form of engineering governance.
When the structure is predictable, teams spend less time searching and more time making decisions.