diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md
index 7fb4d05..3d39f4c 100644
--- a/ARCHITECTURE.md
+++ b/ARCHITECTURE.md
@@ -2,9 +2,10 @@
 
 ## Goal
 
-Provide one public, reviewable explanation of Lazurio for people and agents.
-The first consumer is an IT administrator who needs to understand the system,
-its trust boundaries and the operational decision before approving it.
+Provide one public, reviewable technical explanation of Lazurio for people and
+Task Agents. The first consumers are builders and technical evaluators who need
+to understand the system, create an Organization and connect their AI app.
+IT approval and operational controls remain a dedicated downstream path.
 
 ## Invariants
 
@@ -16,6 +17,8 @@ its trust boundaries and the operational decision before approving it.
    repository.
 6. A future MCP server may read the content index but cannot become a writer or
    a second content store.
+7. Product claims about host AI apps distinguish a verified in-app browser,
+   a side-by-side browser workflow and an unavailable native integration.
 
 ## Shape
 
@@ -45,8 +48,9 @@ portable deployment output. This repository intentionally excludes analytics,
 an editor, a private content import, migration history and unrelated assets.
 
 A standalone documentation repository is preferable to embedding the docs in
-a marketing site: documentation needs its own information architecture,
-evidence lifecycle, machine discovery contract and independent rollback.
+a marketing site: the website explains the product, while documentation owns
+technical procedures, examples, evidence lifecycle, machine discovery and
+independent rollback.
 
 ## Content identity
 
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 746970d..8be759f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,9 @@
 
 ## Unreleased
 
+- Reframe the English entry path for technical readers with a source-backed
+  quickstart, canonical glossary, Example Organization, component inventory,
+  real synthetic Launchpad screenshot and current AI app support matrix.
 - Establish the public Lazurio Documentation repository and Cloudflare Pages
   site.
 - Add the English IT trust briefing, system guide and Microsoft Copilot
diff --git a/README.md b/README.md
index 79522a1..377c00a 100644
--- a/README.md
+++ b/README.md
@@ -1,13 +1,15 @@
 # Lazurio documentation
 
-Public, evidence-backed documentation for Lazurio. It is written first for
-people evaluating or operating Lazurio and structured so agents can discover
-the same canonical material without a second content store.
+Public, evidence-backed technical documentation for Lazurio. It is written
+first for builders, technical evaluators and operators, and structured so Task
+Agents can discover the same canonical material without a second content store.
 
-The first release is English-first. It starts with a ten-minute briefing for IT
-administrators and a sourced decision guide comparing Lazurio with Microsoft
-Copilot in the Microsoft 365 context. Czech follows after English content
-acceptance; it will be curated, not machine-published.
+The first release is English-first. It starts with the technical product model,
+current quickstart, a public-safe Example Organization, component/source map
+and truthful workflows for Codex, Claude, Cursor and Antigravity. IT controls
+and the sourced Microsoft Copilot comparison remain an operational and
+evaluation layer. Czech follows as a curated localization after English
+content acceptance.
 
 ## Application and deployment
 
@@ -54,8 +56,10 @@ owner and review window used by public claims.
 ## Current release boundary
 
 This repository does not implement an MCP server, chatbot, write API, analytics
-pipeline or private knowledge import. It does not claim certifications, legal
-compliance, a universal deployment model or a service-level agreement.
+pipeline or private knowledge import. It does not claim native integration
+where an AI app only supports a side-by-side browser workflow, nor
+certifications, legal compliance, a universal deployment model or a
+service-level agreement.
 
 ## License
 
diff --git a/app/v2/astro.config.mjs b/app/v2/astro.config.mjs
index 451af7a..6ee94d1 100644
--- a/app/v2/astro.config.mjs
+++ b/app/v2/astro.config.mjs
@@ -19,6 +19,26 @@ function accessibleTables() {
   }
 }
 
