Finalize artifact records
Remove sample artifact records and publish only verified release files, package records, checksums, manifests, reports, known issues, and rollback notes.
Publication checklist for the static platform.
This page defines the minimum checks before the website is published as a real SentinelOS public trust platform.
Configure host root
Upload the static site root exactly as packaged. Confirm `index.html`, `404.html`, `_headers`, `_redirects`, `robots.txt`, `sitemap.xml`, and asset paths resolve from the same public origin.
Apply security headers
Use the staged `_headers` / `netlify.toml` rules or equivalent host settings for content type protection, referrer policy, frame blocking, permissions policy, and a conservative static-site CSP.
Set cache boundaries
Cache images, CSS, and JavaScript longer than HTML. Keep HTML and metadata easier to refresh so release status can be corrected quickly.
Publish trust material
Provide release notes, SHA256SUMS, signature instructions, package manifests, validation reports, and signing-key guidance when available.
Run static checks
Check links, keyboard navigation, reduced-motion handling, print output, responsive layout, security headers, and local preview before uploading.
v0.9.5 deployment files
Static host configuration now travels with the site.
`_headers`
Header policy baseline for static hosts that support root header files, including CSP and privacy-focused browser controls.
`_redirects`
404 fallback rule for static hosts that support redirect files while preserving explicit page URLs.
`netlify.toml`
Netlify-compatible deployment metadata and header policy mirror for easy static publication.
Local preview
Preview before publishing.
The platform stays portable and can be tested with a local static server.
python3 -m http.server 8080
# then open http://localhost:8080Deployment boundary
Keep the site static unless a feature truly requires otherwise.
No required account
Downloads, docs, verification, and package records should remain accessible without login.
No cloud control
The website should not manage SentinelOS installations or push remote policy to user systems.
No hidden telemetry
Any future analytics must be privacy-safe, disclosed, and unnecessary for core platform use.