ltcai 11.6.0 → 11.9.0

package/docs/CI_AND_RELEASE_GATES.md

@@ -1,6 +1,6 @@
 # CI & Release Gates
 
-> Status: reference 2026-07-21
+> Status: reference 2026-08-16
 
 Reference for the GitHub Actions workflows that guard `main` and releases, the
 supply-chain hardening applied to them, and the recommended branch-protection
@@ -11,13 +11,79 @@ configuration. Companion to [SECURITY_AUDIT.md](SECURITY_AUDIT.md) and
 
 | Workflow | File | Triggers | Purpose |
 |----------|------|----------|---------|
-| CI | `.github/workflows/ci.yml` | push/PR to `main` | Lint, typecheck, unit + integration tests, brain/agent eval gates, build + wheel smoke |
-| Release | `.github/workflows/release.yml` | tags `v*` / `[0-9]*` | Build & validate all artifacts (no publish) |
-| Visual Smoke | `.github/workflows/visual.yml` | push/PR, nightly cron, dispatch | Playwright visual smoke |
-| **Dependency Audit** | `.github/workflows/dependency-audit.yml` | push/PR, weekly cron, dispatch | pip-audit + npm audit + CycloneDX SBOMs |
-| **Postgres Integration** | `.github/workflows/postgres-integration.yml` | weekly cron, dispatch | Live SQLite→Postgres/pgvector migration test |
+| CI | `.github/workflows/ci.yml` | push/PR to `main` | Lint, typecheck, unit + coverage + integration tests, product-readiness, build + wheel smoke, Rust workspace |
+| Release | `.github/workflows/release.yml` | tags `v*` / `[0-9]*` | Build & validate artifacts (no publish; does not re-run CI lint/tests) |
+| Visual Smoke | `.github/workflows/visual.yml` | push to `main`, nightly cron, dispatch | Playwright visual smoke (not on PRs) |
+| Sidecar E2E | `.github/workflows/e2e-sidecar.yml` | nightly cron, dispatch | Live sidecar Playwright first-value loop |
+| Dependency Audit | `.github/workflows/dependency-audit.yml` | weekly cron, dispatch | pip-audit + npm audit + CycloneDX SBOMs |
+| Postgres Integration | `.github/workflows/postgres-integration.yml` | weekly cron, dispatch | Live SQLite→Postgres/pgvector migration test |
 
