Deployment boundaries
Runtime is in development. These guides explain design intent; they are not a released API or installation reference. Read the release policy →
The public website is static
Section titled “The public website is static”This site builds with Astro and Starlight into static files. A web server serves HTML, CSS, JavaScript, images, and the browser search index. It does not need a database, persistent application backend, or server-side Node.js runtime.
The intended public origin is https://zernova.et/, with documentation initially at /docs/. Actual launch and hosting changes require owner approval and verified TLS.
Runtime deployment is a different concern
Section titled “Runtime deployment is a different concern”No public Runtime installation package, server prerequisites, container image, or deployment command is documented here. A future guide must establish the named release, tested Java and OS versions, resource requirements, configuration, secrets, network boundaries, startup/shutdown behavior, and recovery procedure.
Serving these docs successfully does not validate a Runtime installation.
Planned product boundaries
Section titled “Planned product boundaries”A future customer account portal and Cloud control plane will be separately deployed services. They must not place credentials, private configuration, or execution controls inside this public website’s static bundle.
Subdomains for docs, downloads, accounts, and cloud are only a migration idea. These docs do not assert that those hosts exist or create DNS records.
Portability needs evidence
Section titled “Portability needs evidence”Cloud-neutrality is an architectural goal. Each supported environment still needs its own verification of networking, identity, trust, storage, operational limits, and rollback. Ethio telecom TeleCloud is the first intended Cloud hosting environment, not an available service or partnership claim.
See release lifecycle before treating any deployment example as supported.