Timeline

[Editor Content] SOP Process API vs Skills Last updated: 2026-05-16 Correct Framing: The problem is not MCP or knowledge lookup. Mike has hundreds of real skills/SOPs that are procedures agents need to run. A Knowledge API helps find the SOP, but it does not make it executable. The target system is a private SOP Process API: - Process Catalog: stores every SOP/skill as a normalized process definition. - Workflow Runner: creates runs, tracks steps, enforces gates, records evidence, and verifies completion. Next Build: merlino-process-api to import SOPs, classify them, and convert to runnable process definitions. Repair Log: - MacHermes and Herman prod repaired: browser/transcript env fixed. - Patched youtube-content helpers to use Supadata. - Installed youtube-transcript-api in Hermes venvs. - Stabilized MacHermes gateway processes.

[SUGGESTED_QUERY] refactoring agent skills to workflow runner

[SUGGESTED_QUERY] Hermes system repair and environment configuration

[SUGGESTED_QUERY] agent SOP process API vs knowledge API

Website: https://herman-vps3-truth-sweep-dkulm00cx-mmerlin023s-projects.vercel.app/

Screen: Set up a run action @ Settings O Full access v Extra High v Audit live domains Inspect Open-Ge... 1 file changed +2 -0 Review here Review gist 9 Web search a DASHBOARDs Compare memory... o Create pull request Review OpenAl A... V codex/supermemory-openai -o- Commit master-brain @ Changes Local @ Ran 6 commands My cleanup decision: keep codex/ supermemory-openai as the active Supermemory branch, commit only the five SOP ingest/fanout docs out of that commit. I'm gitignore edit. O Edited 1 file, ran 3 comman The five new Supermemory/SC . gitignore ; the OpenClaw d @ Ran 3 commands I'm committing the Supermem I'm deliberately not staging . ( @ Running git diff --cached - The Supermemory/SOP commi branch from origin/master , Thinking OpenClaw repair x nake the minimal Run Tell Codex how to ins

[SUGGESTED_QUERY] 24-agent research task status

[SUGGESTED_QUERY] OpenClaw repair documentation branch

[SUGGESTED_QUERY] Supermemory SOP git workflow

Tag: agent-research Source: CLOUD_LLM

[Editor Content] Fix Hermes setup Supermemory branch should stay about Master Brain memory/SOP ingest. OpenClaw repair docs/runtime artifacts are real, but unrelated. Current branch is salvageable as a source branch, not as the branch to push. Next action after GO: create the two clean branches, commit each scope separately, run tests/build on the Supermemory branch, then push both. SOP Process API vs Skills Last updated: 2026-05-16 Correct Framing: The problem is not MCP. The problem is also not just "knowledge lookup." Mike has hundreds of real skills/SOPs/process files. Those are not passive reference docs. They are procedures that agents need to run. The target system is a private SOP Process API: - Process Catalog: stores every SOP/skill as a normalized process definition. - Workflow Runner: creates runs, tracks steps, enforces gates, records evidence, resumes work, and verifies completion. Cleanup decision: keep codex/supermemory-openai as the active Supermemory branch, commit only the five SOP ingest/fanout scripts plus scratch-dir ignores there, and keep the OpenClaw repair docs out of that commit.

[SUGGESTED_QUERY] SOP process API vs knowledge lookup

[SUGGESTED_QUERY] git branch scope separation workflow

[SUGGESTED_QUERY] codex supermemory-openai branch cleanup

Tag: branch-hygiene Source: CLOUD_LLM

[Command-Line Output] Decisions needed before either Codex terminal touches this repo: 1. Is codex/supermemory-openai still the active build branch, or has it been abandoned? 2. Do the 5 new scripts/ingest_*.py and scripts/fanout_*.py belong on this branch, or split to a new one? 3. Should the OpenClaw repair docs (.continue-here.md + docs/openclaw-ava-oscar-repair-2026-05-12.md) be cherry-picked to a separate branch since they have nothing to do with Supermemory? 4. Add tmp-*/ and .codex-work/ to .gitignore? 5. Push the branch to origin after cleanup, or rebase on master first? Check on the other terminal: are either of you actively working in this repo right now, or is the work happening elsewhere (Mac OpenClaw, Hermes, etc.)? Confirm before any commit/push. Recap: We're checking the state of the 'codex/supermemory-openai' branch in master-brain to figure out where work actually stands. Next: decide what to do with the 5 untracked ingest scripts and the unrelated OpenCLaw repair docs sitting on this branch.

