ltcai 4.6.0 → 4.7.0

package/docs/PRODUCT_DIRECTION_REVIEW.md

@@ -0,0 +1,88 @@
+# Product Direction Review
+
+Date: 2026-06-14
+
+## Verdict
+
+The direction is coherent and meaningfully differentiated: Lattice AI should be
+positioned as a local-first Digital Brain, not as a graph database, note app,
+dashboard, or model launcher.
+
+The distinction between "Digital Brain" and "Knowledge Graph Product" is
+important. A graph product asks users to operate a data structure. A Brain
+product lets users converse with, grow, protect, and carry their own knowledge
+over time. The graph remains valuable, but it is infrastructure and an advanced
+inspection layer.
+
+## Fit With Current Implementation
+
+Already aligned:
+
+- First launch follows Login -> Environment Analysis -> Recommended Models ->
+  Install & Load -> Brain.
+- The post-setup home is the living Brain plus conversation.
+- The graph appears only after progressive depth: Brain -> Memories ->
+  Knowledge -> Relationships -> Graph.
+- Brain Core, SQLite default storage, optional PostgreSQL/pgvector scale mode,
+  backup/restore, and encrypted `.latticebrain` archives support user ownership.
+- Models are treated as swappable runtime workers rather than the durable asset.
+
+Gaps corrected in this review:
+
+- `KNOWLEDGE_GRAPH.md` described the Knowledge Graph as the durable center. It
+  now states that the Brain is the product and the graph is durable
+  infrastructure inside it.
+- `AI_PHILOSOPHY.md` now explicitly captures "models are temporary, knowledge is
+  durable" and the Brain-first interaction contract.
+- The Brain home header now surfaces ownership guarantees: Local-first,
+  Portable, Private.
+
+## Risks
+
+- "Living Brain" can feel abstract if the user cannot quickly see value from
+  their own documents and conversations. The first successful recall moment must
+  happen early.
+- A brain metaphor can become decorative if backup, restore, provenance, and
+  source evidence are hidden too deeply. The product should keep ownership and
+  evidence visible without becoming an admin console.
+- Model setup is still a high-friction moment. The product should make the first
+  local model recommendation feel safe, short, and reversible.
+- The graph layer must stay inspectable for power users without leaking graph
+  mechanics into the default experience.
+
+## Comparisons
+
+- Rewind / Limitless: personal memory, but Lattice should emphasize portable
+  user-owned Brain archives rather than capture-only recall.
+- Obsidian / Logseq: durable personal knowledge, but Lattice should avoid making
+  users manually manage the graph.
+- Notion AI / Mem: AI-assisted workspace memory, but Lattice should compete on
+  local-first ownership and model replaceability.
+- AnythingLLM / LM Studio: local AI tooling, but Lattice should not be framed as
+  a model runner.
+- Personal graph/RAG tools: relevant infrastructure peers, but not the product
+  category Lattice should lead with.
+
+## Priority
+
+1. Make first value unmistakable: ingest something, recall it in conversation,
+   show source evidence, and preserve it in the Brain.
+2. Keep the Brain as home. Avoid reintroducing dashboards, model catalogs, or
+   graph explorers as the first screen.
+3. Make Brain ownership tangible: backup, restore, export, inspect, and move
+   should be easy to find and phrased as care for the Brain.
+4. Improve the early model path until it feels like choosing a voice for the
+   Brain rather than configuring inference infrastructure.
+5. Keep graph power available as the deepest layer for advanced inspection.
+6. Keep the product reason visible in the first experience: models are
+   replaceable, but the user's knowledge, decisions, projects, and context are
+   the durable asset.
+
+## Product Answer
+
+Yes, this is a product people could want if it reliably turns their own
+knowledge into useful recall and keeps ownership credible. The strongest
+positioning is:
+
+Lattice AI is a local-first Digital Brain. It keeps your knowledge durable,
+portable, private, and useful across changing models.

package/docs/V4_6_0_LIVING_BRAIN_EXPERIENCE_REPORT.md

@@ -5,23 +5,26 @@
 v4.6.0 stops presenting Lattice AI as a graph product or dashboard. The
 first-run product flow is Login -> Environment Analysis -> Recommended Models
 -> Install & Load -> Brain. After setup, the Brain is the center of the desktop
-experience, and the graph is repositioned as an advanced layer for intentional
-relationship exploration.
+experience, and the graph is repositioned as the deepest layer inside Brain
+exploration rather than a separate destination.
 
 ## Product Changes
 
 - First launch opens to a premium minimal Login screen only.
 - Setup runs as a full-screen guided sequence: friendly environment analysis,
   short ranked model recommendations, and install/download/validate/load.
-- After model load, `/app` and `/app#/brain` open into Brain plus conversation.
-- The living Brain remains visible during primary conversation and reacts to
-  listening, recall, thinking, and active agent/workflow signals.
-- `/app#/ask` and `/app#/chat` remain compatible but route to the Brain
+- After model load, `/app` and compatible legacy entry URLs open into Brain plus
   conversation.
