Repository navigation
Incident and Status Page
How platform health is surfaced and how incidents are communicated.
Platform status is published via a status page (OpenStatus). It gives users and integrators a single place to see uptime and any ongoing incidents.
Today, incidents are largely posted manually. Issue #1608 tracks automating status-page incidents via an OpenStatus agent webhook — so a detected outage opens (and updates) an incident without a human copy-pasting. This closes the loop between monitoring and public communication.
- Application quality/security signals flow through SonarCloud, CodeQL, and Aikido — see Code Quality Gates and Security.
- Realtime/backend health during an incident: see Realtime Setup for what is actually wired today (Stream chat, BullMQ workers) versus designed-only.
Security vulnerabilities are not handled through the status page — follow the confidential process in Security.
Home · Architecture · ADRs · Plans · Roadmap · Contributing · Main repo · DeepWiki · Discord
Yosemite Crew is a product of DuneXploration UG (haftungsbeschränkt). This wiki mirrors the repository; where a page and the repo disagree, the repo wins. See the Wiki Style Guide.
Product & Domain
Architecture
Applications
- Backend — Overview
- Frontend / PIMS Web — Overview
- Mobile — Overview
- Desktop PIMS Shell
- Developer Portal
- SuperAdmin
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Meta
Canonical code & docs: main repo · Auto-generated companion: DeepWiki