Status
This page runs a fresh application and known-answer statistics self-check when it loads. It is live deployment evidence, not independently measured uptime or an SLA.
Application self-check
- Operational
Application runtime
The deployed application executed this check.
- Operational
Statistics engine
Known-answer chi-square calculation passed.
- Operational status
operational- Checked at
- Deployment ID
dpl_7nkBdfxpWfa6U97zLkhmemzVFw7G- Source SHA
81abf87ec4c36a4b431a2abfab4eae1d3e98d9fb- Source branch
main- Application version
0.1.0
Build provenance: metadata only. Build identity fields are deployment-platform metadata, not a verified artifact attestation. A source revision or branch does not prove that deployed bytes came from a clean checkout or contain only that revision.
Trust readiness
This release-readiness signal is separate from the live application self-check. Missing review or publication evidence does not turn an otherwise healthy deployment into a degraded uptime result.
Methods ownership and review
Named, consented statistical ownership and revision-bound independent review evidence is pending.
Python registry alignment
Current evidence that PyPI metadata and release artifacts match the declared package contract is pending.
This summarizes checked-in evidence and does not test external systems at request time. The deployable-foundation build and separate Phase-1 certification command are the authoritative release gates.
What this covers
- The website and server runtime were able to render this request.
- Deployment, source branch, and source revision are reported as platform metadata; they do not attest to a clean checkout or verified artifact.
- The shared statistics engine reproduced a fixed chi-square result.
- The public statistical API uses the same calculation engine.
- Core uploaded-file analysis remains browser-local after the app loads.
Monitoring coverage and limits
Production Web Analytics and Speed Insights measure traffic and field performance. The health endpoint emits privacy-safe structured runtime events. These are useful diagnostics, but they are hosted with the app and do not prove historical uptime.
Vercel Observability is the production monitoring surface for this application. Web Analytics and Speed Insights provide aggregate usage and field-performance signals, while the same-origin error bridge emits content-free application failures.
- Provider
- Vercel Observability
- Monitored target
- https://www.crosstabs.com/api/health
- Check ID
crosstabs-observability
This checked-in configuration does not prove that a particular deployment is connected, receiving events, or alerting correctly. Those facts must be verified in Vercel after deployment. No uptime SLA is implied.
- No respondent rows, project data, prompts, or uploaded files are sent in monitoring events.
- Analytics are aggregate occurrence and performance signals, not account or identity tracking.
- Crosstabs runs the public statistics workspace without a hosted-model runtime.
To report an incident, email support@crosstabs.com.