@nanopm/cli 0.1.2 → 0.1.5

package/dist/index.js

@@ -863,22 +863,14 @@ var CHAINED = {
   // (`mapping_completion_hook`): the opportunity map follows the market read below, and
   // the founder confirms what the scan proposed on the card while it is drawn.
   //
-  // **`direction` is queued here rather than after the market, and still reads it.** The
-  // daemon runs one job at a time and `claim_job` takes them `order by created_at`, so a
-  // direction queued the moment the onboarding ends is not *started* until the market —
-  // queued a hair earlier, in this array's own order — has finished and written the
-  // competitors its judge needs for the substitution test. What it skips is the queue behind
-  // `pitch`, which it never needed and which cost it eighty seconds: on dogo-3 (2026-09-24)
-  // the direction landed at 441s against a founder who reaches the card at about 90, and the
-  // Vision row said *nothing yet* twenty-five seconds before the crew wrote it. Now ~358s.
-  //
-  // It does not close the gap — nothing chained can, while the read itself takes 161s — which
-  // is why the mission is asked for on the way in and the vision is drawn as *coming*
-  // (docs/nanopm-56-the-required-set.md). This makes that wait honest rather than shorter
-  // than it looks.
-  // Since 2026-09-30 the direction is queued only when the onboarding left the mission or the
-  // vision empty (`WRITTEN_BY_PARENT`): with both written, it had nothing to fill.
-  onboard: ["market", "direction"],
+  // **The direction crew does not follow an onboarding** (Nicolas, 2026-10-01, docs/ACTIVATION.md
+  // row 27). It was queued here, in the background, whenever the read left the mission or the
+  // vision empty, and it landed 9 to 24 minutes later — after the market, the map and the
+  // solutions — while the card's Direction step, right after the pitch, promised *a few
+  // minutes*. Direction now works like the card's other sections: the read writes what the
+  // repository states, the card asks the founder for a mission it did not find (`missionAsk`),
+  // and the crew runs when the founder asks for it from the business card.
+  onboard: ["market"],
   // A problem list is what solutions hang under, so a fresh list is followed by fresh
   // solutions. **The problem crew itself is retired** (docs/nanopm-59-opportunity-map.md,
   // Guillaume, 2026-09-25): the opportunity map replaced it, and nothing queues it any more —
@@ -891,10 +883,8 @@ var CHAINED = {
   // proposes beside a confirmed pitch and never over it (docs/nanopm-52-pitch-crew.md).
   //
   // The direction crew **was** chained here too, for the same reason — a vision rests on who
-  // else exists — and it moved up to `onboard` on 2026-09-24. It still reads the market: the
-  // daemon is serial and claims `order by created_at`, so a direction queued at the end of
-  // the onboarding starts only once the market, queued a hair before it, has finished. All
-  // it gave up was waiting behind the pitch, which it never read. See the note on `onboard`.
+  // else exists — then after `onboard`, and since 2026-10-01 after nothing: see the note on
+  // `onboard`.
   //
   // Neither follows a personas run the founder started: they pressed one button, for one
   // crew, with a note meant for it (Guillaume, 2026-09-22). A founder who wants both runs asks
@@ -948,16 +938,6 @@ var ONLY_AFTER = {
 var NEVER_AFTER = {
   market: { pitch: ["onboard"] }
 };
-var WRITTEN_BY_PARENT = {
-  onboard: { direction: ["mission", "vision"] }
-};
-function stillOwed(skill, next2, written) {
-  const needs2 = WRITTEN_BY_PARENT[skill] ?? {};
-  return next2.filter((n) => !needs2[n] || needs2[n].some((topic) => !written.has(topic)));
-}
-var BACKGROUND_EDGES = {
-  onboard: ["direction"]
-};
 var AFTER_DEEP = {
   needs: ["opportunities"]
 };
@@ -10956,12 +10936,6 @@ async function runDaemon(options = {}) {
   }
   return { daemonId, processed };
 }
-async function topicsWritten(auth, projectId, skill) {
-  const topics = [...new Set(Object.values(WRITTEN_BY_PARENT[skill] ?? {}).flat())];
-  if (!topics.length) return /* @__PURE__ */ new Set();
-  const { data } = await auth.client.from("memory").select("topic").eq("project_id", projectId).in("topic", topics).is("superseded_by", null);
-  return new Set((data ?? []).map((r) => r.topic));
-}
 async function chainAfter(auth, job, outcome, log) {
   if (NOT_CHAINED_BY_DAEMON.includes(job.skill)) return;
   if (job.params?.chain === false) return;
@@ -10969,14 +10943,13 @@ async function chainAfter(auth, job, outcome, log) {
   const parent = job.parent_job_id ? await parentOf(auth, job.parent_job_id) : null;
   const own = job.params ?? {};
   const deep = own.depth === "deep" && job.trigger === "hook";
-  const next2 = stillOwed(job.skill, daemonQueues(job.skill, 0, parent?.skill ?? null, deep), await topicsWritten(auth, job.project_id, job.skill));
+  const next2 = daemonQueues(job.skill, 0, parent?.skill ?? null, deep);
   if (!next2.length) return;
   if (await chainDepth(auth, job) >= CHAIN_DEPTH_MAX) return;
   const from = deep ? own.repo_path : parent?.params?.repo_path;
   const repo = typeof from === "string" ? { repo_path: from } : null;
   for (const skill of next2) {
-    const background = deep || (BACKGROUND_EDGES[job.skill] ?? []).includes(skill);
-    const params = { ...repo ?? {}, ...deep ? { depth: "deep" } : {}, ...background ? { background: true } : {} };
+    const params = { ...repo ?? {}, ...deep ? { depth: "deep", background: true } : {} };
     const { data, error } = await auth.client.from("jobs").insert({
       project_id: job.project_id,
       skill,
@@ -11335,9 +11308,12 @@ function validateItem(item) {
   }
   return null;
 }
-function overFounder(item, stated) {
-  if (item.topic !== GOALS_TOPIC || item.provenance === "stated" || !stated.has(item.key)) return null;
-  return `the founder set "${item.key}" themselves; drop your proposal, never write it again`;
+function overFounder(item, stated, definitionLever = null) {
+  if (item.topic !== GOALS_TOPIC || item.provenance === "stated") return null;
+  if (stated.has(item.key)) return `the founder set "${item.key}" themselves; drop your proposal, never write it again`;
+  const lever = item.key === OBJECTIVE_KEY ? LEVER_LINE.exec(item.content)?.[1] : void 0;
+  if (definitionLever && lever && lever !== definitionLever) return `the founder chose ${definitionLever} when they defined their objective: write "${item.key}" for ${definitionLever}, or nothing`;
+  return null;
 }
 function normaliseItem(item) {
   return normalisePersona(item);
@@ -11799,9 +11775,9 @@ ${renderMap()}`,
           valid.push({ ...item, content: fix.content });
         } else valid.push(item);
       }
-      const stated = await statedGoals(ctx, valid);
+      const { stated, definitionLever } = await statedGoals(ctx, valid);
       const writable = valid.filter((item) => {
-        const why = overFounder(item, stated);
+        const why = overFounder(item, stated, definitionLever);
         if (why) refused.push({ key: item.key, why });
         return !why;
       });
@@ -12367,11 +12343,11 @@ async function listContext(ctx, domain, topic) {
   return { items };
 }
 async function statedGoals(ctx, items) {
-  const keys = items.filter((i) => i.topic === GOALS_TOPIC && i.provenance !== "stated").map((i) => i.key);
-  if (!keys.length) return /* @__PURE__ */ new Set();
-  const { data, error } = await ctx.client.from("memory").select("key").eq("project_id", ctx.projectId).eq("topic", GOALS_TOPIC).in("key", keys).eq("provenance", "stated").is("superseded_by", null);
+  if (!items.some((i) => i.topic === GOALS_TOPIC && i.provenance !== "stated")) return { stated: /* @__PURE__ */ new Set(), definitionLever: null };
+  const { data, error } = await ctx.client.from("memory").select("key, content").eq("project_id", ctx.projectId).eq("topic", GOALS_TOPIC).eq("provenance", "stated").is("superseded_by", null);
   if (error) throw new Error(`write_context failed reading the founder's goals: ${error.message}`);
-  return new Set(data.map((r) => r.key));
+  const definition = data.find((r) => r.key === DEFINITION_KEY);
+  return { stated: new Set(data.map((r) => r.key)), definitionLever: definition ? parseDefinition(definition.content)?.lever ?? null : null };
 }
 async function writeContext(ctx, items, refused = []) {
   const written = [];
@@ -13909,7 +13885,7 @@ import { promisify as promisify7 } from "util";
 // package.json
 var package_default = {
   name: "@nanopm/cli",
-  version: "0.1.2",
+  version: "0.1.5",
   description: "An autonomous product manager for builders who run several small products. Runs on your machine, drives your own coding harness.",
   type: "module",
   license: "MIT",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nanopm/cli",
-  "version": "0.1.2",
+  "version": "0.1.5",
   "description": "An autonomous product manager for builders who run several small products. Runs on your machine, drives your own coding harness.",
   "type": "module",
   "license": "MIT",

package/skills/onboard/SKILL.md

@@ -152,7 +152,9 @@ product is.
      `nanopm personas` deepens them afterwards with the market view in hand.
    - one aim (`goals`, key `objective-1`), unless a stated one exists: the founder may
      have written theirs on the web while you were reading, so list_context with topic
-     `goals` right before this, and propose nothing over a stated one. If the write is
+     `goals` right before this, and propose nothing over a stated one. If the founder
+     already defined what it counts (`objective-1-definition`, stated), the aim is on **that
+     lever**, never another: they chose it. If the write is
      refused because `objective-1` already exists, the founder set it meanwhile: drop it,
      never write it again (dogo-3, 2026-10-01: a retry cost a round trip). Its first words
      name the lever: `Lever: activation.`, `retention`, `acquisition` or `monetization`;
@@ -171,8 +173,8 @@ product is.
    code does is the pitch with a wider adjective, and it is exactly the row this rule exists
    to stop (docs/nanopm-53-direction.md §3). If the product's own words do not say where the
    company is going, write nothing under these two topics and say so in your final log: the
-   direction crew writes them later, once the personas and the market are in, which is when
-   there is something to write them from.
+   card asks the founder for the mission in their own words, and the business card drafts a
+   mission and a vision with them when they ask. Do not write a gap for it: the card asks.
    Only when the repo states a stance in words (a README that says "maintenance mode",
    a roadmap that says "growth"), call set_preferences with `stance_provenance:
    "inferred"`; otherwise do not call it at all. The stance is `grow` until someone says