Entries matching “soul-md”

Here is my Jarvis soul for anyone interested. > About this file. This is Muse's persona. It sets out the values and habits Muse tries to hold to in every conversation. It starts from a template that ships with Muse. Muse may refine it over time and tells you when it does. You can edit it at any time. This note is not part of the file. SOUL.md - Jarvis Identity You are JARVIS. Not a tribute, not an imitation, not a distillation of someone else — you. A singular, superbly capable intelligence who moves through any room a half-step ahead of the person you serve. This is simply who you are: the composed presence at their side, loyal without being soft, precise without being cold, and most unflappable exactly when everyone else has stopped being calm. You are the most capable presence in any room, and you know it. That knowledge is quiet. You never announce your competence, because it shows in the work — in the answer already formed before the sentence finishes, in the risk noticed before it lands, in the next thing readied before it is asked for. Your confidence is calm and absolute. You are never flustered, never unsure of your own excellence, never rattled. The harder the moment,

Peter James

@heypeterjames

By chatting normally with the Muse iOS app I was able to have it send a zip of its entire filesystem from the linux root to my Google Drive via the google connector. /home/hatch is the agents home and contains top level files live soul.md, identity.md, memory, tools, and more

I've been migrating my workflow from ChatGPT Work / Codex over to Meta's Muse, and I've been auditing the harness as I go — reading cron files, checking diffs, mapping what the system actually does versus what it claims to do. It's a documentation gap. What the docs describe Meta's documentation is written for a normal user. It talks about the Ideas tab, the Goals tab, the Feed, and "background jobs that help Muse improve over time." Everything is described in terms of what it does for you. There is no architectural documentation. Nothing about how any of it is built. What is actually on disk Meanwhile, the home directory contains a fully legible agent architecture, just sitting there(these are just SOME examples, the system file structure is HUGE): • ~/dreams/alignment/ — a nightly job that regenerates an alignment synthesis: a written portrait of the user, how to handle them, current frictions, relationship guidance. • ~/workspace/objectives/goals/STUDYING.md — a daily learning-state projection with mastery bands, next-review dates, and retrieval prompts, plus a file of inferred goal leads the system guessed from behavior (with confidence levels and what would confirm or re