More http post end points filled

docs/RENDER_CADENCE_GOLDEN_RULES.md

@@ -69,6 +69,8 @@ The CPU/build phase may parse manifests, invoke Slang, validate package shape, a
 
 The render thread receives a completed artifact and either commits it at a frame boundary or rejects it. A failed artifact must not disturb the current renderer.
 
+The display/render layer model is app-owned. It may track requested shaders, build state, display metadata, and render-ready artifacts, but it must not perform GL work or drive render cadence directly.
+
 ## 5. No Hidden Blocking In The Cadence Path
 
 The render loop must not do work with unbounded or OS-dependent latency.
@@ -124,6 +126,7 @@ Preferred boundaries:
 - render cadence/thread ownership
 - GL rendering
 - runtime artifact build/bridge
+- app-owned display/render layer model
 - parameter packing
 - system-memory frame exchange
 - DeckLink output scheduling