Real-time Event Renderer — Constitution¶
Hard-Stop Rules¶
These rules must never be violated. Violations require immediate halt and review.
- Never drop events silently — all drops must be logged and counted
- Never allow unbounded buffer growth in long-running sessions
- Never block the rendering thread with synchronous data processing
Mandatory Rules¶
These rules must be followed in all circumstances.
- Maintain 30fps minimum under normal event load
- Automatic WebSocket reconnection with exponential backoff
- Event ordering preserved in visual representation
- Memory budgets enforced for long-running sessions
Preferred Practices¶
Best practices that should be followed when possible.
- Use adaptive frame rate throttling under high load
- Provide event replay functionality from buffer history
- Include connection health indicators in the visual interface