@synap-core/workspace-templates 0.30.0 → 0.32.0

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,6 +29,8 @@ 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: research-finding
@@ -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
@@ -280,10 +291,9 @@ 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
@@ -420,8 +430,6 @@ playbooks:
       proposal-gated and reviewable.
     subjectProfile:
       profileSlug: question
-      statusProperty: questionStatus
-    humanOnlyStatuses: [abandoned]
     activators:
       - { on: created, mode: propose }
     params:
@@ -487,7 +495,6 @@ playbooks:
       support.
     subjectProfile:
       profileSlug: research-finding
-      statusProperty: status
     activators:
       - { on: enters_status, status: validated, mode: propose }
     params:

package/src/research-decision.yaml

@@ -45,6 +45,15 @@ profiles:
     # Pod-wide `question` is a first-class KIND (Decision 1 — the manifest retired
     # w4.convert.question to a keep no-op). Declared as a plain kind to match the
     # seed + research-base and reuse the existing pod-wide row.
+    # 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
@@ -83,6 +92,15 @@ profiles:
     # Pod-wide `decision` is a first-class KIND (Decision 1 — w4.convert.decision
     # retired to a keep no-op). Declared as a plain kind to match the seed; the
     # `resolves` / `considered_in` links resolve against the reused pod-wide row.
+    # 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: decisionStatus
+      options:
+        - { key: proposed, category: open }
+        - { key: accepted, category: done }
+        - { key: superseded, category: lost }
+        - { key: rejected, category: lost }
     properties:
       - slug: summary
         label: Summary
@@ -168,8 +186,6 @@ playbooks:
       superseded.
     subjectProfile:
       profileSlug: decision
-      statusProperty: decisionStatus
-    humanOnlyStatuses: [superseded, rejected]
     activators:
       - { on: created, mode: propose }
     params:

package/src/ship-a-change.template.test.ts

@@ -67,8 +67,9 @@ const outputs = (type: string) =>
   );
 
 describe("Ship a change — the process follows the feature's lifecycle", () => {
-  it("names the lifecycle property, and every status it writes or reads is an option of it", () => {
-    expect(pb.subjectProfile.statusProperty).toBe(feature.lifecycle.property);
+  it("follows the feature's lifecycle (names no statusProperty), and every status it writes or reads is an option of it", () => {
+    expect(pb.subjectProfile.statusProperty).toBeUndefined();
+    expect(pb.subjectProfile.profileSlug).toBe("devplane_feature");
     const options = new Set(feature.lifecycle.options.map((o) => o.key));
     const used = [
       ...pb.stages.map((s) => s.subjectStatus).filter(Boolean),

package/src/social.yaml

@@ -16,6 +16,8 @@ meta:
   # What this space PRODUCES (homes): the purpose word, then its kinds/roles.
   intent:
     label: Distribution
+    # The ONE primary output (One model decision 3): a published post, its one produced kind.
+    primary: post
     produces:
       - profile: post
 
@@ -297,7 +299,8 @@ views:
     slug: content-calendar
     type: kanban
     scopeProfileSlug: post
-    groupBy: post-status
+    config:
+      groupByField: post-status
     description: "Posts on a board by status — idea to published."
   - name: Platforms
     slug: platforms

package/src/start.test.ts

@@ -130,6 +130,28 @@ describe("meta.start — validator rules", () => {
   });
 });
 
+describe("meta.start — the kind defaults to the primary output (one source)", () => {
+  const withPrimary = (start: Partial<TemplateStart>) => {
+    const t = make("t", start);
+    t.meta.intent = { label: "Sales", primary: "deal", produces: [{ profile: "deal" }] };
+    return t;
+  };
+  // Negative control: goes red with the start-profile-* block removed from checkStart.
+  it("an omitted profile reads meta.intent.primary, and the wire carries it", () => {
+    const t = withPrimary({ profile: undefined });
+    expect(startErrors(t)).toEqual([]);
+    expect(toPackageDefinition(t).start?.profile).toBe("deal");
+  });
+
+  it("start-profile-redundant: naming the primary again is a second copy", () => {
+    expect(startErrors(withPrimary({ profile: "deal" }))).toEqual(["start-profile-redundant"]);
+  });
+
+  it("start-profile-missing: no profile and no primary to default to", () => {
+    expect(startErrors(make("t", { profile: undefined }))).toEqual(["start-profile-missing"]);
+  });
+});
+
 describe("meta.start — package door", () => {
   it("carries a top-level start, never in _meta", () => {
     const def = toPackageDefinition(make("t"));