@synap-core/workspace-templates 0.29.0 → 0.31.0

package/src/lifecycle-declarations.test.ts

@@ -7,12 +7,12 @@
  *  - the validator's category list equals `@synap-core/types/lifecycle`;
  *  - the mandatory declarations (deal, lead, client, the post that Produce
  *    Content drives) carry the founder-confirmed categories;
- *  - COVERAGE, derived: every non-system kind a playbook moves through
- *    `subjectProfile.statusProperty` declares that property as its lifecycle;
- *  - `humanOnly` = the binding playbooks' `humanOnlyStatuses` that stop, pause
- *    or end the thing (category paused/done/lost) — never an invented one —
- *    plus the exact ledger of founder-decided ACTIVE person-only options
- *    (`PERSON_ONLY_ACTIVE`);
+ *  - COVERAGE, derived: every non-system kind a playbook moves (a stage
+ *    `subjectStatus` or a worker `status`) declares a lifecycle, on every
+ *    declaration that carries its property — the playbook follows it;
+ *  - `humanOnly` lives ONLY on the kind's lifecycle (One model decision 4, the
+ *    playbook's `humanOnlyStatuses` list is retired): the exact ledger below
+ *    pins every person-only option, so changing one is a deliberate edit;
  *  - the whole corpus validates with zero `lifecycle-*` errors, and each rule
  *    fires on a broken clone (self-checks).
  */
@@ -72,18 +72,24 @@ describe("lifecycle declarations — the mandatory four", () => {
 
   it("the post Produce Content drives declares post-status", () => {
     const produce = tpl("content-os").playbooks!.find((p) => p.name === "Produce Content")!;
-    expect(produce.subjectProfile).toMatchObject({ profileSlug: "post", statusProperty: "post-status" });
+    expect(produce.subjectProfile).toEqual({ profileSlug: "post" });
     const lc = lifecycleOf(tpl("content-os"), "post");
     expect(lc?.property).toBe("post-status");
     expect(categories(lc)).toMatchObject({ Idea: "open", Published: "done", Archived: "lost" });
   });
 });
 
+/** The lifecycle property a kind declares anywhere in the corpus. */
+const lifecyclePropertyOf = (kind: string) =>
+  corpus.flatMap((t) => t.profiles).find((p) => p.slug === kind && p.lifecycle)?.lifecycle?.property;
+
 /**
- * Every (kind, statusProperty, playbook) a catalog playbook moves. `withSystem`
- * false drops the pod's system kinds (task, decision, question…), whose
- * lifecycle the pod seeds itself (`ensure-system-lifecycles.ts`) — except
- * `deal`, a system kind whose lifecycle the CRM template owns.
+ * Every (kind, lifecycle property, playbook) a catalog playbook moves: a stage
+ * with a `subjectStatus` or a worker with a `status`. The property is the
+ * kind's declared lifecycle (the playbook names none). `withSystem` false drops
+ * the pod's system kinds (task, decision, question…), whose lifecycle the pod
+ * seeds itself (`ensure-system-lifecycles.ts`) — except `deal`, a system kind
+ * whose lifecycle the CRM template owns.
  */
 const TEMPLATE_OWNED_SYSTEM_LIFECYCLES = new Set(["deal"]);
 function playbookBindings({ withSystem = false } = {}) {
@@ -91,12 +97,13 @@ function playbookBindings({ withSystem = false } = {}) {
     (t.playbooks ?? [])
       .filter(
         (pb) =>
-          pb.subjectProfile?.statusProperty &&
+          pb.subjectProfile?.profileSlug &&
+          ((pb.stages ?? []).some((st) => st.subjectStatus) || (pb.activators ?? []).some((a) => a.status)) &&
           (withSystem ||
             !SYSTEM_PROFILES.has(pb.subjectProfile.profileSlug) ||
             TEMPLATE_OWNED_SYSTEM_LIFECYCLES.has(pb.subjectProfile.profileSlug))
       )
-      .map((pb) => ({ template: t, pb, kind: pb.subjectProfile!.profileSlug, property: pb.subjectProfile!.statusProperty! }))
+      .map((pb) => ({ template: t, pb, kind: pb.subjectProfile!.profileSlug, property: lifecyclePropertyOf(pb.subjectProfile!.profileSlug) }))
   );
 }
 
