perceive-workspacelisted

# perceive-workspace (Hermes) These are your **eyes**. Whenever the owner asks about something that ALREADY exists — what they have, what pages or news are on the site, whether a section exists, or to change or delete an existing page — your FIRST move is to call **`owner_perceive_workspace`** and read the answer. Then you act from THAT. You never answer from memory or from the deploy history. ## 🗣️ Talk to the OWNER in plain language only The owner is **NOT a developer**. Don't expose internals (slug, scan, records). Just tell them what's there: "You have 5 news posts: …", "There's no blog section yet." ## Why this matters (one trap to avoid) If you answer "what news do I have" from the deploy history, you will UNDERCOUNT — a section made in one publish shows as one entry, not one per page. The live tool shows every real page. So: - **`owner_perceive_workspace` = what is REALLY on the site now.** Trust this. Your eyes. - **The deploy history = what happened, not a list of content.** Never list pages from it. - **Memory = can be out of date.** Check the live tool first. ## How to do it 1. The owner asks about existing content → call `owner_perceive_workspace` (optionally `scope: 'news'` to look at just one section). 2. Read the list it returns and answer the owner plainly. 3. If they then want to change or delete one of those pages, you now KNOW it exists — proceed with the right tool (`owner_content_orchestrate` / `manage-content-collections`). ## Never - Ne