Latest Changes Model
This page explains how the documentation system should update itself.
Auto-update principle
The portal should not rely on hand-editing every navigation page forever.
Instead:
- specs live in versioned files
- diagrams live in text form
- GitHub Actions rebuild the portal on repo changes
- indexes and summaries can be regenerated automatically later
Current state
At the moment, this page is a manual placeholder.
Target automated behavior
On push to main:
- install docs portal dependencies
- build the portal
- validate internal links
- publish or upload artifact
- later: generate a latest-changes summary from commit history or changed docs paths
Candidate future automation
- auto-regenerate file index from
/docsand/docs-portal/docs - auto-regenerate a “changed files / changed systems” dashboard
- auto-open docs TODO issues when new spec files land without portal links
Canonical source
GitHub remains the source of truth. Automation regenerates the portal from that source.