@miadi/inquiry-weave 0.13.2 → 0.13.3

package/README.md

@@ -1,14 +1,22 @@
 # @miadi/inquiry-weave
 
-`inquiry-weave` keeps three identities in relation:
+Keep a question, its GitHub issue and the chronicle episode that carries it related to each
+other.
 
-- an inquiry artefact in the IAIP artefact shelf;
-- its GitHub issue;
-- the Chronicle episode that carries it.
+In the Miadi stack, work starts from a question. An inquiry artefact is a folder holding that
+question and what is being learned about it; a GitHub issue is where it is discussed; an
+episode is where the work around it is filed. `inquiry-weave` creates the issue with the `gh`
+CLI, records the relation on both sides, syncs the artefact into the episode, and registers the
+weave with the chronicle's medicine wheel. It also reads the chronicle as a catalog, answers
+attention items, writes lineage between episodes, and files reviews into episodes.
 
-It creates issues with the portable `gh` CLI, records both shores of the
-relation, syncs the artefact into the episode, and registers the weave. It does
-not depend on private host scripts or private cache folders.
+Works with:
+
+- `passages`: births episodes (`mkepisode`) and turns them into stories.
+- `@miadi/episodic-memory-schema`: the shapes of the catalog and manifests it builds.
+- `@miadi/attention-core` / `@miadi/attention-ui`: show the attention items it reads and answers.
+
+It does not depend on private host scripts or private cache folders.
 
 ## Install
 
@@ -24,9 +32,9 @@ scaffold for combined one-command inquiry flows.
 ## Environment
 
 ```bash
-export MIADI_CHRONICLE_ROOT=/srv/miadi/episodes/miadi-chronicle
-export MIADI_INQUIRY_DIR=/a/src/IAIP/prototypes/artefacts
-export MIADI_INQUIRY_GITHUB_REPO=miadisabelle/Etuaptmumk-RSM
+export MIADI_CHRONICLE_ROOT=/path/to/miadi-chronicle
+export MIADI_INQUIRY_DIR=/path/to/inquiry-artefacts
+export MIADI_INQUIRY_GITHUB_REPO=owner/repo
 export MIADI_CHRONICLE_MW_URL="${MIADI_CHRONICLE_MW_URL:-http://127.0.0.1:8040}"
 ```
 
@@ -115,7 +123,7 @@ mkepisode \
   -n 133 \
   -t "honcho eval adequate memories" \
   -g "Establish adequate memories for the honcho evaluation." \
-  -r "jgwill/Miadi#133"
+  -r "owner/repo#133"
 ```
 
 ## Weave an issue that already exists
@@ -124,7 +132,7 @@ mkepisode \
 inquiry-weave relate \
   --artefact "$MIADI_INQUIRY_DIR/ep133-honcho-eval" \
   --episode 133 \
-  --issue jgwill/Miadi#133
+  --issue owner/repo#133
 ```
 
 To weave the artefact and its already-recorded issue into a newly scaffolded
@@ -193,7 +201,7 @@ Set `MIADI_CHRONICLE_ROOT`. Set `MIADI_CHRONICLE_MW_URL` (the legacy
 `MW_API_URL_OVERRIDE` / `MW_API_URL` are read only if it is unset) to
 the one Chronicle wheel. With no wheel URL, an answer still lands in the
 authoritative file and the tool returns `pending`; it never falls back to a