-- Primary navigation is reduced to Brain, Memory, Files, Automations, Models,
-  and Settings.
-- Brain tabs now follow the product ladder: Brain, Memories, Knowledge,
-  Relationships, Graph, Care.
+- The living Brain is an anatomical, recognizable Brain that remains visible
+  during primary conversation and reacts to listening, recall, thinking,
+  planning, and active agent/workflow signals.
+- Brain exploration now has five depths:
+  Living Brain, Memory Layer, Knowledge Layer, Relationship Layer, and
+  Knowledge Graph.
+- The Knowledge Graph appears only at Level 5 and includes nodes, edges, search,
+  and focus details.
+- `/chat`, `/ask`, `/graph`, and other legacy entry URLs remain compatible app
+  entry points, but the primary user path inward is through the Brain itself.
 - First-run setup no longer appears as dashboard cards above any app page; it
   gates the app before the Brain opens.
 
@@ -29,23 +32,25 @@ relationship exploration.
 
 - Added `frontend/src/components/LivingBrain.tsx` as the animated Brain
   presence component.
-- Added `frontend/src/components/BrainConversation.tsx` to centralize chat
-  streaming, history, image attachment, model status, memory previews, and
-  Brain activity state.
+- Updated `frontend/src/App.tsx` to own the five-depth Brain journey and the
+  emergent graph surface.
+- `frontend/src/components/BrainConversation.tsx` remains available for legacy
+  page compatibility and now shares the expanded Brain activity states.
 - Added `frontend/src/components/ProductFlow.tsx` to own Login, environment
   analysis, recommendation, install/download/validate/load, and Brain entry.
-- Kept graph parsing, Cytoscape rendering, search, provenance, portability, and
-  archive APIs intact.
+- Kept graph APIs, memory APIs, search, provenance, portability, and archive
+  APIs intact.
 - Kept FastAPI, Tauri, StorageEngine, Brain Core, backup/restore, and
   portability unchanged.
 
 ## Compatibility
 
 - Existing backend routes are unchanged.
-- Legacy hash routes continue to resolve through the SPA route alias table.
-- The advanced graph remains available at `/app#/knowledge-graph`.
-- The old Ask page imports the shared Brain conversation component to avoid
-  duplicate chat behavior.
+- Legacy hash routes and redirects continue to arrive inside the SPA.
+- The advanced graph capability remains available as Level 5 of Brain
+  exploration.
+- The older route components remain in source for compatibility while the
+  primary app surface is the Brain Space.
 
 ## Validation Scope
 
@@ -56,3 +61,12 @@ The v4.6.0 work should be validated with:
 - affected visual tests
 - unit tests covering version consistency and route compatibility
 - Tauri cargo check when the desktop toolchain is available
+
+Validated in this update:
+
+- `npm run lint`
+- `npm run test:visual`
+- `npm run check:python`
+- `npm run test:unit`
+- `npm run test:integration` with the local server on port 8899
+- `npm run build`

package/docs/V4_6_1_RELEASE_REFRESH_REPORT.md

@@ -0,0 +1,42 @@
+# v4.6.1 Living Brain Release Refresh Report
+
+## Scope
+
+v4.6.1 is the publishable Living Brain release refresh after the v4.6.0 PyPI
+immutability block. The work intentionally does not redesign backend
+architecture or add unrelated product features.
+
+## Completed Refresh Areas
+
+- Synchronized current-release version metadata to `4.6.1`.
+- Reframed README around the current Living Brain flow:
+  Login -> Environment Analysis -> Recommended Models -> Install & Load ->
+  Brain Chat.
+- Documented the five Brain depths: Living Brain, Memory Layer, Knowledge Layer,
+  Relationship Layer, and Knowledge Graph.
+- Kept the Knowledge Graph positioned as the deepest Brain exploration layer,
+  not a standalone dashboard or home screen.
+- Updated ARCHITECTURE.md for the current Tauri, React/Vite, FastAPI,
+  independent `lattice_brain`, StorageEngine, SQLite default, optional
+  PostgreSQL/pgvector, backup/restore, and `.latticebrain` portability reality.
+- Added v4.6.1 release notes and synchronized the changelog, feature status,
+  security policy, VS Code extension README, and release guide.
+
+## Evidence
+
+Fresh v4.6.1 screenshots and walkthrough media are indexed in
+[output/release/v4.6.1/SCREENSHOT_INDEX.md](../output/release/v4.6.1/SCREENSHOT_INDEX.md).
+
+## Expected Artifacts
+
+- `dist/ltcai-4.6.1-py3-none-any.whl`
+- `dist/ltcai-4.6.1.tar.gz`
+- `dist/ltcai-4.6.1.vsix`
+- `ltcai-4.6.1.tgz`
+- `src-tauri/target/release/bundle/dmg/Lattice AI_4.6.1_aarch64.dmg`
+
+## Validation Checklist
+
+The final release report records command results, artifact SHA256 hashes, commit,
+tag, push, and GitHub Release URL. External package registries are not published
+by this refresh.

package/docs/V4_7_0_ADMIN_SEPARATION_REPORT.md

