Philosophy

Architecture Philosophy

Static-First, Not Static-Only

Cybermaps generates discovery content dynamically: sitemaps, AI manifests, structured data, then writes the output to disk so your web server (Nginx, Apache, Caddy) handles all subsequent requests directly. PHP and MySQL are only involved during generation, never during crawling.

This is not caching. This is materialization: the dynamic content becomes a static file. The web server treats it like any other file: index.html, style.css, sitemap.xml. Zero database queries. Zero PHP execution. Zero WordPress bootstrap.

When a static file doesn’t exist (first generation after deployment, filesystem permission issues, manual purge), the Smart Heal mechanism generates the content dynamically and serves it. The site never returns a broken discovery response: it degrades from static to dynamic, not from working to broken.

Why This Matters

A traditional WordPress sitemap plugin boots WordPress on every request:

Request → PHP → MySQL → XML → Response
                         ↑
                    40 queries
                    500ms latency
                    20MB memory

Cybermaps after the first generation:

Request → Nginx → static file → Response
                         ↑
                    0 queries
                    2ms latency
                    0MB memory

For a site with 100,000 posts being crawled by GPTBot, ClaudeBot, and Googlebot simultaneously, the difference is: servers stay up.

The Container Is Lazy

Services (Orchestrator, discovery handlers, identity hub, loggers) are registered in a PSR-11-style container but not instantiated until their hook fires. A visitor hitting only the homepage triggers zero sitemap or discovery logic. A bot hitting /llms.txt triggers only the LLMS handler, not the ADP handler or the sitemap orchestrator.

---