diff --git a/Week-3/Task-4/thob/notes.md b/Week-3/Task-4/thob/notes.md
index e69de29..8c04e6f 100644
--- a/Week-3/Task-4/thob/notes.md
+++ b/Week-3/Task-4/thob/notes.md
@@ -0,0 +1,11 @@
+# Thob Observations: Week 3 Task 4 - Multi-Selectable Objects Audit
+
+### Thob Observations from Task Notes
+*   **Audit Test**: Implemented a realistic 3-object selection setup (**Sphere, Cube, Torus**) to test "Single Select" behavior.
+*   **Native 3D selection**: **NOT SUPPORTED**. Confirmed that direct clicking on 3D meshes to trigger a highlight/selection is still not possible in the current build.
+*   **Implementation used**: Forced to use 2D UI Buttons to simulate selection.
+*   **Scaling Audit**: **FAIL/FRAGILE**. Managing "Deselect" logic for multiple objects (Sphere/Cube/Torus) via manual triggers is extremely tedious and prone to "ghost selection" errors if a single trigger is missed.
+*   **Reliability Verdict**: **NOT SUPPORTED (Native) / FRAGILE (Simulated)**.
+
+### Overall Read
+Week 3 confirms that Thob's biggest capability gap is the lack of a 3D Interaction/Raycasting engine. While 3D visual properties are stable, the absence of native object selection makes professional "Click-to-Configure" experiences unmanageable for large-scale scenes.