-The last two were added for the P2 deployment-trust / supply-chain workstream.
+There is no `agent-smoke.yml`. Hosted runners have no MLX models; a fail-open
+weekly smoke cannot report anything actionable.
+
+Every workflow sets `concurrency.group` to `<workflow-file-stem>-${{ github.ref }}`
+and cancels in-progress runs except on `main` (`cancel-in-progress: false` on
+`release.yml`, which runs on tags). Job timeouts: test 40, integration 25,
+build 20, rust 40, visual 15, sidecar 20, audit 15, release build 40,
+postgres 20.
+
+## CI matrix (`ci.yml`)
+
+Four legs. Job names are `Test (Python <ver> on <os>)`:
+
+| Leg | OpenAPI generate + upload | Full lint + typecheck + docs | Extension tests | Vitest | `pytest tests/unit/` | Coverage pytest (`tests/` + `--cov`) | Product readiness |
+|-----|---------------------------|------------------------------|-----------------|--------|----------------------|--------------------------------------|-------------------|
+| 3.11 + ubuntu-latest | yes | yes (`npm run lint`, `typecheck`, `docs:check-current`, `docs:check-links`) | yes (`test:browser-extension` && `test:vscode-extension`) | yes | yes | no | yes |
+| 3.12 + ubuntu-latest | no | Python only (`lint:python`) | no | yes | yes | no | no |
+| 3.14 + ubuntu-latest | no | Python only | no | yes | **no** (coverage invocation is the only pytest) | yes, line floor ≥90 | no |
+| 3.11 + macos-latest | no | Python only | no | yes | yes | no | no |
+
+Downstream jobs (after `test`): `Integration smoke test` (25 min), then
+`Build package` (20 min). `Rust workspace` is independent (40 min).
+
+Removed from CI **and deleted from the tree** in 11.8.0 — a script that is not
+a gate is a script that looks like one:
+
+- `scripts/check_python.py` — ruff parses every file on every test leg
+- `scripts/brain_quality_eval.py`
+- `scripts/agent_eval.py`
+- `scripts/bench_agent_smoke.py`
+
+## Local lint chain (`npm run lint`)
+
+Ten members, in order:
+
+1. `lint:python` (ruff + mypy)
+2. `lint:visual`
+3. `lint:frontend`
+4. `frontend:openapi:check`
+5. `scripts/check_i18n_literals.mjs`
+6. `check:i18n-namespaces`
+7. `check:bundle`
+8. `check:server-i18n`
+9. `scripts/check_release_evidence_bound.mjs`
+10. `check:max-file-lines`
+
+Not in the lint chain (CI calls the extension tests directly on the 3.11+ubuntu
+leg; the Python legacy-shim test is authoritative):
+
+- `test:browser-extension` / `test:vscode-extension` (script entries remain)
+- `check:legacy-debt` (script entry and `scripts/check_legacy_debt.mjs` both
+  removed — the mjs mirror had drifted from the Python test)
+- `check:python` (script entry and `scripts/check_python.py` both removed)
+
+`npm run typecheck` is frontend-only (`typecheck:frontend`). The VS Code
+extension is built by `test:vscode-extension` in CI and by `build_vsix.mjs`
+at release.
+
+## Coverage floor
+
+Python: `[tool.coverage.report] fail_under = 90` (line coverage). Branch
+measurement is off (`branch` is not set under `[tool.coverage.run]`). The
+coverage step runs only on 3.14 + ubuntu-latest.
+
+Frontend: `vitest.config.ts` still pins 100% thresholds on all four metrics;
+that is unchanged and still runs on every CI test leg.
 
 ## Supply-chain hardening: pinned actions
 
@@ -36,30 +102,22 @@ from the authoritative upstream refs via `git ls-remote --tags` on 2026-07-21.
 | actions/upload-artifact | v4.6.2 | `ea165f8d65b6e75b540449e92b4886f43607fa02` |
 
 Pinning coverage: **100% of current `uses:` entries** across `ci.yml`,
-`release.yml`, `visual.yml`, `dependency-audit.yml`, and
-`postgres-integration.yml`. All are first-party `actions/*`. If a third-party
-action is added later, resolve and pin its SHA the same way before merge.
+`release.yml`, `visual.yml`, `e2e-sidecar.yml`, `dependency-audit.yml`, and
+`postgres-integration.yml`. First-party `actions/*` plus pinned
+`Swatinem/rust-cache` and `dtolnay/rust-toolchain` on the Rust/integration
+legs. If a third-party action is added later, resolve and pin its SHA the same
+way before merge.
 
-## Dependency-audit gate posture (conservative)
+## Dependency-audit gate posture
 
-The audit workflow is intentionally **non-blocking on day-to-day PRs** and
-**strict on the scheduled/dispatch run**:
-
-- `push` / `pull_request`: `pip-audit` and `npm audit` run with
-  `continue-on-error` keyed on the event name, so a newly-disclosed CVE in a
-  transitive dependency never reddens an unrelated PR. Findings still appear in
-  the job summary and uploaded report artifacts.
-- `schedule` (weekly) / `workflow_dispatch`: the same steps run **strict** —
-  `pip-audit --strict` fails on any known vuln; `npm audit --audit-level=high`
-  fails on high/critical. This is the loud channel for triage.
+The audit workflow is **schedule + dispatch only** (not on push/PR). Both
+`pip-audit --strict` and `npm audit --audit-level=high` fail the job on
+findings. This is the loud channel for triage; a newly-disclosed CVE cannot
+redden an unrelated change.
 
 CycloneDX SBOMs (`sbom-python.json`, `sbom-npm.json`) are produced every run and
 uploaded as artifacts. Regenerate locally with `scripts/generate_sbom.py`.
 
