@synap-core/workspace-templates 0.29.0 → 0.31.0

package/dist/wire.d.ts

@@ -1,4 +1,4 @@
-import { g as PackageDefinitionOutput, X as WorkspaceDefinitionInput } from './define-DqoItRiR.js';
+import { g as PackageDefinitionOutput, X as WorkspaceDefinitionInput } from './define-DHDi8C33.js';
 import '@synap-core/types/presentation';
 import '@synap-core/types/space-brief';
 import '@synap-core/types/capability-intents';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synap-core/workspace-templates",
-  "version": "0.29.0",
+  "version": "0.31.0",
   "type": "module",
   "description": "Canonical workspace definitions — YAML source + typed exports for browser, backend, CLI, and marketplace",
   "repository": {

package/src/brand-library.yaml

@@ -1171,8 +1171,6 @@ playbooks:
       Deprecating an asset is a person's call.
     subjectProfile:
       profileSlug: brand-asset
-      statusProperty: asset-status
-    humanOnlyStatuses: [deprecated]
     params:
       - { name: asset, type: entity, label: Brand asset, required: true }
     executor: is-agent
@@ -1212,8 +1210,6 @@ playbooks:
       is checked against. Retiring a guide is a person's call.
     subjectProfile:
       profileSlug: brand-voice-guide
-      statusProperty: voice-status
-    humanOnlyStatuses: [deprecated]
     params:
       - { name: guide, type: entity, label: Brand voice guide, required: true }
     executor: is-agent
@@ -1249,8 +1245,6 @@ playbooks:
       guideline is a person's call.
     subjectProfile:
       profileSlug: content-guideline
-      statusProperty: guideline-status
-    humanOnlyStatuses: [deprecated]
     params:
       - { name: guideline, type: entity, label: Content guideline, required: true }
     executor: is-agent

package/src/builder-dev-fold.template.test.ts

@@ -45,9 +45,8 @@ const INTRINSIC_COLUMNS = new Set(["title"]);
 type View = {
   name: string;
   scopeProfileSlug?: string;
-  groupBy?: string;
   sortBy?: string;
-  config?: { columns?: unknown[] };
+  config?: { columns?: unknown[]; groupByField?: string };
 };
 
 const def = toWorkspaceDefinition("builder-workspace");
@@ -70,7 +69,7 @@ describe("builder-workspace — dev-dashboard fold (R7)", () => {
     expect(props.size, `${name} scopes "${scope}" which declares no properties`).toBeGreaterThan(0);
 
     const named = [
-      view!.groupBy,
+      view!.config?.groupByField,
       view!.sortBy,
       ...((view!.config?.columns as string[] | undefined) ?? []),
     ].filter((s): s is string => typeof s === "string");

package/src/builder-dev-playbooks.template.test.ts

@@ -35,16 +35,18 @@ describe("builder dev playbooks", () => {
     expect(pb?.subjectProfile?.activators).toBeUndefined();
   });
 
-  it.each(DEV_PLAYBOOKS)("%s names a statusProperty wherever a stage moves a status", (name) => {
-    const pb = find(name);
-    const moves = (pb?.stages ?? []).some((s) => s.subjectStatus);
-    if (moves) expect(pb?.subjectProfile?.statusProperty).toBeTruthy();
+  // One model decision 4 (7 Nov 2026): the process follows the kind's declared
+  // lifecycle — no statusProperty, and no end move (decision of 6 Nov).
+  it.each(DEV_PLAYBOOKS)("%s follows its kind's lifecycle and declares no end move", (name) => {
+    const pb = find(name) as Record<string, any> | undefined;
+    expect(pb?.subjectProfile?.statusProperty).toBeUndefined();
+    expect(pb?.subjectProfile?.onEnd).toBeUndefined();
+    expect(pb?.humanOnlyStatuses).toBeUndefined();
   });
 
   it("Fix a bug works the core `issue` kind through its declared lifecycle", () => {
     const pb = find("Fix a bug");
     expect(pb?.subjectProfile?.profileSlug).toBe("issue");
-    expect(pb?.subjectProfile?.statusProperty).toBe("issueStatus");
     const issue = (getWorkspaceTemplate("builder-workspace")?.profiles ?? []).find((p) => p.slug === "issue") as
       | { lifecycle?: { property: string; options: { key: string; category: string }[] } }
       | undefined;

package/src/builder.yaml

@@ -46,6 +46,8 @@ meta:
   # What this space PRODUCES (homes): the purpose word, then its kinds/roles.
   intent:
     label: Product
+    # The ONE primary output (One model decision 3): the feature is what the dev loop ships (Build a change works one).
+    primary: devplane_feature
     produces:
       - profile: devplane_feature
       - profile: devplane_story
@@ -720,6 +722,12 @@ profiles:
     icon: alert-triangle
     color: red
     description: A production incident with severity, status, and root cause tracking
+    lifecycle:
+      property: incidentStatus
+      options:
+        - { key: open, category: open }
+        - { key: investigating, category: active }
+        - { key: resolved, category: done }
     properties:
       - slug: severity
         label: Severity
@@ -1033,10 +1041,10 @@ profiles:
   # `issue` is a CORE kind: the pod seeds it on every pod (ensure-system-profiles.ts,
   # "an open bug or problem" → issue) with its ONE lifecycle `issueStatus`
   # (ensure-system-lifecycles.ts). Declared here to match the seed exactly, the way
-  # research-base declares `research`, so the Fix a bug playbook can name its
-  # statusProperty. Pod-local extras (severity, night-shift-run) are not core: not here.
+  # research-base declares `research`, so the Fix a bug playbook follows its
+  # lifecycle. Pod-local extras (severity, night-shift-run) are not core: not here.
   # ONE deviation from the seed: `wont_fix` is humanOnly (a person decides an issue
-  # is not worth fixing), which the playbook's humanOnlyStatuses below requires.
+  # is not worth fixing).
   - slug: issue
     displayName: Issue
     icon: bug
@@ -1062,6 +1070,77 @@ profiles:
         inputType: textarea
         constraints: { maxLength: 5000 }
 
+  # A problem with our own product or process, worked by "Fix a finding" below.
+  # Declared as the founder's pod holds it (pod-local profile 0f1eb707, founder
+  # decision on card catalog-home, session 7416a988, 7 Nov 2026): pod-wide rows,
+  # so a finding filed from any space is one list. Property slugs are the live
+  # ones (`supersededby` included) so a reconcile onto that pod adds nothing. Two
+  # differences, both from the catalog's coverage rules: `wont_fix` and
+  # `superseded` are humanOnly (an agent's move into a lost option proposes
+  # anyway), and the unlabelled legacy `ek-claim` is left out. Not research-base's `finding` (a validated fact with a claim and a
+  # confidence): that slug clash is plan b38e5e64 decision 5, a rename of the
+  # Research kind that waits on a data conversion.
+  - slug: finding
+    displayName: Finding
+    icon: bug
+    color: "#F97316"
+    description: A problem report or feedback item, with a severity, raised against our own product or process. Moves open → fixing → fixed → verified, or won't fix / superseded.
+    scope: shared
+    entityScope: pod
+    profileKind: kind
+    lifecycle:
+      property: status
+      options:
+        - { key: open, category: open }
+        - { key: fixing, category: active }
+        - { key: fixed, category: done }
+        - { key: verified, category: done }
+        - { key: wont_fix, category: lost, humanOnly: true }
+        - { key: superseded, category: lost, humanOnly: true }
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [open, fixing, fixed, verified, wont_fix, superseded]
+        constraints: { defaultValue: open }
+      - slug: severity
+        label: Severity
+        valueType: string
+        inputType: select
+        enumValues: [low, medium, high, critical]
+      - slug: area
+        label: Product area
+        valueType: string
+        inputType: text
+        description: "Where it hurts: pod, mcp, bridge, cli, relay, browser, pod-admin, control-plane, governance, infra, process."
+      - slug: evidence
+        label: Evidence
+        valueType: string
+        inputType: textarea
+        constraints: { maxLength: 2000 }
+        description: Proposal, session, file:line, log line or URL that shows it.
+      - slug: summary
+        label: Summary
+        valueType: string
+        inputType: text
+        constraints: { maxLength: 500 }
+      - slug: description
+        label: Description
+        valueType: string
+        inputType: textarea
+        constraints: { maxLength: 5000 }
+      - slug: content
+        label: Content
+        valueType: string
+        inputType: textarea
+        constraints: { maxLength: 50000 }
+      - slug: supersededby
+        label: Superseded by
+        valueType: entity_id
+        inputType: entity_select
+        description: "The record that replaced this finding: the canonical finding it duplicates, or the correct diagnosis when this one was wrong. Recall leaves a superseded finding out."
+
   - slug: skill
     displayName: Skill
     icon: zap
@@ -1226,6 +1305,13 @@ profiles:
     icon: workflow
     color: blue
     description: A user flow or business process — a sequence of steps through system components
+    lifecycle:
+      property: workflowStatus
+      options:
+        - { key: documented, category: open }
+        - { key: in-progress, category: active }
+        - { key: needs-review, category: active }
+        - { key: complete, category: done }
     properties:
       - slug: workflowStatus
         label: Status
@@ -1446,9 +1532,40 @@ views:
     slug: task-board
     type: kanban
     scopeProfileSlug: task
-    groupBy: task-status
+    config:
+      groupByField: task-status
     defaultView: true
     description: "All delegated tasks by status: Backlog → Queued → Running → Review → Done."
+  # The flow boards (One model §8 item 3): each produced kind on a board grouped
+  # by its lifecycle — columns are its states, a drag is the governed status move.
+  - name: Feature Board
+    slug: feature-board
+    type: kanban
+    scopeProfileSlug: devplane_feature
+    description: Features by stage, Idea to Shipped.
+    config:
+      groupByField: featureStatus
+  - name: Story Board
+    slug: story-board
+    type: kanban
+    scopeProfileSlug: devplane_story
+    description: User stories by status, Draft to Done.
+    config:
+      groupByField: storyStatus
+  - name: Issue Board
+    slug: issue-board
+    type: kanban
+    scopeProfileSlug: issue
+    description: Bugs and problems by status, Open to Fixed.
+    config:
+      groupByField: issueStatus
+  - name: Design Board
+    slug: design-board
+    type: kanban
+    scopeProfileSlug: ui-design
+    description: Designs by status, from draft to implemented.
+    config:
+      groupByField: design-status
   - name: Deployments
     type: calendar
     scopeProfileSlug: devplane_deployment
@@ -1476,13 +1593,15 @@ views:
     slug: service-health
     type: kanban
     scopeProfileSlug: devplane_service
-    groupBy: serviceStatus
+    config:
+      groupByField: serviceStatus
     description: Every service by health — healthy, degraded, down, maintenance.
   - name: Services by Type
     slug: services-by-type
     type: kanban
     scopeProfileSlug: devplane_service
-    groupBy: serviceType
+    config:
+      groupByField: serviceType
     description: Services grouped by what they are — API, worker, cron, database, cache, queue.
   - name: Deploy Timeline
     slug: deploy-timeline
@@ -1617,10 +1736,8 @@ playbooks:
       (update_entity with expectedStatus); never invent a status.
     subjectProfile:
       profileSlug: ui-design
-      statusProperty: design-status
     # No stage owns these: `approved` and `archived` are a person's call
     # (humanOnly on the lifecycle).
-    humanOnlyStatuses: [approved, archived]
     activators:
       - { on: manual, mode: propose }
     params:
@@ -1928,8 +2045,7 @@ playbooks:
   # THE DEV LOOP AS STORED CONFIG (plan v5 T2, 2026-10-27). One change = one
   # session on its feature: shaped → building → PR opened → checks green →
   # merged → deployed to lab → dogfooded → criteria verified. It FOLLOWS the
-  # feature's declared lifecycle (`featureStatus`, named as statusProperty, no
-  # second status): Shape writes spec, Build in_progress, PR opened in_review,
+  # feature's declared lifecycle (`featureStatus`, no second status): Shape writes spec, Build in_progress, PR opened in_review,
   # Verify done (an agent's move into done proposes). The stages after PR
   # opened carry no status — the feature stays In review until it ships.
   #
@@ -1974,10 +2090,8 @@ playbooks:
       NEEDS-DOGFOOD.
     subjectProfile:
       profileSlug: devplane_feature
-      statusProperty: featureStatus
     # No stage owns these: Idea is before the change is shaped, Dropped is a
     # person's call (humanOnly on the lifecycle).
-    humanOnlyStatuses: [backlog, cancelled]
     activators:
       - { on: enters_status, status: spec, mode: propose, maxPendingApprovals: 5 }
       - { on: manual, mode: propose }
@@ -2121,24 +2235,18 @@ playbooks:
   # THE SIX DEV PLAYBOOKS (decision d05, founder instruction 2026-11-05): Build a
   # change, Fix a bug, Investigate, Review a change, Maintain, Fix main red.
   # Mirrored field by field from the six draft playbook proposals filed on the Builder
-  # pod (stored shape; humanOnlyStatuses lifted to the top-level wire spelling).
+  # pod (stored shape). No end moves (decision of 6 Nov 2026): a cancelled or failed
+  # session leaves its subject where it is.
   # ALL `status: draft` and NO activators: a pod keeps its own draft/active
   # choice on later template updates, and a person turns each on.
 
   # --- Build a change ---
   - name: Build a change
-    description: 'Dev set (decision d05), key: build. Works one feature (devplane_feature) from shaped criteria to a verified change on main; its stages follow the feature''s lifecycle (spec, in_progress, in_review, done), and a cancelled or failed session puts the feature back to spec so nothing is left half-claimed. One feature per session, never two subjects (founder default, 2026-11-05). A quick change is this playbook with size small (no plan); a night shift run is this playbook with unattended true. No activators until binding is turned on; the shape would be {on: enters_status, status: spec, size: per_thing, mode: propose}, the trigger Ship a change uses today. Reuses Ship a change (2c5aa553) stage text and evidence keys; absorbs AI Dev Session and Quick change once they are re-pointed. Draft until the founder activates it.'
+    description: 'Dev set (decision d05), key: build. Works one feature (devplane_feature) from shaped criteria to a verified change on main; its stages follow the feature''s lifecycle (spec, in_progress, in_review, done); a cancelled or failed session leaves the feature where it is. One feature per session, never two subjects (founder default, 2026-11-05). A quick change is this playbook with size small (no plan); a night shift run is this playbook with unattended true. No activators until binding is turned on; the shape would be {on: enters_status, status: spec, size: per_thing, mode: propose}, the trigger Ship a change uses today. Reuses Ship a change (2c5aa553) stage text and evidence keys; absorbs AI Dev Session and Quick change once they are re-pointed. Draft until the founder activates it.'
     goalTemplate: 'Build {feature} through one session and one PR per repo (or gated commits on main in a private repo), size {size}. SHAPE: write the end state and 2-5 binary criteria on this session (plan skill, skipped when size is small). BUILD: branch <type>/<slug> from origin/main in your own worktree, commit in verified slices, run the smallest gate that answers with its negative control, quote the output. LAND: follow the land stages (Change proposed, Checks green, Landed on main, Deployed to lab, Dogfooded, Criteria verified). Unattended: {unattended}. When unattended is true, ask no person, stop at a draft PR or a gated branch, never merge, push main or deploy, and post one "Look at first:" paragraph in the room.'
     scope: session
     subjectProfile:
-      onEnd:
-        failed: spec
-        cancelled: spec
       profileSlug: devplane_feature
-      statusProperty: featureStatus
-    humanOnlyStatuses:
-    - backlog
-    - cancelled
     params:
     - name: feature
       type: entity
@@ -2293,21 +2401,11 @@ playbooks:
 
   # --- Fix a bug ---
   - name: Fix a bug
-    description: 'Dev set (decision d05), key: fix. Works an issue at its root: reproduce it with a failing test, fix the canonical path, a clean-context review, then the shared land stages. Its stages follow the issue''s lifecycle (open, investigating, fixed); a cancelled or failed session puts the issue back to open, as Fix a finding does. Small fixes may be batched (founder default, 2026-11-05): several issues in one session, one as the subject and the rest as session targets; today a stage moves only the subject, and the session end moves the subject and every target still open. No activators until binding is turned on; a batch would be {on: count, status: open, min: 3} or {on: schedule, cron, status: open} (both one session per moment). A night shift run is this playbook with unattended true. Reuses Bugfix (8c335e2e), Night shift: build an issue (c101dd75) and Ship a change (2c5aa553). Draft until the founder activates it.'
+    description: 'Dev set (decision d05), key: fix. Works an issue at its root: reproduce it with a failing test, fix the canonical path, a clean-context review, then the shared land stages. Its stages follow the issue''s lifecycle (open, investigating, fixed); a cancelled or failed session leaves the issue where it is, as Fix a finding does. Small fixes may be batched (founder default, 2026-11-05): several issues in one session, one as the subject and the rest as session targets; today a stage moves only the subject. No activators until binding is turned on; a batch would be {on: count, status: open, min: 3} or {on: schedule, cron, status: open} (both one session per moment). A night shift run is this playbook with unattended true. Reuses Bugfix (8c335e2e), Night shift: build an issue (c101dd75) and Ship a change (2c5aa553). Draft until the founder activates it.'
     goalTemplate: 'Fix the issue {issue} at its root and prove it with a test that fails before the fix and passes after. REPRODUCE (recall first, smallest reproduction, root cause file:line), FIX on the canonical path in your own worktree, a clean-context REVIEW, then LAND through the shared land stages (Change proposed, Checks green, Landed on main, Deployed to lab, Dogfooded, Criteria verified). Unattended: {unattended}. When unattended is true, ask no person, stop at a draft PR or a gated branch, never merge, push main or deploy; if no code fix is right, write the root cause as a pod document; post one "Look at first:" paragraph in the room.'
     scope: session
     subjectProfile:
-      onEnd:
-        failed: open
-        cancelled: open
       profileSlug: issue
-      statusProperty: issueStatus
-    # Added to the pod draft (it has none; the catalog's lifecycle-coverage check
-    # needs every option owned): `open` is where an issue starts and a failed or
-    # cancelled session returns it (onEnd), `wont_fix` is a person's call.
-    humanOnlyStatuses:
-      - open
-      - wont_fix
     params:
     - name: issue
       type: entity
@@ -2853,6 +2951,38 @@ playbooks:
         statement: Every criterion of the session is graded with its evidence, and nothing unverified is reported as verified.
       description: 'Shared land stage. Never report unverified work as verified. File the lesson, decision or finding the work produced (engineering-memory skill, rule dogfood-journal). Close what you opened: asks answered or withdrawn, worktree removed once merged, then synap_complete_session. Tools: synap_update_session, synap_capture, synap_complete_session. Gate: none. Model tier: quick (advisory until a tier field exists).'
 
+  # Founder's pod playbook 18abd1ea, as it runs since 6 Nov 2026: no onEnd
+  # (decision f06dc507: a cancelled or failed session leaves its finding where it
+  # is); it follows the kind's lifecycle (backend#853).
+  # The two pod automations that move it (PR merged → merged, deployed →
+  # verified) are not shipped: their session_update step scopes on
+  # `whenPlaybookId`, a pod uuid, and there is no catalog-stable reference yet.
+  - name: Fix a finding
+    description: "Work one finding (a problem with Synap itself) until its fix is live. The session's stages move the finding: fixing while the work runs, fixed when the fix is merged, verified once it runs on the pod. A cancelled or failed session leaves the finding where it is."
+    goalTemplate: Fix the finding and see the fix live
+    scope: session
+    subjectProfile:
+      profileSlug: finding
+    params: []
+    executor: is-agent
+    status: active
+    stages:
+    - key: fix
+      name: Fix it
+      goal: Find the root cause and ship the fix as a gated PR or commit
+      category: started
+      subjectStatus: fixing
+    - key: merged
+      name: Fix merged
+      goal: The fix is on main (a merged PR or a gated commit)
+      category: started
+      subjectStatus: fixed
+    - key: verified
+      name: Live and verified
+      goal: The fix runs on the pod (its build contains the fix) and the finding no longer happens
+      category: completed
+      subjectStatus: verified
+
 onboarding:
   goal: Capture the real engineering surface — the apps that are shipped, where their code lives, what runs behind them, where they deploy, and what's in flight — so the workspace mirrors what the team actually builds and runs, not a generic template.
   framing: >

package/src/business-model.yaml

@@ -76,6 +76,15 @@ profiles:
     displayName: Question
     icon: help-circle
     profileKind: kind
+    # 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
@@ -91,6 +100,15 @@ profiles:
     displayName: Decision
     icon: gavel
     profileKind: kind
+    # 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: decisionStatus
         label: Status
@@ -312,7 +330,8 @@ views:
     slug: business-model-open-questions
     type: kanban
     scopeProfileSlug: question
-    groupBy: questionStatus
+    config:
+      groupByField: questionStatus
     description: The nine component questions and everything they spawned, by status.
 
 # ── Seeds: the interrogation, not fake data ────────────────────────────────

package/src/civic-france.yaml

@@ -39,6 +39,15 @@ profiles:
     icon: help-circle
     color: blue
     description: An open question driving a civic-data investigation.
+    # 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

package/src/content-creation.yaml

@@ -115,7 +115,7 @@ views:
     scopeProfileSlug: content-program
     description: Programs grouped by status — a running scoreboard for the content operation.
     config:
-      groupBy: status
+      groupByField: status
 
 onboarding:
   goal: >

package/src/content-os.yaml

@@ -28,7 +28,6 @@ meta:
     label: Content
     promise: Every post from idea to published, on one calendar.
     suggestFor: [writer, creator, marketer, musician, photographer]
-    profile: post
     views: [content-posts, content-calendar]
     example:
       - { title: "Why we left spreadsheets", values: { post-status: Idea, post-format: Article } }
@@ -46,6 +45,8 @@ meta:
   # What this space PRODUCES (homes): the purpose word, then its kinds/roles.
   intent:
     label: Content
+    # The ONE primary output (One model decision 3): a published post is what the editorial flow produces (Produce Content).
+    primary: post
     produces:
       - profile: post
       - profile: newsletter
@@ -713,6 +714,13 @@ profiles:
     color: "#0EA5E9"
     description: "An ordered run of posts that teaches one thing end to end — the curriculum axis of the content engine."
     scope: WORKSPACE
+    lifecycle:
+      property: series-status
+      options:
+        - { key: Planned, category: open }
+        - { key: Running, category: active }
+        - { key: Complete, category: done }
+        - { key: Abandoned, category: lost }
     properties:
       - slug: series-status
         label: Status
@@ -1551,7 +1559,8 @@ views:
     slug: content-posts
     type: kanban
     scopeProfileSlug: post
-    groupBy: post-status
+    config:
+      groupByField: post-status
     description: Content posts by status.
   # The editorial calendar — the "it lands on a calendar" promise. Posts render
   # on a month grid keyed on their Publish Date. The calendar renderer resolves
@@ -1600,7 +1609,8 @@ views:
     slug: content-newsletters
     type: kanban
     scopeProfileSlug: newsletter
-    groupBy: newsletter-status
+    config:
+      groupByField: newsletter-status
     description: Newsletter issues by status.
   # ⚠️ NO `Journey Board` (matrix) view here — DELIBERATE, do not "restore" it.
   # A coverage grid is the right idea and this is the wrong substrate today:
@@ -1806,15 +1816,15 @@ entityLinks:
 # `subjectProfile` binds a playbook to a kind so the Capture → Session matcher
 # (playbooks.subject_profile->>'profileSlug') can offer it when one is captured.
 #
-# THE PROCESS CONTRACT (lifecycle-bound playbooks). `subjectProfile.statusProperty`
-# names the kind's lifecycle select (`post-status`); each stage's `subjectStatus`
-# is the value that stage IS — advancing into the stage writes it to the subject
-# (governed), and the subject entering it advances an open run to the stage.
-# `humanOnlyStatuses` lists the values no stage owns because a person sets them.
+# THE PROCESS CONTRACT (lifecycle-bound playbooks). A playbook FOLLOWS the kind's
+# declared lifecycle (`post-status`); each stage's `subjectStatus` is the value
+# that stage IS — advancing into the stage writes it to the subject (governed),
+# and the subject entering it advances an open run to the stage. A value no stage
+# owns is derived by the pod; a person-only value is `humanOnly` on the lifecycle.
 # `activators` are DECLARATIONS the pod compiles into governed propose-mode rules
 # at install — never hand-written `automations:`. `relationToSubject` is the edge
 # written output → subject when a slot is satisfied. Validated by validate.ts
-# (`checkProcessContract`) and lifecycle-coverage.test.ts.
+# (`checkProcessContract`).
 playbooks:
   - name: Produce Content
     # ONE playbook for every format (plan W3.3): text / visual / video are
@@ -1868,10 +1878,8 @@ playbooks:
       by a person at Publish.
     subjectProfile:
       profileSlug: post
-      statusProperty: post-status
     # Idea is where a capture lands and Archived is a person's call — no stage
     # owns either. The activator below starts the run once the post is Briefed.
-    humanOnlyStatuses: [Idea, Archived]
     activators:
       - { on: enters_status, status: Briefed, mode: propose }
     params:
@@ -2158,8 +2166,7 @@ playbooks:
 
   # One take, several videos (D2, D3, 29 Oct). The take is a content-asset of
   # Kind recording; it has no lifecycle (its state is derived from what was
-  # made from it), so this process declares no statusProperty and its stages
-  # move no status. The person decides at Keep, through one question per
+  # made from it), so its stages move no status. The person decides at Keep, through one question per
   # proposed piece (a slot ask: the door Content Studio and Relay answer), not
   # a stage gate: keeping a piece commits nothing outside the pod, and the raw
   # take is never touched. The per-piece slots are declared by the agent as
@@ -2321,8 +2328,8 @@ playbooks:
   # never one run per post (a subject-bound playbook's `schedule:` field fans
   # out per entity; an activator's `schedule` and a per_moment `manual` do
   # not: api `run-playbook.ts` runWorkerBatch). The `subjectProfile` names the
-  # kind those workers read; there are no stages and no `statusProperty`, so it
-  # never moves a post's status.
+  # kind those workers read; there are no stages, so it never moves a post's
+  # status.
   # Run by hand ("Re-plan" on Content Studio's calendar, or the pod's button)
   # and once a week (founder, report 22fec5ee §6, 3 Nov 2026). The weekly one
   # compiles to a governed rule the owner can pause on the pod; both propose
@@ -2455,7 +2462,6 @@ playbooks:
       and link it derived_from the original. Never republish the original as is.
     subjectProfile:
       profileSlug: post
-      statusProperty: post-status
     activators:
       # A copy or repost sent for another account (post-copy-of) is not repurposed: its original is.
       - { on: enters_status, status: Published, mode: propose, unless: { property: post-copy-of, present: true } }
@@ -2480,8 +2486,6 @@ playbooks:
       a person confirms it went out.
     subjectProfile:
       profileSlug: newsletter
-      statusProperty: newsletter-status
-    humanOnlyStatuses: [Archived]
     params:
       - { name: newsletter, type: entity, label: Newsletter issue, required: true }
     executor: is-agent

package/src/crm-absorbs-outreach.template.test.ts

@@ -114,7 +114,7 @@ describe("CRM absorbs Outreach & Comms", () => {
     expect((reply.stages ?? []).map((s) => s.subjectStatus).filter(Boolean)).toEqual(["replied", "bounced", "no_response"]);
 
     const outreach = playbookOf("Personalized Outreach");
-    expect(outreach.subjectProfile).toMatchObject({ profileSlug: "campaign", statusProperty: "campaign-status" });
+    expect(outreach.subjectProfile).toEqual({ profileSlug: "campaign" });
     expect(outputsOf(outreach)).toEqual([
       { kind: "messaging", label: "Proposed first messages", relationToSubject: "none" },
     ]);

package/src/crm-build-plan.template.test.ts

@@ -88,7 +88,7 @@ describe("CRM build plan — catalog changes", () => {
 
   it("A6: one follow-up process drafts proposed messages on weekdays; no outreach process opens a deal", () => {
     const pb = playbookOf(crm, "Follow up on leads in outreach");
-    expect(pb.subjectProfile).toMatchObject({ profileSlug: "lead", statusProperty: "leadStage" });
+    expect(pb.subjectProfile).toEqual({ profileSlug: "lead" });
     expect(pb.activators).toContainEqual({ on: "schedule", cron: "0 7 * * 1-5", status: "outreach", mode: "propose" });
     expect(outputsOf(pb).map((o) => o.kind)).toEqual(["messaging"]);
     expect(pb.stages?.at(-1)).toMatchObject({ key: "send", gate: { kind: "human" } });