Initial commit: NX9 philosophy, architecture, roadmap and website

PHILOSOPHY.md

@@ -0,0 +1,122 @@
+# NX9 Philosophy: Engineering Beyond Frameworks
+
+**A real-world case study in software minimalism, explicit routing, and reduced attack surface**
+
+> "The best way to reduce complexity is not to manage more software—it is to deploy less software."
+
+## Introduction
+
+Modern software engineering often begins with a familiar question:
+
+> "Which framework should we use?"
+
+NX9 begins with a different question:
+
+> "Do we need one at all?"
+
+This is not an argument against frameworks. Frameworks like React, Angular, Laravel, Spring Boot, and Next.js have solved incredibly hard problems and transformed development.
+
+But they solved *specific* problems.
+
+A personal website, a self-hosted utility, an authentication service, a URL shortener, or an infrastructure component rarely requires thousands of JavaScript packages, multiple runtimes, extensive middleware chains, complex build pipelines, and enormous dependency trees simply to deliver its intended functionality.
+
+For many projects, complexity becomes the default — not the requirement.
+
+NX9 deliberately chooses another path.
+
+## Production Snapshot
+
+The observations presented in this article come directly from the production logs of **nx9.in** after its first public deployment.
+
+They are **not** the result of a penetration test, laboratory simulation, or synthetic benchmark.
+
+During the observation period:
+
+- Multiple independent vulnerability scanners began probing the server shortly after public exposure.
+- Automated requests targeted common framework artifacts, PHP files, WordPress installations, Laravel configuration, Vue projects, Docker deployments, and build-system outputs.
+- Every vulnerability probe resulted in **404 Not Found**.
+- Legitimate visitors — including desktop browsers, Android devices, Twitter/X crawlers, search crawlers, and internal users — continued to access the published resources normally.
+
+These observations provide a useful real-world case study of the NX9 engineering philosophy.
+
+## Engineering Beyond Frameworks
+
+NX9 is founded on a simple engineering principle:
+
+> Deploy only the software necessary to solve the problem.  
+> Nothing more.  
+> Nothing less.
+
+Every project within the NX9 ecosystem follows the same philosophy:
+
+- Privacy First
+- Self-Hosted First
+- Linux Native
+- Rust Native
+- Single Binary Applications
+- Explicit Routing
+- Minimal Dependencies
+- Open Source (FOSS)
+- No Vendor Lock-In
+- Operational Simplicity
+
+Frameworks are not avoided because they are "bad."
+
+They are avoided when they solve problems the application simply does not have.
+
+Every dependency should justify its existence.  
+Every abstraction should earn its maintenance cost.  
+Every additional component should provide value greater than the complexity it introduces.
+
+## Complexity Has a Cost
+
+Modern applications are often assembled from enormous dependency trees.
+
+A simple "Hello World" project may involve:
+
+- thousands of npm packages
+- hundreds of transitive dependencies
+- multiple build tools
+- package managers
+- runtime environments
+- framework-specific tooling
+- automated code generation
+
+Each component is individually useful.  
+Collectively, they increase operational responsibility.
+
+Every additional dependency must eventually be:
+
+- installed
+- configured
+- updated
+- audited
+- monitored
+- patched
+- understood
+
+NX9 asks a simple engineering question:
+
+> Can this problem be solved with significantly less software?
+
+If the answer is yes, simplicity becomes the preferred design.
+
+## Real-World Validation
+
+Shortly after **nx9.in** became publicly accessible, automated scanners began probing the server.
+
+The requests were not random. They were highly characteristic of Internet-wide reconnaissance targeting common deployment technologies.
+
+Representative examples included:
+
+```text
+/.env
+/vendor/.env
+/wp-admin/
+/wp-content/
+/phpinfo.php
+/vercel.json
+/vite.config.ts
+/vendors~main.bundle.js
+/vue/
+/v1/admin/