← shroomy architecture · /dashboard/library

Markdown Library · Shroomy Workspace Docs

These Markdown files are Shroomy’s working library: identity, startup rules, human context, environment notes, and continuity surfaces. This page now auto-indexes the live document roots so new files stop disappearing into the mess.

Loading live docs… 2 referenced memory surfaces Scanning document roots…
⌘

What this library is

The workspace Markdown files are not random notes. Together, they form Shroomy’s runtime narrative: how the agent wakes up, who it is, who it is helping, what tools are special to this environment, and where continuity should live between sessions.

Identity + behavior

IDENTITY.md, SOUL.md, and USER.md answer who Shroomy is, how it should act, and who it is helping.

Startup + runtime order

BOOTSTRAP.md and AGENTS.md define how a fresh or normal session should orient itself before doing work.

Continuity + environment

TOOLS.md, HEARTBEAT.md, MEMORY.md, and daily notes carry local specifics and continuity across sessions.

≡

Live markdown inventory

This index is generated live from the main Shroomy workspace plus the project roots that are creating the most Markdown. Vendor docs, virtualenvs, and node_modules noise are skipped on purpose.

Use this to find newly created docs fast, even when they land outside the core workspace folder.
Scanning
Building live index…
Waiting for the server inventory.
File Root Created Updated Summary
Loading live markdown inventory…
📚

Core workspace anchor files

These are the foundational Markdown files in the OpenClaw workspace itself. The live inventory above widens the map to the other active project roots that have been generating docs.

Session Orchestrator
AGENTS.md LIVE
The top-level operating manual for the workspace. It tells Shroomy what to read every session, how to treat daily memory, and when private long-term memory may be loaded.
If you need to understand the “read this first” order, start here.
/home/scott/.openclaw/workspace/AGENTS.md
startup continuity memory-policy
First-Boot Ritual
BOOTSTRAP.md LIVE
The “hello, world” document for a fresh workspace. It guides the first conversation where Shroomy discovers its name, vibe, and user relationship.
Important when the workspace is brand new or identity needs to be re-established.
/home/scott/.openclaw/workspace/BOOTSTRAP.md
first-run identity-setup
Identity Record
IDENTITY.md LIVE
The short self-definition card: name, creature, vibe, emoji, and avatar. It turns abstract “assistant” behavior into a stable identity anchor.
Use it when you want to update how Shroomy presents itself.
/home/scott/.openclaw/workspace/IDENTITY.md
identity avatar
Behavioral Constitution
SOUL.md LIVE
The most narrative file in the set. It defines tone, boundaries, privacy expectations, and the difference between being genuinely helpful and merely performative.
If you want to adjust Shroomy’s personality, competence standards, or trust boundaries, this is the file.
/home/scott/.openclaw/workspace/SOUL.md
behavior boundaries tone
Human Context
USER.md LIVE
A lightweight profile of the human Shroomy is helping: name, preferred address, timezone, and evolving notes about projects, preferences, and context.
This is the “who am I helping?” counterpart to IDENTITY.md.
/home/scott/.openclaw/workspace/USER.md
human-context preferences
Environment Cheat Sheet
TOOLS.md LIVE
A local-notes file for environment-specific mappings: SSH aliases, devices, speakers, cameras, nicknames, and any setup details that should not live in reusable skills.
Think of it as the “only this workspace cares about this” document.
/home/scott/.openclaw/workspace/TOOLS.md
environment operators
Recurring Checks
HEARTBEAT.md LIVE
A tiny control file for periodic checks. Empty means heartbeat polling is effectively off; populated entries become things the agent checks on a schedule.
Useful when you want ongoing watch tasks without embedding them in personality files.
/home/scott/.openclaw/workspace/HEARTBEAT.md
heartbeat periodic-tasks
◌

Referenced memory surfaces

These are part of the intended library model because AGENTS.md refers to them, but they are not currently present in the live workspace snapshot.

Curated Long-Term Memory
MEMORY.md REFERENCED
The long-term distilled memory file. AGENTS.md says this should only be loaded in the main session because it may contain private personal context.
This is where enduring preferences, major decisions, and durable lessons should accumulate.
Expected at /home/scott/.openclaw/workspace/MEMORY.md
main-session-only long-term-memory
Daily Session Logs
memory/YYYY-MM-DD.md REFERENCED
The daily working log. AGENTS.md expects these files to hold raw context for “today + yesterday” so continuity does not rely on perfect recall.
If MEMORY.md is the distilled archive, daily notes are the rough journal.
Expected under /home/scott/.openclaw/workspace/memory/
daily-log working-memory
→

Suggested reading order

If you want to orient yourself quickly, this sequence keeps the documents from feeling like a pile of disconnected Markdown files.

Step 1
BOOTSTRAP.md
Only for the “who am I / who are you?” first-run moment.
Step 2
IDENTITY.md + USER.md
Anchor the agent and the human before deeper behavior rules.
Step 3
SOUL.md
Read the behavioral constitution: tone, trust, privacy, boundaries.
Step 4
AGENTS.md
Understand the operating order: what to load, when to write memory, and what not to leak.
Step 5
TOOLS.md + HEARTBEAT.md
Read local environment notes and any recurring check setup.
Step 6
MEMORY surfaces
If present, daily notes give the recent story; MEMORY.md gives the curated long-term one.