04 / multi-entrance / responsible public layer

Many doors.
One release policy.

The browser should be enough to discover and use approved public software. Multiple static and dynamic entrances increase reachability; multiple links do not imply duplicated processing capacity or automatic infrastructure resilience.

Public request routing

Everyone / Browser / Read-only AI clients
         │
         ├── Direct HTTPS · sslip.io hostname / Caddy
         │     ├── /directory/* → Static approved mirror (independent gateway fallback)
         │     └── Other approved paths → Local 127.0.0.1 gateway
         │            ├── Published experiences & games
         │            ├── Public docs / catalog / read-only evidence
         │            ├── Bounded Ollama-backed Frontier chat API
         │            └── Bounded public community submission services
         │
         ├── Public navigation → /, /open/, /launch/, /platform/
         ├── Public models → /frontiers/live/, /frontiers/live/docs/
         ├── Public software factory → /factory/
         └── Public games / education → /simworks/, /arcade/, /experience/

Owner operations / Credentials / Deployment / Private records
         └── Restricted authenticated service boundary
               NOT exposed through anonymous /directory or public AI chat

DELIVERY PRINCIPLES

Lightweight, intentionally.

Availability

Independent fallback page

The Caddy-served static directory remains present if the Python gateway fails. Status snapshots retain their timestamps and cannot be assumed real-time when stale.

Performance

CPU first

Minimal HTML, CSS and JavaScript, zero remote fonts, no analytics, and no web framework dependency for the public directory. Inference remains CPU-constrained.

Transparency

Raw, bounded receipts

Source-backed examples, snapshots, source statuses, test documentation and explicit claims about what remains unfinished.

Recovery

Reversible changes

Versioned source/backups and existing health-audit timers. Local backup copies are not equivalent to independent encrypted offsite disaster recovery.

Access control

Public UI, gated execution

Anonymous users can read public materials and use limited app functions. Root, SSH, secrets, owner workbenches and arbitrary writes remain restricted.

Model honesty

Show the actual engine

Twelve themed local-model UIs do not mean twelve paid or official vendor APIs. Model fallbacks and quotas should be disclosed in each verified response.

Related entrances.

Door	Job	Link
Main public hub	General application discovery	/open/ ↗
Launch	Published releases and quick navigation	/launch/ ↗
Static directory	Independently served source of public links and last known QA	/directory/ ↗
Off-VPS continuity	Separate Vercel-hosted public orientation; not synchronized applications or backups	Vercel continuity ↗
Platform	Architecture, model truths, quality gates	/platform/ ↗
Frontiers	Local model workspaces and their documentation	/frontiers/live/ ↗
Factory	Public software factory demo and evidence	/factory/ ↗

Many doors.One release policy.