Verified behaviour across the specified components in a bounded local, non-production demonstration chain.
Status and readiness
Honest about what is connected.
This page describes the state of the public website, its adapters and the engineering registers behind the maturity labels. It is not a live control-plane status board, and it will not report a healthy platform when nothing is connected.
Live probe
What the status adapter actually returns.
The panel below calls the same-origin adapter. If the backend is unconfigured, the adapter returns HTTP 503 and this page displays that state. A failed or unconfigured response is never converted into a healthy one.
Live probe · same-origin adapter
Backend status API
Checking the website’s status adapter…
This panel probes only the website’s own status adapter. It is not live control-plane telemetry and cannot verify the health of NiGeNje platform services.
Read this first
This is not live control-plane telemetry. The probe checks the website’s own adapter, not the NiGeNje platform. It cannot verify that admission, mediation or any backend service is running, and no production availability is measured by this page.
Integration state
What is configured, and what is not.
Status statements should be specific enough to act on. These are the surfaces this site actually depends on.
| Surface | State | What that means |
|---|---|---|
| Public website | Implemented source · pre-product | Pages are built from the current source. No control-plane data is rendered, and no production readiness is implied by the site being reachable. |
| Backend status API | Unconfigured · HTTP 503 | /api/status returns an unconfigured response until a verified public HTTPS backend and response contract exist. It does not invent a healthy state. |
| Intake receiver | Configured · george@nigenje.com | /api/design-partner validates the request, applies same-origin, size, honeypot and Turnstile checks, then delivers to the confirmed receiver george@nigenje.com. Delivery transport: not provisioned yet (HTTP 503, nothing stored or forwarded). /api/design-partner GET reports the receiver and transport without exposing credentials. |
| Human verification | Enabled · Cloudflare Turnstile | Intake forms use a Cloudflare Turnstile challenge verified server-side. Passing the challenge is only an anti-abuse control: it does not itself deliver a request, and delivery depends on the transport state shown above. |
| Public status adapter | Probe only | When a backend is configured, the adapter relays an upstream response. That is adapter data, not a health verdict and not live control-plane telemetry. |
| Deployment | Cloudflare · nigenje.com (deployed) | The canonical origin is deployed on Cloudflare Workers. This records the deployment target; no uptime, latency or availability measurement is claimed. |
Platform maturity
What the engineering registers currently record.
Maturity is read from the product and platform registries. “Integrated” means verified in a bounded, non-production demonstration chain. It is never a production qualification, and no component is marked qualified.
A working development demonstration exists.
Confirmed implementation exists.
Implementation or integration is underway.
Product registry
20 product surfaces are tracked, with 7 marked integrated in the local chain. Every entry carries an evidence note and a stated limitation.
Platform registry
22 components and logical responsibilities are tracked across the lifecycle, from intent to conformance. Logical responsibilities are not presented as separately deployable services.
Maturity labels describe engineering state, not service availability. See technical resources for the documentation, research and evaluation material behind these labels.
Deployment
A target, not an availability claim.
www.nigenje.com
The canonical public origin for this site. Metadata, sitemap and canonical links are anchored to it, and the implementation is deployed here. Uptime, latency and availability are not measured on this page.
Cloudflare
The deployment target is Cloudflare for www.nigenje.com. Edge behaviour, caching and any provider-level security controls are configuration to verify per deployment.
Measurement boundary
No uptime, latency, error rate or availability figure is published on this page. Those are production measurements, and the platform is pre-product. Where a number is not measured, the page does not display one.
Questions about status
If a status claim matters, ask for the evidence.
The status page deliberately publishes no invented uptime figure and no production assurance. For an evaluation, ask what was tested and in which environment.