@@ -0,0 +1,42 @@
+# v4.7.0 Admin Separation Report
+
+## Scope
+
+v4.7.0 turns Lattice AI into a cleaner product split: everyday users live in the
+Living Brain, while operators use a dedicated Admin Console for observability and
+maintenance. This release does not redesign Brain Core or the storage layer.
+
+## Completed Areas
+
+- Separated the admin route into `#/admin` while keeping `/app` focused on Brain
+  plus conversation.
+- Added admin overview cards for users, recent logs, security, and Brain index
+  status.
+- Added admin panels for user directory, audit logs, security events, policies,
+  and index rebuild operations.
+- Added workspace-aware filtering for admin summary, stats, sensitivity, and
+  audit reads when the active workspace header/query is present.
+- Added frontend API helpers for `/admin/stats` and `/admin/security/events`.
+- Updated visual validation to confirm the admin console is separate from the
+  user Brain surface.
+- Synchronized current-release version metadata to `4.7.0`.
+- Updated README, RELEASE.md, release notes, changelog, architecture, security,
+  feature status, VS Code extension docs, and release evidence references.
+
+## Evidence
+
+Fresh v4.7.0 screenshots and walkthrough media are indexed in
+[output/release/v4.7.0/SCREENSHOT_INDEX.md](../output/release/v4.7.0/SCREENSHOT_INDEX.md).
+
+## Expected Artifacts
+
+- `dist/ltcai-4.7.0-py3-none-any.whl`
+- `dist/ltcai-4.7.0.tar.gz`
+- `dist/ltcai-4.7.0.vsix`
+- `ltcai-4.7.0.tgz`
+- `src-tauri/target/release/bundle/dmg/Lattice AI_4.7.0_aarch64.dmg`
+
+## Validation Checklist
+
+The final release report records command results, artifact SHA256 hashes, commit,
+tag, push, GitHub Release URL, and package registry publish status.

package/docs/V4_DIGITAL_BRAIN_RECOVERY.md

@@ -5,21 +5,23 @@
 > completed analysis. **Update this file before ending any phase and before any
 > likely session/context/usage limit.**
 >
-> Last updated: 2026-06-13 — v4.6.0 Living Brain Experience; Remaining Gaps remain empty
+> Last updated: 2026-06-14 — v4.7.0 Admin Separation Release; Remaining Gaps remain empty
 
 ---
 
-## 0. RELEASE STATUS (v4.6.0)
-
-**v4.6.0 makes the Brain the product after the v4.5.1 product-shell reset
-without changing Brain Core, storage, API, model runtime, backup, portability,
-or agent/workflow behavior.** Current implementation milestone: Brain plus
-conversation is the home screen, the living Brain is always visible during the
-primary conversation experience, and graph exploration is preserved as the
-deepest intentional layer behind Memories, Knowledge, and Relationships.
-The v4.6.0 process builds locally validated artifacts only. Tagging, GitHub
-Release creation, PyPI, npm Registry, VS Code Marketplace, Open VSX, and
-production deployments remain out of scope unless explicitly requested.
+## 0. RELEASE STATUS (v4.7.0)
+
+**v4.7.0 is the Admin Separation Release. It keeps the Living Brain
+implementation without changing Brain Core, storage, API, model runtime, backup,
+portability, or agent/workflow behavior.** Current implementation milestone:
+Brain plus conversation is the home screen, the living Brain is always visible
+during the primary conversation experience, graph exploration is preserved as
+the deepest intentional layer, and operators use a separate Admin Console for
+users, logs, security events, policies, and Brain operations.
+The v4.7.0 process builds locally validated artifacts, tag, and GitHub Release
+assets. PyPI, npm Registry, VS Code Marketplace, and Open VSX publishing are
+explicitly requested for v4.7.0 and are gated by available owner credentials.
+Production deployments remain out of scope unless explicitly requested.
 Remaining implementation gaps: **none**.
 Owner-only blockers: pptx history rewrite (requires force-push/owner decision)
 and consent-gated production embedder provisioning (silent default download is
@@ -27,12 +29,12 @@ not permitted).
 
 ## Remaining Gaps
 
-None. v4.6.0 preserves the already-empty v4.3.2/v4.3.3/v4.5.0/v4.5.1 gap list
-and promotes the Living Brain tree: Brain conversation is primary, graph
-exploration remains real and API-backed, readable product state remains in
-place, archive import/restore flows remain exposed through existing APIs,
-desktop sidecar behavior remains validated, and exact v4.6.0 artifacts are the
-validation target.
+None. v4.7.0 preserves the already-empty v4.3.2/v4.3.3/v4.5.0/v4.5.1/v4.6.0
+gap list and promotes the Living Brain tree: Brain conversation is primary,
+admin operations are separate, graph exploration remains real and API-backed,
+readable product state remains in place, archive import/restore flows remain
+exposed through existing APIs, desktop sidecar behavior remains validated, and
+exact v4.7.0 artifacts are the validation target.
 Owner-only blockers above are intentionally not implementation gaps.
 
 ## 1. Program Charter (from the user's v4.0.0 directive)