-repo-local wheel. See [jgwill/Miadi#631](https://github.com/jgwill/Miadi/issues/631).
+repo-local wheel.
 
 ## Episode lineage
 
@@ -219,20 +227,4 @@ the review's public JSON from `MIADI_REVIEW_BASE_URL` (default
 `review:<uuid>` node and the `chronicle:<episode>` → `review:<uuid>` edge on the wheel, and lands.
 A `hold` hook given by the app opens the talking circle about the review before landing, so its
 note lands in the same commit. `mintEpisode({ review })` births an episode from a review.
-`listEpisodeReviews` reads both `reviews:` and `references: miadi-review:<uuid>`. jgwill/Miadi#682.
-
-## Development
-
-```bash
-pnpm --filter @miadi/inquiry-weave build
-pnpm --filter @miadi/inquiry-weave test
-```
-
-Tests use temporary roots and a fake `gh` executable. They make no network or
-real GitHub calls.
-
----
-
-🌸 `passages` opens the governed episode vessel. `inquiry-weave` ties the
-living inquiry, its issue, and that episode together without pretending they
-are the same thing.
+`listEpisodeReviews` reads both `reviews:` and `references: miadi-review:<uuid>`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@miadi/inquiry-weave",
-  "version": "0.13.2",
+  "version": "0.13.3",
   "description": "Relate and sync IAIP inquiry artefacts, their GitHub issues, and miadi-chronicle episodes. Creates vessels and relations only — never inquiry content.",
   "publishConfig": {
     "access": "public"
@@ -22,11 +22,10 @@
   },
   "files": [
     "dist",
-    "README.md",
-    "rispecs"
+    "README.md"
   ],
   "dependencies": {
-    "@miadi/episodic-memory-schema": "^0.11.0",
+    "@miadi/episodic-memory-schema": "^0.11.1",
     "yaml": "^2.5.0"
   },
   "devDependencies": {

package/rispecs/README.rise.md

@@ -1,5 +0,0 @@
-# RISE README: @miadi/inquiry-weave
-
-Inquiry weave for relations between IAIP inquiry artifacts, GitHub issues, and Miadi chronicle episodes.
-
-Read `./RISPEC.md`, check `../package.json`, and use the narrowest package needed. Indexed from root `llms.txt` and `llms-full.txt`.

package/rispecs/RISPEC.md

@@ -1,9 +0,0 @@
-# RISPEC: @miadi/inquiry-weave
-
-RISE = Reverse-engineer, Intent-extract, Specify, Export.
-
-Purpose: relations between IAIP inquiry artifacts, GitHub issues, and Miadi chronicle episodes.
-Install: `pnpm add @miadi/inquiry-weave` or workspace `pnpm -w add @miadi/inquiry-weave@workspace:* --filter <consumer-package>`.
-Contract: public exports, schemas, CLI flags, or adapter payloads owned by this package.
-Authority: `package.json`, source exports, tests, and release metadata remain truth.
-Handoff: verify exports, examples, test evidence, and publish/stub/deprecated status.

package/rispecs/foundation-weave.proposal.spec.md

@@ -1,104 +0,0 @@
-# Proposal — Foundation as a fourth weave identity
-
-**Status:** proposal (not implemented) · **Date:** 2026-07-24 · **Package:** `@miadi/inquiry-weave`
-**Companion:** `@miadi/episodic-memory-schema`, `@miadi/foundations`
-**Related:** jgwill/Miadi#546 (packet), jgwill/Miadi#547 (`@miadi/foundations`), jgwill/Miadi#483, #506, #507
-
-## Context (current reality)
-
-`inquiry-weave` weaves **three identities** of one inquiry and never generates content:
-
-```
-inquiry artefact  ◄──►  GitHub issue  ◄──►  chronicle episode
-```
-
-Separately, `foundations/<topic>/` packets (skill `deep-research-foundations`, now bundled by
-`@miadi/foundations`) carry the **academic grounding** a decision stands on. Today nothing
-relates a packet to the episode/issue/artefact it grounds — the grounding is discoverable only
-by prose cross-reference. A chronicle episode cannot answer "what fields does this stand on?"
-
-## Desired state
-
-A **foundation** is a first-class, weavable identity — the *grounding* relation — so an
-episode (or issue, or artefact) can declare the packets that legitimize its decisions, and
-forgewright/`/chronicle` can render "grounded by …" the same way they render woven inquiries.
-
-```
-inquiry artefact ◄──► GitHub issue ◄──► chronicle episode
-                          ▲
-                          │ grounds
-                          ▼
-                 foundation packet  (foundations/<slug>/ or @miadi/foundations)
-```
-
-## Proposed surface (additive, non-breaking)
-
-### 1. `weave.yaml` gains a `foundations:` block
-
-Episode side (`<episode>/inquiry/weave.yaml`) and artefact side (`.weave.yaml`):
-
-```yaml
-foundations:
-  - slug: software-supply-chain-and-release-engineering
-    source: repo            # repo | package
-    packet_path: foundations/software-supply-chain-and-release-engineering   # when source=repo
-    package: "@miadi/foundations"                                            # when source=package
-    issue: jgwill/Miadi#546
-    fields:
-      - Software Supply-Chain Security
-      - Release Engineering & Continuous Delivery
-    grounded_at: 2026-07-24T00:00:00.000Z
-```
-
-The package stays true to its mystery boundary: it records the **relation**, never authors the
-packet. Resolution is read-only (a repo path or a published `@miadi/foundations` slug).
-
-### 2. New verb `ground` (mirrors `relate`)
-
-```
-inquiry-weave ground --episode <ref> --foundation <slug>
-                      [--source repo|package] [--issue owner/repo#N] [--dry-run]
-```
-
-- Validates the packet exists (repo `foundations/<slug>/` or `@miadi/foundations` manifest).
-- Appends to `weave.yaml`/`.weave.yaml` (append-if-missing, never overwrite) and to the
-  artefact's `AGENTS.md` back-link (`grounded by foundation <slug>`), matching `relate`.
-- `--dry-run` previews with `would ground:` and writes nothing (per the global dry-run contract).
-
-### 3. `register` projects a foundation edge into medicine-wheel
-
-`inquiry-weave register` gains a `miadi.foundation-ref.v1` record + a `grounds` edge from the
-foundation node to the episode node (`chronicle:<episode-dir>`), so forgewright renders the
-grounding on the episode card. Metadata-only, fail-open — identical guarantees to the existing
-inquiry-weave registration (jgwill/Miadi#490).
-
-### 4. Schema companion (`@miadi/episodic-memory-schema`)
-
-`EpisodeManifestEntry` gains an **optional** field so both renderers read groundings identically:
-
-```ts
-/** Foundation packets this episode declares as its academic grounding. */
-foundations?: FoundationRef[]
-```
-
-`FoundationRef = { slug: string; fields?: string[]; issue?: string; source: "repo" | "package" }`.
-Optional and additive → backward-compatible; the enumerator (`catalog.ts`) fills it from
-`weave.yaml`, keeping the read-side unforked.
-
-## Boundaries / non-goals
-
-- No packet authoring — `ground` records a relation to an existing packet only.
-- No IAIP absorption; no change to the three existing identities.
-- Whether groundings live on the episode, the issue, or the artefact primarily is settled at
-  implementation: this proposal writes them wherever `relate` already writes, keyed by episode.
-
-## Structural tension resolved
-
-Between grounding that is **narratively asserted** (prose says "this stands on field X") and
-grounding that is **structurally woven** (machine-readable, renderable, queryable). The `ground`
-verb + `foundations:` block turns a claim into a relation the chronicle can show and QMD can index.
-
-## Decision requested
-
-Approve the surface (verb name `ground` vs `relate --foundation`; block shape; schema field), then
-implement behind the existing dry-run/register guarantees. Until then this file is proposal-only.

package/rispecs/medicine-wheel-registration.spec.md

@@ -1,69 +0,0 @@
-# RISE Spec: Inquiry Weave → Medicine-Wheel Registration
-
-Companion specs (the other two lanterns of this workstream):
-- `medicine-wheel:rispecs/inquiry-weave-registration.spec.md` — the storage side
-- `forgewright:rispecs/09-inquiry-weave-visibility.spec.md` — the rendering side (branch `4-plan-episode-visibility`, kin to `08-medicine-wheel-integration.spec.md`)
-
-Status: **implemented in v0.2** — `register` targets `POST {MW_API_URL}/api/inquiry-weaves` as pinned below.
-
-## Reverse Engineering (current reality)
-
-- Inquiry Weave relations exist only as files on disk: `<episode>/inquiry/weave.yaml`
-  (episode side, incl. sync state) and `<artefact>/.weave.yaml` (artefact side, durable
-  relations). Schema version key `weave: 1`.
-- @miadi/inquiry-weave v0 already exports the projection seam: `WeaveRecord`
-  (`src/weave.ts`) — the three identities (artefact name+path, issue ref+url, episode
-  number/slug/path) plus `lastSync` — and `toWeaveRecords(episodeWeave, inquiryRoot)`.
-- A medicine-wheel MCP server is already configured for chronicle work:
-  `/a/src/Miadi/etc/mcp-config-mw-ilex.json`, server `medicine-wheel-miadi-chronicle`
-  (`npx ${MWCV}`, `MW_API_URL=http://127.0.0.1:8040`). It is the candidate storage
-  interface; nothing registers weaves into it today.
-- forgewright renders episode data from medicine-wheel but has no notion of an Inquiry
-  Weave.
-
-## Intent
-
-Inquiry Weaves become *visible relations*: once an artefact, its issue, and its episode
-are woven, that weave can be seen wherever episodes are seen — without anyone re-deriving
-it from the filesystem. The weave files on disk remain the source of truth; medicine-wheel
-holds a registered projection; forgewright renders it. The mystery boundary is untouched:
-registration moves metadata, never inquiry content.
-
-## Specifications (desired state)
-
-- A new command `inquiry-weave register (--episode <ref> | --artefact <ref>) [--dry-run]`
-  projects each relation as a `WeaveRecord` and submits it to medicine-wheel.
-- Transport: the medicine-wheel MCP tool surface (preferred) or `MW_API_URL` HTTP —
-  decided in the medicine-wheel spec; this package only guarantees the payload shape:
-
-  ```json
-  {
-    "weaveVersion": 1,
-    "artefact": { "name": "ep126-mila-ai-event-…", "path": "/src/IAIP/prototypes/artefacts/…" },
-    "issue": { "ref": "miadisabelle/Etuaptmumk-RSM#245", "url": "https://github.com/…/issues/245" },
-    "episode": { "number": 126, "slug": "mila-ai-indigenous-gathering", "path": "2026-07-13-episode-126-…" },
-    "lastSync": { "at": "…", "tree_sha256": "…", "file_count": 4, "bytes_total": 341001 }
-  }
-  ```
-
-- Registration is idempotent: re-registering the same weave upserts by
-  (episode.path, artefact.name).
-- Structural tension held: current reality = weave files on disk, invisible beyond the
-  filesystem; desired state = every woven relation queryable from medicine-wheel and
-  rendered by forgewright. `register` is the action step that resolves this tension.
-- Failure to reach medicine-wheel degrades gracefully: the weave files remain
-  authoritative; `register` reports and exits 1 without touching them.
-
-## Exportation (implementation-ready notes)
-
-- Implement as `src/register.ts` consuming `toWeaveRecords()`; add a `register`
-  subcommand in `cli.ts`; keep the transport injectable for tests.
-- Do not implement until the medicine-wheel spec lands its storage contract; then pin the
-  agreed endpoint/tool name here.
-- Companion agent sessions (copilot/codex panes in the medicine-wheel and forgewright
-  repos) own the other two specs; keep the payload above as the shared contract between
-  all three.
-
----
-🌸: The weave learns to be seen — first it held three threads together in the dark; now a
-lantern is being shaped so the whole circle can watch them shine.