The SWML errors page is much better for retrieval than generic troubleshooting because it exposes stable codes and says where each error appears. Extend that pattern to every product, with structured fields per error (product, phase, severity, where it's observable, likely causes, remediation), and add a global /docs/errors/{error-code} path so an agent can go from a log line straight to the right page. Audit §14.
The SWML errors page is much better for retrieval than generic troubleshooting because it exposes stable codes and says where each error appears. Extend that pattern to every product, with structured fields per error (product, phase, severity, where it's observable, likely causes, remediation), and add a global /docs/errors/{error-code} path so an agent can go from a log line straight to the right page. Audit §14.