Leios design: Re-organize chapters and seed technical design with impact analysis #601
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Different order of chapters to front-load any considerations about implementation plan and realize that the
Technical design(formerly "Architecture", which is a section in this chapter now) is going to be refined as development progresses.I have used key content of the impact analysis to "seed" the relevant sections, following the same group and topic-based sections within each group/layer.
Does this make sense?
Rendered and built leios-design.pdf
New outline:

etc.
If this sticks, we might want to mark the impact analysis as "superseded" and absorb all the relevant parts into this single document?