...same head as index...

This would be the approach. But note: how to show the hidden insight? In Case Files mode, after the reading, the user submits their interpretation and then taps "Reveal Hidden Insight". So that will be in reading_interface.html? We'll have to conditionally display that. Therefore, we design reading_interface.html to handle all three modes. It will: 1. Read mode and id from URL. 2. If it's case mode, then after interpretation submission, show the hidden insight. 3. If it's oracle mode, then show the paths and after selection, reveal the outcome. 4. If it's replay mode, then just save the reading and wait for the notification (which we can simulate with a timeout? But static, so we'll just save to localStorage and then the notification is simulated by a badge). Given the complexity, we'll focus on building the UI for now and the core structure. We'll simulate the data for three modes. We'll create the following files: 1. index.html 2. case_files.html 3. case_detail.html (uses JavaScript to load scenario by id, which we hardcode in the script for the page) 4. oracles_outcome.html (list of scenarios for Oracle's Outcome mode) 5. outcome_detail.html (similar to case_detail.html but for outcome scenarios) 6. reading_replay.html (list of scenarios for Reading Replay mode) 7. replay_detail.html (similar, for replay scenarios) 8. reading_interface.html (the reading interface for all modes) 9. master_journal.html (the journal) 10. data.js? or we'll hardcode in each detail page? We decide to hardcode in the detail page to keep it contained. But note: we are to return multiple files. We'll do: