diff --git a/Week-2/Task-1/ProductLens.md b/Week-2/Task-1/ProductLens.md
index 443829a..6c27e7c 100644
--- a/Week-2/Task-1/ProductLens.md
+++ b/Week-2/Task-1/ProductLens.md
@@ -5,7 +5,8 @@
 	- Architecture/interior previews with predefined camera tour angles.
 	- Marketing/storytelling scenes that need guided perspective changes.
 - Does Thob feel strong enough for this use case?
-	- Partial. The base setup works (Perspective Camera + Make Default), but interaction wiring for button-driven camera behavior is still hard to discover and execute.
+	- Partial. The base setup works (Perspective Camera + Make Default), but my first instinct was to use buttons for preset switching and that flow did not work reliably end-to-end.
+	- A practical fallback is to use radio buttons that switch between meshes/view proxies preconfigured at different angles.
 - What would improve the experience?
 	- Improve Make Default button UX.
 	- Make button-to-component-prop binding easier and more intuitive.
diff --git a/Week-2/Task-1/TaskNotes.md b/Week-2/Task-1/TaskNotes.md
index 9f094e8..b793b1a 100644
--- a/Week-2/Task-1/TaskNotes.md
+++ b/Week-2/Task-1/TaskNotes.md
@@ -31,10 +31,14 @@ Switch the camera between predefined viewpoints and smoothly transition between
 ## Thob Page Builder
 -Possible: Partial
 -Notes:
-  - We can create the same result by using the Perspective Camera component and toggling the Make Default button.
+  - I found two ways to approach this.
+  - Way 1 (workaround): use radio buttons to switch between meshes/view proxies preconfigured at different angles. This gave stable visual switching.
+  - Way 2 (direct preset intent): use Perspective Camera with Make Default toggling for preset switching. This did not work at all in my testing.
+  - My first intuition was to use buttons for direct camera preset switching, but I could not make that setup work end-to-end.
   - Current button UX needs improvement.
   - It should be easier and more intuitive to connect a button and change target component prop values.
-  - I could not clearly figure out how to make the button functional end-to-end.
+  - The current action wiring flow is not clear enough for reliable button-driven preset changes.
+  - Conclusion: radio-button mesh/view switching is a workaround, not a reliable direct camera-preset flow.
 -Builder steps:
   - Add a Perspective Camera component.
   - Toggle Make Default on the camera.
@@ -67,8 +71,9 @@ Switch the camera between predefined viewpoints and smoothly transition between
 -Is there a workaround?
   - Partial workaround.
 -If yes, what is it?
-  - Use Perspective Camera + Make Default for a static/default view.
-  - For advanced preset switching behavior, implement custom logic outside the current builder button flow.
+  - Use radio buttons to switch between meshes (or view proxies) that are pre-set to different camera angles.
+  - This gives stable visual preset-like switching.
+  - Direct preset switching by toggling Perspective Camera Make Default did not work at all.
 
 ## Suggested Improvement
 -What should improve in Thob?
diff --git a/Week-2/Task-1/builder/BuilderNotes.md b/Week-2/Task-1/builder/BuilderNotes.md
index 8eea870..3d5cb2a 100644
--- a/Week-2/Task-1/builder/BuilderNotes.md
+++ b/Week-2/Task-1/builder/BuilderNotes.md
@@ -3,7 +3,7 @@
 ## Thob Observations from Task Notes
 
 - **Possible:** Partial
-- **Implementation used:** Perspective Camera component with Make Default toggle, plus attempt to bind UI buttons for preset switching.
+- **Implementation used:** Perspective Camera component with Make Default toggle; first intuition was button-based preset switching, but that setup did not work reliably end-to-end.
 - **What worked as expected:**
 	- Perspective Camera can be set as default view.
 	- Static/default camera setup is achievable quickly.
@@ -18,7 +18,7 @@
 	5. Validate if preset switching works reliably.
 - **Complexity:** Hard (for interaction wiring), Easy (for static camera setup).
 - **Main limitation signals:** Editor UX + Event system + Runtime stability concerns.
-- **Workaround status:** Partial workaround only (use default/static camera view; advanced preset switching done outside current builder flow).
+- **Workaround status:** Partial workaround only (use default/static camera view, or use radio buttons to switch between meshes/view proxies preconfigured at different angles when direct button-to-camera binding is unclear).
 
 ## Console Warnings/Errors Seen (Deduplicated) and Probable Meaning
 
@@ -70,6 +70,7 @@
 ## Overall Read
 
 - Task 1 goal is partially achievable in builder: default camera setup works, but interactive preset switching through button binding remains difficult.
+- A workable fallback is radio-button-driven switching across preconfigured angled meshes/view proxies.
 - Logs show a strong pattern of duplicate registration warnings around binding and prop update paths, which aligns with the observed interaction wiring problems.
 - UI controlled/uncontrolled warnings and intermittent WebGL/context/network issues further reduce confidence while testing button-driven camera behavior.
 - Product priority for this task should focus on reliable action-to-prop binding flow and registration lifecycle cleanup.