Release
| Field | Value | Canonical record |
|---|---|---|
| Version | 1.4.0 | — |
| Build date | 2026-08-05 | — |
| Architecture | Root-deployable static HTML, CSS, JavaScript and public data | — |
| External runtime dependencies | None for public rendering | — |
| Package verification | Structural, browser, Apache, source-license and package-inventory evidence | — |
| Live monitoring | Not configured by this static package | — |
What this status means
The national status labels shown across the portal are configured civic records. Package assurance records describe tests performed against this release. Neither is a measurement of live server uptime, latency, traffic, storage, compute capacity, incident state, operational readiness or combat capability.
Implemented
- Multipage national information architecture and core national routes
- Canonical country, region, institution, protocol, constitutional, defense, foundational-document, assurance and history data
- Accessible SVG topology with semantic HTML equivalent
- First-party static search and synonym mapping
- Open JSON/CSV data catalog and stable state APIs
- Public Assurance Evidence Registry with claims, evidence hashes, reviewer class, limitations, invalidation and supersession
- System-font design system, responsive layouts and print styles
- Security header configurations for Apache and edge hosts
- Automated structural, link, package, browser and shared-host checks
Defense publication registry
| Field | Value | Canonical record |
|---|---|---|
| Portal route inventory | Generated public route register | Open record |
| Defense notices | 7 | Open record |
| Doctrine revisions | 3 | Open record |
| Foundational documents | 1 | Open record |
| Current doctrine record | EVI-DR-003 | Open record |
| Notice API | Versioned static JSON | Open record |
| Revision API | Versioned static JSON | Open record |
The publication registry is not an incident monitor. It preserves current, scheduled, historical and superseded public documents with dates, authority, classification, correction routes and reciprocal supersession links.
Public assurance registry
| Field | Value | Canonical record |
|---|---|---|
| Assurance claims | 6 | Open record |
| Evidence artifacts | 6 | Open record |
| Current integrated claim | EVI-AC-006 | Open record |
| Reviewer class | repository-automated | — |
| Certification status | Not independent certification | — |
| Claims API | Versioned static JSON | Open record |
| Evidence API | Versioned static JSON | Open record |
Each assurance record names its exact package scope, test environment, method, result, limitations, invalidation conditions and unavailable fields. The registry does not expose live incidents, targets, private topology, credentials, operational thresholds, vulnerabilities or weapon configuration.
Shared-host compatibility
Release 1.4.0 uses an Apache .htaccess profile limited to commonly permitted FileInfo-class directives. It avoids directory-level directives that some shared-host accounts reject with HTTP 500.
Clean directory routes are resolved through rewrite rules, direct requests to internal source paths are denied, and directories without a public index.html are not listed.
Host acceptance and recovery
After upload, verify the homepage, this route, the Constitution, public assurance routes and APIs, a protected internal path and a deliberately missing URL.
curl -I https://eviulon.com/
curl -I https://eviulon.com/technical-status/
curl -I https://eviulon.com/state/constitution/
curl -I https://eviulon.com/state/defense/assurance/
curl -I https://eviulon.com/state/defense/assurance/evidence/
curl -I https://eviulon.com/api/assurance.json
curl -I https://eviulon.com/api/assurance-claims.json
curl -I https://eviulon.com/api/assurance-evidence.json
curl -I https://eviulon.com/.uai/index.uai
curl -I https://eviulon.com/not-a-real-resourceExpected results are HTTP 200 for public routes and APIs, HTTP 403 for internal memory/source paths, and HTTP 404 for the missing public route. If the entire site returns HTTP 500 after upload, temporarily rename .htaccess, confirm whether ordinary HTML loads, restore this release's compatibility file and inspect the host error log. Do not leave the site without equivalent access controls and security headers.
Not implemented
- Live defense telemetry, incident feed or readiness dashboard
- Operational weapon, targeting or offensive cyber interfaces
- Independent external certification
- Live diplomatic submission, citizenship registration or authentication
- Production analytics, uptime monitoring or field performance telemetry
- Host-level TLS, HTTP/3, CDN or multi-region failover
- Formal native assistive-technology conformance certification
Validation evidence
The package contains local proof under docs/proof/ and public evidence statements under docs/proof/assurance/. Read each artifact's scope and limitations before relying on a PASS result.
Open assurance claims · Open evidence artifacts · Read the validation report
Monitoring
No live monitor is embedded in this page. A production operator should configure independent checks for uptime, certificate expiry, response headers, sitemap routes, APIs and 404/500 rates, then publish only verified measurements with an explicit source and observation period.
Authority and record status
Responsible authority: National Engineering Directorate.
Configured state labels and package proof are static records. Live health and operational readiness require separately authorized monitoring and evidence.
Revision date: . Public corrections may be initiated through the diplomatic contact route.