MANSOQ Integration boundary · STATIC DECLARATIONS
MANSOQ System Diagnostics integration boundary
Source boundary for MANSOQ System Diagnostics: 0 Python backend mappings, 2 client declarations and 0 service routes. Installation, mounts and production qualification require verification.
Static API contract — behavior review pending. Source baseline 76620b8342ef.
Enable JavaScript to inspect structured operation, parameter, schema and permission evidence and download this complete JSON reference. The article text and source links are available below.
Declared component boundary
separate repository / optional app or service. Repository and route declarations do not prove this component is installed, enabled, certified or compatible with the current deployment.
Routes and installation
Plugin routes use their local URL declarations under the deployment-selected mount. Alternative core routes must not be combined as if simultaneously active.
Documentation evidence
- Features
- Printable Resources Check
- Print Templates Validation
- Network Diagnostics
- Plugins & Apps
- Backend Health Monitoring
- Configuration Audit
- Media Device Testing
- Printer Testing
- System Information
Review status
This article establishes repository/contract boundaries and does not prove installed capability, production credentials, regulator acceptance, security completeness or a validated click-by-click workflow.
Pinned source evidence
Links require access to the private source repository.