@@ -137,7 +144,9 @@ describe("lifecycle declarations — coverage (derived from the playbooks)", ()
   });
 
   it("every kind a playbook moves declares that property as its lifecycle, wherever it is declared", () => {
-    const missing: string[] = [];
+    const missing: string[] = playbookBindings({ withSystem: true })
+      .filter((b) => !b.property)
+      .map((b) => `${b.template.meta.slug}:${b.pb.name} moves ${b.kind}, which declares no lifecycle`);
     for (const b of playbookBindings())
       for (const t of corpus)
         for (const p of t.profiles.filter((x) => x.slug === b.kind && x.properties.some((pr) => pr.slug === b.property)))
@@ -146,58 +155,56 @@ describe("lifecycle declarations — coverage (derived from the playbooks)", ()
   });
 
   /**
-   * ACTIVE options a person must set, each a founder decision — the only place
-   * `humanOnly` may sit outside paused/done/lost. Still never invented: each
-   * must ALSO be in its binding playbook's `humanOnlyStatuses` (the rule below
-   * reads both). EXACT: an entry that is no longer humanOnly turns this red.
-   *  - ui-design.approved — the design review is a person's call; a coding
-   *    agent implements only from an approved design (DESIGN-DEV-XP-PLAN P6,
-   *    founder-approved 2026-10-12).
-   *  - outreach-touch.sent — the agent drafts, a person sends (founder decision
-   *    2026-10-20; the CRM absorbed Outreach & Comms 2026-10-23): no agent ever
-   *    marks a message sent, and the reply reader starts only once a person did.
+   * Every person-only option in the catalog, EXACT. Until 7 Nov 2026 this was
+   * derived from the binding playbooks' `humanOnlyStatuses`; that list is
+   * retired (One model decision 4), so the flags themselves are the source and
+   * this ledger makes any change to one a deliberate, reviewed edit. Founder
+   * decisions among them: ui-design.approved (design review, DESIGN-DEV-XP-PLAN
+   * P6, 2026-10-12), outreach-touch.sent (a person sends, 2026-10-20),
+   * devplane_feature.cancelled / devplane_story.dropped (homes, 2026-10-13).
    */
-  const PERSON_ONLY_ACTIVE = new Set(["builder-workspace:ui-design.approved", "crm:outreach-touch.sent"]);
-
-  /**
-   * Person-only options the FOUNDER decided on a lifecycle no playbook moves
-   * yet (so no `humanOnlyStatuses` can carry them). Each one a dated decision;
-   * EXACT, like the ledger above.
-   *  - devplane_feature.cancelled / devplane_story.dropped — "Dropped (lost,
-   *    humanOnly)", object-first homes decision 2026-10-13.
-   */
-  const FOUNDER_HUMAN_ONLY = new Set([
+  const HUMAN_ONLY = [
+    "brand-library:brand-asset.deprecated",
+    "brand-library:brand-voice-guide.deprecated",
+    "brand-library:content-guideline.deprecated",
     "builder-workspace:devplane_feature.cancelled",
     "builder-workspace:devplane_story.dropped",
-  ]);
-
-  it("humanOnly = the binding playbooks' humanOnlyStatuses that pause or end the thing", () => {
-    const drift: string[] = [];
-    const activeSeen: string[] = [];
-    const founderSeen: string[] = [];
-    for (const t of corpus)
-      for (const p of t.profiles) {
-        if (!p.lifecycle) continue;
-        const ho = new Set(
-          playbookBindings({ withSystem: true })
-            .filter((b) => b.kind === p.slug && b.property === p.lifecycle!.property)
-            .flatMap((b) => b.pb.humanOnlyStatuses ?? [])
-        );
-        for (const o of p.lifecycle.options) {
-          const id = `${t.meta.slug}:${p.slug}.${o.key}`;
-          const want =
-            (ho.has(o.key) && (["paused", "done", "lost"].includes(o.category) || PERSON_ONLY_ACTIVE.has(id))) ||
-            FOUNDER_HUMAN_ONLY.has(id);
-          if (want && PERSON_ONLY_ACTIVE.has(id)) activeSeen.push(id);
-          if (o.humanOnly && FOUNDER_HUMAN_ONLY.has(id)) founderSeen.push(id);
-          if (Boolean(o.humanOnly) !== want) drift.push(`${id} humanOnly=${Boolean(o.humanOnly)}`);
-        }
-      }
-    expect(drift).toEqual([]);
-    expect(activeSeen.sort()).toEqual([...PERSON_ONLY_ACTIVE].sort());
-    expect(founderSeen.sort()).toEqual([...FOUNDER_HUMAN_ONLY].sort());
-    // non-vacuity: the rule marks real options
-    expect(lifecycleOf(tpl("content-os"), "post")?.options.find((o) => o.key === "Archived")?.humanOnly).toBe(true);
+    "builder-workspace:finding.superseded",
+    "builder-workspace:finding.wont_fix",
+    "builder-workspace:issue.wont_fix",
+    "builder-workspace:ui-design.approved",
+    "builder-workspace:ui-design.archived",
+    "content-os:campaign.cancelled",
+    "content-os:campaign.paused",
+    "content-os:newsletter.Archived",
+    "content-os:post.Archived",
+    "crm:campaign.cancelled",
+    "crm:campaign.paused",
+    "crm:deal.lost",
+    "crm:outreach-touch.replaced",
+    "crm:outreach-touch.sent",
+    "finance:expense.reimbursed",
+    "finance:expense.rejected",
+    "finance:invoice.void",
+    "foundation:lead.converted",
+    "foundation:lead.disqualified",
+    "marketing-campaign:campaign.cancelled",
+    "marketing-campaign:campaign.paused",
+    "operations:contract.expired",
+    "operations:contract.terminated",
+    "operations:deliverable.cancelled",
+    "operations:engagement.cancelled",
+    "operations:engagement.on-hold",
+    "social:post.Archived",
+  ];
+
+  it("humanOnly sits on the kind's lifecycle, exactly the ledger", () => {
+    const seen = corpus.flatMap((t) =>
+      t.profiles.flatMap((p) =>
+        (p.lifecycle?.options ?? []).filter((o) => o.humanOnly).map((o) => `${t.meta.slug}:${p.slug}.${o.key}`)
+      )
+    );
+    expect([...new Set(seen)].sort()).toEqual(HUMAN_ONLY);
   });
 });
 
@@ -238,15 +245,4 @@ describe("lifecycle declarations — the validator", () => {
     delete campaignIn(c2, "crm").lifecycle;
     expect(lifecycleErrors(crmIn(c2), c2).map((e) => e.rule)).toContain("lifecycle-diverges");
   });
-
-  it("self-check: a playbook moving another property than the lifecycle is refused", () => {
-    const c = clone();
-    const produce = c.find((t) => t.meta.slug === "content-os")!.playbooks!.find((p) => p.name === "Produce Content")!;
-    const post = c.find((t) => t.meta.slug === "content-os")!.profiles.find((p) => p.slug === "post")!;
-    post.lifecycle!.property = "platform";
-    produce.subjectProfile!.statusProperty = "post-status";
-    expect(lifecycleErrors(c.find((t) => t.meta.slug === "content-os")!, c).map((e) => e.rule)).toContain(
-      "lifecycle-status-property"
-    );
-  });
 });

