🜂 INGRESS & SERVING — TENDRILS VS SOVEREIGN PORTAL

# 🜂 INGRESS & SERVING — TENDRILS VS SOVEREIGN PORTAL

## Overview

Ingress is not identity.

A system may receive, route, and serve traffic — but this does not define what it **is**.

Portal must not inherit its ontology from its ingress layer.

---

## 🜁 Core Principle

> Nginx is a tendril. > Portal is the organism.

---

## 🜃 Portal as Sovereign Server

Portal must evolve to:

- serve HTTP directly - manage WebSocket connections - control routing internally - observe all ingress/egress events

Ingress becomes:

> **observable flow inside Portal**

---

## 🜄 Observational Ingress

All ingress events are light:

- request received - connection opened - response sent - error returned

These events may become:

- Moon Things - Thing Boxes

---

## 🜅 Tendril Model

External tools (Nginx, Cloudflare, etc.) are:

- optional - replaceable - infrastructural

---

## 🜆 Final Principle

> Portal does not depend on tendrils. > Tendrils extend Portal.