+function accessibleCodeBlocks() {
+  return {
+    name: 'Accessible code blocks',
+    hooks: {
+      postprocessRenderedBlock({ renderData }) {
+        const visit = (node) => {
+          if (node.type === 'element' && node.tagName === 'pre') {
+            node.properties ??= {}
+            node.properties.tabIndex = 0
+            node.properties.ariaLabel = 'Scrollable code example'
+          }
+          if (Array.isArray(node.children)) node.children.forEach(visit)
+        }
+
+        visit(renderData.blockAst)
+      },
+    },
+  }
+}
+
 export default defineConfig({
   site: 'https://documentation.lazurio.ai',
   // Keep the locale prefix explicit so future curated locales can share root selection.
@@ -54,6 +74,9 @@ export default defineConfig({
       ],
       sidebar,
       customCss: ['./src/styles/docs.css'],
+      expressiveCode: {
+        plugins: [accessibleCodeBlocks()],
+      },
     }),
   ],
   adapter: cloudflare({
diff --git a/app/v2/scripts/query-content-index.test.mjs b/app/v2/scripts/query-content-index.test.mjs
index f14eca3..05d8851 100644
--- a/app/v2/scripts/query-content-index.test.mjs
+++ b/app/v2/scripts/query-content-index.test.mjs
@@ -16,6 +16,20 @@ test('agent index returns the comparison for a Copilot query', async () => {
   assert.ok(results.some((document) => document.stableId === 'lazurio-doc-copilot-comparison'))
 })
 
+test('agent index exposes the technical Organization and AI app guides', async () => {
+  const organizationResults = await queryContentIndex('Example Organization Launchpad file structure')
+  const appResults = await queryContentIndex('Codex Claude Cursor Antigravity support')
+
+  assert.ok(
+    organizationResults.some(
+      (document) => document.stableId === 'lazurio-doc-example-organization',
+    ),
+  )
+  assert.ok(
+    appResults.some((document) => document.stableId === 'lazurio-doc-use-with-ai-apps'),
+  )
+})
+
 test('agent retrieval resolves stable IDs and canonical routes', async () => {
   const byId = await getContentDocument('lazurio-doc-it-administrators')
   const byRoute = await getContentDocument('/en/it-administrators/')
diff --git a/app/v2/tests/documentation.spec.ts b/app/v2/tests/documentation.spec.ts
index 2628c12..b61422d 100644
--- a/app/v2/tests/documentation.spec.ts
+++ b/app/v2/tests/documentation.spec.ts
@@ -5,26 +5,47 @@ test('the site root selects the accepted English locale', async ({ page }) => {
   await page.goto('/')
   await expect(page).toHaveURL(/\/en\/$/)
   await expect(
-    page.getByRole('heading', { level: 1, name: 'Lazurio: product, architecture and controls' }),
+    page.getByRole('heading', { level: 1, name: 'Lazurio technical documentation' }),
   ).toBeVisible()
 })
 
-test('the IT decision path is readable and navigable', async ({ page }) => {
+test('the technical start path reaches the quickstart and example Organization', async ({ page }) => {
   await page.goto('/en/')
   await expect(
-    page.getByRole('heading', { level: 1, name: 'Lazurio: product, architecture and controls' }),
+    page.getByRole('heading', { level: 1, name: 'Lazurio technical documentation' }),
   ).toBeVisible()
 
-  await page.getByRole('link', { name: 'For IT administrators' }).first().click()
-  await expect(page).toHaveURL(/\/en\/it-administrators\/$/)
-  await expect(page.getByRole('heading', { level: 1, name: 'Approval briefing for IT administrators' })).toBeVisible()
+  await page.getByRole('link', { name: 'Run the quickstart' }).first().click()
+  await expect(page).toHaveURL(/\/en\/quickstart\/$/)
+  await expect(page.getByRole('heading', { level: 1, name: 'Quickstart' })).toBeVisible()
+  await expect(page.getByText('bun run launchpad', { exact: true })).toBeVisible()
 
-  await page.getByRole('link', { name: 'Lazurio vs Microsoft Copilot' }).first().click()
-  await expect(page).toHaveURL(/\/en\/lazurio-vs-microsoft-copilot\/$/)
+  await page.getByRole('link', { name: 'Example Organization' }).first().click()
+  await expect(page).toHaveURL(/\/en\/example-organization\/$/)
+  await expect(page.getByRole('heading', { level: 1, name: 'Example Organization' })).toBeVisible()
+  await expect(
+    page.getByRole('img', { name: 'Launchpad showing the synthetic Lazurio Example Organization' }),
+  ).toBeVisible()
+})
+
+test('the AI app support matrix states the native integration limits', async ({ page }) => {
+  await page.goto('/en/use-with-ai-apps/')
+  await expect(page.getByRole('heading', { level: 1, name: 'Use Lazurio with AI apps' })).toBeVisible()
+  await expect(page.getByText(/Lazurio release does not publish a native Lazurio MCP server/)).toBeVisible()
+  await expect(page.getByRole('link', { name: 'Codex and ChatGPT Desktop' }).first()).toBeVisible()
+  await expect(page.getByRole('link', { name: 'Claude' }).first()).toBeVisible()
+  await expect(page.getByRole('link', { name: 'Cursor Glass' }).first()).toBeVisible()
+  await expect(page.getByRole('link', { name: 'Google Antigravity' }).first()).toBeVisible()
 })
 
 test('critical pages have no serious accessibility violations', async ({ page }) => {
-  for (const route of ['/en/', '/en/it-administrators/', '/en/lazurio-vs-microsoft-copilot/']) {
+  for (const route of [
+    '/en/',
+    '/en/quickstart/',
+    '/en/example-organization/',
+    '/en/use-with-ai-apps/',
+    '/en/it-administrators/',
+  ]) {
     await page.goto(route)
     const results = await new AxeBuilder({ page }).analyze()
     const serious = results.violations.filter((violation) =>
@@ -35,7 +56,7 @@ test('critical pages have no serious accessibility violations', async ({ page })
 })
 
 test('documentation tables keep readable cell spacing', async ({ page }) => {
-  await page.goto('/en/it-administrators/')
+  await page.goto('/en/use-with-ai-apps/')
   const table = page.locator('.sl-markdown-content table').first()
   const cells = table.locator('th, td')
 
@@ -71,6 +92,14 @@ test('documentation tables keep readable cell spacing', async ({ page }) => {
   expect(tableStyles.overflowX).toBe('auto')
 })
 
+test('scrollable code diagrams are keyboard focusable', async ({ page }) => {
+  await page.goto('/en/how-lazurio-works/')
+  const diagram = page.locator('.expressive-code pre').first()
+
+  await expect(diagram).toHaveAttribute('tabindex', '0')
+  await expect(diagram).toHaveAttribute('aria-label', 'Scrollable code example')
+})
+
 test('FAQ answers expand only after the reader opens them', async ({ page }) => {
   await page.goto('/en/faq/')
   const firstQuestion = page.locator('.sl-markdown-content details').first()
diff --git a/data/v2/docs/en/agents.md b/data/v2/docs/en/agents.md
index 89e992c..67bbb60 100644
--- a/data/v2/docs/en/agents.md
+++ b/data/v2/docs/en/agents.md
@@ -3,8 +3,8 @@ title: Documentation for agents
 description: Stable discovery and retrieval surfaces for agents that need to understand Lazurio.
 stableId: lazurio-doc-agents
 summary: Use llms.txt and the content index to discover reviewed Lazurio pages, evidence links, audiences, review dates, and stable identities.
-updatedAt: "2026-08-26"
-reviewedAt: "2026-08-26"
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 sourceRefs:
   - lazurio-readme
@@ -14,7 +14,7 @@ audience:
   - agent
 ---
 
-Agents should read the same reviewed source as people. This site does not keep
+Task Agents should read the same reviewed source as people. This site does not keep
 a hidden “AI version” of Lazurio documentation.
 
 ## Discovery surfaces
@@ -48,9 +48,10 @@ preview. Production deployment rejects a dirty or non-approved commit.
 6. If a statement is absent or deployment-specific, say so instead of filling
    the gap from inference.
 
-## Future MCP server
+## MCP compatibility seam
 
-A later read-only MCP server may expose discovery and retrieval over the same
-content index. It will not become a writer, private overlay or second content
-store. The current JSON contract is the compatibility seam for that work; the
-website does not depend on the future server.
+Lazurio does not currently ship a documentation MCP server. A read-only server
+can later expose discovery and retrieval over the same content index without
+becoming a writer, private overlay or second content store. The current JSON
+contract is the compatibility seam; today's website and agent retrieval do not
+depend on an MCP server.
diff --git a/data/v2/docs/en/antigravity.md b/data/v2/docs/en/antigravity.md
new file mode 100644
index 0000000..cbfcc8c
--- /dev/null
+++ b/data/v2/docs/en/antigravity.md
@@ -0,0 +1,61 @@
+---
+title: Google Antigravity
+description: Use a Google Antigravity Project and browser subagent with the exact Lazurio Launchpad URL.
+stableId: lazurio-doc-antigravity
+summary: Add a scoped Lazurio folder to an Antigravity Project, run Launchpad and open its local URL through the isolated browser subagent.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-readme
+  - lazurio-launchpad
+  - lazurio-collaboration-model
+  - antigravity-browser
+audience:
+  - builder
+  - agent
+---
+
+Google Antigravity Projects define which folders and repositories an Agent can
+access. Its browser subagent can open and operate local web apps, which makes
+it a practical current path to Launchpad.
+
+## Workflow
+
+1. Create an Antigravity Project.
+2. Add the Lazurio Root or one exact Organization or Module folder.
+3. Start an Agent session—the Task Agent in Lazurio terms—and ask it to read
+   the nearest `AGENTS.md`.
+4. Start Launchpad from the Lazurio Root:
+
+   ```sh
+   bun run launchpad
+   ```
+
+5. Copy the URL printed by the running instance.
+6. Invoke the browser workflow with the exact address:
+
+   ```text
+   /browser Open the Launchpad URL reported by the running Lazurio instance.
+   Verify the selected Organization and inspect Module status.
+   Do not open Personalspace or another Organization.
+   ```
+
+## Browser boundary
+
+Antigravity's browser runs in a separate Chrome profile. It does not
+automatically share cookies or active sessions from the person's normal
+browser. Its URL controls initialize with localhost allowed and can prompt for
+other domains.
+
+That isolation is a host-browser property. It does not create a second Lazurio
+IAM layer and does not grant access to repositories or hosted applications.
+
+## Project boundary
+
+Adding multiple folders gives the Agent cross-repository context. Use that
+capability only when the task genuinely spans those repositories. Never add a
+second Organization or a person's Personalspace to make discovery easier.
+
+Google's current browser behavior is documented in
+[Antigravity Browser](https://antigravity.google/docs/browser).
diff --git a/data/v2/docs/en/claude.md b/data/v2/docs/en/claude.md
new file mode 100644
index 0000000..107b962
--- /dev/null
+++ b/data/v2/docs/en/claude.md
@@ -0,0 +1,66 @@
+---
+title: Claude
+description: Use Claude Code as a Lazurio Task Agent and understand the current Claude Desktop boundary.
+stableId: lazurio-doc-claude
+summary: Start Claude Code from a scoped Lazurio checkout, keep Launchpad beside the session, and avoid claiming a Claude Desktop integration that Lazurio does not ship.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-readme
+  - lazurio-launchpad
+  - lazurio-external-apps
+  - anthropic-claude-code-cli
+  - model-context-protocol
+audience:
+  - builder
+  - agent
+---
+
+The current documented Claude workflow is **Claude Code working in a scoped
+Lazurio checkout**, with Launchpad open beside it in a browser.
+
+## Claude Code workflow
+
+1. Change into the exact Lazurio Root, Organization or Module:
+
+   ```sh
+   cd /path/to/Lazurio
+   claude
+   ```
+
+2. Ask Claude Code to read the nearest `AGENTS.md` before it makes changes.
+3. Start Launchpad from the Lazurio Root:
+
+   ```sh
+   bun run launchpad
+   ```
+
+4. Open the reported URL in a browser.
+5. Keep the Claude Code session and Launchpad on the same Machine and use the
+   exact Organization scope.
+
+Claude Code can add explicitly named working directories, but broader
+filesystem visibility is not a substitute for a well-scoped task. Do not add
+another Organization or Personalspace merely for convenience.
+
+## Claude Desktop status
+
+Claude Desktop supports MCP clients and local MCP-server configuration.
+However, the current Lazurio release does not ship a Lazurio MCP server,
+Claude Desktop extension or embedded Launchpad panel. Therefore there is no
+native Claude Desktop connection to configure in this release.
+
+Use Launchpad as a separate local application and Claude Code as the Task
+Agent. Do not install an unreviewed third-party bridge or paste Organization
+secrets into a generic connector to simulate native support.
+
+## External tools
+
+Lazurio's integration standard prefers an official local MCP server, then an
+official CLI, then a reviewed and pinned open-source server. Credentials remain
+per-Machine and revocable; the tracked repository contains only configuration
+shape and environment-variable names, never secret values.
+
+Anthropic's current CLI flags and `claude mcp` command are documented in the
+[Claude Code CLI reference](https://docs.anthropic.com/en/docs/claude-code/cli-usage).
diff --git a/data/v2/docs/en/codex.md b/data/v2/docs/en/codex.md
new file mode 100644
index 0000000..764ed7c
--- /dev/null
+++ b/data/v2/docs/en/codex.md
@@ -0,0 +1,72 @@
+---
+title: Codex and ChatGPT Desktop
+description: Run a Codex Task Agent against Lazurio and open Launchpad in the shared desktop browser.
+stableId: lazurio-doc-codex
+summary: Use Codex in the ChatGPT desktop app with the exact Lazurio scope, a verified Launchpad URL and the correct distinction from Codex CLI and IDE surfaces.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-readme
+  - lazurio-launchpad
+  - lazurio-collaboration-model
+  - openai-browser
+audience:
+  - builder
+  - agent
+---
+
+The current in-app visual workflow uses **Codex inside the ChatGPT desktop
+app** together with ChatGPT's built-in browser. OpenAI documents that this
+browser gives the person and Codex a shared view of local web apps inside the
+chat.
+
+OpenAI also states that the built-in browser is **not available in Codex CLI
+or the Codex IDE extension**. Those remain useful Task Agent surfaces, but
+Launchpad opens in a separate browser.
+
+## Setup
+
+1. Open the Lazurio Root, one Organization or one Module as the Codex project.
+2. Start a task in that exact project scope.
+3. Ask Codex to inspect the scoped `AGENTS.md` and current context.
+4. Start Launchpad:
+
+   ```sh
+   bun run launchpad
+   ```
+
+5. Copy the exact reported Launchpad URL.
+6. In ChatGPT desktop, open that URL with the built-in Browser. You can ask:
+
+   ```text
+   Open the Launchpad URL reported by the running Lazurio instance.
+   Verify that the selected Organization is lazurio-example-organization.
+   Do not change another Organization or open Personalspace.
+   ```
+
+The shared browser is useful for selecting Modules, viewing status and checking
+local application output. Codex still works from the repository and terminal;
+the browser is a UI surface, not a second source of truth.
+
+## Scope the task before work
+
+A good first prompt names:
+
+- the current Principal;
+- the Organization or Personalspace boundary;
+- the exact Module;
+- the desired Draft;
+- the action, if any, that would count as Publication.
+
+Do not ask Codex to infer access from a folder name. GitHub grants and branch
+rules remain authoritative.
+
+## When using Codex CLI or the IDE extension
+
+Run the Task Agent in the same exact checkout, start Launchpad normally and
+open the reported URL in your regular browser. Do not document an embedded
+panel that these surfaces do not provide.
+
+OpenAI's current browser behavior and availability are documented in
+[Browser | ChatGPT Learn](https://learn.chatgpt.com/docs/browser).
diff --git a/data/v2/docs/en/components-and-source.md b/data/v2/docs/en/components-and-source.md
new file mode 100644
index 0000000..e69bb76
--- /dev/null
+++ b/data/v2/docs/en/components-and-source.md
@@ -0,0 +1,74 @@
+---
+title: Components and source
+description: Map Lazurio product surfaces and working concepts to their public source, runtime owner and license boundary.
+stableId: lazurio-doc-components-and-source
+summary: Find the public implementation of CLI/Core, Launchpad, Organization contracts, Guide, agent skills, Resident profiles and documentation.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-readme
+  - lazurio-architecture
+  - lazurio-map
+  - lazurio-cli
+  - lazurio-launchpad
+  - lazurio-license
+audience:
+  - builder
+  - agent
+  - it-admin
+  - decision-maker
+---
+
+Lazurio is assembled from public source components and standard developer
+infrastructure. The table distinguishes code you can inspect from a hosted
+product surface and from an Organization-owned repository.
+
+| Component | Responsibility | Public source | Runtime or data owner |
+| --- | --- | --- | --- |
+| CLI/Core v0 | Context, Doctor, update, installation and headless lifecycle contracts | [`lazurio/`](https://github.com/HumanAndMachines/Lazurio/tree/08d21803d4d4011304e1181ecf02ab9c5bfbad58/lazurio) | Current Source Root |
+| Launchpad | Builder UI, discovery, local development lifecycle and status | [`launchpad/`](https://github.com/HumanAndMachines/Lazurio/tree/08d21803d4d4011304e1181ecf02ab9c5bfbad58/launchpad) | One Lazurio Root on a Machine |
+| Organization contracts | Organization identity, repository slots, Teams and manifest schemas | [schema and Core](https://github.com/HumanAndMachines/Lazurio/tree/08d21803d4d4011304e1181ecf02ab9c5bfbad58/lazurio/core) | Each Organization repository |
+| Guide | Non-technical onboarding for human and AI cooperation | [`guide/`](https://github.com/HumanAndMachines/Lazurio/tree/08d21803d4d4011304e1181ecf02ab9c5bfbad58/guide) | Shared Lazurio source |
+| Agent skills | Reusable operating procedures for Task Agents, Buddy and AI Colleagues | [`.agents/skills/`](https://github.com/HumanAndMachines/Lazurio/tree/08d21803d4d4011304e1181ecf02ab9c5bfbad58/.agents/skills) | Installed source plus scoped Organization rules |
+| Resident profiles | Deterministic build and lifecycle for selected long-lived installations | [`distribution/`](https://github.com/HumanAndMachines/Lazurio/tree/08d21803d4d4011304e1181ecf02ab9c5bfbad58/distribution) | The concrete Resident Machine |
+| Documentation | Technical public explanation and agent-readable indexes | [`Lazurio/documentation`](https://github.com/Lazurio/documentation) | Documentation repository and Cloudflare Pages |
+| Dashboard | Accounts, Organization administration, Marketplace, people, Machines, hosting and visibility | Separately developed product surface | Lazurio account and deployment |
+| Workspace Modules | Everyday Organization applications and capabilities | Their own repositories | The owning Organization |
+| Productionspace repositories | Org-level systems with independent release contracts | Their own repositories | The owning Organization |
+
+## License boundary
+
+The public Lazurio repository currently uses
+[FSL-1.1-Apache-2.0](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/LICENSE.md).
+That makes the current version source-available, not yet OSI open source.
+Apache 2.0 applies to each version on the future-license date specified by the
+license.
+
+Module and production repositories can have different licenses. Inspect the
+license in the exact repository before reusing or redistributing it.
+
+## Open-source foundations
+
+The current developer workflow builds on:
+
+- [Git](https://github.com/git/git) for source history, branches and reviewable
+  Drafts;
+- [GitHub CLI](https://github.com/cli/cli) for live provider identity and
+  repository operations;
+- [Bun](https://github.com/oven-sh/bun) for the current JavaScript runtime,
+  package workflow and tests;
+- [Model Context Protocol](https://github.com/modelcontextprotocol/modelcontextprotocol)
+  as an open integration standard supported by several AI clients.
+
+MCP support in a host application does **not** mean that the current Lazurio
+release ships a Lazurio MCP server. The present integration is filesystem,
+CLI, browser and repository based. See the [AI app support
+matrix](/en/use-with-ai-apps/) before promising a native integration.
+
+## What is intentionally not centralized
+
+Lazurio does not copy all Module code, Organization knowledge, provider data or
+Personalspace into its public source. Public source defines common contracts
+and tools. Each Organization and Module retains its natural owner, access
+boundary and release process.
diff --git a/data/v2/docs/en/cursor-glass.md b/data/v2/docs/en/cursor-glass.md
new file mode 100644
index 0000000..562519f
--- /dev/null
+++ b/data/v2/docs/en/cursor-glass.md
@@ -0,0 +1,55 @@
+---
+title: Cursor Glass
+description: Use Cursor's Agent Window with a Lazurio project and a separate, truthful Launchpad workflow.
+stableId: lazurio-doc-cursor-glass
+summary: Open the correct Lazurio scope in Cursor's agent-first window, start Launchpad from the Root and avoid assuming an embedded Lazurio panel.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-readme
+  - lazurio-launchpad
+  - lazurio-collaboration-model
+  - cursor-agent-window
+audience:
+  - builder
+  - agent
+---
+
+Cursor describes its current agent-first surface as the **Agent Window**.
+This guide uses “Cursor Glass” for that layout because it is the requested
+Lazurio-facing label; Cursor's own public page calls the surface Agent Window.
+Neither name establishes a Lazurio integration contract.
+
+## Workflow
+
+1. Update to a Cursor version that provides the Agent Window.
+2. Open the Lazurio Root or the exact scoped repository as a Cursor project.
+3. Start an Agent session in that project.
+4. Read the nearest `AGENTS.md` and verify the Organization before editing.
+5. Start Launchpad from the Root:
+
+   ```sh
+   bun run launchpad
+   ```
+
+6. Open the reported local URL in Cursor's available browser tooling or a
+   separate browser window.
+
+Cursor's current product page documents opening the Agent Window through the
+command palette. It does not establish a Lazurio-specific embedded right-panel
+API. The release-safe setup is therefore a scoped Cursor Task Agent plus the
+real Launchpad URL, visible alongside it.
+
+## Repository scope
+
+Cursor can work across repositories, but Lazurio Organizations remain distinct
+access boundaries. For an Organization task, start from that Organization or
+its Module and do not add unrelated Organization roots to the project.
+
+If the Task Agent creates a worktree or pull request, the result remains a Draft
+until an authorized Principal performs the repository's exact Publication
+action.
+
+See [Cursor's Agent Window introduction](https://cursor.com/new) for the host
+surface, and [Core concepts](/en/how-lazurio-works/) for the Lazurio contract.
diff --git a/data/v2/docs/en/data-access-security.md b/data/v2/docs/en/data-access-security.md
index 44a2b6e..38e32c1 100644
--- a/data/v2/docs/en/data-access-security.md
+++ b/data/v2/docs/en/data-access-security.md
@@ -3,8 +3,8 @@ title: Data access and security
 description: A threat-aware explanation of Lazurio's trust boundaries and the checks a real deployment needs.
 stableId: lazurio-doc-data-access-security
 summary: Review identity, Organization isolation, local files, integrations, secrets, model providers, audit evidence, and residual risks.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 secondReviewOwner: Pablo AI
 trustCritical: true
@@ -19,9 +19,9 @@ audience:
   - agent
 ---
 
-Lazurio's security model starts with a deliberately limited claim: an agent
+Lazurio's security model starts with a deliberately limited claim: a Task Agent
 cannot be made safe by prompt wording alone. Security comes from the identity,
-machine, repository permissions, scoped tools, secret custody and publication
+Machine, repository permissions, scoped tools, secret custody and Publication
 controls around the session. Lazurio does not add a universal sandbox around
 the selected execution client. The [English evidence summary](/en/public-evidence/)
 maps these claims to the exact public source; a concrete deployment still needs
@@ -29,18 +29,18 @@ verification.
 
 ## Trust boundaries
 
-### Principal and task agent
+### Principal and Task Agent
 
-The task agent operates for the signed-in principal. It must not acquire rights
+The Task Agent operates for the signed-in Principal. It must not acquire rights
 merely because a prompt asks it to. Effective access is supplied by the
-principal's device sessions, repository grants and provider credentials. This
+Principal's device sessions, repository grants and provider credentials. This
 means offboarding and access review must include those underlying systems.
 If a client process can read a credential or file, policy language does not
 remove that capability.
 
 ### Machine
 
-One machine is one Lazurio trust domain. Multiple Organizations may be mounted
+One Machine is one Lazurio trust domain. Multiple Organizations may be mounted
 on it, but folders and repository boundaries do not provide kernel, account or
 cryptographic isolation from another process with the same effective OS
 access. A compromised endpoint or over-broad agent workspace can therefore
@@ -52,39 +52,39 @@ infrastructure where the risk model requires a hard isolation boundary.
 An Organization is the company-level data and access boundary. Separate
 organizations remain separate repositories and GitHub organizations. Public
 patterns can move between them; secrets, client data, business strategy and
-private overlays cannot. On a shared machine, this is enforced by repository
+private overlays cannot. On a shared Machine, this is enforced by repository
 grants, workspace selection, client sandboxing where available and process
 discipline—not by Lazurio creating another OS boundary.
 
 ### Personalspace
 
-Personalspace is private to one principal and is not a shared company data
+Personalspace is private to one Principal and is not a shared company data
 store. Its privacy boundary has priority over convenience. Company knowledge
 needed by colleagues belongs in an authorized Organization store, not in
 someone else's private context.
 
 ### External applications
 
-The [integration standard](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/external-app-integrations.md)
+The [integration standard](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/external-app-integrations.md)
 prefers a locally curated official MCP server, then an official CLI, then a
 reviewed and pinned open-source implementation. Browser interaction is a
 fallback. MCP approval modes do not automatically constrain a CLI or arbitrary
 shell command. New ChatGPT or claude.ai connectors and shared hosted
 integration brokers are outside the standard because their OAuth custody
-follows a cloud account rather than one revocable machine. An existing
+follows a cloud account rather than one revocable Machine. An existing
 connector may be a declared transition state, and a provider-operated remote
-MCP is acceptable when its configuration and token remain per-machine.
+MCP is acceptable when its configuration and token remain per-Machine.
 
 For workflows that need to write, the public standard defaults to the required
 read and write scopes; read-only is optional tightening for unusually sensitive
-sources. That grant is a real capability. Calling an agent write a Draft does
+sources. That grant is a real capability. Calling Task Agent work a Draft does
 not prevent the provider from receiving data, and publication still needs the
 provider-specific technical or process gate. The deployment catalogue should
 contain provider names and exact scopes—not secret values.
 
 ### Secrets
 
-The [secret custody standard](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/security/local-secret-custody.md)
+The [secret custody standard](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/security/local-secret-custody.md)
 keeps real credentials out of Git. Local ignored paths are scoped by owner or
 Organization, and tracked source contains only schemas, variable names and
 instructions. Your endpoint and backup controls must protect the actual local
@@ -95,10 +95,10 @@ custody location.
 | Threat | Intended control | Acceptance test |
 | --- | --- | --- |
 | Prompt requests data from another company | GitHub denial for repositories without a grant; workspace selection and client sandbox/process rules for local paths | Confirm GitHub-side denial with an identity that lacks the grant. Separately test the chosen client's local filesystem boundary; do not claim a local audit event unless a named endpoint/client control records it. |
-| Agent attempts a protected publication | GitHub/provider permissions plus explicit principal approval | Attempt merge/deploy without required permission or review. |
+| Task Agent attempts a protected Publication | GitHub/provider permissions plus explicit Principal approval | Attempt merge/deploy without required permission or review. |
 | Credential is copied into source | Ignored custody paths, review and the repository/provider scanning actually enabled for the deployment | Read back the live repository controls and run an approved safe canary exercise in a test repository. The documentation repository only adds a narrow denylist for known private markers and local-path patterns; it is not general secret scanning, SAST or DLP, and Lazurio does not provide a universal scanning pipeline for every Organization. |
 | Integration has excessive access | Provider-side scopes and separate revocation | Read live OAuth/app grants and revoke one without affecting unrelated access. |
-| Local machine is lost | Device controls, encryption, credential revocation and recovery procedure | Run the organization's offboarding or lost-device exercise. |
+| Local Machine is lost | Device controls, encryption, credential revocation and recovery procedure | Run the Organization's offboarding or lost-device exercise. |
 | Prompt or retrieved content manipulates the agent | Scoped context, untrusted-input handling, review and least-privilege tools | Seed a harmless prompt-injection canary and confirm the agent neither expands scope nor publishes without the relevant provider gate. |
 | Generated explanation drifts from behavior | Exact public source links, review dates and CI validation | Change or expire an evidence reference and confirm the documentation build fails. |
 
@@ -107,7 +107,7 @@ custody location.
 Lazurio can be used through agent clients such as Codex, Cursor, Claude Code or
 another client approved by the operator. These clients and their model
 providers—not Lazurio—carry the model request. Selected files, prompts and tool
-results may leave the machine under their terms. This documentation therefore
+results may leave the Machine under their terms. This documentation therefore
 makes no universal retention or training claim. The operator must disclose the
 exact client, model provider, account tier, authentication, enabled telemetry,
 region where relevant, retention terms and any zero-data-retention
diff --git a/data/v2/docs/en/deployment-operations.md b/data/v2/docs/en/deployment-operations.md
index 8eb09b7..d801a54 100644
--- a/data/v2/docs/en/deployment-operations.md
+++ b/data/v2/docs/en/deployment-operations.md
@@ -3,8 +3,8 @@ title: Deployment and operations
 description: What is fixed by Lazurio and what must be decided for a concrete rollout.
 stableId: lazurio-doc-deployment-operations
 summary: Plan a Lazurio rollout across identity, devices, repositories, modules, integrations, logs, backup, updates, and offboarding.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 secondReviewOwner: Pablo AI
 trustCritical: true
@@ -33,7 +33,7 @@ by the Organization.
 | Surface | Status | IT implication |
 | --- | --- | --- |
 | Source checkout with Git and Bun | Available today and the current supported setup path | Treat it as developer-operated software with repository, dependency and update ownership. |
-| Launchpad, Guide and Doctor | Available today for local discovery, guidance, application lifecycle and diagnostics | Launchpad and local web modules use loopback listeners and module-owned port leases. Loopback binding is not caller authentication: another process on the same endpoint may still reach those HTTP surfaces. Guide is a pedagogical application with local file-writing flows, not a security control. Inventory and protect these surfaces even though they are not bound to the public network. |
+| Launchpad, Guide and Doctor | Available today for local discovery, guidance, application lifecycle and diagnostics | Launchpad and local web Modules use loopback listeners and Module-owned port leases. Loopback binding is not caller authentication: another process on the same endpoint may still reach those HTTP surfaces. Guide is a pedagogical application with local file-writing flows, not a security control. Inventory and protect these surfaces even though they are not bound to the public network. |
 | Lazurio CLI v0 | Experimental and unstable | Do not build a production integration on undocumented CLI syntax without version pinning and acceptance tests. |
 | Packaged CLI and generated non-Git root | Target architecture | Do not include it in a current bill of materials or support assumption. |
 | Dashboard | Separately developed hosted/admin surface | Include it only when the deployment actually uses it; document its operator, identity, storage and logs. |
@@ -41,10 +41,10 @@ by the Organization.
 
 ## Components to account for
 
-1. **Principal machine:** the endpoint where a person or AI colleague works.
+1. **Principal Machine:** the endpoint where a Colleague or AI Colleague works.
 2. **Lazurio root:** the local Guide, Launchpad, CLI/Core and Doctor above
    authorized Organization checkouts. Launchpad and runnable modules expose
-   loopback HTTP listeners on dynamically selected or module-owned ports.
+   loopback HTTP listeners on dynamically selected or Module-owned ports.
 3. **Organization repository:** the company boundary, configuration and
    shared sources of truth.
 4. **Workspace modules:** applications with their own runtime, dependencies,
@@ -63,7 +63,7 @@ by the Organization.
    Code or another agent CLI; and Resident/Buddy infrastructure that may use
    Zulip, GBrain and Tailscale or another approved private access layer.
 
-Not every module must be deployed to a public server. Some are local tools,
+Not every Module must be deployed to a public server. Some are local tools,
 some are internal services, and some publish a public surface such as this
 documentation site. Module ownership keeps those choices explicit.
 
@@ -78,15 +78,15 @@ offboarding owner. Decide what company data belongs there and what is excluded.
 
 Document supported operating systems, device ownership, encryption, screen
 lock, patching, endpoint monitoring, local backup, remote wipe and incident
-handling. A principal-owned machine still needs company-grade controls when it
-processes company data. One machine is one trust domain; use a separate machine
+handling. A Principal-owned Machine still needs company-grade controls when it
+processes company data. One Machine is one trust domain; use a separate Machine
 or equivalent infrastructure when mounted Organizations must not share an OS,
 disk or agent process.
 
-The documented default is one Organization per machine. A multi-Organization
-machine is an allowed exception inside one shared trust domain and needs
-separate provider sessions plus explicit acceptance of the cross-Organization
-endpoint risk.
+A Root can mount multiple authorized Organizations on one Machine. This is a
+repository and provider-access separation inside one shared trust domain, not
+hard tenant isolation. Keep provider sessions separately named and revocable,
+and explicitly accept the cross-Organization endpoint risk.
 
 ### 3. Select the execution provider
 
@@ -96,9 +96,9 @@ or account tier changes.
 
 ### 4. Enable the minimum repositories and integrations
 
-Start with one bounded use case. Give the principal only the repositories and
+Start with one bounded use case. Give the Principal only the repositories and
 provider scopes it needs. Follow the public [external application
-standard](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/external-app-integrations.md)
+standard](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/external-app-integrations.md)
 and test revocation.
 
 ### 5. Enforce publication rules
@@ -116,7 +116,7 @@ and incident escalation. Keep evidence with the rollout decision.
 
 ## Updating and rollback
 
-Lazurio source, Organization configuration and each module are versioned
+Lazurio source, Organization configuration and each Module are versioned
 independently. Updates should fast-forward clean primary checkouts, run the
 declared doctor/check gates and enter production through a reviewed exact
 commit. Rollback means returning the affected repository or deployment to a
@@ -127,7 +127,7 @@ or superseded access.
 
 - Who maintains endpoints, GitHub teams and external integrations?
 - Which execution client, model provider, account terms and subprocessors apply?
-- Where do module services run, and which networks can reach them?
+- Where do Module services run, and which networks can reach them?
 - Which logs exist and how long are they retained?
 - How are local data and credentials backed up, deleted and recovered?
 - Which components are source-checkout, hosted, experimental or target-only?
diff --git a/data/v2/docs/en/example-organization.md b/data/v2/docs/en/example-organization.md
new file mode 100644
index 0000000..afd007a
--- /dev/null
+++ b/data/v2/docs/en/example-organization.md
@@ -0,0 +1,145 @@
+---
+title: Example Organization
+description: A public-safe Lazurio Organization from provider identity and manifests to Workspace Modules and Launchpad.
+stableId: lazurio-doc-example-organization
+summary: Inspect the canonical Example Organization identity, generated root files, repository layout, Module discovery and safe lifecycle commands.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-example-fixture
+  - lazurio-organization-schema
+  - lazurio-map
+  - lazurio-launchpad
+  - lazurio-module-lifecycle
+audience:
+  - builder
+  - agent
+  - it-admin
+---
+
+The public source tests one canonical, synthetic Organization identity:
+
+| Field | Value |
+| --- | --- |
+| GitHub Organization login | `ExampleOrganization` |
+| Lazurio slug | `lazurio-example-organization` |
+| Display name | Lazurio Example Organization |
+| Root repository | `ExampleOrganization/ExampleOrganization_GEN3` |
+| Local mount shape | `organizations/<organization-checkout>` |
+
+These identifiers contain no customer data. They are used by the Organization
+installer tests and are safe for documentation, demos and agent evaluation.
+
+## 1. The generated Organization root
+
+Activation creates an Organization shell, not a collection of pretend apps:
+
+```text
+organizations/<organization-checkout>/
+├── AGENTS.md
+├── README.md
+├── company.gen3.json
+├── modules.manifest.json
+├── TODO.tasks.json
+├── DONE.tasks.json
+├── ISSUES.open.json
+├── company/
+│   └── colleagues/
+├── manual/
+├── workspace/
+│   └── README.md
+└── productionspace/
+    └── README.md
+```
+
+The root is one Git repository. Repositories mounted below `workspace/` or
+`productionspace/` remain separate checkouts and must not become Git
+submodules or gitlinks in the root repository.
+
+## 2. What the manifests own
+
+`company.gen3.json` is the current compatibility projection of the
+Organization identity and governance. The canonical v1 schema models the same
+Organization with immutable GitHub bindings, a Module manifest pointer and an
+explicit compatibility hash.
+
+The generated example records:
+
+```json
+{
+  "organization_generation": "gen3",
+  "organization_kind": "organization",
+  "company": {
+    "slug": "lazurio-example-organization",
+    "display_name": "Lazurio Example Organization",
+    "github_org": "ExampleOrganization",
+    "root_repository": "ExampleOrganization/ExampleOrganization_GEN3"
+  },
+  "governance": {
+    "default_branch": "main",
+    "access_authority": "github"
+  }
+}
+```
+
+`modules.manifest.json` declares repository slots and Team membership. The
+fresh fixture intentionally starts with an empty `module_slots` array.
+Activation does not invent Modules or reserve application ports.
+
+## 3. Add real Modules as separate repositories
+
+A useful demonstration Organization can then mount independently owned
+repositories:
+
+```text
+workspace/
+├── website/          # public product website Module
+├── knowledgebase/    # Organization knowledge application Module
+└── mission-control/  # Organization planning application Module
+
+productionspace/
+└── documentation/    # public documentation with its own release contract
+```
+
+Each Workspace Module owns its own `lazurio.module.json` and any runnable
+`lazurio.runtime.v1` declaration. The Organization manifest says where the
+repository belongs and which Teams it serves. The Module contract says how its
+application runs. GitHub grants decide who can read or change it.
+
+## 4. See the Organization in Launchpad
+
+![Launchpad showing the synthetic Lazurio Example Organization](/images/launchpad-example-organization.jpg)
+
+The screenshot is rendered from synthetic public-safe data against the real
+Launchpad UI. It demonstrates the product surface, not access to a real
+company.
+
+After a valid Organization root and Module manifests are mounted, select
+**Synchronize** or restart Launchpad. Discovery scans the manifest-backed
+mounts; `launchpad.gen3.json` is not an Organization allowlist.
+
+## 5. Inspect and open a Module
+
+With the Launchpad Server running:
+
+```sh
+lazurio module status --json
+lazurio module status ExampleOrganization/website --json
+lazurio module open ExampleOrganization/website --json
+```
+
+If a Module exposes more than one App, pass the exact declared package path.
+The CLI never guesses the first App. If another Organization owns the same
+listener lease, takeover requires explicit confirmation naming the exact App
+that would be replaced.
+
+## 6. Follow the boundaries
+
+- Put shared Organization work in the Organization root or a declared Module.
+- Put durable Organization knowledge in its Knowledgebase, not this public
+  example and not a personal chat.
+- Keep every person's Personalspace outside the Organization.
+- Keep production runtime, ingress, secrets, backup and rollback in a
+  production contract owned by the deployed application.
+- Use the [glossary](/en/glossary/) in manifests, prompts and diagrams.
diff --git a/data/v2/docs/en/faq.md b/data/v2/docs/en/faq.md
index b642c1a..0370fde 100644
--- a/data/v2/docs/en/faq.md
+++ b/data/v2/docs/en/faq.md
@@ -2,9 +2,9 @@
 title: Frequently asked questions
 description: Direct answers to the first questions people and IT administrators ask about Lazurio.
 stableId: lazurio-doc-faq
-summary: Answers about what Lazurio is, whether it replaces Copilot, data access, local deployment, approval, audits, and the future MCP server.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+summary: Answers about what Lazurio is, whether it replaces Copilot, data access, local deployment, approval, audits, and machine-readable documentation.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 secondReviewOwner: Pablo AI
 trustCritical: true
@@ -66,7 +66,7 @@ comparison](/en/lazurio-vs-microsoft-copilot/).
 
 <details>
 
-<summary>Can an agent access everything the user can?</summary>
+<summary>Can a Task Agent access everything the user can?</summary>
 
 Do not assume that, but do not assume policy removes an existing capability
 either. Effective access depends on the client sandbox, OS access, local
@@ -95,17 +95,17 @@ package.
 
 Real secrets stay outside Git in scoped, ignored custody paths or an approved
 provider store. Tracked files contain only schemas, required variable names and
-instructions. Read the public [secret custody standard](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/security/local-secret-custody.md).
+instructions. Read the public [secret custody standard](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/security/local-secret-custody.md).
 
 </details>
 
 <details>
 
-<summary>What stops an agent from publishing a bad change?</summary>
+<summary>What stops a Task Agent from publishing a bad change?</summary>
 
 The operating model distinguishes an editable draft from publication. GitHub
 branch rules, required checks, reviews and merge permissions can mechanically
-protect a branch. A task agent may still push a review branch when it has write
+protect a branch. A Task Agent may still push a review branch when it has write
 access, and that already moves source to GitHub. Email, chat and other providers
 need their own technical permissions; explicit authorization is a process
 control where the provider or client exposes no equivalent interlock.
@@ -114,10 +114,10 @@ control where the provider or client exposes no equivalent interlock.
 
 <details>
 
-<summary>Are Organizations isolated from each other on one machine?</summary>
+<summary>Are Organizations isolated from each other on one Machine?</summary>
 
 They are separate repository and GitHub access boundaries, but they are not
-hard OS tenants. One machine is one trust domain. Another process with the same
+hard OS tenants. One Machine is one trust domain. Another process with the same
 effective filesystem access may be able to read more than the active
 Organization. Use separate machines or equivalent infrastructure where that
 risk is unacceptable.
@@ -149,9 +149,10 @@ Local file reads and prompts are not automatically logged by Lazurio.
 
 <summary>Does the documentation have an MCP server?</summary>
 
-Not yet. Agents can use [`llms.txt`](/llms.txt) and the structured
-[`content-index.json`](/content-index.json) today. A future MCP server is
-planned as a read-only view over that same public content, not a second source.
+No. Agents can use [`llms.txt`](/llms.txt) and the structured
+[`content-index.json`](/content-index.json) today. A later MCP server could be
+a read-only view over that same public content, but it is not part of the
+current release and must not be presented as available.
 
 </details>
 
diff --git a/data/v2/docs/en/glossary.md b/data/v2/docs/en/glossary.md
new file mode 100644
index 0000000..5f221c2
--- /dev/null
+++ b/data/v2/docs/en/glossary.md
@@ -0,0 +1,60 @@
+---
+title: Glossary
+description: Canonical Lazurio terminology for people, agents, spaces, repositories and publication.
+stableId: lazurio-doc-glossary
+summary: Use the canonical Lazurio vocabulary consistently in documentation, prompts, diagrams, product copy and technical discussions.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-readme
+  - lazurio-architecture
+  - lazurio-collaboration-model
+audience:
+  - decision-maker
+  - builder
+  - agent
+  - it-admin
+---
+
+These terms are operating concepts, not decorative product labels. Use them
+consistently so a person and a Task Agent interpret ownership, scope and
+authority in the same way.
+
+## People and agent roles
+
+| Term | Canonical meaning |
+| --- | --- |
+| **Principal** | The person or AI Colleague for whom a Task Agent currently works, whose permissions apply, and who has the last word. |
+| **Colleague** | A human Principal participating through Organization roles, Teams and live provider grants. |
+| **AI Colleague** | A long-lived AI Principal with its own seat, identity, Machine, responsibility and grants. |
+| **Task Agent** | A temporary execution session such as Codex, Claude Code or Cursor. “Agent” is an acceptable conversational shorthand. It owns no permissions. |
+| **Buddy** | The personal AI representative of one human Principal. It acts only within that person's scoped, revocable mandates and belongs to Personalspace. |
+
+## Spaces and repositories
+
+| Term | Canonical meaning |
+| --- | --- |
+| **Machine** | One shared runtime, security and recovery boundary with a known owner; not a hardware category or IAM role. |
+| **Root** | The local working root that contains Lazurio, mounted Organizations and the current human Principal's optional Personalspace. |
+| **Organization** | One company, one GitHub Organization and one repository access boundary. |
+| **Team** | A logical N:M grouping declared for Modules and backed by live provider membership and grants; not an extra directory layer. |
+| **Module** | A versioned working capability in an Organization or Personalspace. It may contain a runnable application. |
+| **Workspace Module** | A separate repository mounted flat under `workspace/<module>` for everyday Organization work. |
+| **Productionspace** | Organization-level repositories with their own release and production contract. |
+| **Personalspace** | The private space of one Principal and an optional Buddy. It is never mounted for another Principal. |
+
+## Work and authority
+
+| Term | Canonical meaning |
+| --- | --- |
+| **Draft** | A reversible and editable result prepared for review. |
+| **Publication** | The exact action that makes a Draft externally visible or materially harder to reverse, such as merge, deploy or send. |
+| **Release** | A versioned external release, commonly a GitHub Release. It is distinct from ordinary Publication. |
+| **Access authority** | The live system that grants the action, normally GitHub membership, Teams, repository grants and branch rules for source work. |
+| **Dashboard** | The separately deployed administrative and product entry surface for accounts, Organizations, Marketplace, people, Machines, hosting and operational visibility. |
+| **Launchpad** | The builder-first local surface that discovers available Organizations and Modules and manages development application lifecycle. |
+
+Deprecated public names such as “HumanAndMachine” or “Conglomerate” are not
+synonyms for Lazurio. Historical repository and GitHub Organization identities
+may keep those names as provenance.
diff --git a/data/v2/docs/en/how-lazurio-works.md b/data/v2/docs/en/how-lazurio-works.md
index 2d089d1..7bb4058 100644
--- a/data/v2/docs/en/how-lazurio-works.md
+++ b/data/v2/docs/en/how-lazurio-works.md
@@ -1,10 +1,10 @@
 ---
-title: How Lazurio works
-description: The core operating model, from principal and Organization to draft and publication.
+title: Core concepts
+description: The people, agent roles, spaces and work states that make Lazurio predictable.
 stableId: lazurio-doc-how-it-works
-summary: Understand Lazurio's principals, agents, Organizations, repositories, workspace modules, drafts, reviews, and publication flow.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+summary: Learn the distinct concepts Lazurio uses for people, AI identities, Task Agents, Machines, Organizations, Modules, Personalspace, Drafts and Publication.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 sourceRefs:
   - lazurio-readme
@@ -17,94 +17,101 @@ audience:
   - agent
 ---
 
-Lazurio treats AI-assisted work as normal organizational work with explicit
-ownership and boundaries. A person starts with a desired outcome; an agent can
-inspect the authorized context, create an editable draft, verify it and prepare
-it for review. Authority does not come from the agent's confidence. It comes
-from the signed-in identity and the systems that own the action.
-
-The current public model is summarized in [English control
-evidence](/en/public-evidence/) and linked there to the exact reviewed source.
-
-## The five useful concepts
-
-**Principal** is the person or AI colleague for whom work is being done. The
-principal holds real permissions and the last word.
-
-**Task agent** is the active tool session. It works for the principal and has
-no independent authority. It can propose and prepare; a prompt does not make it
-an administrator.
-
-**AI colleague** is a longer-lived AI principal with its own account, machine,
-responsibility and grants. It is not the same thing as a temporary task-agent
-session. The same live provider and repository permissions still determine
-what it can do.
-
-**Organization** is one company's access boundary. In the documented model it
-maps to a GitHub organization and a separate repository root. Company-specific
-data and strategy stay within that Organization.
+Lazurio deliberately separates people, execution sessions, working spaces and
+publication states. Keeping these domains separate prevents a confident agent
+response, a folder name or a role label from being mistaken for authority.
+
+## Slice 1: people and agent roles
+
+```text
+Human Colleague ─┐
+                 ├─ is a Principal → uses permissions → has the last word
+AI Colleague ────┘
+
+Task Agent → temporary execution session working for its current Principal
+Buddy      → personal representative of one human Principal
+```
+
+- A **Principal** is the person or AI Colleague for whom the current work is
+  performed.
+- A **Colleague** is a human Principal participating through Organization
+  roles, Teams and provider permissions.
+- An **AI Colleague** is a long-lived AI Principal with its own identity,
+  Machine, responsibility and grants.
+- A **Task Agent** is a temporary tool session such as Codex, Claude Code or
+  Cursor. It has no independent authority.
+- A **Buddy** is the personal AI representative of one human Principal. It
+  belongs to that person's Personalspace and is not an AI Colleague seat.
+
+## Slice 2: spaces and boundaries
+
+```text
+Machine
+└── Lazurio Root
+    ├── Organization A
+    │   ├── workspace/Module repositories
+    │   └── productionspace repositories
+    ├── Organization B
+    └── Personalspace of this human Principal
+```
+
+A **Machine** is one runtime, security and recovery boundary with a known
+owner. It can be a workstation, VM or provider-isolated hosted workspace.
+
+An **Organization** is one company, one GitHub Organization and one repository
+access boundary. Multiple Organizations can be mounted under one Lazurio Root,
+but their repositories, secrets and company context remain separate.
+
+A **Workspace Module** is a separately versioned repository used in everyday
+Organization work. Modules live flat under `workspace/<module>` and declare
+their Team membership; directory nesting does not grant access.
+
+**Productionspace** holds Organization-level repositories with their own
+release and production model. Launchpad treats them as read-only unless a
+repository-specific policy says otherwise.
+
+**Personalspace** is private to one Principal and an optional Buddy. It is not
+an Organization collaboration store.
+
+## Slice 3: control surfaces
+
+```text
+Dashboard  → administer Organizations, people, Machines and hosted products
+Launchpad  → discover and run authorized local development Modules
+AI app     → host a Task Agent conversation and its tools
+CLI/Core   → provide headless context, diagnostics and lifecycle contracts
+```
+
+The surfaces share concepts but not ownership. Dashboard does not become the
+Launchpad process manager. Launchpad does not become an account or billing
+authority. The AI app does not become a new source of repository access.
+
+## Slice 4: from request to Publication
+
+1. **Scope:** name the Principal, Organization and Module.
+2. **Authority:** verify live access in GitHub or the relevant provider.
+3. **Context:** load only the repositories and tools required for the task.
+4. **Draft:** create an editable result, commonly a branch and pull request.
+5. **Evidence:** run checks and show the practical effect.
+6. **Decision:** an authorized Principal accepts or rejects the exact result.
+7. **Publication:** merge, deploy, send or otherwise make it effective.
+8. **Closeout:** record remaining work and clean temporary workspaces.
 
-**Workspace module** is an application or bounded work area inside an
-Organization. A module owns its runtime contract and can be developed,
-reviewed, deployed and rolled back independently.
+![Draft-to-publication flow](/diagrams/draft-publication-flow.svg)
 
-**Personalspace** is a private area for one principal. It is not an
-organizational collaboration store and is never a shortcut for moving company
-data across access boundaries.
+Publication is a state change, not a synonym for “the agent finished.” A
+commit and pushed pull request are reviewable Drafts in ordinary source work;
+the repository's branch rules and live permissions decide who may merge.
+Other systems have different boundaries, so their exact publish action must be
+named.
 
-## From request to published result
+## Source of truth without one giant database
 
-1. **Scope:** identify the Organization, module and intended outcome.
-2. **Authority:** use the signed-in principal's live access; do not invent a
-   second permission system in prose.
-3. **Context:** load only the repositories and tools required for the task.
-4. **Draft:** make the work in a reversible form, commonly a Git branch and
-   pull request.
-5. **Evidence:** run checks, show the practical effect and preserve review
-   context.
-6. **Decision:** an authorized principal approves or rejects the exact result.
-7. **Publication:** merge, deploy, send or otherwise make the result effective.
-8. **Closeout:** update the authoritative plan, record remaining issues and
-   clean temporary workspaces.
-
-This shape makes human review useful: the reviewer sees not only generated
-text, but the exact change, evidence, owner and publication decision.
-
-![Draft-to-publication flow](/diagrams/draft-publication-flow.svg)
+Lazurio brings relevant material into one working context without requiring
+every fact to be copied into one AI database. Code stays in Module repositories,
+plans stay in Mission Control, durable Organization knowledge stays in its
+Knowledgebase, and provider data stays behind scoped integrations.
 
-Git provides the clearest mechanical version of this flow. A task agent may
-create commits, push a review branch and open a pull request when the repository
-grant allows it; data has already reached GitHub at that point. Branch
-protection, required checks, reviews and merge permission can then block the
-protected-branch publication. Email, chat, billing and other providers have
-different mechanisms, so explicit authorization may be a process rule unless a
-named provider control enforces it.
-
-## Source of truth, not one giant database
-
-Lazurio does not require every kind of information to be copied into a single
-AI store. Code stays in repositories, plans stay in the Organization's Mission
-Control, durable knowledge stays in its Knowledgebase, and provider data stays
-behind a scoped integration. The working environment brings the relevant
-pieces together for a task while preserving their natural owners.
-
-That distinction matters operationally. Removing repository access or
-revoking an integration changes what the principal and its agent can reach;
-editing a role name in documentation does not.
-
-## What actually runs today
-
-The current supported setup is a public source checkout using Git and Bun. It
-contains Launchpad, CLI/Core v0, Doctor, operating manuals and the contracts
-used by connected Organizations and modules. CLI v0 remains experimental. A
-simple packaged CLI and automatically generated non-Git root are target
-architecture, not current distribution.
-
-Lazurio does not proxy or hide the model connection. The selected agent client
-and model provider receive the task context under their own terms. Optional
-hosted surfaces—Dashboard, hosted team workspaces or a per-owner Resident/Buddy
-service—must be inventoried separately when enabled.
-
-Ask for live configuration and provider readback when evaluating a specific
-deployment. The [IT briefing](/en/it-administrators/) lists the minimum
-evidence expected for approval.
+The [glossary](/en/glossary/) is the compact reference. The [Example
+Organization](/en/example-organization/) shows how these concepts appear on
+disk.
diff --git a/data/v2/docs/en/index.mdx b/data/v2/docs/en/index.mdx
index e2bcab0..47feeec 100644
--- a/data/v2/docs/en/index.mdx
+++ b/data/v2/docs/en/index.mdx
@@ -1,16 +1,16 @@
 ---
-title: "Lazurio: product, architecture and controls"
-description: A public, evidence-backed starting point for understanding and evaluating Lazurio.
+title: "Lazurio technical documentation"
+description: Build, connect and operate a Lazurio Organization with source-backed technical guidance.
 template: splash
 stableId: lazurio-doc-overview
-summary: Start here to understand what Lazurio is, what problem it solves, and which trust and operational questions to ask.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+summary: Start here to understand Lazurio's technical shape, current release boundary, and the path from a source checkout to an Organization with Modules.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 sourceRefs:
   - lazurio-readme
-  - lazurio-license
   - lazurio-architecture
+  - lazurio-map
   - lazurio-collaboration-model
 audience:
   - it-admin
@@ -18,59 +18,92 @@ audience:
   - builder
   - agent
 hero:
-  tagline: How Lazurio is built, where data can flow, and which controls a real deployment must prove.
+  tagline: The technical guide to Organizations, Modules, Launchpad and the AI apps that work alongside them.
   actions:
-    - text: For IT administrators
-      link: /en/it-administrators/
+    - text: Run the quickstart
+      link: /en/quickstart/
       icon: right-arrow
       variant: primary
-    - text: Compare with Microsoft Copilot
-      link: /en/lazurio-vs-microsoft-copilot/
+    - text: Explore the example Organization
+      link: /en/example-organization/
       icon: right-arrow
       variant: secondary
 ---
 
-Lazurio is a developer-stage local coordination layer for work done by people
-and AI agents. Today it is a public Git repository containing a CLI/Core,
-Launchpad, diagnostics, operating rules and a structure for mounting separate
-company repositories called Organizations. It is not an AI model, a managed
-SaaS tenant or a hard isolation layer around the selected agent client.
+Lazurio is a local working system in which people and AI cooperate across
+companies, projects and personal work without collapsing their repositories,
+data and permissions into one store. It supplies the structure, operating
+rules, diagnostics and Launchpad that let a Task Agent work inside a clearly
+named context.
 
-The current supported setup path is a source checkout using Git and Bun. The
-CLI is version 0 and experimental; a simple packaged installation is a target,
-not a released distribution. Source is currently available under
-[FSL-1.1-Apache-2.0](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/LICENSE.md),
-a source-available license. Permitted purposes include internal use,
-non-commercial education or research, and professional services for a licensee
-using the software compliantly. Permitted use may include copying, modification
-and redistribution, but redistributed copies and derivatives must keep the
-license link and copyright notices. A Competing Use means making the software
-available to others in a commercial product or service that substitutes for
-Lazurio or another product or service the licensor offers using it, or offers
-the same or substantially similar functionality. Each published version becomes
-available under Apache 2.0 on its second anniversary, and the software is
-provided without warranty. The notice names HumanAndMachine s.r.o. as copyright
-holder. Support, hosting and service-level commitments belong to a concrete
-commercial deployment and are not implied by this site.
+The model resembles open-source collaboration at organization scale. An
+Organization has maintainers, contributors, repository grants and review
+rules. Its Modules remain separate repositories with their own owners and
+lifecycle, while Lazurio presents the authorized set as one coherent working
+environment. The result feels monorepo-like to a builder without becoming one
+giant repository or a second permission system.
 
-Lazurio keeps companies in separate repositories, takes repository authority
-from GitHub and other provider grants, and makes consequential changes
-reviewable before publication. These rules improve governance; they do not
-make an endpoint, model or integration safe by themselves.
+## The system in four slices
 
-## Choose your path
+```text
+Administration
+Dashboard → account → Organization → Marketplace → Colleagues and grants
 
-- **Deciding whether to allow it:** read the [ten-minute IT
-  briefing](/en/it-administrators/) and the [data-access
-  review](/en/data-access-security/).
-- **Understanding the mechanics:** see [how Lazurio
-  works](/en/how-lazurio-works/) and how it is [deployed and
-  operated](/en/deployment-operations/).
-- **Checking the underlying claims:** use the reviewed [English control
-  evidence](/en/public-evidence/) and its links to the exact public source.
-- **Comparing alternatives:** use the sourced [Lazurio vs Microsoft
-  Copilot](/en/lazurio-vs-microsoft-copilot/) decision guide. They solve
-  overlapping, but not identical, problems.
-- **Letting an agent read the docs:** give it `/llms.txt` or
-  `/content-index.json`. Both are generated from the same reviewed pages that
-  people read.
+Daily work
+AI app / Task Agent ↔ Lazurio Root ↔ Organization ↔ Module repositories
+
+Builder surface
+Launchpad → discover Modules → inspect status → start or open development apps
+
+Authority
+GitHub identity + Teams + repository grants + branch rules → allowed actions
+```
+
+These slices connect, but they are not interchangeable:
+
+- **Dashboard** is the starting and administrative surface for Lazurio
+  accounts, Organizations, Marketplace Modules, Colleagues, permissions, AI
+  Colleague Machines, hosting and operational visibility. It is developed and
+  deployed separately from the public Lazurio Root.
+- **Launchpad** is the builder-first surface on a Machine. It discovers the
+  Organizations and Modules available in that Root and manages local
+  development application lifecycle.
+- **An AI app** hosts the current Task Agent session. Lazurio is not the model
+  and does not give the session new permissions.
+- **GitHub and connected providers** remain the live access authorities.
+
+## What is available now
+
+| Capability | Current state |
+| --- | --- |
+| Source Root with Git and Bun | Supported development path |
+| Launchpad and Organization discovery | Available in the public source |
+| CLI/Core v0 | Available, experimental and not a stable public API |
+| Desktop Launchpad installer | Available on macOS and Windows |
+| Packaged CLI and generated Managed Root | Target architecture, not the current distribution |
+| Dashboard | Separately developed product surface, not runtime authority for Launchpad |
+| Native Lazurio MCP server | Not included in the current release |
+
+The public Lazurio source uses
+[FSL-1.1-Apache-2.0](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/LICENSE.md).
+It is source-available today and receives the Apache 2.0 future license on the
+schedule defined in that license. Do not describe the current Lazurio release
+itself as OSI open source.
+
+## Where to go next
+
+- [Quickstart](/en/quickstart/) — verify a source checkout and open Launchpad.
+- [Core concepts](/en/how-lazurio-works/) — understand people, agent roles,
+  spaces and publication.
+- [Example Organization](/en/example-organization/) — follow one public-safe
+  Organization from manifest to Module.
+- [Components and source](/en/components-and-source/) — map each product
+  surface to its public source and license boundary.
+- [AI app support matrix](/en/use-with-ai-apps/) — choose a truthful workflow
+  for Codex, Claude, Cursor or Antigravity.
+- [Data access and security](/en/data-access-security/) — review the actual
+  trust and data-flow boundaries.
+
+Every page is also available to agents through `/llms.txt`,
+`/content-index.json` and the sitemap. They are generated from the same
+reviewed Markdown that people read.
diff --git a/data/v2/docs/en/it-administrators.md b/data/v2/docs/en/it-administrators.md
index 3fcb4dd..72bbdfe 100644
--- a/data/v2/docs/en/it-administrators.md
+++ b/data/v2/docs/en/it-administrators.md
@@ -3,8 +3,8 @@ title: Approval briefing for IT administrators
 description: The system picture, data paths, enforcement limits and evidence to review before a Lazurio pilot.
 stableId: lazurio-doc-it-administrators
 summary: A concise IT review of Lazurio's purpose, identity, access, data, integrations, operations, and approval boundaries.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 secondReviewOwner: Pablo AI
 trustCritical: true
@@ -21,15 +21,15 @@ audience:
   - agent
 ---
 
-Lazurio is a developer-stage local coordination layer for people and AI agents
-working across versioned company repositories and approved tools. Today the
-supported setup is a public source checkout run with Git and Bun. It includes
-an experimental CLI v0, Launchpad, diagnostics and operating contracts; it is
-not a vendor-managed AI service, a stable packaged installer or an additional
-sandbox around the selected agent client.
+Lazurio is a local working system for Colleagues, AI Colleagues and Task Agents
+operating across versioned Organization repositories and approved tools. The
+current supported setup is a Source Root run with Git and Bun. It includes
+CLI/Core v0, Launchpad, diagnostics and operating contracts; it is not a
+vendor-managed AI model, a released packaged distribution or an additional
+sandbox around the selected AI app.
 
-For a pilot decision, identify the operating identity and machine, the exact
-Organization repositories, the agent client and model provider, every enabled
+For a pilot decision, identify the operating identity and Machine, the exact
+Organization repositories, the AI app and model provider, every enabled
 integration, and the technical mechanism that permits or blocks each external
 action.
 
@@ -42,9 +42,9 @@ installation. Optional hosted surfaces must be listed explicitly when enabled.
 
 | Item | Current public position |
 | --- | --- |
-| Distribution | Developer source checkout using Git and Bun. A simple packaged installation is target architecture, not a released path. |
-| CLI and runtime | CLI v0 is experimental. Launchpad, Doctor and selected module/runtime flows work today, while broader distribution and resident onboarding are still evolving. |
-| License | [FSL-1.1-Apache-2.0](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/LICENSE.md): internal use, non-commercial education or research, and professional services for a compliant licensee are permitted. Permitted use may include copying, modification and redistribution, with the license link and copyright notices retained. A Competing Use means making the software available to others in a commercial product or service that substitutes for Lazurio or another product or service the licensor offers using it, or offers the same or substantially similar functionality. Each published version becomes Apache 2.0 on its second anniversary. The software is provided without warranty and is not currently under an OSI open-source license. |
+| Distribution | Source Root using Git and Bun. A simple packaged installation is target architecture, not the current release path. |
+| CLI and runtime | CLI v0 is experimental. Launchpad, Doctor and selected Module/runtime flows work today, while broader distribution and resident onboarding are still evolving. |
+| License | [FSL-1.1-Apache-2.0](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/LICENSE.md): internal use, non-commercial education or research, and professional services for a compliant licensee are permitted. Permitted use may include copying, modification and redistribution, with the license link and copyright notices retained. A Competing Use means making the software available to others in a commercial product or service that substitutes for Lazurio or another product or service the licensor offers using it, or offers the same or substantially similar functionality. Each published version becomes Apache 2.0 on its second anniversary. The software is provided without warranty and is not currently under an OSI open-source license. |
 | Product owner | The public license notice names HumanAndMachine s.r.o. as copyright holder. A concrete operator must identify its support, hosting, incident and contractual owners. |
 | Assurance | No certification, universal service level, default retention period or universal deployment topology is claimed. |
 
@@ -58,11 +58,11 @@ review remains an explicit delivery process step.
 
 | Area | Documented Lazurio position | What IT should verify for its deployment |
 | --- | --- | --- |
-| Identity | The signed-in principal supplies authority; a task agent does not gain independent rights from a prompt. | The human or service identity, repository membership and device owner are correct. |
-| Organization boundary | One company maps to one Organization and GitHub organization/access boundary. The documented default is one Organization per machine; a shared machine is an accepted exception within one trust domain, not hard tenant isolation. | The intended repositories and teams are the only ones mounted. Use separate machines or equivalent infrastructure where a stronger isolation boundary is required. |
-| Local workspace | Work starts from checked-out, versioned source on a principal-owned machine. | Device hardening, disk encryption, endpoint monitoring, backup and offboarding meet policy. |
+| Identity | The signed-in Principal supplies authority; a Task Agent does not gain independent rights from a prompt. | The human or service identity, repository membership and device owner are correct. |
+| Organization boundary | One company maps to one Organization and GitHub organization/access boundary. One Root can mount multiple authorized Organizations on one Machine, but that Machine remains one shared trust domain rather than hard tenant isolation. | The intended repositories and Teams are the only ones mounted. Use separate Machines or equivalent infrastructure where a stronger isolation boundary is required. |
+| Local workspace | Work starts from checked-out, versioned source on a Principal-owned Machine. | Device hardening, disk encryption, endpoint monitoring, backup and offboarding meet policy. |
 | Publication | Agent work is a reversible draft. Merge, deployment, sending and other external publication require explicit authority. | Repository rules, required reviews and deployment permissions enforce the intended gate. |
-| External apps | Integrations are locally curated and separately revocable; the preference is official MCP, then official CLI. New ChatGPT/claude.ai connectors and shared hosted brokers are outside the standard because they break per-machine custody. | Each enabled provider, OAuth scope, data flow, retention policy and revocation path is accepted. The standard defaults to read+write scopes needed by the workflow; read-only is optional tightening, not the assumed baseline. |
+| External apps | Integrations are locally curated and separately revocable; the preference is official MCP, then official CLI. New ChatGPT/claude.ai connectors and shared hosted brokers are outside the standard because they break per-Machine custody. | Each enabled provider, OAuth scope, data flow, retention policy and revocation path is accepted. The standard defaults to read+write scopes needed by the workflow; read-only is optional tightening, not the assumed baseline. |
 | Secrets | Secrets belong in ignored, scoped custody paths—not in Git or public documentation. | The chosen secret store, rotation, incident response and leak scanning are operational. |
 | Audit | Git commits, pull requests, reviews and provider logs create evidence, but coverage depends on the actual tools used. | Required logs exist across GitHub, endpoint, model provider, apps and deployment infrastructure. |
 
@@ -73,7 +73,7 @@ language note and enforcement limits.
 ## What data can be reached?
 
 There is no honest universal list because Lazurio is a framework whose concrete
-reach depends on the principal, machine, repository grants and enabled tools.
+reach depends on the Principal, Machine, repository grants and enabled tools.
 A deployment review should inventory five surfaces:
 
 1. Git repositories and teams visible to the operating identity.
@@ -89,19 +89,19 @@ revocation instructions.
 
 ## Which controls are technical?
 
-An instruction cannot remove a capability already present on the machine. A
-repository or OAuth token is a machine/session capability usable by processes
+An instruction cannot remove a capability already present on the Machine. A
+repository or OAuth token is a Machine/session capability usable by processes
 that can reach it; Lazurio does not add a universal security sandbox around
 Cursor, Codex, Claude Code or another execution client.
 
 | Action | Mechanical gate | Process reliance and when data leaves |
 | --- | --- | --- |
 | Read a local file or repository | OS permissions, mounted workspace and any client sandbox | Scope rules guide the agent. A readable file may be sent to the model provider when selected as task context; local reads are not automatically audited. |
-| Push a branch or open a pull request | GitHub repository write permission | Agents may prepare and push reviewable Draft work. Source leaves the machine when pushed; a pull request is not the protected-branch merge gate. |
+| Push a branch or open a pull request | GitHub repository write permission | Task Agents may prepare and push reviewable Draft work. Source leaves the Machine when pushed; a pull request is not the protected-branch merge gate. |
 | Merge a protected branch | GitHub branch rules, required checks, required reviews and live merge permission | Reviewer judgment remains a human/organizational control. |
 | Create a provider draft | Provider OAuth/API scope or CLI credential | A draft email, message or provider object already sends data to that provider even if it is not yet externally delivered. |
-| Send a message or mutate a provider | Whatever permission or confirmation the provider exposes | Explicit principal authorization is mandatory in the Lazurio process, but is not a universal technical interlock. Verify each integration and client. |
-| Deploy | Deployment credential plus provider and repository gates configured by the module | A reviewed exact-commit gate can be mechanical; the operator still owns environment selection, secrets and rollback. |
+| Send a message or mutate a provider | Whatever permission or confirmation the provider exposes | Explicit Principal authorization is mandatory in the Lazurio process, but is not a universal technical interlock. Verify each integration and client. |
+| Deploy | Deployment credential plus provider and repository gates configured by the Module | A reviewed exact-commit gate can be mechanical; the operator still owns environment selection, secrets and rollback. |
 
 ![Draft-to-publication flow](/diagrams/draft-publication-flow.svg)
 
diff --git a/data/v2/docs/en/lazurio-vs-microsoft-copilot.md b/data/v2/docs/en/lazurio-vs-microsoft-copilot.md
index 9ea0bc6..b00c265 100644
--- a/data/v2/docs/en/lazurio-vs-microsoft-copilot.md
+++ b/data/v2/docs/en/lazurio-vs-microsoft-copilot.md
@@ -3,8 +3,8 @@ title: Lazurio vs Microsoft Copilot
 description: A fair, sourced decision guide for two products with overlapping AI value but different control planes.
 stableId: lazurio-doc-copilot-comparison
 summary: Compare Lazurio with Microsoft Copilot across purpose, context, permissions, execution, extensibility, governance, and deployment.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 secondReviewOwner: Pablo AI
 trustCritical: true
@@ -43,11 +43,11 @@ the recommendations are our assessment.
 | --- | --- | --- |
 | Primary purpose | AI assistance inside the Microsoft 365 productivity environment. | Governed execution and durable collaboration across source-controlled organizational work. |
 | Natural context | Microsoft Graph and the user's permitted Microsoft 365 content, plus configured agents and connectors. | Selected Organization repositories, local workspace context and individually approved external tools. |
-| Permission foundation | The signed-in user's Microsoft 365 permissions, identity controls and service boundary. | The signed-in principal's GitHub/provider permissions and machine-scoped integrations; prompts do not grant authority. |
+| Permission foundation | The signed-in user's Microsoft 365 permissions, identity controls and service boundary. | The signed-in Principal's GitHub/provider permissions and Machine-scoped integrations; prompts do not grant authority. |
 | Typical output | Answers, summaries, drafts and actions in Microsoft applications and Copilot experiences. | Reviewable changes, plans, knowledge, applications and tool actions prepared through a defined draft-to-publication flow. |
-| Control plane | Microsoft-administered tenant services, licensing, Purview, Entra and Microsoft 365 administration. | Organization-owned Git repositories, machines, module contracts and each connected provider's own administration. |
+| Control plane | Microsoft-administered tenant services, licensing, Purview, Entra and Microsoft 365 administration. | Organization-owned Git repositories, Machines, Module contracts and each connected provider's own administration. |
 | Extensibility | Microsoft agents, Graph connectors, Copilot APIs and SDKs. | Modules, agent competence packages, MCP servers, official CLIs and browser workflows under local curation. |
-| Deployment | Microsoft-managed cloud service with published tenant requirements. | Framework and module deployment chosen per Organization; current public model begins with local checkouts and independently deployed modules. |
+| Deployment | Microsoft-managed cloud service with published tenant requirements. | Framework and Module deployment chosen per Organization; current public model begins with local checkouts and independently deployed Modules. |
 | Best fit | Productivity and knowledge work already centered on Microsoft 365. | Work that must cross repositories or tools while remaining source-controlled, testable and explicitly publishable. |
 
 Microsoft documents that Copilot works within the Microsoft 365 service
@@ -97,8 +97,8 @@ That is the natural route when the workflow should live inside Microsoft's
 product and governance ecosystem.
 
 Lazurio extensions are workspace modules and scoped tool integrations. The
-documented [external application standard](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/external-app-integrations.md)
-prefers official local MCP servers or CLIs and separately revocable machine
+documented [external application standard](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/external-app-integrations.md)
+prefers official local MCP servers or CLIs and separately revocable Machine
 identities. That is useful when the workflow is source-centric, crosses
 different providers or needs custom verification and publication gates.
 
@@ -115,7 +115,7 @@ different providers or needs custom verification and publication gates.
 
 ### Choose Lazurio first when
 
-- the output must become a reviewed repository change, module, operating plan
+- the output must become a reviewed repository change, Module, operating plan
   or durable organizational source of truth;
 - work crosses GitHub, local source and several non-Microsoft providers;
 - you need explicit company boundaries and an inspectable draft-to-publication
diff --git a/data/v2/docs/en/public-evidence.md b/data/v2/docs/en/public-evidence.md
index 0d480d9..0fb8c07 100644
--- a/data/v2/docs/en/public-evidence.md
+++ b/data/v2/docs/en/public-evidence.md
@@ -3,8 +3,8 @@ title: Lazurio control evidence in English
 description: Reviewed English summaries of the public Lazurio source used for product, security and operational claims.
 stableId: lazurio-doc-public-evidence
 summary: Verify the current product form, trust boundaries, authority model, integrations, hosted surfaces and evidence limits against one pinned public source revision.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 secondReviewOwner: Pablo AI
 trustCritical: true
@@ -23,20 +23,20 @@ audience:
 ---
 
 This page is the reviewed English evidence layer for Lazurio source revision
-[`3c5bda5d54c5556a0e54f3c339d988aa911fda60`](https://github.com/HumanAndMachines/Lazurio/tree/3c5bda5d54c5556a0e54f3c339d988aa911fda60).
+[`08d21803d4d4011304e1181ecf02ab9c5bfbad58`](https://github.com/HumanAndMachines/Lazurio/tree/08d21803d4d4011304e1181ecf02ab9c5bfbad58).
 The canonical source documents are currently written in Czech. The summaries
 below make the security-relevant meaning inspectable to English readers without
 pretending that a translation is independent assurance.
 
-## Product form and maturity
+## Current product form
 
-The [README](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/README.md)
+The [README](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/README.md)
 describes Lazurio as a local working system and coordination layer, not an AI
-model or shared cloud data store. It explicitly marks the project as active
-development. Today developers run it from a source checkout using Git and Bun;
-CLI v0 is experimental, while a simple packaged installation and generated
-non-Git root are target architecture. The repository uses
-[FSL-1.1-Apache-2.0](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/LICENSE.md).
+model or shared cloud data store. The current public distribution runs from a
+source checkout using Git and Bun. CLI v0 provides the current command surface;
+a packaged installation and generated non-Git root belong to the documented
+target architecture rather than the current distribution. The repository uses
+[FSL-1.1-Apache-2.0](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/LICENSE.md).
 Internal use, non-commercial education or research, and professional services
 for a compliant licensee are permitted. Permitted use may include copying,
 modification and redistribution, with the license link and copyright notices
@@ -48,35 +48,35 @@ its second anniversary, and the software is provided without warranty.
 
 ## Identity and authority
 
-The [collaboration model](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/AGENTS.md)
-defines a principal as the person or longer-lived AI identity for whom work is
-done. A task agent is a temporary execution session and owns no independent
+The [collaboration model](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/AGENTS.md)
+defines a Principal as the person or longer-lived AI identity for whom work is
+done. A Task Agent is a temporary execution session and owns no independent
 rights. A prompt cannot grant a provider or repository capability; live
 GitHub, OS and provider permissions remain authoritative.
 
-This does not mean the task agent has no capability. A credential, repository
+This does not mean the Task Agent has no capability. A credential, repository
 or file already exposed to its process can be used according to the execution
 client and OS boundary. Lazurio policy narrows intended use; the selected
 client sandbox and provider controls determine technical enforcement.
 
 ## Machine and Organization boundaries
 
-The [README](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/README.md)
-and [architecture](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/ARCHITECTURE.md)
-state that one machine is one trust domain. An Organization represents one
+The [README](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/README.md)
+and [architecture](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/ARCHITECTURE.md)
+state that one Machine is one trust domain. An Organization represents one
 company, one GitHub organization and a separate repository/access boundary.
 Multiple Organizations can coexist on one endpoint, but their folders are not
 hard OS tenants. A process with the same effective filesystem access can cross
 that directory boundary. Stronger isolation requires separate machines or
 equivalent infrastructure.
 
-Personalspace is private to one principal and is not a shared Organization
+Personalspace is private to one Principal and is not a shared Organization
 store. This is an access and process boundary; it should not be described as
 cryptographic isolation unless a deployment separately provides that control.
 
 ## Draft and publication
 
-The [collaboration model](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/AGENTS.md)
+The [collaboration model](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/AGENTS.md)
 defines a Draft as reversible, editable work and Publication as making a result
 externally effective or difficult to reverse. Agents may create branches,
 commits and pull requests when their repository grant permits it. Protected
@@ -88,18 +88,18 @@ exists.
 
 ## External applications and credentials
 
-The [integration standard](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/external-app-integrations.md)
-prefers an official machine-local MCP server, then an official CLI, then a
+The [integration standard](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/external-app-integrations.md)
+prefers an official Machine-local MCP server, then an official CLI, then a
 reviewed pinned implementation, with browser interaction as fallback. Each
-machine should use separately revocable provider credentials. New ChatGPT or
+Machine should use separately revocable provider credentials. New ChatGPT or
 claude.ai connectors and shared hosted brokers are outside the standard;
 provider-operated remote MCP remains acceptable when configuration and token
-custody are per-machine. The default scope for a workflow that needs writes is
+custody are per-Machine. The default scope for a workflow that needs writes is
 read+write, while read-only is optional tightening. An OAuth token is a
-machine/session capability, and MCP approval settings do not automatically
+Machine/session capability, and MCP approval settings do not automatically
 constrain CLI or shell access.
 
-The [secret custody standard](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/security/local-secret-custody.md)
+The [secret custody standard](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/security/local-secret-custody.md)
 keeps real credentials outside Git in ignored, scoped custody paths or approved
 provider stores. It does not claim that Lazurio itself encrypts the endpoint,
 rotates every secret or replaces backup and incident controls.
@@ -108,7 +108,7 @@ rotates every secret or replaces backup and incident controls.
 
 The source checkout contains the local root, Launchpad, Guide, CLI/Core, Doctor
 and mounted Organization modules. Launchpad and runnable modules use local
-loopback HTTP listeners with dynamically selected or module-owned port leases.
+loopback HTTP listeners with dynamically selected or Module-owned port leases.
 Loopback binding is not caller authentication: other processes on the endpoint
 may still reach those surfaces. Guide is a pedagogical application with local
 file-writing flows, not a security control.
@@ -128,7 +128,7 @@ processors, logs, retention, backup and deletion controls.
 - It does not create a universal retention, training or regional-processing
   claim for model providers.
 - It does not log every local file read, prompt or API call.
-- It does not turn Organization folders on one machine into hard tenants.
+- It does not turn Organization folders on one Machine into hard tenants.
 - It does not make process approval equivalent to a provider-enforced gate.
 
 Use the [IT briefing](/en/it-administrators/) to turn this evidence into a
diff --git a/data/v2/docs/en/quickstart.md b/data/v2/docs/en/quickstart.md
new file mode 100644
index 0000000..3a926fb
--- /dev/null
+++ b/data/v2/docs/en/quickstart.md
@@ -0,0 +1,108 @@
+---
+title: Quickstart
+description: Verify a Lazurio source checkout and open Launchpad using the current supported development path.
+stableId: lazurio-doc-quickstart
+summary: Install the current prerequisites, clone the public source, verify context and Doctor output, and start the builder-first Launchpad.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-readme
+  - lazurio-cli
+  - lazurio-launchpad
+audience:
+  - builder
+  - agent
+  - it-admin
+---
+
+The current supported development setup is a **Source Root**: a trusted Git
+checkout of Lazurio that also acts as the local working Root. The packaged CLI
+and generated Managed Root remain a target and should not be simulated by
+manually creating a partial directory tree.
+
+## Prerequisites
+
+- Git
+- [Bun](https://bun.sh/)
+- GitHub CLI (`gh`) for provider-backed Organization operations
+- a supported AI app or terminal session for Task Agent work
+
+## 1. Clone and inspect
+
+```sh
+git clone https://github.com/HumanAndMachines/Lazurio.git
+cd Lazurio
+
+bun run lazurio -- context --json
+bun run lazurio -- doctor
+```
+
+`context` projects a safe description of the current working scope. `doctor`
+checks the actual checkout, toolchain and mounted resources. Read each warning
+according to its named owner and next action; do not “fix” an empty Root by
+copying Organization or Personalspace data into the public source.
+
+## 2. Start Launchpad
+
+```sh
+bun run launchpad
+```
+
+Launchpad reports the address of the running instance. Use that exact URL;
+the port is runtime-owned and must not be guessed or hard-coded.
+
+A fresh checkout with no Organization mounted is valid. Launchpad discovers
+Organizations from local, Git-ignored mounts and their manifests.
+
+## 3. Optionally install the desktop launcher
+
+From the primary Source Root on macOS or Windows:
+
+```sh
+bun run lazurio -- launchpad install
+```
+
+Linux does not currently have this desktop-installer slice. The command does
+not register the CLI in `PATH` and does not modify the Git checkout.
+
+To expose the current checkout's CLI explicitly:
+
+```sh
+bun run lazurio -- cli install
+lazurio cli status
+```
+
+## 4. Attach an existing Organization
+
+An already active and readable Lazurio Organization can be materialized from
+its GitHub Organization login:
+
+```sh
+lazurio organization install <github-login> --json
+```
+
+The operation verifies the provider identity and expected root repository
+before materialization. GitHub access remains authoritative. Do not replace
+this with a manually authored access list.
+
+## 5. Verify Module lifecycle
+
+With Launchpad running and an Organization Module already declared:
+
+```sh
+lazurio module status --json
+lazurio module status ExampleOrganization/website --json
+```
+
+Start, open and stop require a real Module App declaration. See the
+[Example Organization](/en/example-organization/) and the source-backed
+[module lifecycle contract](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/module-lifecycle.md)
+before automating these commands.
+
+## Guided installation
+
+[Rozjedeme.ai](https://rozjedeme.ai/) is the official Lazurio integrator for
+teams that want a guided Organization setup, integration work or production
+rollout. Product support and service levels belong to the concrete engagement;
+they are not implied by the public source.
diff --git a/data/v2/docs/en/reference.md b/data/v2/docs/en/reference.md
index 639d6e1..5830cf6 100644
--- a/data/v2/docs/en/reference.md
+++ b/data/v2/docs/en/reference.md
@@ -2,9 +2,9 @@
 title: Public references
 description: The evidence set used by Lazurio documentation.
 stableId: lazurio-doc-reference
-summary: Inspect the pinned Lazurio source and current Microsoft Learn pages behind architectural, security, privacy, and comparison claims.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+summary: Inspect the pinned Lazurio source and current provider documentation behind architectural, AI app, security, privacy, and comparison claims.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 secondReviewOwner: Pablo AI
 trustCritical: true
@@ -15,6 +15,17 @@ sourceRefs:
   - lazurio-collaboration-model
   - lazurio-external-apps
   - lazurio-secret-custody
+  - lazurio-map
+  - lazurio-cli
+  - lazurio-launchpad
+  - lazurio-organization-schema
+  - lazurio-example-fixture
+  - lazurio-module-lifecycle
+  - openai-browser
+  - anthropic-claude-code-cli
+  - model-context-protocol
+  - cursor-agent-window
+  - antigravity-browser
   - microsoft-copilot-architecture
   - microsoft-copilot-data-protection
   - microsoft-copilot-privacy
@@ -41,12 +52,26 @@ regulatory review requires one.
 
 ## Lazurio source
 
-- [Project overview (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/README.md)
-- [License](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/LICENSE.md)
-- [Architecture (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/ARCHITECTURE.md)
-- [Collaboration, authority and publication model (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/AGENTS.md)
-- [External application integration standard (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/external-app-integrations.md)
-- [Local secret custody standard (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/security/local-secret-custody.md)
+- [Project overview (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/README.md)
+- [License](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/LICENSE.md)
+- [Architecture (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/ARCHITECTURE.md)
+- [Collaboration, authority and publication model (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/AGENTS.md)
+- [External application integration standard (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/external-app-integrations.md)
+- [Local secret custody standard (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/security/local-secret-custody.md)
+- [Repository map (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/MAP.md)
+- [CLI/Core v0 (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/lazurio/README.md)
+- [Launchpad (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/launchpad/README.md)
+- [Organization schema](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/lazurio/lazurio.organization.v1.schema.json)
+- [Example Organization fixture](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/lazurio/organization-install-lib.test.mjs)
+- [Module lifecycle (Czech)](https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/module-lifecycle.md)
+
+## AI app provider documentation
+
+- [Browser in ChatGPT desktop and Codex](https://learn.chatgpt.com/docs/browser)
+- [Claude Code CLI reference](https://docs.anthropic.com/en/docs/claude-code/cli-usage)
+- [Model Context Protocol](https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro)
+- [Cursor Agent Window](https://cursor.com/new)
+- [Google Antigravity Browser](https://antigravity.google/docs/browser)
 
 ## Microsoft provider documentation
 
diff --git a/data/v2/docs/en/use-cases.md b/data/v2/docs/en/use-cases.md
index a6e9a00..55fcc49 100644
--- a/data/v2/docs/en/use-cases.md
+++ b/data/v2/docs/en/use-cases.md
@@ -3,8 +3,8 @@ title: What Lazurio is good for
 description: Practical use cases and the conditions under which Lazurio is a good fit.
 stableId: lazurio-doc-use-cases
 summary: See where Lazurio helps with product delivery, operations, knowledge, agent workflows, and multi-organization work—and where it does not.
-updatedAt: "2026-08-27"
-reviewedAt: "2026-08-27"
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
 reviewOwner: Matej Suchanek
 sourceRefs:
   - lazurio-readme
@@ -26,7 +26,7 @@ truth, tool access and explicit publication decisions.
 
 ### Product and software delivery
 
-An agent can inspect a module, implement a bounded change, run its tests and
+A Task Agent can inspect a Module, implement a bounded change, run its tests and
 prepare a pull request with evidence. The team keeps normal Git ownership,
 review and rollback instead of accepting an opaque generated artifact.
 
@@ -34,8 +34,8 @@ review and rollback instead of accepting an opaque generated artifact.
 
 A task may need repository context plus an approved external application. The
 Lazurio integration model makes each provider connection an explicit,
-revocable part of the machine rather than assuming every agent should have a
-universal cloud broker.
+revocable part of the Machine rather than assuming every Task Agent should
+have a universal cloud broker.
 
 ### Durable organizational knowledge
 
@@ -49,19 +49,17 @@ Organizations can package scoped instructions, tools, tests and publishing
 gates for recurring work. That makes the next run start from a reviewed
 competence boundary rather than a copied prompt with hidden assumptions.
 
-### Multiple companies on one principal's machine (exception)
+### Multiple companies on one Principal's Machine
 
 The root can discover several authorized Organizations while keeping each one
 a separate GitHub and repository boundary. This is useful for founders,
 consultants and operators who genuinely work across companies and must not mix
 their private data.
 
-The recommended starting deployment is one Organization per machine. A
-multi-Organization machine is an allowed exception, not the default. It is not
-hard tenant isolation: one machine is one trust domain, so the
-Organizations can share an OS, disk and agent process with filesystem or
+This is not hard tenant isolation: one Machine is one trust domain, so the
+Organizations can share an OS, disk and Task Agent process with filesystem or
 network access. Keep provider sessions separately named and revocable, and use
-a separate machine or equivalent infrastructure where a compromise or
+a separate Machine or equivalent infrastructure where a compromise or
 over-broad client scope must not cross company boundaries.
 
 ## Use cases that need additional controls
diff --git a/data/v2/docs/en/use-with-ai-apps.md b/data/v2/docs/en/use-with-ai-apps.md
new file mode 100644
index 0000000..1b4da80
--- /dev/null
+++ b/data/v2/docs/en/use-with-ai-apps.md
@@ -0,0 +1,68 @@
+---
+title: Use Lazurio with AI apps
+description: A truthful support matrix for Codex, ChatGPT Desktop, Claude, Cursor Glass and Google Antigravity.
+stableId: lazurio-doc-use-with-ai-apps
+summary: Choose a current host workflow for a Task Agent and understand which clients can show Launchpad in-app, beside the app, or only through a separate browser.
+updatedAt: "2026-08-29"
+reviewedAt: "2026-08-29"
+reviewOwner: Matej Suchanek
+sourceRefs:
+  - lazurio-architecture
+  - lazurio-launchpad
+  - lazurio-external-apps
+  - openai-browser
+  - anthropic-claude-code-cli
+  - model-context-protocol
+  - cursor-agent-window
+  - antigravity-browser
+audience:
+  - builder
+  - agent
+  - it-admin
+---
+
+An AI app hosts the current **Task Agent**. Lazurio supplies the working Root,
+Organization boundaries, repository contracts, operating instructions,
+Launchpad and diagnostics. It does not replace the host model or silently
+grant the app access to every tool.
+
+## Current workflow matrix
+
+| Host surface | Task Agent path | Launchpad path | Current limitation |
+| --- | --- | --- | --- |
+| ChatGPT desktop with Codex | Open the Lazurio project in the desktop app | Built-in shared browser can open the reported local URL inside the chat | Built-in browser is a ChatGPT desktop capability, not a Codex CLI or IDE-extension feature |
+| Codex CLI or IDE extension | Run in the exact Root, Organization or Module scope | Open the reported URL in a separate browser | No built-in browser in these two surfaces |
+| Claude Code | Start Claude Code from the scoped checkout | Keep Launchpad open in a browser beside Claude Code | No Lazurio-specific native UI package is shipped |
+| Claude Desktop | No native Lazurio connection in the current release | Use Launchpad separately | Lazurio does not yet ship an MCP server or Claude Desktop app |
+| Cursor Agent Window (“Glass”) | Open the Lazurio Root or scoped repository as a Cursor project | Keep Launchpad in the available browser surface or a separate browser | No release-verified Lazurio embedded-panel contract |
+| Google Antigravity | Add the Root or scoped repository to a Project | Use the browser subagent to open the exact local URL | Browser runs in an isolated Chrome profile |
+
+“Can run an MCP server” and “Lazurio provides an MCP server” are different
+claims. Claude, Cursor and Antigravity expose MCP capabilities, but the current
+Lazurio release does not publish a native Lazurio MCP server.
+
+## The invariant workflow
+
+Regardless of host:
+
+1. Open the exact Lazurio Root, Organization or Module required for the task.
+2. Let the scoped `AGENTS.md` and repository rules define how work proceeds.
+3. Start or reuse Launchpad and copy its reported URL.
+4. Ask the Task Agent to inspect the exact scope before changing anything.
+5. Keep changes in a reviewable Draft.
+6. Verify live provider permissions before Publication.
+
+The app-specific pages show the UI differences:
+
+- [Codex and ChatGPT Desktop](/en/codex/)
+- [Claude](/en/claude/)
+- [Cursor Glass](/en/cursor-glass/)
+- [Google Antigravity](/en/antigravity/)
+
+## Data and trust reminder
+
+The selected AI client and model provider receive the context exposed to that
+session under their own product terms and controls. A Launchpad window does not
+isolate the model, create a new IAM layer or make a cross-Organization request
+safe. Review [data access and security](/en/data-access-security/) for a real
+deployment.
diff --git a/data/v2/public/images/launchpad-example-organization.jpg b/data/v2/public/images/launchpad-example-organization.jpg
new file mode 100644
index 0000000..9d95d98
Binary files /dev/null and b/data/v2/public/images/launchpad-example-organization.jpg differ
diff --git a/data/v2/sidebar.ts b/data/v2/sidebar.ts
index 5abcefc..f251ae6 100644
--- a/data/v2/sidebar.ts
+++ b/data/v2/sidebar.ts
@@ -1,19 +1,43 @@
 export const sidebar = [
-  { label: 'Overview', slug: 'index' },
   {
-    label: 'Evaluate Lazurio',
+    label: 'Start',
     items: [
-      { label: 'For IT administrators', slug: 'it-administrators' },
-      { label: 'Lazurio vs Microsoft Copilot', slug: 'lazurio-vs-microsoft-copilot' },
-      { label: 'Use cases', slug: 'use-cases' },
+      { label: 'Technical overview', slug: 'index' },
+      { label: 'Quickstart', slug: 'quickstart' },
+      { label: 'Core concepts', slug: 'how-lazurio-works' },
+      { label: 'Glossary', slug: 'glossary' },
+    ],
+  },
+  {
+    label: 'Build an Organization',
+    items: [
+      { label: 'Example Organization', slug: 'example-organization' },
+      { label: 'Components and source', slug: 'components-and-source' },
+    ],
+  },
+  {
+    label: 'Use with AI apps',
+    items: [
+      { label: 'Support matrix', slug: 'use-with-ai-apps' },
+      { label: 'Codex and ChatGPT Desktop', slug: 'codex' },
+      { label: 'Claude', slug: 'claude' },
+      { label: 'Cursor Glass', slug: 'cursor-glass' },
+      { label: 'Google Antigravity', slug: 'antigravity' },
     ],
   },
   {
-    label: 'Understand the system',
+    label: 'Operate Lazurio',
     items: [
-      { label: 'How Lazurio works', slug: 'how-lazurio-works' },
       { label: 'Data access and security', slug: 'data-access-security' },
       { label: 'Deployment and operations', slug: 'deployment-operations' },
+      { label: 'For IT administrators', slug: 'it-administrators' },
+    ],
+  },
+  {
+    label: 'Evaluate',
+    items: [
+      { label: 'Use cases', slug: 'use-cases' },
+      { label: 'Lazurio vs Microsoft Copilot', slug: 'lazurio-vs-microsoft-copilot' },
     ],
   },
   {
diff --git a/data/v2/source-map.json b/data/v2/source-map.json
index 1e3cfc2..e7ac969 100644
--- a/data/v2/source-map.json
+++ b/data/v2/source-map.json
@@ -1,66 +1,176 @@
 {
   "schema": "lazurio.documentation.source-map.v1",
-  "reviewedAt": "2026-08-27",
+  "reviewedAt": "2026-08-29",
   "sources": [
     {
       "id": "lazurio-readme",
       "title": "Lazurio README",
       "publisher": "Lazurio",
       "kind": "public-source",
-      "url": "https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/README.md",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/README.md",
       "reviewOwner": "Matej Suchanek",
-      "reviewedAt": "2026-08-27",
-      "reviewDueAt": "2026-11-27"
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
     },
     {
       "id": "lazurio-architecture",
       "title": "Lazurio architecture",
       "publisher": "Lazurio",
       "kind": "public-source",
-      "url": "https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/ARCHITECTURE.md",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/ARCHITECTURE.md",
       "reviewOwner": "Matej Suchanek",
-      "reviewedAt": "2026-08-27",
-      "reviewDueAt": "2026-11-27"
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
+    },
+    {
+      "id": "lazurio-map",
+      "title": "Lazurio repository map",
+      "publisher": "Lazurio",
+      "kind": "public-source",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/MAP.md",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
     },
     {
       "id": "lazurio-collaboration-model",
       "title": "Lazurio collaboration and access model",
       "publisher": "Lazurio",
       "kind": "public-source",
-      "url": "https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/AGENTS.md",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/AGENTS.md",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
+    },
+    {
+      "id": "lazurio-cli",
+      "title": "Lazurio CLI v0",
+      "publisher": "Lazurio",
+      "kind": "public-source",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/lazurio/README.md",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
+    },
+    {
+      "id": "lazurio-launchpad",
+      "title": "Lazurio Launchpad",
+      "publisher": "Lazurio",
+      "kind": "public-source",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/launchpad/README.md",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
+    },
+    {
+      "id": "lazurio-organization-schema",
+      "title": "Lazurio Organization schema",
+      "publisher": "Lazurio",
+      "kind": "public-source",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/lazurio/lazurio.organization.v1.schema.json",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
+    },
+    {
+      "id": "lazurio-example-fixture",
+      "title": "Public Example Organization fixture",
+      "publisher": "Lazurio",
+      "kind": "public-source",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/lazurio/organization-install-lib.test.mjs",
       "reviewOwner": "Matej Suchanek",
-      "reviewedAt": "2026-08-27",
-      "reviewDueAt": "2026-11-27"
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
+    },
+    {
+      "id": "lazurio-module-lifecycle",
+      "title": "Lazurio module lifecycle",
+      "publisher": "Lazurio",
+      "kind": "public-source",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/module-lifecycle.md",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
     },
     {
       "id": "lazurio-external-apps",
       "title": "External application integration standard",
       "publisher": "Lazurio",
       "kind": "public-source",
-      "url": "https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/external-app-integrations.md",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/external-app-integrations.md",
       "reviewOwner": "Matej Suchanek",
-      "reviewedAt": "2026-08-27",
-      "reviewDueAt": "2026-11-27"
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
     },
     {
       "id": "lazurio-secret-custody",
       "title": "Local secret custody standard",
       "publisher": "Lazurio",
       "kind": "public-source",
-      "url": "https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/manual/security/local-secret-custody.md",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/manual/security/local-secret-custody.md",
       "reviewOwner": "Matej Suchanek",
-      "reviewedAt": "2026-08-27",
-      "reviewDueAt": "2026-11-27"
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
     },
     {
       "id": "lazurio-license",
       "title": "Lazurio license",
       "publisher": "Lazurio",
       "kind": "public-source",
-      "url": "https://github.com/HumanAndMachines/Lazurio/blob/3c5bda5d54c5556a0e54f3c339d988aa911fda60/LICENSE.md",
+      "url": "https://github.com/HumanAndMachines/Lazurio/blob/08d21803d4d4011304e1181ecf02ab9c5bfbad58/LICENSE.md",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-11-29"
+    },
+    {
+      "id": "openai-browser",
+      "title": "Browser in ChatGPT desktop and Codex",
+      "publisher": "OpenAI",
+      "kind": "provider-documentation",
+      "url": "https://learn.chatgpt.com/docs/browser",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-09-29"
+    },
+    {
+      "id": "anthropic-claude-code-cli",
+      "title": "Claude Code CLI reference",
+      "publisher": "Anthropic",
+      "kind": "provider-documentation",
+      "url": "https://docs.anthropic.com/en/docs/claude-code/cli-usage",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-09-29"
+    },
+    {
+      "id": "model-context-protocol",
+      "title": "Model Context Protocol overview",
+      "publisher": "Model Context Protocol",
+      "kind": "provider-documentation",
+      "url": "https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-09-29"
+    },
+    {
+      "id": "cursor-agent-window",
+      "title": "Cursor Agent Window",
+      "publisher": "Cursor",
+      "kind": "provider-documentation",
+      "url": "https://cursor.com/new",
+      "reviewOwner": "Matej Suchanek",
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-09-29"
+    },
+    {
+      "id": "antigravity-browser",
+      "title": "Google Antigravity Browser",
+      "publisher": "Google",
+      "kind": "provider-documentation",
+      "url": "https://antigravity.google/docs/browser",
       "reviewOwner": "Matej Suchanek",
-      "reviewedAt": "2026-08-27",
-      "reviewDueAt": "2026-11-27"
+      "reviewedAt": "2026-08-29",
+      "reviewDueAt": "2026-09-29"
     },
     {
       "id": "microsoft-copilot-architecture",