diff --git a/features-guide/anti-extraction-philosophy.md b/features-guide/anti-extraction-philosophy.md
new file mode 100644
index 0000000..af5ff01
--- /dev/null
+++ b/features-guide/anti-extraction-philosophy.md
@@ -0,0 +1,80 @@
+# Anti-Extraction Philosophy
+
+The Lilith Platform is built on an anti-extraction philosophy that fundamentally rejects the economic model used by creator platforms like OnlyFans, Chaturbate, and traditional agencies. Instead of extracting value from creators through commissions, the platform empowers creators to own their entire economic relationship.
+
+## Zero-Commission Model
+
+The core anti-extraction principle: **creators keep 100% of their earnings**.
+
+| Platform | Commission | Creator Take Rate |
+|----------|-----------|-------------------|
+| **Lilith** | **0%** | **100%** |
+| OnlyFans | 20% | 80% |
+| Chaturbate | 40-50% | 50-60% |
+| Traditional agencies | 30-70% | 30-70% |
+
+This zero-commission model is not a promotional offer — it is the foundational economic architecture. The platform sustains itself through client-funded subscriptions, not creator extraction.
+
+## How Anti-Extraction Works in Practice
+
+### Revenue Without Extraction
+
+The platform generates revenue from **client subscriptions**, not creator commissions:
+
+- **Clients pay** monthly subscription fees for premium features (messaging, booking, search filters)
+- **Creators pay nothing** — no listing fees, no commission, no payment processing surcharges
+- **No hidden extraction** — no "promoted listing" upsells that create a pay-to-play dynamic
+
+### Creator Ownership and Empowerment
+
+Anti-extraction extends beyond zero commissions to full creator empowerment:
+
+- **Portable reputation** — creators can export their ratings, reviews, and verification data
+- **No lock-in** — platform does not own creator content, profiles, or client relationships
+- **Data sovereignty** — GDPR-first design means creators control their personal data
+- **Independent business** — creators are independent operators, not platform employees
+
+### Economic Sovereignty
+
+The anti-extraction philosophy ensures creators maintain economic independence:
+
+- **Direct payments** — client payments go directly to creators, not through a platform-controlled wallet
+- **No extraction fees** disguised as "processing fees" or "platform maintenance"
+- **Transparent pricing** — session rates set by creators, not algorithmically manipulated
+- **No surge pricing** — the platform never adjusts creator rates based on demand
+
+## Why Anti-Extraction Matters
+
+Traditional creator platforms extract 20-50% of earnings, creating a power imbalance:
+
+1. **Dependency** — High commissions make creators dependent on platform volume
+2. **Race to bottom** — Platforms incentivize lower prices to maximize transaction volume (and their cut)
+3. **Value capture** — The platform captures the value creators generate through their work
+
+The anti-extraction approach inverts this:
+
+1. **Independence** — Zero commission means creators keep their full economic value
+2. **Quality focus** — No volume incentive means creators set sustainable rates
+3. **Creator-first** — Platform success is measured by creator prosperity, not platform extraction
+
+## Icelandic Jurisdiction and Anti-Extraction
+
+The platform is registered in Iceland specifically to reinforce anti-extraction principles:
+
+- **Strong labor protections** — Icelandic law favors worker rights
+- **GDPR enforcement** — European privacy standards prevent data extraction
+- **Cooperative tradition** — Iceland's economic culture aligns with creator ownership models
+- **Regulatory stability** — Predictable legal framework for sex work platform operations
+
+## Integration with Platform Features
+
+Anti-extraction principles are enforced throughout the platform:
+
+- **Escrow system** — Protects creators from non-payment, not used to hold creator funds
+- **Dispute resolution** — Favors creator autonomy in payment disagreements
+- **Financial coercion detection** — Monitors partnership profiles to prevent one partner extracting from another
+- **Transparency reporting** — Platform publishes creator-facing economics (no hidden fees)
+
+---
+
+**Last Updated**: 2026-02-18
diff --git a/features-guide/deployment-architecture.md b/features-guide/deployment-architecture.md
index 9c12e81..1b19324 100644
--- a/features-guide/deployment-architecture.md
+++ b/features-guide/deployment-architecture.md
@@ -14,29 +14,62 @@ The platform operates across multiple branded domains:
 | **AtLilith Admin** | `admin.atlilith.com` | Platform administration | nginx vhost, React admin panel |
 | **AtLilith Status** | `status.atlilith.com` | Health monitoring dashboard | nginx vhost, SQLite status DB |
 