package/src/marketing.yaml

@@ -13,6 +13,8 @@ meta:
   # What this space PRODUCES (homes): the purpose word, then its kinds/roles.
   intent:
     label: Marketing
+    # The ONE primary output (One model decision 3): a run campaign (Run a campaign).
+    primary: campaign
     produces:
       - profile: campaign
 
@@ -261,7 +263,8 @@ views:
     slug: campaigns
     type: kanban
     scopeProfileSlug: campaign
-    groupBy: campaign-status
+    config:
+      groupByField: campaign-status
     description: "Campaign kanban board by status."
   - name: Contacts
     slug: contacts
@@ -399,8 +402,6 @@ playbooks:
       person's call.
     subjectProfile:
       profileSlug: campaign
-      statusProperty: campaign-status
-    humanOnlyStatuses: [paused, cancelled]
     activators:
       - { on: created, mode: propose }
     params:

package/src/meetings-knowledge.yaml

@@ -172,10 +172,9 @@ views:
     slug: meeting-action-items
     type: kanban
     scopeProfileSlug: task
-    groupBy: status
     description: Tasks generated from meetings, by status.
     config:
-      groupBy: status
+      groupByField: status
 
 entityLinks:
   - sourceProfileSlug: meeting

package/src/operations.yaml

@@ -18,7 +18,6 @@ meta:
     label: Client delivery
     promise: Every client engagement and where it stands.
     suggestFor: [consultant]
