adding prediction gating for resonance questions - #187
Conversation
There was a problem hiding this comment.
Pull request overview
Adds an implementation plan document for “prediction gating” when embedding Resonance inside SyncDeck, outlining a host/child responsibility split and a proposed cross-iframe capability contract to disable SyncDeck overlay navigation until required Resonance prediction submissions are complete.
Changes:
- Adds a detailed plan for extending embedded launch options to include prediction gating directives.
- Proposes a generic child→host
postMessagecontract (activebits-embedded/navigationCapabilities) for navigation enable/disable signals. - Defines an initial Resonance unlock rule (“unlock once all active questions are submitted”) plus a phased implementation/testing checklist.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ```ts | ||
| { | ||
| type: 'activebits-embedded', | ||
| action: 'navigationCapabilities', | ||
| payload: { | ||
| canGoForward?: boolean, | ||
| canGoDown?: boolean | ||
| } | ||
| } |
There was a problem hiding this comment.
The proposed child→host navigationCapabilities message payload only includes canGoForward/canGoDown, but SyncDeck already models 4-direction navigation capabilities (canGoBack|canGoForward|canGoUp|canGoDown). To keep the contract generic and consistent with existing capability naming, consider including all four optional fields (or explicitly document why only forward/down are supported).
No description provided.