Replies: 2 comments
-
|
Hi Dear Dev. Sorry for missing the discussion. The AI tends to use the frontal lobe to store memory, but in practice this only leads to hallucinations. Taking all of the above into account, we have removed the frontal-lobe component, allowing OpenAlice to focus more on running the Trading Harness. |
Beta Was this translation helpful? Give feedback.
-
|
Additionally, if you'd like to extend the AI's memory system, we will support injecting new MCPs from external sources when creating a Workspace in the future, and referencing specific memories via MCP. This way, you can losslessly preserve the prefrontal-lobe extensions you've already built, and continue to enjoy the advantages of the Workspace architecture. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I'm wondering whether I should follow the
Brain/frontal-loberetirement changes (commit 0a10b3f) from the main repo in my fork, and I ran into a real architecture question.I did read the commit message, and I understand the core rationale:
frontal-lobemainly existed to preserve continuity across compacted chat sessions, and with workspaces becoming the main substrate, that continuity is expected to come instead from the workspace transcript / scrollback / working tree / local markdown files, rather than from one global persistent self-note.What I’m unsure about is how far that reasoning should be taken in a setup where
frontal-lobeis part of the live monitoring and decision loop, rather than just a continuity aid for chat.In my fork,
frontal-lobeis currently doing more than just “memory” work: it carries regime context, temporary no-trade constraints, open hypotheses, and general continuity acrossmarket-monitor,heartbeat,daily-review, chat, and some operator/UI flows.So my assumption is that removing it naively would reduce hidden prompt state and make syncing changes easier, but it might also make trading behavior less consistent unless there’s a clear replacement for the useful carry-forward state it currently provides.
Can anyone here pls help me understand:
Brain/frontal-lobein practice beyond the commit summaryIn other words: where do you think this kind of operational state should live long term — typed control/config models, task-owned prompts, session/event logs, workspace-local markdown, or something else?
Many thanks in advance for any hints or answers 🙏
Best regards from Bangkok!
Beta Was this translation helpful? Give feedback.
All reactions