-**To promote to a required blocking PR check:** remove the `continue-on-error`
-expressions in `dependency-audit.yml` and add `python-audit` / `npm-audit` to
-the required-checks list below.
-
 ## Postgres integration gate
 
 `postgres-integration.yml` runs the migration-integrity suite
@@ -70,31 +128,58 @@ the workflow sets that variable, and the test itself starts and tears down a
 GitHub-hosted `ubuntu-latest`). It is deliberately kept off the PR path (slow,
 image pull, needs Docker) and runs weekly + on demand.
 
+## Visual smoke and sidecar E2E
+
+This repository typically commits straight to `main`.
+
+- `visual.yml` runs on push to `main`, the nightly cron, and dispatch. It does
+  **not** run on pull requests.
+- `e2e-sidecar.yml` is nightly + dispatch only (no push, no PR).
+
 ## Recommended branch protection for `main`
 
-Required status checks (blocking):
+Required status checks (blocking). Names match the job `name:` fields:
+
+- `Test (Python 3.11 on ubuntu-latest)`
+- `Test (Python 3.12 on ubuntu-latest)`
+- `Test (Python 3.14 on ubuntu-latest)`
+- `Test (Python 3.11 on macos-latest)`
+- `Integration smoke test`
+- `Build package`
+- `Rust workspace`
 
-- `CI / Test (Python 3.11)`
-- `CI / Test (Python 3.12)`
-- `CI / Integration smoke test`
-- `CI / Build package`
-- `Visual Smoke / Playwright visual smoke`
+`Playwright visual smoke` is **not** a PR-blocking check: `visual.yml` no
+longer has a `pull_request` trigger. It still runs on every push to `main`.
 
-Advisory / non-blocking today (promote when the team is ready):
+Advisory / non-blocking (schedule + dispatch only):
 
-- `Dependency Audit / Python dependency audit (pip-audit)`
-- `Dependency Audit / npm dependency audit`
+- `Python dependency audit (pip-audit)`
+- `npm dependency audit`
 
-Additional recommended settings: require PRs before merge, require branches to
-be up to date, require linear history, and dismiss stale approvals on new
-commits.
+Additional recommended settings if pull requests are used: require PRs before
+merge, require branches to be up to date, require linear history, and dismiss
+stale approvals on new commits.
 
 ## Release gate (publication safety)
 
-`release.yml` builds and validates artifacts only — it never publishes. Package
-publication (PyPI / npm / VS Code Marketplace / Open VSX) is a manual step
-(`npm run publish:*`) using **exact version filenames**, never a `dist/*` glob,
-so pushing a tag can never publish by accident. See
+`release.yml` builds and validates artifacts only — it never publishes. A tag
+is only pushed on a commit that already passed CI, so the workflow does **not**
+re-run `npm run lint`, `npm run typecheck`, `docs:check-links`, frontend tests,
+or `pytest tests/unit/`.
+
+It still runs:
+
+- checkout / setup / installs
+- `npm run docs:check-current` (release-specific current-version docs gate)
+- `npm run build:assets`
+- `python scripts/product_readiness.py` (safety net)
+- `python -m build`, `wheel_smoke.py`, `twine check`
+- `npm pack`, vsce package
+- `validate_release_artifacts.py <v> --require-vsix --require-tgz`
+
+Package publication (PyPI / npm / VS Code Marketplace / Open VSX) is a manual
+step (`npm run publish:*`) using **exact version filenames**, never a `dist/*`
+glob, so pushing a tag can never publish by accident. See
 [../RELEASE.md](../RELEASE.md) for the full procedure.
 
 ## Limitations (honest)

package/docs/COMMUNITY_AND_PLUGINS.md

@@ -1,6 +1,6 @@
 # Community And Plugins
 
