docs: preserve historical design intent in roadmap

10-modernization-roadmap.md

@@ -13,6 +13,30 @@ This is not a strict PHP feature port checklist. The objective is to preserve ar
 - Service role is config-driven from one binary.
 - The white-paper target is a Twitter-like backend showcase (SPEW) launched by configuration and template/domain declarations, with zero core framework code changes.
 
+## Historical Design Intent (Preserved)
+
+These points come from operational experience in Namaste and are treated as architectural intent, not nostalgia.
+
+1. Expensive resources should be long-lived:
+- Logger transport clients, AMQP connections, and database clients should not be repeatedly instantiated for per-event semantic changes.
+
+2. Template-derived operational state should live with runtime objects:
+- The object that executes work should carry the template-derived state it needs for its full lifetime.
+
+3. Public API contract must remain decoupled from internal schema:
+- External developers interact with remapped/public field names and operation contracts.
+- Internal table/collection names and DBO names remain private unless explicitly authorized.
+
+4. Runtime template drift must be controlled:
+- Running nodes should operate from a stable template snapshot for deterministic behavior.
+- Template changes are applied through controlled reload/restart, not accidental file edits mid-run.
+
+5. Template integrity is a future acceptance feature:
+- Track per-template and registry-level fingerprints to detect drift and support cluster consistency checks.
+
+6. Resource constraints are first-class requirements:
+- BEDS must run on low-resource hardware (including RPi-class systems), so memory strategy must be intentional and bounded.
+
 ## Current Program Mode
 
 The project is currently in POC-first mode.