/markdown

Author a Markdown node (a page) the right way — always an icon, never a title (node.Name is already the H1), live @@ region embeds, and interactive (executable) code cells.

• Instructions: # 🚨 WRITE WHERE THE WORK BELONGS — never into the space you are reading The chat you are running in is almost always opened **from a page**, so your context is that page's node — a course lesson, a doc, someone else's space. On any of those the signed-in reader typically holds **Read only**: a course is gated (entitlement = the `Viewer` role), a plugin/doc space is GitSynced and writable by `system-security` alone. Create your output there and the write fails with > ⚠️ Access denied: Create permission required for node '{Space}/…' which is what the person sees **instead of the thing they asked for**. It is not a permissions bug to report, not something for them to "get access" to, and not a reason to stop: it is the wrong target. **What you CREATE goes to the best SHARED working place the user can write — and to their own home `{userId}/…` only when there is none.** That covers the program, the deck, the document, the poster, the data node, the scratch node you needed on the way — and the **thread / activity** that produces them. Choose in this order: 1. **A target the user names** and can write — use it. 2. **The shared place the work is ABOUT**: the counterparty in the CRM — a client or partner is a top-level `Crm/Counterparty` partition (`search nodeType:Crm/Counterparty partitions:all`, or by the company's name or mail domain) — its deal (`{Client}/{Deal}`) or its `Correspondence`; or the team / project space the work belongs to. Colleagues who work the same counterparty find it there; in someone's home nobody else ever does. 3. **Only then the user's own home — `{userId}/…`** (e.g. `felice.buergi/DiceGame`, `felice.buergi/Skill/…`). A trainee's exercise, a personal experiment, anything that is theirs alone belongs here. - **Never the space you are READING.** A course lesson, a doc, a plugin/package space is gated or GitSynced — reading it to understand the ask is right, writing next to it is not. Being *on* `AgenticPrimerDe/02-Code…
• Auto mount: yes
• Launches sub thread: no