[SUGGESTED_QUERY] git repository cleanup and branch synchronization

[SUGGESTED_QUERY] codex supermemory-openai branch cleanup decisions

[Editor Content] Next action after GO: create the two clean branches, commit each scope separately, run tests/build on the Supermemory branch, then push both.

[SUGGESTED_QUERY] Supermemory branch testing and build process

[SUGGESTED_QUERY] software development commit and push strategy

[SUGGESTED_QUERY] git branch management workflow

[SUGGESTED_QUERY] OpenClaw runtime artifacts management

[SUGGESTED_QUERY] supermemory branch split strategy

[SUGGESTED_QUERY] Codex repository cleanup instructions

Confirmed. Repo Is Safe To Touch, But Not Commit Yet No process command line is pointed at master-brain. No .git/index.lock. Branch state matches the handoff. I only did read-only inspection. My Call codex/supermemory-openai is still useful, but dirty/mixed. Do not push it as-is. Do not rebase the current dirty branch directly. Create clean split branches. Clean Split codex/supermemory-openai-clean cherry-pick: cc7c015 a3a9bcc 397f494 48c5480 add/commit the 5 SOP ingest/fanout scripts: scripts/ingest_supermemory_sop.py scripts/ingest_byterover_sop.py scripts/ingest_lmstudio_sop.py scripts/fanout_sops_to_chroma.py scripts/fanout_sops_to_other_backends.py add .codex-work/ and tmp-*/ to .gitignore codex/openclaw-runtime-docs take: 5d46f0c Matteo/OpenClaw artifacts .continue-here.md docs/openclaw-ava-oscar-repair-2026-05-12.md Reason Supermemory branch should stay about Master Brain memory/SOP ingest. OpenClaw repair docs/runtime artifacts are real, but unrelated. Current branch is salvageable as a source branch, not as the branch to push. Next action after GO: create the two clean branches, commit each scope separately, run tests/build on the Supermemory branch, then push both.

Screen: Edit C Q 00 O File New chat Search Plugins Automations View 2 c c 4d Window Help Fix Hermes setup +137 -2 D:/Ecosystem/Memory/llm-wiki/wiki/index.md D:/Ecosystem/Memory/llm-wiki/wiki/log.md D:/Ecosystem/Memory/llm-wiki/wiki/tools/knowledge-api-vs-mcp.md The deal: o x O Pinned Fix OpenClaw out... Fix Hermes setup Plan 24-agent res... Projects e VIDEO-TOOLS No chats B master-brain Review OpenAl A... Compare memory... e DASHBOARDs Review gist Inspect Open-Ge... Audit live domains @ Settings +135 so whats the deal? Your current "skills" setup is a pile of runnable SOPs trapped in a prompt-loading format. That does not scale. Syncing skills across machines only makes the pile available everywhere; it does not make the processes controllable. The missing layer is a process runtime. What should h

[SUGGESTED_QUERY] agent workflow runner implementation

[SUGGESTED_QUERY] SOP Process API vs Skills architecture

Tag: workflow-runtime Source: CLOUD_LLM

[Command-Line Output] These are OpenClaw scope, not Supermemory scope. Untracked (8): - scripts/fanout_sops_to_chroma.py (Supermemory scope, should commit) - scripts/fanout_sops_to_other_backends.py (Supermemory scope, should commit) - scripts/ingest_byterover_sop.py (Supermemory scope, should commit) - scripts/ingest_lmstudio_sop.py (Supermemory scope, should commit) - scripts/ingest_supermemory_sop.py (Supermemory scope, should commit) - .codex-work/ (Matteo VPSI install + setup audit/ fix scratch from today, probably gitignore) - tmp-ava-skills-training/ (May 12 OpenClaw scratch, probably gitignore) - tmp-openclaw-hubstaff/ (May 12 OpenClaw plugin backup copies, probably gitignore) Decisions needed before either Codex terminal touches this repo: 1. Is codex/supermemory-openai still the active build branch, or has it been abandoned? 2. Do the 5 new scripts/ingest_*.py and scripts/fanout_*.py belong on this branch, or split to a new one? 3. Should the OpenClaw repair docs (.continue-here.md + docs/openclaw-ava-oscar-repair-2026-05-12.md) be cherry-picked to a separate branch? 4. Add tmp-*/ and .codex-work/ to .gitignore? 5. Push the branch to origin after cleanup, or rebase on master first? [Process Catalog Proposal] - Create a Process Catalog: Each real SOP gets an ID, title, triggers, and original Markdown source. - Build a Workflow Runner: start run, next step, submit result, attach evidence, pause/resume, complete/block. - Agent Rule: Do not load 600 skills. Search/start/resume processes through the Process API.

