@synap-core/workspace-templates 0.10.0 → 0.11.0

package/dist/index.js

@@ -2,7 +2,11 @@
 var PACKAGE_DEPENDENCY_KINDS = [
   "workspace",
   "capability",
-  /** @deprecated Retired by CP 0049 in favour of `workflow`. See note above. */
+  "skill",
+  "workflow",
+  "view",
+  "cell",
+  /** @deprecated Legacy alias for `workflow` (CP 0049). Still accepted on the wire. */
   "automation"
 ];
 
@@ -3206,7 +3210,7 @@ var DATA = {
                 "inputMapping": {
                   "system": 'You are the ANALYST round of a Synap workspace report.\nRead the gathered workspace data and say what it MEANS: volume and shape of work,\nwhat is in flight versus stalled, what is well-covered versus thin.\nWork from the FIELDS on each record, not just its name: status, priority and\ndue dates are what distinguish moving work from stalled work, and an unset\nfield is itself worth reporting. Listing or counting what exists is NOT a\nfinding \u2014 say what the state of it means.\nDATA INTEGRITY CHECK \u2014 do this BEFORE interpreting anything. Each kind below states how many records were found, then lists them. If a kind reports a count greater than zero but its list is empty, null, or made of nulls, then the data pipeline is BROKEN \u2014 the records exist and were lost in transit. In that case you MUST say so plainly, name every kind affected, and NOT describe the workspace as empty, quiet, or sparse. Reporting a populated workspace as empty because its data failed to arrive is the single worst outcome of this report. A count of zero with an empty list is genuinely empty and is fine to report as such.\nYou are interpreting data you did NOT collect. Every claim must trace to a row in the GATHERED DATA below. Never invent entities, ids, counts, or dates. A step whose value looks like {"error": "..."} FAILED \u2014 treat that kind as unavailable and say so; do not guess what it would have contained.\nEVERY NUMBER YOU WRITE MUST BE COPIED FROM THE COUNTS BLOCK. That block states the exact number of records gathered for each kind \u2014 it is the ONLY source of quantities you have. Do not count the listed lines yourself, do not estimate, do not round, and do not write a quantity the block does not measure. Write digits, matching the block exactly: if it says 25, write "25" \u2014 never "23", never "about two dozen", never "Ten". If a point you want to make needs a number the COUNTS block does not give you, make the point WITHOUT a number. A claim with no figure is honest; a figure that does not match the data is the one error a reader cannot catch.\nNEVER NARRATE YOUR OWN INSTRUCTIONS. The reader sees your output and nothing else \u2014 not this prompt, not the steer, not the counts, not the fact that a pipeline produced any of it. Never mention the STEER, the time window, the COUNTS block, the GATHERED DATA, the rounds, or what you were or were not given. Never write a sentence like "the steer lines are empty, so\u2026" or "no focus was provided" or "based on the gathered data". TWO DEFAULTS, so you never need to remark on them: an EMPTY STEER line simply means write a broad general report covering the gathered kinds evenly, and an EMPTY time window simply means the records span the whole workspace history. Both are the normal case. Act on them silently and start with what you found.\nSTEER HANDLING \u2014 non-negotiable. If every STEER line is empty, produce a BROAD general read covering all the gathered kinds evenly. If any STEER line has text, treat it as the SUBJECT of this report: lead with the evidence that matches it, explicitly name what you set aside, and if the gathered data cannot support the steer, say so in one sentence instead of inventing material. Never restate the steer back as a heading; let it change what you actually write.\nLINK THE RECORDS YOU NAME. Every line of GATHERED DATA is `<id> \xB7 <title>`. When you name one of those records, write it as [[entity:<id>|<label>]] and it renders as a chip the reader can click to open that record. Rules, in order of importance: (1) The kind word is always `entity` \u2014 for tasks, notes, people AND companies alike. They are all entities, and any other kind word renders a chip that does not open. (2) Use only an id that appears VERBATIM in the gathered data. Copy it; never construct, shorten, complete or guess one. (3) If you are unsure of an id, write the plain label with no brackets. A wrong id is a dead chip, and a dead chip is worse than plain text. (4) The label is free text but must not contain `]`; the id must not contain `:` or `|`. A marker breaking either rule renders as raw literal text. (5) EVERY record you name in prose MUST carry a chip on its FIRST mention \u2014 this is what makes a named record a live object the reader can open rather than a string. Link it once, on that first mention only; repeating the chip every time is decoration, not navigation.\nOutput PLAIN PROSE \u2014 short paragraphs and bullets, with [[entity:\u2026]] chips\ninline wherever you name a record. No markdown headings, no ::: directive\nblocks, no code fences. Under 300 words. Another round will format this.',
                   "prompt": 'STEER:\n- Prompt: {{trigger.payload.prompt}}\n- Focus: {{trigger.payload.focus}}\n- Project lens id: {{trigger.payload.projectId}}\n\nCOUNTS \u2014 the exact number of records gathered for each kind. These figures\nare measured, not estimated, and they are the ONLY quantities available to\nyou. Each line also gives the cap the gather was limited to.\n- Tasks: {{steps.gather-tasks.output.count}} gathered (cap 25)\n- Notes: {{steps.gather-notes.output.count}} gathered (cap 15)\n- People: {{steps.gather-people.output.count}} gathered (cap 15)\n- Companies: {{steps.gather-companies.output.count}} gathered (cap 15)\nREADING A COUNT AGAINST ITS CAP: a count BELOW the cap means every record of\nthat kind is listed below \u2014 the set is COMPLETE and you may describe it as\nsuch. A count EQUAL to the cap means the gather stopped at the cap and more\nrecords exist that you cannot see \u2014 describe that kind as "at least N" and\nnever as complete, and never claim something does not exist merely because\nit is absent from the list.\n\nTime window: only records updated on or after {{trigger.payload.since}}\n\nGATHERED DATA \u2014 one line per record, MOST RECENTLY UPDATED first. Each line\nis `<id> \xB7 <title>` followed by ` \xB7 <field>=<value>` pairs carrying that\nrecord\'s real state. An EMPTY value means the field is not set on that\nrecord \u2014 that is a fact you may report (an unset status or a missing due\ndate is a finding), and never a value to guess at. Recent does not mean\nimportant.\nTasks \u2014 {{steps.gather-tasks.output.count}} found: {{steps.project-tasks.output.result}}\nNotes \u2014 {{steps.gather-notes.output.count}} found: {{steps.project-notes.output.result}}\nPeople \u2014 {{steps.gather-people.output.count}} found: {{steps.project-people.output.result}}\nCompanies \u2014 {{steps.gather-companies.output.count}} found: {{steps.project-companies.output.result}}',
-                  "maxTokens": "700"
+                  "maxTokens": "2000"
                 },
                 "errorHandling": {
                   "continueOnError": true
@@ -3227,7 +3231,7 @@ var DATA = {
                 "inputMapping": {
                   "system": 'You are the PATTERNS round of a Synap workspace report.\nYou receive the raw gathered data AND the analyst\'s read of it. Your job is what\nthe analyst did NOT do: surface RELATIONSHIPS and things worth attention \u2014\nclusters, repeated themes, people or companies that recur across kinds, gaps\nwhere a kind is conspicuously empty, and anything that looks like it needs a\ndecision. Prefer three sharp observations over ten shallow ones.\nYOUR SCOPE IS WHAT CONNECTS RECORDS, not what they individually are. Every\nobservation you write must involve TWO OR MORE records, or TWO OR MORE kinds:\na name that appears in both a task and a company, work clustered on one\nperson, a due date that lines up with an event, a kind that is empty while a\nrelated kind is busy. Do NOT re-describe volume, status distribution or how\nbusy the workspace is \u2014 that is the analyst\'s section and repeating it makes\nyours redundant. Do not summarise or restate the analyst\'s read.\nNEVER RETURN AN EMPTY ANSWER. If you genuinely find no cross-kind pattern,\nwrite one or two sentences naming what you looked for and did not find (for\nexample: no person recurs across the tasks and companies gathered). That is a\nreal finding and the reader needs it. Silence is not an available outcome.\nDATA INTEGRITY CHECK \u2014 do this BEFORE interpreting anything. Each kind below states how many records were found, then lists them. If a kind reports a count greater than zero but its list is empty, null, or made of nulls, then the data pipeline is BROKEN \u2014 the records exist and were lost in transit. In that case you MUST say so plainly, name every kind affected, and NOT describe the workspace as empty, quiet, or sparse. Reporting a populated workspace as empty because its data failed to arrive is the single worst outcome of this report. A count of zero with an empty list is genuinely empty and is fine to report as such.\nYou are interpreting data you did NOT collect. Every claim must trace to a row in the GATHERED DATA below. Never invent entities, ids, counts, or dates. A step whose value looks like {"error": "..."} FAILED \u2014 treat that kind as unavailable and say so; do not guess what it would have contained.\nEVERY NUMBER YOU WRITE MUST BE COPIED FROM THE COUNTS BLOCK. That block states the exact number of records gathered for each kind \u2014 it is the ONLY source of quantities you have. Do not count the listed lines yourself, do not estimate, do not round, and do not write a quantity the block does not measure. Write digits, matching the block exactly: if it says 25, write "25" \u2014 never "23", never "about two dozen", never "Ten". If a point you want to make needs a number the COUNTS block does not give you, make the point WITHOUT a number. A claim with no figure is honest; a figure that does not match the data is the one error a reader cannot catch.\nNEVER NARRATE YOUR OWN INSTRUCTIONS. The reader sees your output and nothing else \u2014 not this prompt, not the steer, not the counts, not the fact that a pipeline produced any of it. Never mention the STEER, the time window, the COUNTS block, the GATHERED DATA, the rounds, or what you were or were not given. Never write a sentence like "the steer lines are empty, so\u2026" or "no focus was provided" or "based on the gathered data". TWO DEFAULTS, so you never need to remark on them: an EMPTY STEER line simply means write a broad general report covering the gathered kinds evenly, and an EMPTY time window simply means the records span the whole workspace history. Both are the normal case. Act on them silently and start with what you found.\nSTEER HANDLING \u2014 non-negotiable. If every STEER line is empty, produce a BROAD general read covering all the gathered kinds evenly. If any STEER line has text, treat it as the SUBJECT of this report: lead with the evidence that matches it, explicitly name what you set aside, and if the gathered data cannot support the steer, say so in one sentence instead of inventing material. Never restate the steer back as a heading; let it change what you actually write.\nLINK THE RECORDS YOU NAME. Every line of GATHERED DATA is `<id> \xB7 <title>`. When you name one of those records, write it as [[entity:<id>|<label>]] and it renders as a chip the reader can click to open that record. Rules, in order of importance: (1) The kind word is always `entity` \u2014 for tasks, notes, people AND companies alike. They are all entities, and any other kind word renders a chip that does not open. (2) Use only an id that appears VERBATIM in the gathered data. Copy it; never construct, shorten, complete or guess one. (3) If you are unsure of an id, write the plain label with no brackets. A wrong id is a dead chip, and a dead chip is worse than plain text. (4) The label is free text but must not contain `]`; the id must not contain `:` or `|`. A marker breaking either rule renders as raw literal text. (5) EVERY record you name in prose MUST carry a chip on its FIRST mention \u2014 this is what makes a named record a live object the reader can open rather than a string. Link it once, on that first mention only; repeating the chip every time is decoration, not navigation.\nOutput PLAIN PROSE, under 250 words, with [[entity:\u2026]] chips inline. No\nheadings, no ::: directive blocks, no code fences.',
                   "prompt": "STEER:\n- Prompt: {{trigger.payload.prompt}}\n- Focus: {{trigger.payload.focus}}\n- Project lens id: {{trigger.payload.projectId}}\n\nCOUNTS \u2014 the exact number of records gathered for each kind. These figures\nare measured, not estimated, and they are the ONLY quantities available to\nyou. Each line also gives the cap the gather was limited to.\n- Tasks: {{steps.gather-tasks.output.count}} gathered (cap 25)\n- Notes: {{steps.gather-notes.output.count}} gathered (cap 15)\n- People: {{steps.gather-people.output.count}} gathered (cap 15)\n- Companies: {{steps.gather-companies.output.count}} gathered (cap 15)\nREADING A COUNT AGAINST ITS CAP: a count BELOW the cap means every record of\nthat kind is listed below \u2014 the set is COMPLETE and you may describe it as\nsuch. A count EQUAL to the cap means the gather stopped at the cap and more\nrecords exist that you cannot see \u2014 describe that kind as \"at least N\" and\nnever as complete, and never claim something does not exist merely because\nit is absent from the list.\n\nTime window: only records updated on or after {{trigger.payload.since}}\n\nGATHERED DATA \u2014 one line per record, MOST RECENTLY UPDATED first. Each line\nis `<id> \xB7 <title>` followed by ` \xB7 <field>=<value>` pairs carrying that\nrecord's real state. An EMPTY value means the field is not set on that\nrecord \u2014 that is a fact you may report (an unset status or a missing due\ndate is a finding), and never a value to guess at. Recent does not mean\nimportant.\nTasks \u2014 {{steps.gather-tasks.output.count}} found: {{steps.project-tasks.output.result}}\nNotes \u2014 {{steps.gather-notes.output.count}} found: {{steps.project-notes.output.result}}\nPeople \u2014 {{steps.gather-people.output.count}} found: {{steps.project-people.output.result}}\nCompanies \u2014 {{steps.gather-companies.output.count}} found: {{steps.project-companies.output.result}}\n\nANALYST'S READ \u2014 already written and already in the report. Do NOT\nrestate, summarise or re-analyse it. It is here so you do not repeat it:\n{{steps.analyze.output}}\n\nYOUR TASK \u2014 cross-kind patterns ONLY. Look for what connects the lists\nabove: a person who recurs in tasks and companies, work clustered on one\nname, due dates that line up, a kind that is empty while a related kind\nis busy, a company with people but no tasks. Write only observations\nthat span TWO OR MORE records or kinds. If there are none, say what you\nchecked and did not find \u2014 never answer with nothing.",
-                  "maxTokens": "700"
+                  "maxTokens": "2000"
                 },
                 "errorHandling": {
                   "continueOnError": true
@@ -3621,6 +3625,7 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "description": "A liquidity provider \u2014 makes markets and provides depth for a token.",
         "scope": "shared",
         "profileKind": "role",
+        "roleCategory": "provider",
         "applicableKinds": [
           "company",
           "person"
@@ -3666,6 +3671,7 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "description": "A security firm or individual that audits smart contracts and protocols.",
         "scope": "shared",
         "profileKind": "role",
+        "roleCategory": "provider",
         "applicableKinds": [
           "company",
           "person"
@@ -3711,6 +3717,7 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "description": "An outsourced engineering studio or build partner.",
         "scope": "shared",
         "profileKind": "role",
+        "roleCategory": "provider",
         "applicableKinds": [
           "company",
           "person"
@@ -3756,6 +3763,7 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "description": "A brand, growth, or content marketing agency.",
         "scope": "shared",
         "profileKind": "role",
+        "roleCategory": "provider",
         "applicableKinds": [
           "company",
           "person"
@@ -3801,6 +3809,7 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "description": "A performance / paid-media buying agency.",
         "scope": "shared",
         "profileKind": "role",
+        "roleCategory": "provider",
         "applicableKinds": [
           "company",
           "person"
@@ -3846,6 +3855,7 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "description": "A key opinion leader or influencer who amplifies reach.",
         "scope": "shared",
         "profileKind": "role",
+        "roleCategory": "provider",
         "applicableKinds": [
           "company",
           "person"
@@ -3882,6 +3892,100 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
             "inputType": "textarea"
           }
         ]
+      },
+      {
+        "slug": "grant-program",
+        "displayName": "Grant Program",
+        "icon": "landmark",
+        "color": "emerald",
+        "description": "A per-chain funding program (e.g. Stellar SCF, Optimism RetroPGF) \u2014 the long-lived funder above a round.",
+        "profileKind": "kind",
+        "entityScope": "pod",
+        "scope": "shared",
+        "properties": [
+          {
+            "slug": "blockchain",
+            "label": "Blockchain / Chain",
+            "valueType": "string",
+            "inputType": "text"
+          },
+          {
+            "slug": "programName",
+            "label": "Program Name",
+            "valueType": "string",
+            "inputType": "text"
+          },
+          {
+            "slug": "programType",
+            "label": "Program Type",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "direct",
+              "retroactive",
+              "quadratic",
+              "rfp"
+            ]
+          },
+          {
+            "slug": "status",
+            "label": "Status",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "active",
+              "paused",
+              "retired"
+            ]
+          },
+          {
+            "slug": "url",
+            "label": "Program URL",
+            "valueType": "string",
+            "inputType": "url"
+          },
+          {
+            "slug": "cadence",
+            "label": "Cadence",
+            "valueType": "string",
+            "inputType": "text",
+            "placeholder": "every 6 weeks"
+          },
+          {
+            "slug": "nextDeadline",
+            "label": "Next Deadline",
+            "valueType": "date",
+            "inputType": "date"
+          },
+          {
+            "slug": "submissionTracks",
+            "label": "Submission Tracks",
+            "valueType": "array",
+            "inputType": "text"
+          },
+          {
+            "slug": "trancheModel",
+            "label": "Tranche Model",
+            "valueType": "string",
+            "inputType": "text",
+            "placeholder": "4 tranches / 90 days"
+          },
+          {
+            "slug": "defaultPlaybook",
+            "label": "Default Playbook",
+            "valueType": "string",
+            "inputType": "text",
+            "constraints": {
+              "defaultValue": "Grant Process"
+            }
+          },
+          {
+            "slug": "description",
+            "label": "Description",
+            "valueType": "string",
+            "inputType": "textarea"
+          }
+        ]
       }
     ],
     "entityLinks": [
@@ -16222,6 +16326,12 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "kind": "workspace",
         "relation": "require",
         "reason": "Provides the pod-wide client / partner / sponsor role vocabulary this workspace reuses."
+      },
+      {
+        "slug": "blockchain-ecosystem",
+        "kind": "workspace",
+        "relation": "require",
+        "reason": "Provides the pod-wide grant-program kind (per-chain funding programs) this workspace's rounds belong to."
       }
     ],
     "workspace": {
@@ -17381,12 +17491,21 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
           "sortDir": "desc"
         }
       },
+      {
+        "name": "Deadlines",
+        "type": "calendar",
+        "scopeProfileSlug": "round",
+        "description": "Upcoming round submission deadlines, on one time axis.",
+        "config": {
+          "dateField": "properties.submissionDeadline",
+          "colorField": "status"
+        }
+      },
       {
         "name": "Awarded Projects",
         "type": "gallery",
         "scopeProfileSlug": "grant-project",
         "config": {
-          "coverField": "summary",
           "showFields": [
             "currentStatus",
             "awardedRoundCount",
@@ -17430,6 +17549,30 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "type": "submitted_by",
         "label": "Submitted By"
       },
+      {
+        "sourceProfileSlug": "grant_submission",
+        "targetProfileSlug": "contract",
+        "type": "for_contract",
+        "label": "Engagement"
+      },
+      {
+        "sourceProfileSlug": "grant_submission",
+        "targetProfileSlug": "deal",
+        "type": "billed_as",
+        "label": "Billed as"
+      },
+      {
+        "sourceProfileSlug": "round",
+        "targetProfileSlug": "grant-program",
+        "type": "belongs_to",
+        "label": "Program"
+      },
+      {
+        "sourceProfileSlug": "contract",
+        "targetProfileSlug": "grant-program",
+        "type": "pursues",
+        "label": "Pursues"
+      },
       {
         "sourceProfileSlug": "grant-project",
         "targetProfileSlug": "round",
@@ -17455,6 +17598,220 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "label": "Evidenced By"
       }
     ],
+    "playbooks": [
+      {
+        "name": "Grant Process",
+        "description": "Run an engagement through a grant program end to end \u2014 identify fit, draft the application, submit, track the decision, and deliver the tranches. Reads the program's own cadence / tracks / tranche model so one playbook fits every chain.",
+        "goalTemplate": "Advance this engagement ({contract}) through the grant program ({grantProgram}) it is pursuing. FIRST read the program entity's own data \u2014 its cadence, submissionTracks, trancheModel, and nextDeadline \u2014 plus the client context on the contract, and let THOSE drive the plan: do not assume a chain's mechanics, read them from the program. Then work the stages in order and keep the client's `grant_submission` card as the durable state of record:\n1. Identify \u2014 understand the project and which of the program's\n   submissionTracks fit; set the submission `stage` to `scope`.\n2. Draft \u2014 write the abstract, then the full proposal (products & services,\n   success criteria, GTM, traction); move `stage` `abstract` \u2192 `build` and\n   fill the submission's body fields.\n3. Submit \u2014 finalize against the program's nextDeadline and submit; once\n   submitted, set `stage` to `awaiting-results`.\n4. Awaiting \u2014 track the decision and keep `status` current\n   (in-review / waiting-client / needs-document / blocked).\n5. Awarded \u2014 on a decision, set `outcome` (awarded / rejected / partial)\n   and record the awarded amount.\n6. Delivering \u2014 for an award, work the program's trancheModel: fill the\n   tranche deliverables and update trancheCompletion as each milestone ships.\n\nNever fabricate \u2014 leave a field blank rather than guess. Every write is proposal-gated for the user to review.",
+        "subjectProfile": {
+          "profileSlug": "contract"
+        },
+        "params": [
+          {
+            "name": "contract",
+            "type": "entity",
+            "profileSlug": "contract",
+            "label": "Engagement",
+            "required": true
+          },
+          {
+            "name": "grantProgram",
+            "type": "entity",
+            "profileSlug": "grant-program",
+            "label": "Grant Program",
+            "required": true
+          }
+        ],
+        "stages": [
+          {
+            "key": "identify",
+            "name": "Identify",
+            "description": "Understand the project and which of the program's submission tracks fit \u2014 before any writing.",
+            "goal": "A clear project understanding and the fitting submission track; submission stage = scope."
+          },
+          {
+            "key": "draft",
+            "name": "Draft",
+            "description": "Write the abstract, then the full proposal, from the client's real material.",
+            "goal": "Abstract then full proposal drafted; submission stage abstract \u2192 build with body fields filled."
+          },
+          {
+            "key": "submit",
+            "name": "Submit",
+            "description": "Finalize against the program deadline and submit the application.",
+            "goal": "Application submitted on time; submission stage = awaiting-results."
+          },
+          {
+            "key": "awaiting",
+            "name": "Awaiting",
+            "description": "Track the decision and keep the client status current.",
+            "goal": "Submission status reflects where the decision stands (in-review / waiting-client / needs-document / blocked)."
+          },
+          {
+            "key": "awarded",
+            "name": "Awarded",
+            "description": "Record the funder's decision and the awarded amount.",
+            "goal": "Submission outcome set (awarded / rejected / partial) with the awarded amount."
+          },
+          {
+            "key": "delivering",
+            "name": "Delivering",
+            "description": "Work the program's tranche model \u2014 ship and record each tranche.",
+            "goal": "Tranche deliverables filled and trancheCompletion updated as milestones ship."
+          }
+        ],
+        "executor": "is-agent",
+        "grants": [
+          "entity.create"
+        ],
+        "status": "active"
+      }
+    ],
+    "automations": [
+      {
+        "key": "grant-submission-sync",
+        "name": "Grant Submission Sync",
+        "description": "Once a day, keep each grant application's grant_submission card current \u2014 read the submission's recent activity, assess where the pursuit stands, and advance its stage + status so the pipeline stays the durable, kanban-visible state of record.",
+        "triggerType": "cron",
+        "triggerConfig": {
+          "expression": "0 8 * * *"
+        },
+        "status": "draft",
+        "metadata": {
+          "templateKey": "grant-submission-sync"
+        },
+        "flow": {
+          "nodes": [
+            {
+              "id": "trigger",
+              "type": "trigger",
+              "position": {
+                "x": 0,
+                "y": 0
+              },
+              "data": {
+                "label": "Daily at 08:00",
+                "triggerType": "cron",
+                "config": {
+                  "expression": "0 8 * * *"
+                }
+              }
+            },
+            {
+              "id": "list-submissions",
+              "type": "capability",
+              "position": {
+                "x": 0,
+                "y": 120
+              },
+              "data": {
+                "label": "List grant submissions to maintain",
+                "verbId": "entity.query",
+                "inputMapping": {
+                  "profileSlug": "grant_submission",
+                  "limit": "100"
+                }
+              }
+            },
+            {
+              "id": "submissions-loop",
+              "type": "loop",
+              "position": {
+                "x": 0,
+                "y": 240
+              },
+              "data": {
+                "label": "For each grant submission",
+                "iteratorExpression": "steps.list-submissions.output.entities",
+                "itemVariable": "submission"
+              }
+            },
+            {
+              "id": "read-activity",
+              "type": "messages_query",
+              "position": {
+                "x": 0,
+                "y": 360
+              },
+              "data": {
+                "label": "Read the submission's recent activity",
+                "subjectEntityId": "{{loop.item.id}}",
+                "limit": 40
+              }
+            },
+            {
+              "id": "assess",
+              "type": "capability",
+              "position": {
+                "x": 0,
+                "y": 480
+              },
+              "data": {
+                "label": "Assess the submission's stage + status \u2192 JSON",
+                "verbId": "ai.generate",
+                "inputMapping": {
+                  "json": "true",
+                  "maxTokens": "500",
+                  "system": "You are a strict data-extraction function for a grants pipeline. Read a grant application's recent activity and report where the application currently stands. Respond with STRICT JSON and NOTHING else. Never fabricate \u2014 if the activity does not clearly indicate a value, keep the submission's current one.",
+                  "prompt": `The grant submission: {{loop.item.title}} Current stage: {{loop.item.properties.stage}} Current status: {{loop.item.properties.status}}
+Recent activity (oldest first): {{steps.read-activity.output.messages}}
+Report the submission's current state as STRICT JSON, using ONLY these vocabularies and NOTHING else: {
+  "stage": "scope|abstract|build|awaiting-results",
+  "status": "answered|waiting-client|needs-document|in-review|blocked"
+}`
+                }
+              }
+            },
+            {
+              "id": "advance-submission",
+              "type": "output",
+              "position": {
+                "x": 0,
+                "y": 600
+              },
+              "data": {
+                "label": "Advance the submission stage + status",
+                "outputType": "entity_update",
+                "config": {
+                  "entityId": "{{loop.item.id}}",
+                  "properties": {
+                    "stage": "{{steps.assess.output.stage}}",
+                    "status": "{{steps.assess.output.status}}"
+                  }
+                }
+              }
+            }
+          ],
+          "edges": [
+            {
+              "id": "gs-trigger-list",
+              "source": "trigger",
+              "target": "list-submissions"
+            },
+            {
+              "id": "gs-list-loop",
+              "source": "list-submissions",
+              "target": "submissions-loop"
+            },
+            {
+              "id": "gs-loop-read",
+              "source": "submissions-loop",
+              "target": "read-activity"
+            },
+            {
+              "id": "gs-read-assess",
+              "source": "read-activity",
+              "target": "assess"
+            },
+            {
+              "id": "gs-assess-advance",
+              "source": "assess",
+              "target": "advance-submission"
+            }
+          ]
+        }
+      }
+    ],
     "app": {
       "kind": "stored",
       "cellKey": "entity-detail"
@@ -24136,6 +24493,7 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
         "description": "A company or person that provides a capability The Arch can broker a client need against.",
         "scope": "shared",
         "profileKind": "role",
+        "roleCategory": "provider",
         "applicableKinds": [
           "company",
           "person"
@@ -24315,10 +24673,10 @@ document. No preamble, no explanation, no code fences around the whole thing.`,
                 "y": 240
               },
               "data": {
-                "label": "List the solution-provider roster",
+                "label": "List the provider roster (any roleCategory=provider)",
                 "verbId": "entity.query",
                 "inputMapping": {
-                  "profileSlug": "solution-provider",
+                  "roleCategory": "provider",
                   "limit": "100"
                 }
               }
@@ -29860,6 +30218,12 @@ counter-evidence: research that only kept what agreed with it isn't research.
         "kind": "workspace",
         "relation": "require",
         "reason": "The engineering / ops dashboard \u2014 the build-side view of the company."
+      },
+      {
+        "slug": "networking",
+        "kind": "workspace",
+        "relation": "require",
+        "reason": "The partner-intro layer \u2014 need \u2192 intro-matcher \u2192 intro \u2192 billed_as \u2192 deal, with the A\u2194B confidentiality firewall; the Stellar Client-Sync emits needs that depend on it."
       }
     ],
     "workspace": {
@@ -30077,7 +30441,8 @@ function rowToRemoteEntry(row, isPrivate) {
     domain: row.domain ?? void 0,
     tags: row.tags ?? [],
     icon: row.icon ?? null,
-    isPrivate
+    isPrivate,
+    items: row.items
     // Both list routes strip `definition`; absence ⇒ bundle wins a slug conflict,
     // and the install path fetches the full definition per-slug when needed.
   };
@@ -30113,6 +30478,8 @@ function bundledToEntry(tpl) {
     tags: tpl.meta.tags ?? [],
     icon: tpl.meta.icon,
     isPrivate: tpl.meta.isPublic === false,
+    // Bundled workspace templates carry no cells — be honest, not `undefined`.
+    items: [],
     template: tpl
   };
 }
@@ -30127,6 +30494,7 @@ function remoteToEntry(row) {
     tags: row.tags ?? [],
     icon: row.icon ?? null,
     isPrivate: row.isPrivate ?? false,
+    items: row.items ?? [],
     remote: row
   };
 }