# Session: 2026-03-25 00:21:20 UTC - **Session Key**: agent:main:telegram:direct:8032472383 - **Session ID**: 745cfa6c-f38a-47eb-ad0b-085091a9905e - **Source**: telegram ## Conversation Summary assistant: I’ll fetch that Notion page, inspect its current structure, then append or place the worker contract content in the appropriate section and report exactly what changed. assistant: I found the OpenClaw Notion page. It already has a child page for `SPECIALIST-ARCHITECTURE.md`, but not an obvious `WORKER-CONTRACT.md` child page in the top-level section I inspected. Before I write, I need one quick clarification so I update the right place: Do you want me to: 1. create/update a new child page on the OpenClaw page called `WORKER-CONTRACT.md`, or 2. paste the worker contract into an existing child page if one already exists elsewhere? user: Conversation info (untrusted metadata): ```json { "message_id": "3159", "reply_to_id": "3158", "sender_id": "8032472383", "sender": "Braden McLeish", "timestamp": "Tue 2026-03-24 15:54 PDT", "has_reply_context": true } ``` Sender (untrusted metadata): ```json { "label": "Braden McLeish (8032472383)", "id": "8032472383", "name": "Braden McLeish" } ``` Replied message (untrusted, for context): ```json { "sender_label": "Dorian", "body": "I found the OpenClaw page, and it already includes a child page for SPECIALIST-ARCHITECTURE.md, but I don’t yet see a top-level WORKER-CONTRACT.md child page there.\n\nQuick clarification\nDo you want me to:\n\n1. create a new child page on the OpenClaw page called WORKER-CONTRACT.md and populate it with the canonical worker contract, or\n2. update an existing Notion page if you already created one for the worker contract?" } ``` Option 1 please assistant: I’ll create a new `WORKER-CONTRACT.md` child page under the OpenClaw page, populate it from the canonical worker contract, then report the resulting page link. assistant: [[reply_to_current]] Done. Final Answer I created a new child page under the OpenClaw Notion page named `WORKER-CONTRACT.md` and populated it from the canonical worker contract. Structured Deliverable - New Notion page: - - New page ID: - `32df8b3e-f83d-81ae-91f1-ce2ea7d632f6` Notes - Source used: - `/Users/openclaw/.openclaw/workspace-worker/WORKER-CONTRACT.md` - I translated the markdown into Notion blocks so it’s readable as a native page. Next Actions If you want, I can also add a short cross-reference at the top of `SPECIALIST-ARCHITECTURE.md` in Notion pointing to the new `WORKER-CONTRACT.md` page. user: Conversation info (untrusted metadata): ```json { "message_id": "3162", "sender_id": "8032472383", "sender": "Braden McLeish", "timestamp": "Tue 2026-03-24 16:09 PDT" } ``` Sender (untrusted metadata): ```json { "label": "Braden McLeish (8032472383)", "id": "8032472383", "name": "Braden McLeish" } ``` Can you help me understand what that would do? assistant: [[reply_to_current]] Yes. Final Answer That would add a small note or link inside the `SPECIALIST-ARCHITECTURE.md` Notion page that points readers to the canonical `WORKER-CONTRACT.md` page. Structured Deliverable What it would do: - Improve navigation: - someone reading the specialist architecture can jump directly to the worker contract - Clarify document roles: - `SPECIALIST-ARCHITECTURE.md` explains routing/model/role structure - `WORKER-CONTRACT.md` defines the execution contract the worker follows - Reduce ambiguity: - makes it obvious which document is the source of truth for worker payload format and execution rules What it would likely look like: - A short paragraph near the top such as: - “See also: `WORKER-CONTRACT.md` for the canonical worker execution contract.” - Or a small “Related Documents” section linking: - `WORKER-CONTRACT.md` - maybe later `OPERATING-MODE.md` or `AGENTS.md` What it would not do: - It would not change behavior or config - It would not alter the worker contract itself - It would not affect routing logic - It is just a documentation cross-reference Why it may be useful Right now the architecture doc describes the three-tier system conceptually, but the actual worker execution rules live elsewhere. Linking them makes the architecture page more complete and easier to use. Next step If you want, I can add a very minimal one-line “See also” link so the page stays clean. user: Conversation info (untrusted metadata): ```json { "message_id": "3164", "sender_id": "8032472383", "sender": "Braden McLeish", "timestamp": "Tue 2026-03-24 16:10 PDT" } ``` Sender (untrusted metadata): ```json { "label": "Braden McLeish (8032472383)", "id": "8032472383", "name": "Braden McLeish" } ``` Go ahead assistant: I’ll add a minimal cross-reference near the top of the `SPECIALIST-ARCHITECTURE.md` Notion page pointing to the new `WORKER-CONTRACT.md` page, then I’ll confirm the update. assistant: [[reply_to_current]] Done. Final Answer I added a minimal `See also: WORKER-CONTRACT.md` link near the top of the `SPECIALIST-ARCHITECTURE.md` Notion page. Structured Deliverable Updated page: - Link target: - Result - Readers of the architecture page can now jump directly to the canonical worker contract without changing any behavior or configuration. user: Conversation info (untrusted metadata): ```json { "message_id": "3167", "sender_id": "8032472383", "sender": "Braden McLeish", "timestamp": "Tue 2026-03-24 16:17 PDT" } ``` Sender (untrusted metadata): ```json { "label": "Braden McLeish (8032472383)", "id": "8032472383", "name": "Braden McLeish" } ``` Great, now please replace the entire content of ~/.openclaw/workspace-worker/WORKER-CONTRACT.md with the content from the Notion page at: https://www.notion.so/32df8b3ef83d81ae91f1ce2ea7d632f6 Fetch the page, extract the markdown content, and write it to the file. Then confirm the file was written successfully with wc -l ~/.openclaw/workspace-worker/WORKER-CONTRACT.md. Once that lands, Phase 2 is updating AGENTS.md to reference SPECIALIST-ARCHITECTURE.md in the delegation framework. Ready to move there?​​​​​​​​​​​​​​​​ assistant: I’ll fetch the canonical Notion page content, overwrite `~/.openclaw/workspace-worker/WORKER-CONTRACT.md` with the extracted markdown, verify it with `wc -l`, and commit the change in the worker workspace. assistant: [[reply_to_current]] Done. Final Answer I replaced the entire contents of `~/.openclaw/workspace-worker/WORKER-CONTRACT.md` with markdown extracted from the Notion page and verified the write. Structured Deliverable Verification: ```zsh wc -l /Users/openclaw/.openclaw/workspace-worker/WORKER-CONTRACT.md ``` Result: ```text 227 /Users/openclaw/.openclaw/workspace-worker/WORKER-CONTRACT.md ``` Git: - Worker workspace commit: `d869dc4` - Message: `Sync worker contract from Notion` Next Actions Yes — ready to move to Phase 2: updating `AGENTS.md` to reference `SPECIALIST-ARCHITECTURE.md` in the delegation framework. user: Conversation info (untrusted metadata): ```json { "message_id": "3171", "sender_id": "8032472383", "sender": "Braden McLeish", "timestamp": "Tue 2026-03-24 17:13 PDT" } ``` Sender (untrusted metadata): ```json { "label": "Braden McLeish (8032472383)", "id": "8032472383", "name": "Braden McLeish" } ``` rollover assistant: [[reply_to_current]] Completion Contract Done: - Fetched the new `WORKER-CONTRACT.md` Notion page and replaced the entire local worker contract file with extracted markdown. - Verified the file write with `wc -l`. - Created the new Notion child page `WORKER-CONTRACT.md` under the OpenClaw page and added a cross-reference from `SPECIALIST-ARCHITECTURE.md`. - Patched the OAuth watchdog to reduce false positives and committed that change. - Investigated the embedded gateway token warning and confirmed the root issue: the LaunchAgent plist still contains `OPENCLAW_GATEWAY_TOKEN` and other secrets directly in `EnvironmentVariables`. Findings: - Local worker contract file now reflects the Notion page: - `/Users/openclaw/.openclaw/workspace-worker/WORKER-CONTRACT.md` - verification: `227` lines - Relevant commits: - main workspace: `5a8681c` — `Tighten OAuth watchdog alert conditions` - worker workspace: `d869dc4` — `Sync worker contract from Notion` - Gateway warning root cause: - `~/Library/LaunchAgents/ai.openclaw.gateway.plist` still embeds: - `OPENCLAW_GATEWAY_TOKEN` - `OPENAI_API_KEY` - `NOTION_API_KEY` - `TELEGRAM_BOT_TOKEN` - `openclaw gateway status` still flags this as out-of-date/non-standard. - The attempted gateway reinstall did not complete cleanly; warning remains unresolved. - Phase 2 is next: - update `AGENTS.md` to reference `SPECIALIST-ARCHITECTURE.md` in the delegation framework. Decision needed: - In the next session, proceed with Phase 2 and update `AGENTS.md`. - Optionally after that, return to the gateway LaunchAgent remediation and cleanly remove embedded secrets from the plist. Next step: - Start with Phase 2: - edit `/Users/openclaw/.openclaw/workspace/AGENTS.md` - add explicit reference to `/Users/openclaw/.openclaw/workspace/SPECIALIST-ARCHITECTURE.md` in the delegation framework / worker-dispatch guidance - commit the change - Then, if desired, debug `openclaw gateway install --force` behavior and fully resolve the embedded-token LaunchAgent warning.