docs(journal): additional notes for the expo.

apps/kbve.com/src/content/journal/11-10.mdx

@@ -110,4 +110,15 @@ import { Adsense, Tasks } from '@kbve/astropad';
     This would be the barebone component, aka, `TamaOnboard`, and it would have two states that it would manage.
     The first state would be for the `username` and making sure that it is unique before setting it up, however it would be noted that it is the user's public username.
     The second state would be for the profile card, the core specific here would be preparing the basic information for the init card.
-    Hmm, okay these two states should be enough for us to move forward, I believe we can always go back around and double check the onboarding when it goes live into production.
+    Hmm, okay these two states should be enough for us to move forward, I believe we can always go back around and double check the onboarding when it goes live into production.
+
+    I am thinking that for error management, we should push the error up in the component, so that the parent component that calls the Tamaonboard can process the error?
+    This would be easier for us to handle, without having to create multiple error handlers inside of the sub-components, okay let me do that next.
+
+
+
+    **FredAgain**
+
+    While working on the expo component, I am jamming to that radio session with Fred and Jim!
+    The whole work is flames, just nearly a perfect set for this expo work.
+    Here is the link to the [set](https://www.youtube.com/watch?v=DE_yVb3JMD8), which should be thrown into that future music application.