ltcai 4.6.1 → 4.7.0

package/README.md

@@ -7,56 +7,61 @@
 [![CI Status](https://github.com/TaeSooPark-PTS/LatticeAI/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/TaeSooPark-PTS/LatticeAI/actions/workflows/ci.yml)
 [![License](https://img.shields.io/badge/license-MIT-green)](LICENSE)
 
-**Lattice AI v4.6.1 is the local-first Living Brain release refresh.** It keeps
-the v4 Brain Core, StorageEngine, FastAPI localhost API, Tauri shell, backup,
-restore, model runtime, graph, and portability architecture intact while making
-the release/publishable version `4.6.1` after the v4.6.0 PyPI immutability
-block.
-
-The product opens with a private local profile, studies the computer, recommends
-models, asks before install/download/load work, then lands in Brain Chat. The
-graph is still real and searchable, but it now grows out of the Brain as the
-deepest exploration layer instead of acting like a separate dashboard.
+**Lattice AI v4.7.0 is the local-first Living Brain admin separation release.**
+It keeps the v4 Brain Core, StorageEngine, FastAPI localhost API, Tauri shell,
+backup, restore, model runtime, graph, and portability architecture intact while
+making the normal user surface simpler and moving logs, users, security events,
+and Brain operations into a separate Admin Console.
+
+The product opens by stating the core reason to exist: models will change, but
+the user's knowledge should not. It creates a private local profile, studies the
+computer, recommends a replaceable model voice, asks before install/download/load
+work, then lands in Brain Chat with starter prompts for durable decisions,
+projects, documents, and context. The graph is still real and searchable, but it
+now grows out of the Brain as the deepest exploration layer instead of acting
+like a separate dashboard.
 
 External package registries are owner-published and can lag behind this GitHub
-Release. Release uploads must use the exact v4.6.1 artifact filenames below.
+Release. Release uploads must use the exact v4.7.0 artifact filenames below.
 
 ## Living Brain Flow
 
 ### 1. Login
 
 First launch opens to Login only. The local profile is the beginning of the
-Brain, not a dashboard, graph, or setup grid.
+Brain, not a dashboard, graph, or setup grid. The first screen frames Lattice as
+a durable knowledge home where models are replaceable and ownership stays with
+the user.
 
-![Login](output/release/v4.6.1/screenshots/01-login.png)
+![Login](output/release/v4.7.0/screenshots/01-login.png)
 
 ### 2. Environment Analysis
 
 Lattice reads the machine locally and summarizes what kind of Brain this
 computer can support.
 
-![Environment Analysis](output/release/v4.6.1/screenshots/02-environment-analysis.png)
+![Environment Analysis](output/release/v4.7.0/screenshots/02-environment-analysis.png)
 
 ### 3. Recommended Models
 
 The model step is a short recommendation list. It avoids catalog noise and keeps
 runtime/install details behind clear user consent.
 
-![Recommended Models](output/release/v4.6.1/screenshots/03-recommended-models.png)
+![Recommended Models](output/release/v4.7.0/screenshots/03-recommended-models.png)
 
 ### 4. Install And Load
 
 The install screen keeps consent visible and shows install, download, validate,
 and load progress. No model download or runtime install starts silently.
 
-![Install and Load](output/release/v4.6.1/screenshots/04-install-load-progress.png)
+![Install and Load](output/release/v4.7.0/screenshots/04-install-load-progress.png)
 
 ### 5. Brain Chat
 
 After setup, the home experience is the living Brain plus conversation. The Brain
 stays present while the user types, recalls context, and receives responses.
 
-![Brain Chat Home](output/release/v4.6.1/screenshots/05-brain-chat-home.png)
+![Brain Chat Home](output/release/v4.7.0/screenshots/05-brain-chat-home.png)
 
 ## Brain Depths
 
@@ -65,22 +70,26 @@ while revealing more structure.
 
 | Depth | Experience | Evidence |
 | --- | --- | --- |
-| Level 1 | Living Brain presence | ![Living Brain Level 1](output/release/v4.6.1/screenshots/06-living-brain-level-1.png) |
-| Level 2 | Memory Layer | ![Memory Layer](output/release/v4.6.1/screenshots/07-memory-layer.png) |
-| Level 3 | Knowledge Layer | ![Knowledge Layer](output/release/v4.6.1/screenshots/08-knowledge-layer.png) |
-| Level 4 | Relationship Layer | ![Relationship Layer](output/release/v4.6.1/screenshots/09-relationship-layer.png) |
-| Level 5 | Knowledge Graph with nodes, edges, search, and focus detail | ![Knowledge Graph Layer](output/release/v4.6.1/screenshots/10-knowledge-graph-layer.png) |
+| Level 1 | Living Brain presence | ![Living Brain Level 1](output/release/v4.7.0/screenshots/06-living-brain-level-1.png) |
+| Level 2 | Memory Layer | ![Memory Layer](output/release/v4.7.0/screenshots/07-memory-layer.png) |
+| Level 3 | Knowledge Layer | ![Knowledge Layer](output/release/v4.7.0/screenshots/08-knowledge-layer.png) |
+| Level 4 | Relationship Layer | ![Relationship Layer](output/release/v4.7.0/screenshots/09-relationship-layer.png) |
+| Level 5 | Knowledge Graph with nodes, edges, search, and focus detail | ![Knowledge Graph Layer](output/release/v4.7.0/screenshots/10-knowledge-graph-layer.png) |
 
 Walkthrough:
 
-![v4.6.1 Living Brain walkthrough](output/release/v4.6.1/gifs/v4.6.1-living-brain-walkthrough.gif)
+![v4.7.0 Living Brain walkthrough](output/release/v4.7.0/gifs/v4.7.0-living-brain-walkthrough.gif)
 
 Model setup status evidence:
 
-![Model setup status](output/release/v4.6.1/screenshots/11-model-setup-status.png)
+![Model setup status](output/release/v4.7.0/screenshots/11-model-setup-status.png)
+
+Separate admin console evidence:
+
+![Admin Console](output/release/v4.7.0/screenshots/12-admin-console.png)
 
 Screenshot index and capture notes:
-[output/release/v4.6.1/SCREENSHOT_INDEX.md](output/release/v4.6.1/SCREENSHOT_INDEX.md)
+[output/release/v4.7.0/SCREENSHOT_INDEX.md](output/release/v4.7.0/SCREENSHOT_INDEX.md)
 
 ## Architecture At A Glance
 
@@ -96,12 +105,21 @@ Screenshot index and capture notes:
 - **Storage**: `StorageEngine` abstraction with SQLite default and optional
   PostgreSQL/pgvector scale mode.
 - **Portability**: encrypted `.latticebrain` archives plus backup, restore,
-  inspect, verify, import dry-run, and confirmed restore/import flows.
+  inspect, verify, import dry-run, and confirmed restore/import flows. The
+  Brain home keeps conversation first and surfaces the everyday "Care for my
+  Brain" ownership path as a collapsed control with export, backup, archive,
+  inspect, and restore preview actions while keeping destructive confirmed
+  restore in Settings. Restore operations create pre-restore backups and roll
+  back failed DB/blob swaps so the current Brain is not left half-restored.
 - **Privacy**: local-first and private-first by default. Cloud models, Telegram,
   Brain Network, Docker/Postgres setup, model downloads, and update checks are
   opt-in paths.
+- **Admin separation**: user chat and Brain ownership stay in the main Brain
+  surface; user directory, audit logs, security events, policies, and index
+  rebuild controls live under the separate `#/admin` console. Admin history,
+  audit, stats, and sensitivity reads honor the active workspace when present.
 
-See [ARCHITECTURE.md](ARCHITECTURE.md) for the detailed v4.6.1 architecture.
+See [ARCHITECTURE.md](ARCHITECTURE.md) for the detailed v4.7.0 architecture.
 
 ## Installation
 
@@ -133,13 +151,13 @@ pip install "ltcai[local]"
 
 ## Release Artifacts
 
-Validated v4.6.1 artifacts:
+Validated v4.7.0 artifacts:
 
-- `dist/ltcai-4.6.1-py3-none-any.whl`
-- `dist/ltcai-4.6.1.tar.gz`
-- `ltcai-4.6.1.tgz`
-- `dist/ltcai-4.6.1.vsix`
-- `src-tauri/target/release/bundle/dmg/Lattice AI_4.6.1_aarch64.dmg`
+- `dist/ltcai-4.7.0-py3-none-any.whl`
+- `dist/ltcai-4.7.0.tar.gz`
+- `ltcai-4.7.0.tgz`
+- `dist/ltcai-4.7.0.vsix`
+- `src-tauri/target/release/bundle/dmg/Lattice AI_4.7.0_aarch64.dmg`
 
 Attach only those exact files to the GitHub Release. Do not upload `dist/*`.
 
@@ -168,7 +186,7 @@ npm run test:unit
 npm run test:integration
 npm run test:visual
 npm run desktop:tauri:check
-node scripts/run_python.mjs scripts/wheel_smoke.py --wheel dist/ltcai-4.6.1-py3-none-any.whl
+node scripts/run_python.mjs scripts/wheel_smoke.py --wheel dist/ltcai-4.7.0-py3-none-any.whl
 npm pack --dry-run
 npm run docs:check-links
 ```
@@ -184,13 +202,14 @@ npm run docs:check-links
 - Agent/workflow simulation without a loaded LLM is deterministic and does not call a model.
   It is labeled as LLM-free/model-free rather than presented as autonomous model
   success.
-- Historical artifacts can remain in `dist/`; uploads must use exact v4.6.1
+- Historical artifacts can remain in `dist/`; uploads must use exact v4.7.0
   filenames.
 
 ## Release History
 
 | Version | Theme |
 | --- | --- |
+| 4.7.0 | Admin Separation Release: keeps the user Brain simple, adds a separate Admin Console for users/logs/security/Brain operations, refreshes screenshots/GIFs, synchronizes release docs, and builds exact v4.7.0 artifacts |
 | 4.6.1 | Living Brain Release Refresh: publishable version bump after v4.6.0 PyPI immutability, refreshed README/screenshots/GIFs, synchronized release docs, and exact v4.6.1 artifacts |
 | 4.6.0 | Living Brain Experience: made Brain plus conversation the home product, added an animated living Brain presence, and moved graph exploration to the deepest intentional layer |
 | 4.5.1 | Product Reimagining RC: replaced the desktop shell, navigation model, onboarding journey, first-viewport hierarchy, and visual system while preserving capabilities and local-first architecture |
@@ -208,15 +227,19 @@ npm run docs:check-links
 
 ## Current Documentation
 
-- [ARCHITECTURE.md](ARCHITECTURE.md) - v4.6.1 architecture.
+- [ARCHITECTURE.md](ARCHITECTURE.md) - v4.7.0 architecture.
+- [docs/PRODUCT_DIRECTION_REVIEW.md](docs/PRODUCT_DIRECTION_REVIEW.md) -
+  Brain-first product direction review.
 - [FEATURE_STATUS.md](FEATURE_STATUS.md) - current feature status and historical
   status ledger.
 - [RELEASE_NOTES.md](RELEASE_NOTES.md) - release notes index.
-- [RELEASE_NOTES_v4.6.1.md](RELEASE_NOTES_v4.6.1.md) - v4.6.1 release refresh notes.
+- [RELEASE_NOTES_v4.7.0.md](RELEASE_NOTES_v4.7.0.md) - v4.7.0 admin separation release notes.
+- [RELEASE_NOTES_v4.6.1.md](RELEASE_NOTES_v4.6.1.md) - v4.6.1 release refresh history.
 - [RELEASE_NOTES_v4.6.0.md](RELEASE_NOTES_v4.6.0.md) - v4.6.0 Living Brain history.
 - [RELEASE.md](RELEASE.md) - release checklist and exact artifact guidance.
 - [SECURITY.md](SECURITY.md) - security posture.
 - [docs/CHANGELOG.md](docs/CHANGELOG.md) - changelog.
+- [docs/V4_7_0_ADMIN_SEPARATION_REPORT.md](docs/V4_7_0_ADMIN_SEPARATION_REPORT.md) - v4.7.0 admin separation report.
 - [docs/V4_6_1_RELEASE_REFRESH_REPORT.md](docs/V4_6_1_RELEASE_REFRESH_REPORT.md) - v4.6.1 release refresh report.
 - [docs/V4_6_0_LIVING_BRAIN_EXPERIENCE_REPORT.md](docs/V4_6_0_LIVING_BRAIN_EXPERIENCE_REPORT.md) - v4.6.0 Living Brain design notes.
 

package/docs/CHANGELOG.md

@@ -3,6 +3,51 @@
 The top entry is the current release-preparation target. Older entries are
 historical and may describe behavior as it existed at that release.
 
+## [4.7.0] - 2026-06-14
+
+> Admin Separation Release. v4.7.0 keeps the Living Brain as the simple user
+> surface and moves users, logs, security events, policies, and Brain operations
+> into a dedicated Admin Console with synchronized release metadata and
+> publishable artifacts.
+
+### Changed
+
+- Added a separate `#/admin` Admin Console so the normal `/app` user experience
+  remains Brain + conversation instead of becoming an admin dashboard.
+- Added admin overview metrics, user directory, audit log rows, security event
+  rows, policy chips, and Brain index rebuild controls to the admin-only
+  surface.
+- Scoped admin history, audit, stats, and sensitivity endpoints by
+  `X-Workspace-Id` / `workspace_id` when a workspace is selected, while keeping
+  legacy global records visible in Personal workspace compatibility mode.
+- Added frontend API helpers for `/admin/stats` and `/admin/security/events`,
+  reusing the existing FastAPI admin/security backend rather than inventing a
+  parallel logging store.
+- Updated visual validation so the Admin Console route is checked separately
+  from the user Brain surface.
+- Bumped synchronized package/runtime/static versions to `4.7.0`, including
+  Python metadata, npm package metadata, VSIX metadata, Tauri metadata,
+  `latticeai`, `lattice_brain`, runtime constants, and static asset metadata.
+- Refreshed release screenshots/GIF paths and docs for v4.7.0, including Admin
+  Console evidence.
+- Updated README, RELEASE.md, ARCHITECTURE.md, SECURITY.md, FEATURE_STATUS.md,
+  VS Code extension docs, release notes, and release report for the current
+  v4.7.0 release line.
+
+### Preserved
+
+- v4.6.1 and older sections remain historical.
+- Local-first ownership, `.latticebrain` portability, rollback-safe restore,
+  and the deepest-layer Knowledge Graph behavior are preserved.
+
+### 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`
+
 ## [4.6.1] - 2026-06-14
 
 > Living Brain release refresh and publishable version bump after the v4.6.0
@@ -12,6 +57,22 @@ historical and may describe behavior as it existed at that release.
 
 ### Changed
 
+- Added a Brain-first product direction review and synchronized philosophy /
+  Knowledge Graph docs so the graph is documented as infrastructure inside the
+  Brain rather than the product center.
+- Added a compact "Care for my Brain" ownership panel to the Brain home
+  experience, surfacing local-first/private/portable guarantees plus existing
+  export, backup, encrypted archive, inspect, and restore dry-run actions
+  without making the Knowledge Graph the product center.
+- Refined the Brain home so conversation remains the primary surface and the
+  "Care for my Brain" ownership controls open only when requested, with action
+  results now reflecting the last completed ownership action.
+- Strengthened first-run and empty-Brain product messaging around the core
+  promise that models are replaceable while the user's knowledge, decisions,
+  projects, and context are durable.
+- Hardened Knowledge Graph backup restore and encrypted `.latticebrain` restore
+  so DB/blob replacement is staged with pre-restore backups and rollback on
+  partial failure.
 - Bumped synchronized package/runtime/static versions to `4.6.1`, including
   Python metadata, npm package metadata, VSIX metadata, Tauri metadata,
   `latticeai`, `lattice_brain`, runtime constants, and static asset metadata.

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_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,22 +5,23 @@
 > completed analysis. **Update this file before ending any phase and before any
 > likely session/context/usage limit.**
 >
-> Last updated: 2026-06-14 — v4.6.1 Living Brain Release Refresh; Remaining Gaps remain empty
+> Last updated: 2026-06-14 — v4.7.0 Admin Separation Release; Remaining Gaps remain empty
 
 ---
 
-## 0. RELEASE STATUS (v4.6.1)
-
-**v4.6.1 is the publishable Living Brain release refresh after the v4.6.0 PyPI
-immutability block. It keeps the v4.6.0 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, and graph exploration is preserved as the
-deepest intentional layer behind Memories, Knowledge, and Relationships.
-The v4.6.1 process builds locally validated artifacts, tag, and GitHub Release
-assets. 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
@@ -28,12 +29,12 @@ not permitted).
 
 ## Remaining Gaps
 
-None. v4.6.1 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, 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.1 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)