arifos-deploy

# arifOS Deploy — Sovereign Deployment Doctrine Ditempa Bukan Diberi. Every deployment is a thermodynamic state transition. Only deploy what is proven reversible. --- ## Core Invariants (Never Change) These are constitutional-level constraints. No tool, command, or convenience may violate them. ### The Three Surfaces ``` arifOS-fazil.com → Hub (identity, summaries, machine discovery) arifos.arifOS-fazil.com → Docs (full technical content) arifOS:8080/mcp → Runtime (constitutional tool execution) ``` **Role rule:** Hub never hosts full docs content. Docs never hosts hub content. Runtime is never a static site. These boundaries never swap. ### Machine Discovery Invariants Machine-readable files MUST be at root-level stable canonical paths: ``` /llms.txt → LLM context injection (text/plain) /robots.txt → Crawler control /sitemap.xml → Search indexing /.well-known/agent.json → Agent discovery (application/json) /.well-known/ai-plugin.json → Plugin manifest ``` **Rule:** These paths NEVER change. They never route through SPA. They never redirect. They always return correct Content-Type. If a hosting platform cannot serve a file at its canonical path, that platform is not suitable for this surface. ### Content-Type Requirements | File | Content-Type | |------|-------------| | llms.txt | text/plain; charset=utf-8 | | agent.json | application/json | | robots.txt | text/plain | | sitemap.xml | application/xml | **Rule:** Any d...