Maintainers¶
Choose the contract for the documentation or repository surface you maintain. To learn an algorithm as a user, go to the algorithm tutorials.
Documentation¶
| Task | Canonical guide |
|---|---|
| Decide where content belongs and preserve existing links | Documentation architecture and content map. |
| Maintain generated API pages and compatibility bookmarks | Maintaining API documentation. |
| Update an algorithm lesson, source example, or result figure | Maintaining algorithm tutorials. |
| Update T01–T03, their shared template, downloads, and observed output | Maintaining fundamental tutorials. |
| Update T06–T08, retained measurements, figures, and the recorded report | Maintaining study tutorials. |
| Build a preview, preserve release archives, or publish | Documentation delivery. |
| Understand domains and hosting | Hosting and domains. |
Validation and releases¶
| Task | Canonical guide |
|---|---|
| Choose and run validation gates | Testing and validation. |
| Check public typing contracts and the development baseline | Typing policy. |
| Change module boundaries or repository structure | Architecture Health and Repository hygiene. |
| Validate a package release | Release verification. |
| Understand ownership and release policy | Repository governance. |
For implementation work, start with Extending VAMOS. The Roadmap remains the first entry in Developer and records the project's direction.