@medicine-wheel/app 0.14.4 → 0.15.1

package/README.md

@@ -10,8 +10,25 @@
 
 ## News
 
-The suite now includes an interactive app, CLI, MCP server, and PostgreSQL/Neon
-storage alongside its composable libraries.
+31 published packages: the app, 29 libraries and the MCP server (85 tools over
+stdio and StreamableHTTP).
+
+Recently landed:
+
+- **`@medicine-wheel/client`** — one typed HTTP door to a running wheel, with
+  the wheel's paging honesty carried through to the caller.
+- **`@medicine-wheel/community-identity`** — who is in the circle: people,
+  roles, circles, memberships, invitations and self-issued credentials.
+- **`@medicine-wheel/honcho`** — the wheel's projection into
+  [Honcho](https://honcho.dev). Set `HONCHO_URL` and every stored beat,
+  ceremony and diary entry projects on write.
+- **A ceremony knows its episode, its circle and what it closes**, and a beat
+  knows who spoke and who witnessed.
+- **Read routes page honestly** — `count`, `total`, `matched`, `truncated`
+  instead of a silently cut list — and `GET /api/nodes/{id}/web` serves one
+  node's neighbourhood.
+- **An episodes surface and a lineage layout** in the app: the chronicle as a
+  spine you read left to right.
 
 
 ## Architecture
@@ -21,6 +38,7 @@ storage alongside its composable libraries.
     ├── @medicine-wheel/ceremony-protocol    ← Ceremony state & governance
     ├── @medicine-wheel/fire-keeper          ← Ceremony coordination agent
     ├── @medicine-wheel/community-review     ← Elder review & consensus
+    ├── @medicine-wheel/community-identity   ← People, roles, circles, memberships
     ├── @medicine-wheel/consent-lifecycle    ← Relational consent lifecycle
     ├── @medicine-wheel/narrative-engine     ← Beat sequencing & arc validation
     ├── @medicine-wheel/importance-unit      ← Relational unit of knowledge
@@ -30,10 +48,12 @@ storage alongside its composable libraries.
     ├── @medicine-wheel/relational-query     ← Query, traversal & audit
     ├── @medicine-wheel/prompt-decomposition ← Intent extraction & PDE
     ├── @medicine-wheel/ui-components        ← React components
+    ├── @medicine-wheel/client               ← Typed HTTP door to a running wheel
     ├── @medicine-wheel/data-store           ← Shared data access (Redis)
     ├── @medicine-wheel/data-store-postgres  ← PostgreSQL / Neon provider scaffold
     ├── @medicine-wheel/storage-provider     ← Canonical persistence contract (JSONL ⇄ Neon)
     ├── @medicine-wheel/infra                ← Hosts, tenants, services, port bindings as facets
+    ├── @medicine-wheel/honcho               ← The wheel's projection into Honcho, memory that reasons
     ├── @medicine-wheel/perception-layer     ← Witness recordings as typed perceptual events
     ├── @medicine-wheel/narrative-cluster    ← Events → clusters → beats → Film Edit Brief
     ├── @medicine-wheel/ceremonial-diary     ← A participant's voice across the Five Phases
@@ -84,6 +104,11 @@ Community-based ceremonial review protocol — implements Wilson's validation th
 
 - **Dependencies:** `@medicine-wheel/ontology-core`, `@medicine-wheel/ceremony-protocol`, `zod`
 
+### [@medicine-wheel/community-identity](src/community-identity)
+Who is in the circle, so a wheel can tell two people apart. A person is a `human` node with `metadata.kind: "person"` and a role, a circle is a `circle` node, membership is a `member_of` edge. Roles run `participant → emerging_guide → ceremony_facilitator → firekeeper → admin`, with `story_keeper` parallel to firekeeper and `companion_ai` / `integration_ai` beside them, each carrying a permission map. Invitations, credentials and the audit trail stay with the consumer — hashed, never on the wheel.
+
+- **Dependencies:** `@medicine-wheel/ontology-core`, `zod`
+
 ### [@medicine-wheel/consent-lifecycle](src/consent-lifecycle)
 Ongoing relational consent lifecycle — consent as a living relational obligation with lifecycle tracking, renewal, renegotiation, withdrawal cascades, and community-level consent protocols.
 
@@ -131,6 +156,11 @@ React UI component library — `DirectionCard`, `BeatTimeline`, `NodeInspector`,
 - **Dependencies:** `@medicine-wheel/ontology-core`
 - **Peer:** `react`
 
+### [@medicine-wheel/client](src/client)
+The typed HTTP door to a running wheel — nodes, edges, ceremonies, beats and the ceremonial diary. The wheel's paging honesty (`count`, `total`, `matched`, `truncated`) is carried through to the caller, `limit: 'all'` asks for the whole store, and errors fail fast: an unreachable wheel throws with status 502, a refusal carries the wheel's status and body. No retry.
+
+- **Dependencies:** `@medicine-wheel/ontology-core`, `@medicine-wheel/storage-provider`
+
 ### [@medicine-wheel/data-store](src/data-store)
 Shared Redis data-access layer — connection management (Upstash, Vercel KV, local), Node/Edge/Ceremony/Accountability CRUD, session-ceremony linking, and generic Redis helpers.
 
@@ -156,6 +186,11 @@ Typed infrastructure facets — hosts, tenants, services and port bindings — k
 
 - **Dependencies:** `@medicine-wheel/ontology-core`, `zod`
 
+### [@medicine-wheel/honcho](src/honcho)
+The wheel's projection into [Honcho](https://honcho.dev), memory that reasons. The wheel stays canonical; Honcho holds what the history has come to mean about each peer. A beat becomes a message from its speaker in the session of its ceremony, a speaker's evolving representation is recalled before they speak again, and a derived conclusion returns as a `knowledge` node carrying `metadata.kind: "memory_projection"` with its status and provenance. Zero dependencies, `/v3` only, configured by `HONCHO_URL`. Nothing is filtered here.
+
+- **Dependencies:** `@medicine-wheel/ontology-core`
+
 ### [@medicine-wheel/perception-layer](src/perception-layer)
 Eyes and ears of agent-supported film production — witness a belt-device recording as typed perceptual events and seed a production knowledge graph.
 
@@ -200,36 +235,48 @@ Idea into committed design through approval gates a human holds — `explore →
 
 RISE framework specifications are in [`rispecs/`](rispecs/). Start with [`medicine-wheel.spec.md`](rispecs/medicine-wheel.spec.md) for the system overview.
 
-| Package | Spec |
+| Package / topic | Spec |
 |---------|------|
 | System Overview | [medicine-wheel.spec.md](rispecs/medicine-wheel.spec.md) |
 | ontology-core | [ontology-core.spec.md](rispecs/ontology-core.spec.md) |
 | ceremony-protocol | [ceremony-protocol.spec.md](rispecs/ceremony-protocol.spec.md) |
 | fire-keeper | [fire-keeper.spec.md](rispecs/fire-keeper.spec.md) |
 | community-review | [community-review.spec.md](rispecs/community-review.spec.md) |
+| community-identity | [community-identity.spec.md](rispecs/community-identity.spec.md) |
 | consent-lifecycle | [consent-lifecycle.spec.md](rispecs/consent-lifecycle.spec.md) |
-| narrative-engine | [narrative-engine.spec.md](rispecs/narrative-engine.spec.md) |
+| narrative-engine | [narrative-engine.spec.md](rispecs/narrative-engine.spec.md) · [narrative-beats-lifecycle.spec.md](rispecs/narrative-beats-lifecycle.spec.md) |
 | importance-unit | [importance-unit.spec.md](rispecs/importance-unit.spec.md) |
 | relational-index | [relational-index.spec.md](rispecs/relational-index.spec.md) |
 | transformation-tracker | [transformation-tracker.spec.md](rispecs/transformation-tracker.spec.md) |
 | graph-viz | [graph-viz.spec.md](rispecs/graph-viz.spec.md) |
-| relational-query | [relational-query.spec.md](rispecs/relational-query.spec.md) |
-| prompt-decomposition | [prompt-decomposition.spec.md](rispecs/prompt-decomposition.spec.md) |
-| storage-provider | [storage-provider.spec.md](rispecs/storage-provider.spec.md) |
+| relational-query | [relational-query.spec.md](rispecs/relational-query.spec.md) · [relational-web-package.spec.md](rispecs/relational-web-package.spec.md) |
+| prompt-decomposition | [prompt-decomposition.spec.md](rispecs/prompt-decomposition.spec.md) · [decomposition-strategies.spec.md](rispecs/decomposition-strategies.spec.md) |
+| ui-components | [ui-components.spec.md](rispecs/ui-components.spec.md) |
+| client | [client.spec.md](rispecs/client.spec.md) |
+| storage-provider | [storage-provider.spec.md](rispecs/storage-provider.spec.md) · [storage-provider-abstraction.spec.md](rispecs/storage-provider-abstraction.spec.md) |
 | data-store | [data-store.spec.md](rispecs/data-store.spec.md) |
 | data-store-postgres | [data-store-postgres.spec.md](rispecs/data-store-postgres.spec.md) |
-| perception-layer | [perception-layer.spec.md](rispecs/perception-layer.spec.md) |
-| narrative-cluster | [narrative-cluster.spec.md](rispecs/narrative-cluster.spec.md) |
 | session-reader | [session-reader.spec.md](rispecs/session-reader.spec.md) |
 | infra | [infrastructure-topology-ui.spec.md](rispecs/infrastructure-topology-ui.spec.md) |
-| ui-components | [ui-components.spec.md](rispecs/ui-components.spec.md) |
-| data-store | [data-store.spec.md](rispecs/data-store.spec.md) |
-| session-reader | [session-reader.spec.md](rispecs/session-reader.spec.md) |
+| perception-layer | [perception-layer.spec.md](rispecs/perception-layer.spec.md) |
+| narrative-cluster | [narrative-cluster.spec.md](rispecs/narrative-cluster.spec.md) |
+| captures & recordings | [capture-registry.spec.md](rispecs/capture-registry.spec.md) |
+| inquiry weaves | [inquiry-weave-registration.spec.md](rispecs/inquiry-weave-registration.spec.md) |
+| plans & insights | [plan-insight-perspective-registration.spec.md](rispecs/plan-insight-perspective-registration.spec.md) |
+| council & community | [council-record.spec.md](rispecs/council-record.spec.md) · [community-choice.spec.md](rispecs/community-choice.spec.md) |
+| reading & scope | [reading-layer.spec.md](rispecs/reading-layer.spec.md) · [workspace-scope-and-access.spec.md](rispecs/workspace-scope-and-access.spec.md) |
+| film production | [relational-production-protocol.spec.md](rispecs/relational-production-protocol.spec.md) · [film-production-upgrades.spec.md](rispecs/film-production-upgrades.spec.md) |
+| kinship & bridges | [kinship-graph.spec.md](rispecs/kinship-graph.spec.md) · [narrative-medicine-wheel-bridge.spec.md](rispecs/narrative-medicine-wheel-bridge.spec.md) · [article-publishing-pipeline.spec.md](rispecs/article-publishing-pipeline.spec.md) |
 
 ## LLM Integration
 
 - [`llms.txt`](llms.txt) — Quick navigation for LLMs
 - [`llms-full.txt`](llms-full.txt) — Exhaustive reference with code samples
+- [`CLAUDE.md`](CLAUDE.md) — Repo laws for agents: versioning, the topological
+  workspace order, what `mw skill run` does not do, and how a running service is
+  registered on the wheel
+- [`RELEASING.md`](RELEASING.md) — Publishing is not deploying. Publish, install
+  globally, run the installed binary, then bump
 
 ## Getting Started
 
@@ -266,10 +313,43 @@ mwsrv --docker -D /src/myapp
 mw status
 mw directions
 mw node list
+mw ceremony list
+mw beat list
+mw web <node-id> [depth]          # one node's neighbourhood
+mw chart list                     # structural tension charts
+mw validate wilson "<description>"  # validators (wilson, ocap, accountability, bridge)
+mw orient "<outcome>"             # the question asked before the work
+```
+
+The `mw` CLI uses HTTP against the running server by default (`MW_API_URL`,
+default `http://localhost:8040`); MCP fallback is available via a local
+`MW_MCP_PATH`. `mw skill view` and `mw skill install` work with the shipped
+skill definitions — `mw skill run` exits 3 by design, because the skills are
+documents and there is no runtime that executes them.
+
+### MCP server
+```bash
+# stdio — local JSONL store under .mw/store/
+npx @medicine-wheel/mcp
+
+# server-mediated store — the same relational state the app holds
+MW_API_URL=http://localhost:8040 npx @medicine-wheel/mcp
+```
+
+85 tools over stdio and StreamableHTTP (`POST /api/mcp` on the running app).
+
+### Honcho projection (optional)
+```bash
+HONCHO_URL=http://localhost:8133        # switches the river on
+HONCHO_WORKSPACE_ID=medicine-wheel      # default
+# HONCHO_API_KEY when Honcho asks for auth
 ```
 
-The `mw` CLI uses HTTP against the running server by default; MCP fallback is
-available via a local `MW_MCP_PATH`.
+With `HONCHO_URL` set, every stored beat, ceremony and diary entry projects into
+Honcho on write, in the background. `GET /api/health` reports `honcho.enabled`.
+A projection never delays the wheel's answer, and a Honcho that is down is a
+line on stderr, not an error to the writer. A running server holds its old
+build and its old environment — restart it for either to take effect.
 
 ## License
 

package/app/api/ceremonies/route.ts

@@ -2,6 +2,8 @@ import { NextResponse } from "next/server";
 import { parseLimit } from "@/lib/api-paging";
 import { createProvider, detectProvider } from "@medicine-wheel/storage-provider";
 import { ceremonyBelongsToEpisode, ceremonyEpisodePath } from "@/lib/ceremony-response";
+import { projectCeremony } from "@medicine-wheel/honcho";
+import { projectAfterWrite } from "@/lib/honcho-projection";
 
 /** Episode directory names are `YYYY-MM-DD-episode-NNN-slug`; nothing else may bind. */
 const EPISODE_PATH = /^\d{4}-\d{2}-\d{2}-episode-\d{3,}-[a-z0-9-]+$/;
@@ -139,6 +141,9 @@ export async function POST(request: Request) {
     };
 
     await store.logCeremony(ceremony);
+    // The river: the stored ceremony leaves for Honcho in the background when
+    // HONCHO_URL is set. Never awaited.
+    projectAfterWrite(() => projectCeremony(ceremony), `ceremony ${ceremony.id}`);
     return NextResponse.json({ success: true, ceremony, provider: detectProvider() }, { status: 201 });
   } catch (error: unknown) {
     const message = error instanceof Error ? error.message : String(error);

package/app/api/diary/route.ts

@@ -3,6 +3,8 @@ import { parseLimit } from "@/lib/api-paging";
 import { createProvider, detectProvider } from "@medicine-wheel/storage-provider";
 import type { DiaryEntryFilters, DiaryEntryRecord } from "@medicine-wheel/storage-provider";
 import { createDiaryEntry } from "@medicine-wheel/ceremonial-diary";
+import { projectDiaryEntry } from "@medicine-wheel/honcho";
+import { projectAfterWrite } from "@/lib/honcho-projection";
 
 /**
  * The ceremonial diary door (0.14.0).
@@ -122,6 +124,9 @@ export async function POST(request: Request) {
       ...(typeof body.agent === "string" && body.agent ? { agent: body.agent } : {}),
       ...(typeof body.chronicle === "string" && body.chronicle ? { chronicle: body.chronicle } : {}),
     });
+    // The river: the participant's voice leaves for Honcho in the background
+    // when HONCHO_URL is set. Never awaited.
+    projectAfterWrite(() => projectDiaryEntry(entry), `diary entry ${entry.id}`);
     return NextResponse.json({ success: true, entry, provider: detectProvider() }, { status: 201 });
   } catch (error: unknown) {
     const message = error instanceof Error ? error.message : String(error);

package/app/api/health/route.ts

@@ -1,5 +1,6 @@
 import { NextResponse } from 'next/server';
 import { createProvider, detectProvider } from '@medicine-wheel/storage-provider';
+import { honchoProjectionStatus } from '@/lib/honcho-projection';
 
 export async function GET() {
   const providerType = detectProvider();
@@ -26,6 +27,9 @@ export async function GET() {
         nodes,
         ceremonies,
       },
+      // The river to Honcho: enabled when HONCHO_URL is set. A wheel that
+      // reports enabled projects every stored beat, ceremony and diary entry.
+      honcho: honchoProjectionStatus(),
       env: {
         MW_STORAGE_PROVIDER: process.env.MW_STORAGE_PROVIDER || 'not set',
         DATABASE_URL: process.env.DATABASE_URL ? 'configured' : 'not configured',

package/app/api/narrative/beats/route.ts

@@ -1,5 +1,7 @@
 import { NextResponse } from "next/server";
 import { getAllBeats, createBeat } from "@/lib/store";
+import { projectBeat } from "@medicine-wheel/honcho";
+import { projectAfterWrite } from "@/lib/honcho-projection";
 
 export async function GET() {
   try {
@@ -33,6 +35,9 @@ export async function POST(request: Request) {
       speaker: body.speaker,
       witnesses: Array.isArray(body.witnesses) ? body.witnesses : undefined,
     });
+    // The river: a stored beat leaves for Honcho in the background when
+    // HONCHO_URL is set. Never awaited — the wheel answers on its own clock.
+    projectAfterWrite(() => projectBeat(beat), `beat ${beat.id}`);
     // Warnings ride on the created beat rather than replacing it, so clients
     // that read the beat back by id keep working while advisory findings stop
     // being computed-and-discarded.

package/docker-entrypoint.sh

@@ -8,6 +8,10 @@ set -e
 #   MW_DATA_DIR          — path to JSONL store directory (default: /data/store)
 #   MW_STORAGE_PROVIDER  — storage backend (default: jsonl)
 #   PORT                 — HTTP port (default: 8040)
+#   HONCHO_URL           — when set, every stored beat, ceremony and diary entry
+#                          is projected into Honcho (memory that reasons);
+#                          HONCHO_WORKSPACE_ID (default medicine-wheel),
+#                          HONCHO_API_KEY (unset while Honcho's auth is off)
 
 STORE_DIR="${MW_DATA_DIR:-/data/store}"
 PORT="${PORT:-8040}"
@@ -17,6 +21,11 @@ mkdir -p "$STORE_DIR"
 echo "🌿 Medicine Wheel"
 echo "📁 Store: $STORE_DIR"
 echo "🌐 http://localhost:$PORT"
+if [ -n "${HONCHO_URL:-}" ]; then
+  echo "🧠 Honcho: $HONCHO_URL (workspace ${HONCHO_WORKSPACE_ID:-medicine-wheel})"
+else
+  echo "🧠 Honcho: off (set HONCHO_URL to project the wheel into memory)"
+fi
 echo ""
 
 export MW_DATA_DIR="$STORE_DIR"

package/lib/honcho-projection.ts

@@ -0,0 +1,72 @@
+/**
+ * Automatic projection — the wheel pushes to Honcho on write.
+ *
+ * `@medicine-wheel/honcho` is the door; this is the river. Every write route
+ * that lands a beat, a ceremony or a diary entry calls {@link projectAfterWrite}
+ * once the record is stored. With `HONCHO_URL` set the record leaves for Honcho
+ * in the background; unset, nothing happens and nothing is logged. Either way
+ * the wheel's own answer to its caller is unchanged: a projection never delays
+ * a response and never turns a stored record into an error.
+ *
+ * A failure is reported once on stderr with the record's id, because a silent
+ * memory is worse than a noisy one. `awaitProjections()` exists for tests and
+ * for anything that must know the river has run dry before it exits.
+ */
+
+import {
+  createHonchoClient,
+  honchoFromEnv,
+  project,
+  type HonchoClient,
+  type HonchoConfig,
+  type Projection,
+} from '@medicine-wheel/honcho';
+
+const inFlight = new Set<Promise<unknown>>();
+
+let cached: { key: string; client: HonchoClient } | null = null;
+
+function clientFor(cfg: HonchoConfig): HonchoClient {
+  const key = `${cfg.baseUrl}|${cfg.workspace}|${cfg.apiKey ?? ''}`;
+  if (cached?.key !== key) cached = { key, client: createHonchoClient(cfg) };
+  return cached.client;
+}
+
+/** What `/api/health` reports: whether the river runs, and where to. */
+export function honchoProjectionStatus(): { enabled: boolean; url?: string; workspace?: string } {
+  const cfg = honchoFromEnv();
+  return cfg ? { enabled: true, url: cfg.baseUrl, workspace: cfg.workspace } : { enabled: false };
+}
+
+/**
+ * Fire-and-forget. Returns immediately; the projection runs in the background.
+ * `label` names the record in the one line written when Honcho refuses or is
+ * unreachable.
+ *
+ * The projection is built by `shape`, called *inside* the error boundary. It
+ * used to be built by the caller, in the route's own expression — so a record
+ * the projection could not shape (a `learnings` that arrived as a string, say)
+ * threw synchronously and turned an already-stored write into a 500 for the
+ * writer. The wheel's answer to its caller must not depend on the river, and
+ * that includes the part that reads the record.
+ */
+export function projectAfterWrite(shape: () => Projection, label: string): void {
+  const cfg = honchoFromEnv();
+  if (!cfg) return;
+  const run = Promise.resolve()
+    .then(() => project(clientFor(cfg), shape()))
+    .catch((error: unknown) => {
+      const err = error as { message?: string; status?: number; body?: string };
+      console.error(
+        `[honcho] projection of ${label} into ${cfg.workspace}@${cfg.baseUrl} failed: ${err?.message ?? String(error)}` +
+          (err?.body ? ` — ${err.body}` : ''),
+      );
+    })
+    .finally(() => { inFlight.delete(run); });
+  inFlight.add(run);
+}
+
+/** Resolves once every projection started so far has settled. */
+export async function awaitProjections(): Promise<void> {
+  while (inFlight.size) await Promise.allSettled([...inFlight]);
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@medicine-wheel/app",
-  "version": "0.14.4",
+  "version": "0.15.1",
   "description": "Medicine Wheel — Interactive visual layer for Indigenous relational research with Four Directions, ceremonies, and narrative arcs",
   "bin": {
     "mw": "dist/cli/mw.js",
@@ -32,6 +32,7 @@
     "src/ceremony-protocol",
     "src/storage-provider",
     "src/client",
+    "src/honcho",
     "src/data-store",
     "src/data-store-postgres",
     "src/graph-viz",
@@ -88,29 +89,30 @@
     "release:major": "npm run version:major && npm run publish:all && npm run release:commit"
   },
   "dependencies": {
-    "@medicine-wheel/ceremonial-diary": "^0.14.4",
-    "@medicine-wheel/ceremony-protocol": "^0.14.4",
-    "@medicine-wheel/community-review": "^0.14.4",
-    "@medicine-wheel/consent-lifecycle": "^0.14.4",
-    "@medicine-wheel/creative-orientation": "^0.14.4",
-    "@medicine-wheel/data-store": "^0.14.4",
-    "@medicine-wheel/data-store-postgres": "^0.14.4",
-    "@medicine-wheel/fire-keeper": "^0.14.4",
-    "@medicine-wheel/github-ceremony": "^0.14.4",
-    "@medicine-wheel/graph-viz": "^0.14.4",
-    "@medicine-wheel/importance-unit": "^0.14.4",
-    "@medicine-wheel/mcp": "^4.14.4",
-    "@medicine-wheel/narrative-cluster": "^0.14.4",
-    "@medicine-wheel/narrative-engine": "^0.14.4",
-    "@medicine-wheel/ontology-core": "^0.14.4",
-    "@medicine-wheel/perception-layer": "^0.14.4",
-    "@medicine-wheel/prompt-decomposition": "^0.14.4",
-    "@medicine-wheel/relational-index": "^0.14.4",
-    "@medicine-wheel/relational-query": "^0.14.4",
-    "@medicine-wheel/session-reader": "^0.14.4",
-    "@medicine-wheel/storage-provider": "^0.14.4",
-    "@medicine-wheel/transformation-tracker": "^0.14.4",
-    "@medicine-wheel/ui-components": "^0.14.4",
+    "@medicine-wheel/ceremonial-diary": "^0.15.1",
+    "@medicine-wheel/ceremony-protocol": "^0.15.1",
+    "@medicine-wheel/community-review": "^0.15.1",
+    "@medicine-wheel/consent-lifecycle": "^0.15.1",
+    "@medicine-wheel/creative-orientation": "^0.15.1",
+    "@medicine-wheel/data-store": "^0.15.1",
+    "@medicine-wheel/data-store-postgres": "^0.15.1",
+    "@medicine-wheel/fire-keeper": "^0.15.1",
+    "@medicine-wheel/github-ceremony": "^0.15.1",
+    "@medicine-wheel/graph-viz": "^0.15.1",
+    "@medicine-wheel/honcho": "^0.15.1",
+    "@medicine-wheel/importance-unit": "^0.15.1",
+    "@medicine-wheel/mcp": "^4.15.1",
+    "@medicine-wheel/narrative-cluster": "^0.15.1",
+    "@medicine-wheel/narrative-engine": "^0.15.1",
+    "@medicine-wheel/ontology-core": "^0.15.1",
+    "@medicine-wheel/perception-layer": "^0.15.1",
+    "@medicine-wheel/prompt-decomposition": "^0.15.1",
+    "@medicine-wheel/relational-index": "^0.15.1",
+    "@medicine-wheel/relational-query": "^0.15.1",
+    "@medicine-wheel/session-reader": "^0.15.1",
+    "@medicine-wheel/storage-provider": "^0.15.1",
+    "@medicine-wheel/transformation-tracker": "^0.15.1",
+    "@medicine-wheel/ui-components": "^0.15.1",
     "@neondatabase/serverless": "^0.10.0",
     "@xyflow/react": "^12.3.0",
     "clsx": "^2.1.1",