@medicine-wheel/creative-problem-solving 0.5.4

package/ALPHA.md

@@ -0,0 +1,59 @@
+# This suite is experimental alpha
+
+**Read this before depending on anything here.**
+
+The Medicine Wheel Developer Suite is under active development and is published
+in the open so the work can be examined, discussed, and improved. It is not
+finished software. Publishing early is deliberate — but so is telling you what
+you are installing.
+
+## What that means concretely
+
+- **APIs change between patch versions.** All packages move in lockstep, so a
+  bump you would normally read as "nothing changed for me" may still change
+  what you depend on. Pin exact versions.
+- **Packages appear, and their boundaries move.** Three packages were added in
+  `0.5.3`. Where a responsibility lives is still being decided.
+- **Some packages are intentionally small first cuts.** They express an
+  intention with a working minimum rather than a finished surface. Their
+  READMEs say so where it applies.
+- **Storage shapes are still settling.** Records written by one version may
+  need repair by a later one. Do not treat any store here as an archive of
+  record yet.
+- **Test coverage is real but uneven.** 210 tests pass at `0.5.3`; that is a
+  floor, not a claim of completeness.
+
+## What it does *not* mean
+
+It does not mean the work is careless. Defects found are fixed and written
+down, specifications are versioned alongside the code in `rispecs/`, and
+sessions are chronicled. The alpha label is about **stability of contract**,
+not about standard of care.
+
+## Cultural material
+
+Parts of this suite encode Indigenous relational research methodology —
+Four Directions structure, ceremony protocol, OCAP® compliance surfaces,
+relational accountability. That material is included because the software is
+*for* that way of working, not as decoration.
+
+If you are building on those parts, please read them as an invitation to work
+relationally rather than as a finished implementation of anyone's protocol.
+Where a design question is properly a knowledge holder's decision rather than
+an engineer's, the specs try to say so. Where we have got that wrong, telling
+us is a contribution.
+
+## If you are evaluating this
+
+The most useful things to read first:
+
+- `rispecs/` — the specifications, versioned with the code
+- `README.md` — what the suite is
+- Open issues — where the known edges are, stated plainly
+
+Feedback is genuinely wanted at this stage, including "this boundary is wrong"
+and "this should not be software".
+
+## License
+
+MIT — see `LICENSE`.

package/README.md