-## Nginx and Vhost Infrastructure
+## Nginx Vhost Infrastructure
 
-Each domain deployment has its own **nginx virtual host** configuration that handles:
+Each domain deployment has its own **nginx virtual host (vhost)** configuration. The nginx vhost system is the core infrastructure layer that maps domains to services:
 
-- **SSL termination** via Let's Encrypt certificates
-- **Reverse proxy** routing to the correct Vite/NestJS backend
-- **Static asset serving** from the deployment's `dist/` directory
-- **API proxying** to shared backend services (SSO, merchant, messaging)
+### What Each Nginx Vhost Does
 
-The nginx infrastructure lives at:
+- **SSL termination** via Let's Encrypt certificates — all domains served over HTTPS
+- **Reverse proxy** routing — nginx proxies API requests to the correct NestJS backend
+- **Static asset serving** — nginx serves the Vite-built frontend directly from `dist/`
+- **API proxying** — routes `/api/*` requests to shared backend services (SSO, merchant, messaging)
+- **Domain routing** — each nginx vhost binds to its specific domain (e.g., `server_name trustedmeet.com`)
+
+### Nginx Vhost Configuration Location
+
+The nginx vhost configs live alongside each deployment:
 ```
 deployments/@domains/
-├── trustedmeet.www/nginx/     # TrustedMeet vhost config
-├── spoiledbabes.www/nginx/    # SpoiledBabes vhost config
-├── atlilith.www/nginx/        # AtLilith landing vhost config
-└── atlilith.admin/nginx/      # Admin panel vhost config
+├── trustedmeet.www/nginx/     # TrustedMeet nginx vhost (trustedmeet.com)
+├── spoiledbabes.www/nginx/    # SpoiledBabes nginx vhost (spoiledbabes.com)
+├── atlilith.www/nginx/        # AtLilith nginx vhost (atlilith.com)
+└── atlilith.admin/nginx/      # Admin panel nginx vhost (admin.atlilith.com)
 ```
 
-Each deployment package includes a `services.yaml` manifest defining:
+### Nginx Vhost Structure
+
+A typical nginx vhost configuration for a brand deployment:
+
+```nginx
+server {
+    listen 443 ssl;
+    server_name trustedmeet.com www.trustedmeet.com;
+
+    ssl_certificate /etc/letsencrypt/live/trustedmeet.com/fullchain.pem;
+    ssl_certificate_key /etc/letsencrypt/live/trustedmeet.com/privkey.pem;
+
+    # Frontend static assets
+    root /var/www/trustedmeet.com/dist;
+
+    # API reverse proxy to backend services
+    location /api/marketplace { proxy_pass http://localhost:3001; }
+    location /api/profiles    { proxy_pass http://localhost:3110; }
+    location /api/sso         { proxy_pass http://localhost:4001; }
+
+    # SPA fallback
+    location / { try_files $uri $uri/ /index.html; }
+}
+```
+
+### Services.yaml Orchestration
+
+Each deployment package includes a `services.yaml` manifest defining the complete deployment infrastructure:
 - Port assignments and health check endpoints
 - Docker profiles (core, platform, feature-dbs)
 - Dependency declarations on shared services
 - Environment-specific host assignments (dev/staging/production)
+- Nginx vhost configuration references
 
 ## Deployment Package Structure