Anthony Luo will be reformatting the document soon.
Operating principles, guidelines, āhow-toāsā should live in subteam spaces and be linked in as references or supporting documentation to the arch document
Year-by-year (year specific) decisions & explanations should live as subpages
top-level should really be a āhereās what the system is and what it does and how to use itā
not āwhy did we do thisā but āhereās what this doesā.
Should let someone who is new to the team or new to integration see what goes together and how it goes together with minimal complexity.
This top-level will later be copied-pasted as a āoperators guideā (maybe split up into sub-pages) into the sysint space.
should link to other docs with justifications
Document to be updated continually at the top-level. Subsystems may keep changelogs as sub-pages (theyāre revisioned in history regardless, but it can be hard to search through)