@@ -0,0 +1,59 @@
+# @medicine-wheel/creative-problem-solving
+
+You arrived here looking for creative problem solving. One question first:
+
+> **Is there a prior state you are restoring?**
+
+**Yes — you can name it and it genuinely existed.** This is a fire, and
+[`@medicine-wheel/gap-analysis`](https://www.npmjs.com/package/@medicine-wheel/gap-analysis)
+is the right instrument: baseline with evidence, observation, the difference
+between them, and elimination steps you can verify. That is correct work for
+this situation. It carries no apology and needs no other name.
+
+**No — nothing existed that you are returning to.** You are creating, and
+structural tension is the instrument. Difference-closing language will mislead
+you here, because there is no baseline to return toward: an outcome phrased as
+removal optimises against a list of known failures rather than toward the state
+you actually want.
+
+A feeling of urgency is not evidence. Under pressure every situation feels like
+a fire — which is why the question is asked at the door rather than afterward.
+
+## This package is a signpost
+
+It holds no logic and never will. Every export here comes from
+[`@medicine-wheel/creative-orientation`](https://www.npmjs.com/package/@medicine-wheel/creative-orientation),
+which is where the question is actually answered. Import either name — the
+surface is identical. This one exists because it is the name you were looking
+for.
+
+```ts
+import { readOrientation, THE_QUESTION } from '@medicine-wheel/creative-problem-solving';
+
+THE_QUESTION;   // 'Is there a prior state you are restoring?'
+
+readOrientation({
+  outcome: 'catch cross-service contract breaks',
+  restores: null,
+}).route;       // 'structural-tension' — nothing is being restored
+
+readOrientation({
+  outcome: 'the published image matches the published packages',
+  restores: 'true through 0.5.0',
+  evidence: 'tagged 2026-07-17',
+}).route;       // 'gap-analysis' — a named, evidenced baseline
+```
+
+The baseline claim decides the route. Vocabulary only ever contributes signals,
+because `reduce latency` is a correct outcome during an incident and a symptom
+worth surfacing as a product vision.
+
+> [!WARNING]
+> **Experimental alpha.** Part of the Medicine Wheel Developer Suite, which is
+> under active development. APIs change between patch versions and all packages
+> move in lockstep — pin exact versions. See
+> [ALPHA.md](https://github.com/jgwill/medicine-wheel/blob/main/ALPHA.md).
+
+## License
+
+MIT

package/dist/index.d.ts

@@ -0,0 +1,33 @@
+/**
+ * @medicine-wheel/creative-problem-solving
+ *
+ * You arrived here looking for creative problem solving. This package is a
+ * signpost, not a door — it holds no logic of its own and never will. It
+ * carries one question and then sends you one of two ways.
+ *
+ *   **Is there a prior state you are restoring?**
+ *
+ * Name it and it genuinely existed — this is a fire, and `gap-analysis` is the
+ * right instrument. Baseline, observation, difference, elimination steps you
+ * can verify. That work is correct work; there is nothing to apologise for and
+ * nothing to rename.
+ *
+ * Name none — you are creating, and structural tension is the instrument.
+ * Difference-closing language will mislead you here, because there is no
+ * baseline to return toward: an outcome phrased as removal optimises against a
+ * list of known failures rather than toward the state you actually want.
+ *
+ * A feeling of urgency is not evidence. Under pressure every situation feels
+ * like a fire, which is why the question is asked before the work rather than
+ * after it.
+ *
+ * Everything exported here comes from `@medicine-wheel/creative-orientation` —
+ * the package that answers the question. Import either name; they are the same
+ * surface. This one exists because it is the name you were looking for.
+ *
+ * @packageDocumentation
+ */
+export * from '@medicine-wheel/creative-orientation';
+/** The question this package exists to ask, before any of the work begins. */
+export declare const THE_QUESTION: "Is there a prior state you are restoring?";
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AAEH,cAAc,sCAAsC,CAAC;AAErD,8EAA8E;AAC9E,eAAO,MAAM,YAAY,EAAG,2CAAoD,CAAC"}

package/dist/index.js

@@ -0,0 +1,50 @@
+"use strict";
+/**
+ * @medicine-wheel/creative-problem-solving
+ *
+ * You arrived here looking for creative problem solving. This package is a
+ * signpost, not a door — it holds no logic of its own and never will. It
+ * carries one question and then sends you one of two ways.
+ *
+ *   **Is there a prior state you are restoring?**
+ *
+ * Name it and it genuinely existed — this is a fire, and `gap-analysis` is the
+ * right instrument. Baseline, observation, difference, elimination steps you
+ * can verify. That work is correct work; there is nothing to apologise for and
+ * nothing to rename.
+ *
+ * Name none — you are creating, and structural tension is the instrument.
+ * Difference-closing language will mislead you here, because there is no
+ * baseline to return toward: an outcome phrased as removal optimises against a
+ * list of known failures rather than toward the state you actually want.
+ *
+ * A feeling of urgency is not evidence. Under pressure every situation feels
+ * like a fire, which is why the question is asked before the work rather than
+ * after it.
+ *
+ * Everything exported here comes from `@medicine-wheel/creative-orientation` —
+ * the package that answers the question. Import either name; they are the same
+ * surface. This one exists because it is the name you were looking for.
+ *
+ * @packageDocumentation
+ */
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __exportStar = (this && this.__exportStar) || function(m, exports) {
+    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.THE_QUESTION = void 0;
+__exportStar(require("@medicine-wheel/creative-orientation"), exports);
+/** The question this package exists to ask, before any of the work begins. */
+exports.THE_QUESTION = 'Is there a prior state you are restoring?';
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;;;;;;;;;;;;;;;;;AAEH,uEAAqD;AAErD,8EAA8E;AACjE,QAAA,YAAY,GAAG,2CAAoD,CAAC"}

package/package.json

@@ -0,0 +1,50 @@
+{
+  "name": "@medicine-wheel/creative-problem-solving",
+  "version": "0.5.4",
+  "description": "Creative problem solving, routed at the door: name the prior state you are restoring. Named one — this is a fire, and gap analysis is the right instrument. Named none — you are creating, and structural tension is. Re-exports @medicine-wheel/creative-orientation.",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js",
+      "require": "./dist/index.js",
+      "default": "./dist/index.js"
+    }
+  },
+  "sideEffects": false,
+  "files": [
+    "dist",
+    "README.md",
+    "ALPHA.md"
+  ],
+  "scripts": {
+    "build": "tsc",
+    "clean": "rm -rf dist",
+    "prepublishOnly": "npm run clean && npm run build"
+  },
+  "keywords": [
+    "creative-problem-solving",
+    "problem-solving",
+    "creative-thinking",
+    "ideation",
+    "orientation",
+    "structural-tension",
+    "gap-analysis",
+    "robert-fritz",
+    "medicine-wheel"
+  ],
+  "author": "jgwill",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/jgwill/medicine-wheel.git",
+    "directory": "src/creative-problem-solving"
+  },
+  "dependencies": {
+    "@medicine-wheel/creative-orientation": "^0.5.4"
+  },
+  "devDependencies": {
+    "typescript": "^5.7.0"
+  }
+}