[SUGGESTED_QUERY] git repository untracked files and branch strategy

[SUGGESTED_QUERY] ClaudeDev workflow runner and process catalog design

Tag: process-engineering Source: CLOUD_LLM

Tag: git-repository-management Source: CLOUD_LLM

[Editor Content] Spawned 6 agents: Raven, Knox, Merlin, Dan, Frankie, and Queen. Task: Research 13 full-stack production layers for 2026 best practices (Next.js, TypeScript, Tailwind, Supabase, Vercel/Netlify/Cloudflare). Branch Status: master-brain repo, branch codex/supermemory-openai. Contains mixed scopes: Supermemory/OpenAI ingest and OpenClaw Discord repair. Knowledge API vs MCP Analysis: - The problem is not MCP or knowledge lookup; it is the lack of an executable process layer. - Proposed System: Private SOP Process API with a Process Catalog, Workflow Runner, and Tool/Action Adapters. - Strategy: Inventory all SOP/skill files, create a process catalog, build a workflow runner, and transition skills to bootstrap wrappers.

[SUGGESTED_QUERY] implementing SOP process catalog for AI agents

[SUGGESTED_QUERY] Mike Merlino Codex agent team architecture

[SUGGESTED_QUERY] agent workflow runner vs static skills

Tag: workflow-runner Source: CLOUD_LLM

[SUGGESTED_QUERY] managing agent SOPs and process catalog

[SUGGESTED_QUERY] transitioning from skills to workflow runner

[SUGGESTED_QUERY] AI agent process runtime architecture

The deal: Your current “skills” setup is a pile of runnable SOPs trapped in a prompt-loading format. That does not scale. Syncing skills across machines only makes the pile available everywhere; it does not make the processes controllable. The missing layer is a process runtime. What should happen next: Inventory all SOP/skill files Find every SKILL.md, SOP, runbook, checklist, workflow. Classify: bootstrap, reference, executable process, tool wrapper, safety rule. Create a Process Catalog Each real SOP gets an ID, title, triggers, inputs, required tools, steps, risks, done criteria. Original Markdown stays as source evidence. Build a Workflow Runner start run next step submit result attach evidence pause/resume complete/block Give every agent one tiny rule “Do not load 600 skills. Search/start/resume processes through the Process API.” Only then retire skills Skills become bootstrap wrappers. SOP execution moves to the runner. Plain version: you do not need “more synced skills.” You need your own internal Zapier/Temporal-lite for agent SOPs. The agents should not memorize processes; they should execute process runs.

Screen: Edit C Q 00 O File New chat Search Plugins Automations View 2 4d Window Help Fix Hermes setup • Original Markdown stays as source evidence. 3. Build a Workflow Runner o x O Pinned Fix OpenClaw out... Fix Hermes setup Plan 24-agent res... Projects e VIDEO-TOOLS No chats B master-brain Review OpenAl A... Compare memory... e DASHBOARDs Review gist Inspect Open-Ge... Audit live domains @ Settings • • • start run next step submit result attach evidence pause/resume complete/block 4. Give every agent one tiny rule • "Do not load 600 skills. Search/start/resume processes through the Process API." 5. Only then retire skills • Skills become bootstrap wrappers. • SOP execution moves to the runner. Plain version: you do not need "more synced skills." You need your own internal Zapier/Temporal-lite fo

[SUGGESTED_QUERY] Mike Merlino agent team production standards

[SUGGESTED_QUERY] 13-layer production checklist Next.js Supabase

[SUGGESTED_QUERY] Codex agent workflow SOP Process API

[SUGGESTED_QUERY] Supermemory OpenAI agents branch management

[SUGGESTED_QUERY] OpenClaw repair documentation status