0
No active public advisory in this snapshot
Operational catalogue
Known clearly.
Handled deliberately.
A public, reviewed view of product errors, technology dependencies and operational changes across Kaos Modularity.
Catalogue available
This is a reviewed catalogue, not the future live service-status page.
3
Portal, mobile application and public sites
05.11
Versions checked against repository manifests
What belongs here
Only information that helps customers understand product behaviour and maintenance decisions. Internal endpoints, credentials, bindings, administrative tooling and unreviewed diagnostics never belong in the public catalogue.
What this is not
This is not a support forum, a vulnerability-submission form or a live uptime dashboard. Those responsibilities can grow independently later.
Product Errors
Reviewed product notices
Known behaviour becomes public only after impact, workaround and resolution status are verified.
Publication model
| Field | Public meaning |
|---|---|
| Impact | What the user can actually observe. |
| Affected surface | Portal, mobile or a named public site. |
| Workaround | A safe temporary action, when one exists. |
| Status | Investigating, identified, fixed or monitored. |
Runtime & SDKs
Execution foundations
Major runtimes and monitoring SDKs that materially affect product behaviour.
| Surface | Runtime / SDK | Current | State |
|---|
Dependencies
Software supply chain
A focused public subset of libraries with direct operational relevance.
| Product | Dependency | Current | Purpose |
|---|
External Services
Managed connections
Third-party services grouped by responsibility, without exposing tenant configuration or internal identifiers.
| Category | Services | Role |
|---|
Infrastructure
Public architecture boundary
Enough detail to explain responsibility, never enough to disclose private topology.
CF
Public applications and Workers
D1 / R2
Managed relational and object storage
EU
Filtered diagnostics and reviewed telemetry
Deliberately limited
Regions, bindings, administrative hosts, backup routes and internal repository topology are omitted.
Releases
Verified change history
Only releases with a confirmed distribution boundary appear in the public timeline.
Security
Reviewed security notices
Security information is disclosed when it is accurate, actionable and safe for customers.
Privacy boundary
The catalogue stores no customer account, IP address, crash payload or submission. Operational evidence remains in the systems responsible for collecting and protecting it.
Catalogue search