This page explains which parts of SignalPulse are publicly available and where to verify production-facing behavior. It is not a claim of real-time uptime or live incident reporting.
SignalPulse currently publishes product docs, reference scenarios, and runtime behavior details. If you later need live operational monitoring, add a dedicated source of truth rather than a static uptime claim.
Decision API for `/check`, `/health`, and policy design metadata.
Public docs describe request validation, quota behavior, request IDs, policy versions, and fail-closed integration expectations.
Customer dashboard for API keys, logs, analytics, billing, and docs.
This site documents product surfaces and operational behavior, but it does not publish a live uptime feed from the app itself.
Quickstarts, runtime contract, and production behavior references.
Use the docs as the source of truth for buyer-facing platform behavior and integration patterns.
This page is not a live uptime monitor
It is a public overview of what is available and where production behavior is documented. It does not claim real-time operational telemetry.
Production behavior belongs in docs and runtime responses
For real implementation guarantees, verify `/docs#production`, `/docs#contract`, and actual API responses such as `request_id`, `policy_version`, quota errors, and fail-closed handling.
Incident communication should be explicit
If you later add a true status feed, it should come from a real incident workflow or monitoring backend, not from hardcoded page copy.
Need production behavior details? Start with production docs and 執行契約.
For support, contact [email protected]