-Current release: **11.6.0 — One Door**.
+Current release: **11.9.0 — Working Order**.
 
 LatticeAI defines the path from a strong local-first framework (8.4.0
 action-aware baseline, 8.5.0 registry+DI hardening, 8.6.0 capture/navigation

package/docs/DEVELOPMENT.md

@@ -3,7 +3,7 @@
 > **Status: canonical** — current contributor guidance, kept in sync with the
 > current release.
 
-Current release: **11.6.0 — One Door**.
+Current release: **11.9.0 — Working Order**.
 
 This document is for contributors working on the local-first Digital Brain
 codebase. Product positioning and quick start stay in `README.md`; supported
@@ -32,15 +32,20 @@ Engineering work should preserve these boundaries:
 
 ```bash
 npm install
-npm run dev
+npm start
 ```
 
-The local app is served through the FastAPI sidecar at:
+`npm start` (or `bin/ltcai.js` / the `LTCAI` binary) is the product: it
+boots `lattice-host` and serves the SPA at:
 
 ```text
 http://127.0.0.1:4825/app
 ```
 
+`npm run dev` is **not** the product. It starts the 19-route Python AI
+worker with `--reload` (`latticeai.cli.entrypoint`). Use it when iterating
+on worker compute seams, not to serve the app.
+
 Apple Silicon local model extras:
 
 ```bash
@@ -53,7 +58,6 @@ Run the smallest affected gate while iterating. Before committing broad runtime,
 API, UI, or release work, run:
 
 ```bash
-npm run check:python
 npm run lint
 npm run typecheck
 npm run test:frontend
@@ -61,9 +65,21 @@ npm run test:unit
 npm run docs:check-links
 ```
 
-`npm run lint` runs the Python Ruff baseline, frontend TypeScript lint gate,
-visual smoke syntax checks, an exact generated-OpenAPI drift check, i18n literal
-checks, and browser-extension syntax/behavior tests.
+`npm run lint` is **ten** gates since 11.8.0, in order: `lint:python`
+(ruff + mypy), `lint:visual`, `lint:frontend`, `frontend:openapi:check`,
+`check_i18n_literals.mjs`, `check:i18n-namespaces`, `check:bundle`,
+`check:server-i18n`, `check_release_evidence_bound.mjs`, and
+`check:max-file-lines`. Three left in 11.8.0: `check:python` (ruff already
+parses every file on every CI test leg), `check:legacy-debt` (the mjs mirror had
+drifted from the Python test that states the same rule — the Python test is
+authoritative), and the extension tests, which CI now invokes directly on the
+3.11 + ubuntu leg.
+
+Coverage floors are not symmetrical, and the difference is deliberate rather
+than an oversight: **Python is a line-coverage floor of 90**
+(`[tool.coverage.report] fail_under = 90`, branch measurement off) and the
+frontend still pins **100% on all four vitest metrics**. Run
+`npm run test:coverage` / `npm run test:frontend:coverage` to see either.
 
 Use these when the change touches the relevant surface:
 
@@ -140,7 +156,8 @@ pre-tool/post-tool lifecycle:
 
 - browser `read-url` ingestion dispatches `tool.kg_ingest.*` events;
 - browser `ingest-current-tab` ingestion dispatches the same lifecycle;
-- `IngestionPipeline` remains the common ingestion boundary behind those routes.
+- the native ingest door in `lattice-ingest` (writing through `graph_write`)
+  remains the single ingestion boundary behind those routes.
 
 ## Documentation Sync
 
@@ -158,10 +175,13 @@ For user-facing, API, runtime, release, or packaging changes, check:
 Release/publish examples must use exact target-version filenames. Do not
 document wildcard artifact upload commands.
 
-For 9.9.0 release work, exact artifacts are:
+For 11.9.0 release work, exact artifacts are:
+
+- `dist/ltcai-11.9.0-py3-none-any.whl`
+- `dist/ltcai-11.9.0.tar.gz`
+- `ltcai-11.9.0.tgz`
+- `dist/ltcai-11.9.0.vsix`
+- `src-tauri/target/release/bundle/dmg/Lattice AI_11.9.0_aarch64.dmg`
 
-- `dist/ltcai-9.9.0-py3-none-any.whl`
-- `dist/ltcai-9.9.0.tar.gz`
-- `ltcai-9.9.0.tgz`
-- `dist/ltcai-9.9.0.vsix`
-- `src-tauri/target/release/bundle/dmg/Lattice AI_9.9.0_aarch64.dmg`
+The dmg is ad-hoc signed (effectively unsigned); `npm run release:validate`
+checks the names and presence, not a Developer ID signature.

package/docs/LEGACY_COMPATIBILITY.md

@@ -26,14 +26,18 @@ Removed layers stay listed in `legacy_compatibility.REMOVED_SHIMS` and in the
 
 ## Legacy Debt Gate
 
-Two gates keep the debt paid down:
+**One** gate keeps the debt paid down:
 
-- `scripts/check_legacy_debt.mjs` (part of `npm run lint`) — fails if a
-  disallowed root-level Python module reappears, or if any source tree imports
-  a removed root shim.
 - `tests/unit/test_legacy_root_shims.py` — asserts removed shims stay
-  unimportable, canonical replacements import, and the registry in
-  `latticeai.core.legacy_compatibility` matches reality.
+  unimportable and canonical replacements import.
+
+There used to be two. `scripts/check_legacy_debt.mjs` stated the same rule in
+JavaScript as part of `npm run lint`, and by 11.8.0 the two implementations had
+drifted apart — at which point having both was worse than having one, because
+neither could be trusted as the answer. The Python test is authoritative and the
+mjs mirror was deleted. `latticeai.core.legacy_compatibility` went with the
+platform code in 11.6.0; the registry it held described modules that no longer
+exist to shim.
 
 ## Root Module Map (removed in 9.9.1)
 

package/docs/ONBOARDING.md

@@ -1,6 +1,6 @@
 # Lattice AI Onboarding
 
-Current release: **11.6.0 — One Door**.
+Current release: **11.9.0 — Working Order**.
 
 The first-run goal is a five-minute path from "I opened the app" to "my Brain
 has a source, a question, and proof." This page is the product contract behind
@@ -10,8 +10,10 @@ read the docs first.
 ## Five-Minute Flow
 
 1. Wake the Brain and confirm the local owner profile.
-2. Let Lattice inspect local model/runtime readiness.
-3. Pick the recommended Brain voice or skip model loading.
+2. Let Lattice inspect local model/runtime readiness (`/setup/scan` is a
+   real probe; brew/pip items stay manual).
+3. Pick the recommended Brain voice (`/models/recommendations` probes RAM
+   and the worker catalog) or skip model loading.
 4. Add one source: upload a file, choose and scan a folder, save a note, or
    capture a browser/source event.
 5. Ask one grounded question and inspect the answer proof.

package/docs/OPERATIONS.md

@@ -1,4 +1,4 @@
-# Lattice AI — Operations Guide (v11.6.0)
+# Lattice AI — Operations Guide (v11.9.0)
 
 > **Status: canonical** — kept in sync with the current release. Storage layout
 > below reflects the SQLite live Brain store and workspace scoping, not the
@@ -29,6 +29,10 @@ tar -czf ltcai-backup-$(date +%Y%m%d).tar.gz ~/.ltcai ~/ltcai-agent
 tar -xzf ltcai-backup-YYYYMMDD.tar.gz -C ~
 ```
 
+인앱 복원(`.latticebrain` / `VACUUM INTO` 스냅샷)은 원자적입니다. **오래
+떠 있는 프로세스에서 복원하면 커넥션이 재활용되기 전까지 복원 전
+바이트를 줄 수 있습니다.** 복원 뒤에는 호스트를 재시작하십시오.
+
 ### 2.3 히스토리만 초기화
 ```bash
 rm ~/.ltcai/history.json

package/docs/PERMISSION_MODE.md

@@ -97,18 +97,23 @@ before routers are mounted would otherwise pin the store to the fallback
 
 ## Code map
 
+The dial is native. v11.6.0 moved the agent loop into `lattice-agent` and the
+routes into `lattice-platform`; v11.8.0 deleted the last Python module that
+still carried a copy of the gate helpers (`latticeai/core/agent_permission.py`,
+whose only readers were already ported).
+
 | Module | Role |
 |--------|------|
-| `latticeai/core/permission_mode.py` | Pure decision table |
-| `latticeai/core/agent_permission.py` | Agent plan/tool gate helpers |
-| `latticeai/core/agent/` | `SingleAgentRuntime` gates (mode-aware in-line: `planning.py` for the plan gate, `execution.py` for the per-tool gates) |
+| `rust/lattice-agent/src/mode.rs` | Pure decision table (port of `latticeai.core.permission_mode`) |
+| `rust/lattice-agent/src/permission.rs` | Plan/tool gate helpers — the ordered block-reason chain |
+| `rust/lattice-agent/src/breaker.rs` | Mode-invariant circuit breakers |
+| `rust/lattice-agent/src/agentloop/gates.rs` | The gates one executor step passes, in the order that decides it |
+| `rust/lattice-agent/src/agentloop/planning.rs` | The plan gate |
+| `rust/lattice-platform/src/permission_mode.rs` | HTTP routes + persistence (`permission_mode.json`, atomic replace) |
+| `rust/lattice-auth/src/policy.rs` | The tool policy table the gates read |
 | `frontend/src/components/PermissionModePanel.tsx` | Settings selector |
-| `latticeai/services/permission_mode_service.py` | Persistence |
-| `latticeai/runtime/permission_mode_wiring.py` | Process-wide service + router mount |
-| `latticeai/runtime/chat_wiring.py` | Agent runtime injection |
-| `latticeai/runtime/router_registration.py` | HTTP mount |
-| `latticeai/services/tool_dispatch.py` | `enforce_policy` + `build_agent_runtime` |
-| `latticeai/api/permission_mode.py` | HTTP routes |
+| `frontend/src/lib/permissionCopy.ts` | The plain-language wording for each mode |
+| `latticeai/core/permission_mode.py` | The worker's own `is_circuit_breaker`, asked by `POST /agent/tool` — the mode-invariant refusal holds on the executing side too, not only at the gate that dispatched |
 
 ## AGENTS.md note
 

package/docs/TRUST_MODEL.md

@@ -1,6 +1,6 @@
 # Lattice AI Trust Model
 
-Current release: **11.6.0 — One Door**.
+Current release: **11.9.0 — Working Order**.
 
 Lattice AI is local-first, explicit about external communication, and honest
 when a capability is unavailable.
@@ -24,10 +24,14 @@ Local data can include:
 
 External communication requires configuration plus a user/admin action:
 
-- cloud model calls after keys are configured and a cloud model is selected;
+- cloud model calls after credentials resolve (`cloud_provider.json` / env
+  key / locally OAuth-authenticated `agy` or `grok`) and the escalation
+  policy — or an explicit `/cloud` prefix — uses them. Every such turn
+  writes a shape-only egress audit (provider / model / reason, never
+  content) and stages extracted knowledge as a Review Center proposal;
 - model downloads from registries after install consent;
-- Telegram bridge after the integration is enabled, the chat is allowlisted,
-  and a dedicated server session bearer is configured;
+- Telegram bridge — removed in 11.6.0 with the platform code that became
+  the AI worker; nothing replaces it;
 - Brain Network peer actions after pairing;
 - Docker/Postgres setup after opt-in scale configuration;
 - update checks only when enabled;
@@ -51,7 +55,7 @@ Lattice AI should fail closed or show an unavailable state for:
 - no graph/context evidence available;
 - unavailable external integration;
 - unknown or unreadable Knowledge Graph workspace scope;
-- missing Telegram chat allowlist or dedicated server session token;
+- Telegram inbound (the bridge was removed in 11.6.0; nothing replaces it);
 - wrong archive passphrase;
 - archive tampering, unsupported archive versions, or path traversal.
 
@@ -67,7 +71,10 @@ does not mean secrets should appear in clear text.
 - Local files are only as protected as the user's machine, OS account, backups,
   and disk encryption.
 - Cloud model prompts follow the selected provider's policy once the user
-  explicitly chooses that provider.
+  explicitly chooses that provider (or the `auto`/`always` escalation
+  policy does, behind `cloud_allowed`). The `api_key` path is
+  mock-verified only in this release; live OAuth used `cli_oauth` at
+  zero billing. Extracted cloud knowledge is proposal-first.
 - A local admin can inspect local files and process memory outside Lattice AI.
 - Marketplace and model registries are third-party services when explicitly
   contacted.

package/docs/USABILITY_AUDIT.md

@@ -86,6 +86,11 @@ Heuristics:
 
 ## Journey 4 — Brain hierarchy
 
+> **Dated snapshot (2026-07-21).** `DepthEmergence.tsx` was deleted in v11.8.0
+> when the Brain home was redesigned; the depth-tiered reveal it describes is no
+> longer how the home discloses structure. The findings below are kept as the
+> record of what was evaluated at the time, not as current-truth surface notes.
+
 Surface: `frontend/src/features/brain/DepthEmergence.tsx`,
 `.../BrainMemoryLayer.tsx`.
 

package/docs/WHY_LATTICE.md

@@ -1,6 +1,6 @@
 # Why Lattice AI Exists
 
-Current release: **11.6.0 — One Door**.
+Current release: **11.9.0 — Working Order**.
 
 **Lattice AI is a local-first Digital Brain that keeps your knowledge durable
 across any AI model.**
@@ -25,8 +25,9 @@ material. That breaks down for real work:
 ## The Lattice Answer
 
 Lattice AI keeps conversations, documents, memories, decisions, relationships,
-and source provenance in a private local Brain. Models can be local, cloud,
-current, or future. The Brain remains.
+and source provenance in a private local Brain. Models can be local, or an
+optional cloud worker you hire (OAuth CLI or an API key). Default is local.
+The Brain remains.
 
 The graph matters as visible proof, but a graph editor is not the product
 identity. The product identity is a local-first Digital Brain: the user talks or
@@ -48,7 +49,8 @@ secondary.
 - Ask what the team decided and see the source.
 - Add documents and build a searchable private memory.
 - Prepare from old notes, project decisions, and files.
-- Preserve context when moving between models.
+- Preserve context when moving between models. Cloud is optional; default
+  is local.
 - Export or restore the Brain as an encrypted `.latticebrain` archive.
 - Use Korean or English without changing the underlying Brain.
 - Avoid fake answers when no model or evidence is available.

package/docs/kg-schema.md

@@ -1,6 +1,6 @@
 # Knowledge Graph Schema
 
-Current release: **11.6.0 — One Door**.
+Current release: **11.9.0 — Working Order**.
 
 명세 출처: `lattice_ai_full_spec.pptx` 슬라이드 20·21·22
 구현: `lattice_brain/graph/schema.py`
@@ -142,8 +142,12 @@ provenance(source_type, source_uri, content_hash, captured_at, modified_at,
   범위 없는 로컬 폴더는 개인 Brain으로 재투영하되 기존 노드 ID는 보존하며,
   같은 폴더를 다른 워크스페이스로 조용히 재할당하지 않는다.
 
-구현: `lattice_brain/ingestion/` (`IngestionPipeline`) 가 단일 진입점이며,
-파일/로컬폴더/URL/브라우저 탭/텍스트를 모두 이 형태로 정규화한다.
+구현: 단일 진입점은 v11.6.0부터 Rust의 네이티브 ingest 문
+(`lattice-ingest` → `lattice_core::graph_write`)이며, 파일/로컬폴더/URL/
+브라우저 탭/텍스트를 모두 이 형태로 정규화한다. `lattice_brain/ingestion/`은
+양쪽이 공유하는 어휘 — 라우팅 상수, DTO, 콘텐츠 해시, 추출 품질 점수 — 만
+남았고, v11.8.0이 마지막 잔재였던 `IngestionPipeline` 능력 프로브 클래스를
+그 유일한 호출 라우트와 함께 삭제했다.
 
 ---