Public service components

Public website

Pages and interactive tools delivered through Vercel.

Forms and comments

Protected application routes backed by Neon where persistence is required.

Transactional email

Requested delivery through Resend; operational replies through Google Workspace.

Scheduled work

Authenticated Vercel jobs for declared retention and procurement workflows.

Machine-readable point-in-time checks

• Application liveness answers only whether the application process can return a response. It does not test the database or critical user journeys.
• Configuration and database readiness performs bounded configuration, database, and schema checks and fails closed when any check is unavailable.
• A successful response is evidence for that request at that time, not an uptime history, incident declaration, recovery guarantee, or proof that email and every workflow work.

Availability and maintenance

• No default uptime percentage, 24/7 monitoring promise, or recovery-time objective is published as a contractual commitment.
• The source includes scheduled GitHub probes and durable issue creation on failure; activation still requires observed production runs, issue delivery, and a subscribed operator.
• Deployments and maintenance may briefly affect service; customer-specific maintenance windows must be written into an agreement.
• Provider dashboards, logs, alerts, backups, and recovery controls require private operator access and are not exposed here.
• A green build or post-deployment check demonstrates only the checks it ran at that time.

Report an interruption

Email info@kaizenstrategic.ai with the affected page or workflow, the time and timezone, what you expected, and a non-sensitive description of what happened. Do not send passwords, tokens, database records, or personal information in the first message.

If the issue may involve security or privacy, use the private process on the Security page. Response targets and escalation are listed on the Support page.

Activation and next maturity step

Before Kaizen publishes a green status assertion, the independent checks must be deployed, their alert path must be exercised, an incident owner must be subscribed, and observed runs must be retained. Component telemetry, missed-cron alerting, a timestamped incident update process, and an externally hosted status service remain later maturity steps. Until then, this page is an explicit disclosure rather than a coloured uptime dashboard.