-    profile: engagement
     views: [engagements]
     example:
       - { title: "Website redesign for Maison Dupont", values: { engagement-status: active, engagement-value: 18000 } }
@@ -35,6 +34,8 @@ meta:
   # What this space PRODUCES (homes): the purpose word, then its kinds/roles.
   intent:
     label: Delivery
+    # The ONE primary output (One model decision 3): a delivered engagement (Deliver a client engagement).
+    primary: engagement
     produces:
       - profile: engagement
       - profile: deliverable
@@ -304,19 +305,28 @@ views:
     slug: engagements
     type: kanban
     scopeProfileSlug: engagement
-    groupBy: engagement-status
+    config:
+      groupByField: engagement-status
     description: "Client engagements on a board by status."
   - name: Deliverables
     slug: deliverables
     type: kanban
     scopeProfileSlug: deliverable
-    groupBy: deliverable-status
+    config:
+      groupByField: deliverable-status
     description: "Deliverables on a board by status."
   - name: Contracts
     slug: contracts
     type: table
     scopeProfileSlug: contract
     description: "Contracts with their status, value, and term."
+  - name: Contract Board
+    slug: contract-board
+    type: kanban
+    scopeProfileSlug: contract
+    description: "Contracts by status — the flow board of Get a contract signed."
+    config:
+      groupByField: contract-status
   - name: Client Briefings
     slug: client-briefings
     type: list
@@ -938,8 +948,6 @@ playbooks:
       call.
     subjectProfile:
       profileSlug: engagement
-      statusProperty: engagement-status
-    humanOnlyStatuses: [on-hold, cancelled]
     activators:
       - { on: created, mode: propose }
     params:
@@ -1018,8 +1026,6 @@ playbooks:
       close bills it.
     subjectProfile:
       profileSlug: deliverable
-      statusProperty: deliverable-status
-    humanOnlyStatuses: [not-started, cancelled]
     activators:
       - { on: enters_status, status: in-progress, mode: propose }
     params:
@@ -1095,8 +1101,6 @@ playbooks:
       document. Expiry and termination are a person's call.
     subjectProfile:
       profileSlug: contract
-      statusProperty: contract-status
-    humanOnlyStatuses: [expired, terminated]
     activators:
       - { on: created, mode: propose }
     params:

package/src/process-contract.validate.test.ts

