Repository navigation
docs: record frontend-direction spike-then-decide approach - #155
Merged
Merged
Conversation
Resolves #152 with a spike plan rather than a direct choice between keep-React / Streamlit / NiceGUI / Reflex. Spike target: M4 review screen in Streamlit, 1-day time-box. Three defined outcomes, each with a next step.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the DECISIONS record for the frontend-direction spike-then-decide approach, decided 2 November 2026.
Resolves #152 with a spike plan: rebuild the M4 review screen in Streamlit as a 1-day learning exercise, then decide the real direction based on what it teaches.
Three outcomes defined (Streamlit works / Python-native right but Streamlit limiting / Python-native wrong), each with a next step.
Related: #69 (ended Lovable platform dependency), new spike issue to be filed.