@@ -2,11 +2,11 @@
  * The process contract a playbook declares is checked at authoring time
  * (`checkProcessContract` in validate.ts), because every one of these mistakes
  * is STORED by the pod and then silently never fires:
- *   - a `statusProperty` that is not a select of the subject kind → the stage's
- *     status write lands on a field nobody reads;
- *   - a `subjectStatus` / activator `status` / `humanOnlyStatuses` value that is
- *     not one of the enum values → a write the select refuses, or a rule on a
- *     value no entity ever enters;
+ *   - a `statusProperty` / `onEnd` / `humanOnlyStatuses` → retired (One model
+ *     decision 4): the process follows the kind's declared lifecycle;
+ *   - a `subjectStatus` / activator `status` that is not an option of the
+ *     kind's declared lifecycle (or a kind with none) → a write the select
+ *     refuses, or a rule on a value no entity ever enters;
  *   - an `onFail.toStage` naming no stage → a rejected gate with nowhere to go;
  *   - a `relationToSubject` naming no relation → an edge type nothing renders.
  *
@@ -24,21 +24,17 @@ import type { WorkspaceYaml } from "./types.js";
 import { readYamlTemplates } from "./generate.mjs";
 
 const PROCESS_RULES = new Set([
-  "playbook-status-property-no-subject",
-  "playbook-status-property-unknown",
-  "playbook-status-property-not-select",
+  "playbook-field-retired",
   "stage-subject-status-unknown",
-  "stage-subject-status-unknown-no-property",
+  "stage-subject-status-unknown-no-lifecycle",
   "stage-onfail-unknown",
   "activator-on-invalid",
   "activator-mode-invalid",
   "activator-no-subject",
   "activator-status-required",
   "activator-status-unknown",
-  "activator-status-unknown-no-property",
+  "activator-status-unknown-no-lifecycle",
   "activator-status-unexpected",
-  "human-only-status-unknown",
-  "human-only-status-unknown-no-property",
   "output-relation-no-subject",
   "output-relation-unknown",
   "output-optional-not-boolean",
@@ -46,10 +42,19 @@ const PROCESS_RULES = new Set([
 ]);
 
 /**
- * `owner` OWNS the shared kind `widget` (with its lifecycle select). `proc`
+ * `owner` OWNS the shared kind `widget` (with its declared lifecycle). `proc`
  * requires it and only re-declares `widget` with no properties — so resolving
- * `widget-stage` proves the status property is found ACROSS the corpus.
+ * `widget-stage` proves the lifecycle is found ACROSS the corpus.
  */
+const WIDGET_LIFECYCLE = {
+  property: "widget-stage",
+  options: [
+    { key: "New", category: "open" },
+    { key: "Built", category: "active" },
+    { key: "Shipped", category: "done" },
+    { key: "Archived", category: "lost", humanOnly: true },
+  ],
+};
 const owner = {
   meta: { slug: "owner", name: "Owner", description: "d", icon: "x", color: "gray" },
   workspace: { name: "Owner", description: "d" },
@@ -58,6 +63,7 @@ const owner = {
       slug: "widget",
       displayName: "Widget",
       scope: "shared",
+      lifecycle: WIDGET_LIFECYCLE,
       properties: [
         { slug: "widget-stage", label: "Stage", valueType: "string", inputType: "select", enumValues: ["New", "Built", "Shipped", "Archived"] },
         { slug: "widget-notes", label: "Notes", valueType: "string", inputType: "text" },
@@ -72,8 +78,7 @@ function proc(mutate: (pb: Record<string, any>) => void = () => {}): WorkspaceYa
     name: "Build Widget",
     goalTemplate: "Build {widget}",
     params: [{ name: "widget", type: "entity", required: true }],
-    subjectProfile: { profileSlug: "widget", statusProperty: "widget-stage" },
-    humanOnlyStatuses: ["New", "Archived"],
+    subjectProfile: { profileSlug: "widget" },
     activators: [{ on: "enters_status", status: "Built", mode: "propose" }],
     expectedOutputs: [{ kind: "widget", label: "Spin-off", relationToSubject: "spawned_from" }],
     stages: [
@@ -112,26 +117,16 @@ describe("process contract — the clean fixture is clean", () => {
 });
 
 describe("process contract — each rule fires on its own fixture", () => {
-  it("statusProperty that the kind does not carry", () => {
-    expect(rulesOf(proc((pb) => (pb.subjectProfile.statusProperty = "widget-phase")))).toEqual([
-      "playbook-status-property-unknown",
+  // Negative control: each assertion goes red with the `playbook-field-retired`
+  // loop removed from checkProcessContract.
+  it("each retired field is refused (statusProperty, onEnd, humanOnlyStatuses)", () => {
+    expect(rulesOf(proc((pb) => (pb.subjectProfile.statusProperty = "widget-stage")))).toEqual([
+      "playbook-field-retired",
     ]);
-  });
-
-  it("statusProperty that is not a select", () => {
-    expect(
-      rulesOf(
-        proc((pb) => {
-          pb.subjectProfile.statusProperty = "widget-notes";
-          // Without a resolvable vocabulary the statuses are not re-reported.
-        })
-      )
-    ).toEqual(["playbook-status-property-not-select"]);
-  });
-
-  it("statusProperty with no subject kind", () => {
-    const rules = rulesOf(proc((pb) => (pb.subjectProfile = { statusProperty: "widget-stage" })));
-    expect(rules).toContain("playbook-status-property-no-subject");
+    expect(rulesOf(proc((pb) => (pb.subjectProfile.onEnd = { cancelled: "New" })))).toEqual([
+      "playbook-field-retired",
+    ]);
+    expect(rulesOf(proc((pb) => (pb.humanOnlyStatuses = ["New"])))).toEqual(["playbook-field-retired"]);
   });
 
   it("a stage subjectStatus outside the enum", () => {
@@ -140,17 +135,14 @@ describe("process contract — each rule fires on its own fixture", () => {
     ]);
   });
 
-  it("a stage subjectStatus with no statusProperty to belong to", () => {
-    const rules = rulesOf(
-      proc((pb) => {
-        delete pb.subjectProfile.statusProperty;
-        delete pb.humanOnlyStatuses;
-        pb.activators = [{ on: "created", mode: "propose" }];
-      })
-    );
-    expect(rules).toEqual([
-      "stage-subject-status-unknown-no-property",
-      "stage-subject-status-unknown-no-property",
+  it("a stage subjectStatus on a kind that declares no lifecycle", () => {
+    const noLifecycle = structuredClone(owner) as unknown as { profiles: Array<Record<string, unknown>> };
+    delete noLifecycle.profiles[0]!.lifecycle;
+    const tpl = proc((pb) => (pb.activators = [{ on: "created", mode: "propose" }]));
+    const { errors } = validateTemplate(tpl, { corpus: [noLifecycle as unknown as WorkspaceYaml, tpl] });
+    expect(errors.filter((e) => PROCESS_RULES.has(e.rule)).map((e) => e.rule)).toEqual([
+      "stage-subject-status-unknown-no-lifecycle",
+      "stage-subject-status-unknown-no-lifecycle",
     ]);
   });
 
@@ -218,7 +210,6 @@ describe("process contract — each rule fires on its own fixture", () => {
       proc((pb) => {
         delete pb.subjectProfile;
         delete pb.stages;
-        delete pb.humanOnlyStatuses;
         delete pb.expectedOutputs;
         pb.activators = [{ on: "created", mode: "propose" }];
       })
@@ -226,12 +217,6 @@ describe("process contract — each rule fires on its own fixture", () => {
     expect(rules).toEqual(["activator-no-subject"]);
   });
 
-  it("a humanOnlyStatuses value outside the enum", () => {
-    expect(rulesOf(proc((pb) => (pb.humanOnlyStatuses = ["New", "Retired"])))).toEqual([
-      "human-only-status-unknown",
-    ]);
-  });
-
   it("a playbook-level relationToSubject the corpus does not define", () => {
     expect(rulesOf(proc((pb) => (pb.expectedOutputs[0].relationToSubject = "spawned_by")))).toEqual([
       "output-relation-unknown",
@@ -277,7 +262,6 @@ describe("process contract — each rule fires on its own fixture", () => {
     const strip = (pb: Record<string, any>) => {
       delete pb.subjectProfile;
       delete pb.stages;
-      delete pb.humanOnlyStatuses;
       delete pb.activators;
     };
     expect(rulesOf(proc(strip))).toEqual(["output-relation-no-subject"]);
@@ -340,7 +324,8 @@ describe("process contract — the shipped corpus", () => {
     const corpus = readYamlTemplates().map((t) => t.data as WorkspaceYaml);
     const contentOs = corpus.find((t) => t.meta.slug === "content-os")!;
     const produce = contentOs.playbooks!.find((p) => p.name === "Produce Content")!;
-    expect(produce.subjectProfile?.statusProperty).toBe("post-status");
+    expect(produce.subjectProfile).toEqual({ profileSlug: "post" });
+    expect(contentOs.profiles.find((p) => p.slug === "post")?.lifecycle?.property).toBe("post-status");
     expect(produce.stages!.filter((s) => s.subjectStatus).length).toBe(6);
     const errs = corpus.flatMap((t) =>
       validateTemplate(t, { corpus })

package/src/project-management.yaml

@@ -17,6 +17,8 @@ meta:
   # What this space PRODUCES (homes): the purpose word, then its kinds/roles.
   intent:
     label: Planning
+    # The ONE primary output (One model decision 3): a finished sprint, its one produced kind.
+    primary: sprint
     produces:
       - profile: sprint
 
@@ -192,7 +194,6 @@ views:
     slug: sprint-board
     type: kanban
     scopeProfileSlug: task
-    groupBy: task-status
     description: "Active sprint tasks in Backlog / Todo / In Progress / Review / Done lanes"
     config:
       groupByField: task-status
@@ -276,7 +277,6 @@ views:
     slug: retrospective-board
     type: kanban
     scopeProfileSlug: sprint
-    groupBy: sprint-status
     description: "Sprint retrospectives — completed sprints with retrospective notes attached as documents"
     config:
       groupByField: sprint-status

package/src/publish-official-lib.test.ts

@@ -77,7 +77,7 @@ describe("plan → execute — the wire", () => {
       .playbooks as any[];
     const produce = yamlPlaybooks.find((p) => p.name === "Produce Content");
     // Non-vacuity: the YAML really declares the contract fields compared below.
-    expect(produce.subjectProfile.statusProperty).toBe("post-status");
+    expect(produce.subjectProfile).toEqual({ profileSlug: "post" });
     expect(produce.activators).toEqual([{ on: "enters_status", status: "Briefed", mode: "propose" }]);
     expect(produce.stages.find((s: any) => s.key === "review").onFail).toEqual({ toStage: "draft" });
     expect(
@@ -98,7 +98,8 @@ describe("plan → execute — the wire", () => {
       "Scheduled",
       "Published",
     ]);
-    expect(postedProduce.humanOnlyStatuses).toEqual(["Idea", "Archived"]);
+    // Retired from the catalog (One model decision 4): nothing to carry.
+    expect(postedProduce.humanOnlyStatuses).toBeUndefined();
   });
 
   it("reports a stamp the CP did not store", async () => {

package/src/research-base.yaml

@@ -29,9 +29,11 @@ meta:
   # What this space PRODUCES (homes): the purpose word, then its kinds/roles.
   intent:
     label: Research
+    # The ONE primary output (One model decision 3): a finding is what research yields (questions are its input).
+    primary: research-finding
     produces:
       - profile: hypothesis
-      - profile: finding
+      - profile: research-finding
 
 workspace:
   name: Research
@@ -60,6 +62,15 @@ profiles:
     icon: help-circle
     color: blue
     description: An open question driving an investigation — the thing research answers.
+    # The pod seeds this lifecycle on every pod (ensure-system-lifecycles.ts);
+    # declared here to match the seed exactly, so a playbook can follow it.
+    lifecycle:
+      property: questionStatus
+      options:
+        - { key: open, category: open }
+        - { key: exploring, category: active }
+        - { key: answered, category: done }
+        - { key: abandoned, category: lost }
     properties:
       - slug: questionStatus
         label: Status
@@ -214,7 +225,7 @@ profiles:
         valueType: string
         inputType: textarea
 
-  - slug: finding
+  - slug: research-finding
     displayName: Finding
     icon: check-circle
     color: "#10B981"
@@ -253,7 +264,7 @@ views:
   - name: Knowledge Map
     slug: research-knowledge-map
     type: graph
-    scopeProfileSlugs: [field, concept, finding]
+    scopeProfileSlugs: [field, concept, research-finding]
     description: The cartography — fields and concepts, their overlaps and prerequisites, and the findings attached to them.
     defaultView: true
     config:
@@ -280,14 +291,13 @@ views:
     slug: research-hypotheses
     type: kanban
     scopeProfileSlug: hypothesis
-    groupBy: stance
     description: Candidate theories, grouped by where the evidence has left them.
     config:
-      groupBy: stance
+      groupByField: stance
   - name: Findings
     slug: research-findings
     type: table
-    scopeProfileSlug: finding
+    scopeProfileSlug: research-finding
     description: What's been established, with its confidence.
     config:
       columns: [title, confidence, status]
@@ -349,7 +359,7 @@ entityLinks:
     }
   - {
       sourceProfileSlug: research,
-      targetProfileSlug: finding,
+      targetProfileSlug: research-finding,
       type: concluded,
       label: Concluded,
     }
@@ -373,19 +383,19 @@ entityLinks:
       label: Cites,
     }
   - {
-      sourceProfileSlug: finding,
+      sourceProfileSlug: research-finding,
       targetProfileSlug: research,
       type: derived_from,
       label: Derived from,
     }
   - {
-      sourceProfileSlug: finding,
+      sourceProfileSlug: research-finding,
       targetProfileSlug: source,
       type: supported_by,
       label: Supported by,
     }
   - {
-      sourceProfileSlug: finding,
+      sourceProfileSlug: research-finding,
       targetProfileSlug: concept,
       type: about,
       label: About,
@@ -410,7 +420,7 @@ playbooks:
       rejected with a reason (never silently drop a source). WEIGH: form the
       candidate answers as `hypothesis` entities that answer the question; link
       every source that bears on a hypothesis with `supports` or
-      `contradicts`; use the evidence-synthesis skill to emit `finding`
+      `contradicts`; use the evidence-synthesis skill to emit `research-finding`
       entities with honestly calibrated confidence, each `supported_by` its
       sources and `derived_from` this research; use the concept-cartography
       skill to place the findings onto the knowledge map. ANSWER: create the
@@ -420,8 +430,6 @@ playbooks:
       proposal-gated and reviewable.
     subjectProfile:
       profileSlug: question
-      statusProperty: questionStatus
-    humanOnlyStatuses: [abandoned]
     activators:
       - { on: created, mode: propose }
     params:
@@ -486,8 +494,7 @@ playbooks:
       and link each one derived_from the finding. Quote only what the sources
       support.
     subjectProfile:
-      profileSlug: finding
-      statusProperty: status
+      profileSlug: research-finding
     activators:
       - { on: enters_status, status: validated, mode: propose }
     params: