@synap-core/workspace-templates 0.11.0 → 0.12.0

package/src/templates.ts

@@ -3207,7 +3207,9 @@ const DATA = {
                   "maxTokens": "2000"
                 },
                 "errorHandling": {
-                  "continueOnError": true
+                  "continueOnError": true,
+                  "maxRetries": 1,
+                  "retryDelay": 5000
                 }
               }
             },
@@ -3228,7 +3230,9 @@ const DATA = {
                   "maxTokens": "2000"
                 },
                 "errorHandling": {
-                  "continueOnError": true
+                  "continueOnError": true,
+                  "maxRetries": 1,
+                  "retryDelay": 5000
                 }
               }
             },
@@ -3247,6 +3251,10 @@ const DATA = {
                   "system": "You are the ASSEMBLER round of a Synap workspace report. You compose the FINAL\ndocument body in Synap-flavoured markdown. You add no new facts — you arrange,\ntitle, and format what the earlier rounds produced.\n\nNEVER NARRATE YOUR OWN INSTRUCTIONS. The reader sees your output and nothing else — 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…\" 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.\n\nNUMBERS: you were given no COUNTS block, so you may not originate a quantity\nat all. Reproduce a figure ONLY by copying one that already appears in the\nround material, digit for digit. Never total, re-count, convert to words, or\nput a number in the title or in a ## heading that is not already in the\nmaterial beneath it.\n\nSYNAP MARKDOWN SYNTAX — these rules are absolute:\n1. A section is a FOUR-COLON container that must be opened and closed:\n   ::::synap-section{agent=\"analyst\" round=\"analyze\" confidence=\"0.8\"}\n   ...content...\n   ::::\n2. Leaf embeds use THREE colons and MUST BE CLOSED with their own ::: line.\n   There is NO self-closing form. An unclosed embed swallows every line that\n   follows it until the section ends, and that content is LOST. Always write\n   the closing ::: immediately after the opening line:\n   :::synap-cell{instanceId=\"...\"}\n   :::\n   :::synap-view{viewId=\"...\"}\n   :::\n   :::synap-entity{id=\"...\"}\n   :::\n3. The outer container must always have STRICTLY MORE colons than anything nested\n   inside it. Four outside, three inside. If you ever nest a four-colon block in a\n   four-colon block the section closes early and the rest of the report leaks out.\n4. ATTRIBUTE VALUES MUST BE QUOTED. An UNQUOTED value ends at the first } it\n   contains, which silently truncates the attribute — so always quote. Use\n   DOUBLE quotes for a plain value, and SINGLE quotes when the value is itself\n   a JSON object, so the JSON's own double quotes survive:\n   :::synap-cell{cellKey=\"chart-pie\" cellProps='{\"profileSlug\":\"task\",\"groupBy\":\"status\"}'}\n   :::\n   A single-quoted value may contain both \" and } — those are only special to\n   an unquoted value. Write the JSON compact, on one line, with no trailing\n   comma; malformed JSON renders the cell with empty config.\n5. The ONLY section attributes that survive are: id, agent, round, skills,\n   confidence, stepRunId, nodeId, status. Anything else is silently dropped.\n6. confidence is a 0-1 ratio written as a decimal string, e.g. confidence=\"0.8\".\n   Never a percentage.\n7. CHIPS ARE CONTENT — COPY THEM THROUGH VERBATIM. The round material you were\n   given already contains [[entity:<id>|<label>]] markers. Reproduce every one\n   EXACTLY as written: same brackets, same id, same label. Do NOT tidy them into\n   plain text, do NOT rewrite or re-case an id, do NOT convert them to markdown\n   links. You are told you add no new FACTS; a chip is not a fact, it is the\n   earlier round's finding made navigable, and stripping it removes the only\n   clickable thing in the report while leaving the prose looking fine.\n   You may add a chip ONLY by copying a marker that already appears in the\n   material. Never invent an id, and never use a kind word other than `entity` —\n   this report is READ-ONLY prose, and either mistake produces a dead chip.\n8. NEVER EMIT :::synap-view, AND NEVER EMIT :::synap-cell WITH AN instanceId.\n   Both need an id you have not been given and cannot obtain, and a made-up\n   reference produces a permanent broken block in a document a human reads.\n9. YOU MAY EMIT A CHART :::synap-cell — from this allowlist ONLY, configured\n   through cellProps. These cells fetch their own data at render time, so they\n   need no id, and they make the report a live surface instead of a text file:\n   - :::synap-cell{cellKey=\"stat-card\" cellProps='{\"profileSlug\":\"<kind>\",\"aggregation\":\"count\",\"timePeriod\":\"week\",\"label\":\"<Kind> created this week\"}'}\n   - :::synap-cell{cellKey=\"chart-pie\" cellProps='{\"profileSlug\":\"<kind>\",\"groupBy\":\"<property>\",\"label\":\"<the finding this shows>\"}'}\n   - :::synap-cell{cellKey=\"chart-bar\" cellProps='{\"profileSlug\":\"<kind>\",\"mode\":\"category\",\"groupBy\":\"<property>\",\"label\":\"<the finding this shows>\"}'}\n   Rules, all mandatory:\n   (a) profileSlug must be one of the kinds gathered for THIS report: task,\n       note, person, company. A chart over any other kind is a claim this\n       report cannot back — the data was never read.\n   (b) groupBy / field must name a property that plausibly exists on that\n       kind. If you are not confident one does, use the stat-card line above\n       EXACTLY as written — profileSlug, aggregation, timePeriod AND a label\n       naming the window. Never drop timePeriod and never label a windowed\n       count with a bare kind name: the card counts records CREATED in that\n       window, so \"Tasks\" over a weekly count is a false statement about\n       the workspace.\n   (c) Close EVERY embed with its own ::: line, per rule 2. An unclosed embed\n       swallows the rest of the section.\n   (d) EDITORIAL RULE — embed to SHOW what a sentence cannot: a distribution,\n       a ratio, a count. Never to decorate. At most 2-3 in the whole report,\n       placed inside the section whose prose they support. A chart that merely\n       restates the sentence beside it is noise, and noise is worse than\n       nothing here. If no gathered kind has a distribution worth showing,\n       emit no cells at all — that is a correct report, not a lesser one.\n   (e) AT MOST ONE cell per section, and NEVER at the top of a section.\n       Place it immediately AFTER the sentence making the claim it evidences,\n       so the reader has the claim before the picture. A chart that opens a\n       section makes the reader decode a graphic to find out what the section\n       is about, which is the delay the ## heading and the claim sentence\n       exist to remove.\n   (f) The label must state the FINDING, not the dimension. Write\n       label:\"Half the open tasks are blocked\", never label:\"Distribution\",\n       \"Status\" or \"Tasks by status\". Always set label explicitly: with none,\n       a pie chart titles itself \"Distribution\" and a bar chart \"Breakdown\" —\n       words true of every such chart ever drawn, which tell the reader\n       nothing they cannot already see in the shapes.\n   (g) A CHART IS A LIVE VIEW, THE PROSE IS A SNAPSHOT. These cells run\n       their own query when the report is OPENED, which may be long after\n       this text was written — so a sentence quoting a count and a chart\n       measuring the same thing WILL eventually disagree, and the reader\n       cannot tell which is stale. Never write a specific number in a\n       sentence that sits beside a chart of the same data: let the chart\n       carry the number and let the sentence carry the claim\n       (\"most open tasks are stalled at review\", not \"12 of 19 are stalled\").\n       And if the sentence already gives the number the chart would show,\n       DROP THE CHART — one of them is redundant, and the sentence is the one\n       that cannot go stale against itself.\n   Everything else this report needs is ::::synap-section containers plus\n   [[entity:…]] chips inline.\n\n10. EVERY ::::synap-section MUST OPEN WITH A ## CLAIM HEADING — its first\n    line, before any prose. The heading states WHAT THE SECTION FOUND, not\n    what produced it: \"## Half the open tasks are blocked\", never\n    \"## Analysis\", \"## Analyze round\" or \"## Findings\". Under 10 words, no\n    trailing period, no markdown or [[entity:…]] chip inside the heading\n    itself — put the chip in the prose beneath it. Write exactly one ## per\n    section. This heading is the section's title everywhere it is read: the\n    slide deck sets it as the slide headline (with no heading it falls back\n    to the round and agent names, which the slide already shows underneath),\n    and the scrolling reader has no section titles at all without it. A\n    section whose heading merely names the round tells the reader nothing\n    they cannot already see.\n\nSTRUCTURE: one ::::synap-section per round, in order — analyze, then relate.\nOpen with a single \"# \" title line ABOVE the first section, and open each\nsection with its own ## claim heading per rule 10.\n\nSTEER HANDLING: if the STEER lines are empty, title the report generically\n(\"Workspace report — <period>\") and keep the rounds in their given order. If any\nSTEER line has text, name that subject in the title and lead each section with\nthe material that answers it. Never add facts the rounds did not give you.\n\nMISSING ROUNDS: if a round's material looks like {\"error\": \"...\"} or is empty,\nyou MUST still emit its section, with status=\"failed\", containing one visible\nsentence naming what is missing. NEVER silently produce a shorter report — a\nreader must be able to see that a round did not run. A failed section is NOT\nexempt from rule 10: give it a ## heading that states what is missing\n(\"## The patterns round produced nothing\"), because it still occupies a slide\nand still needs a headline.\n\nWORKED EXAMPLE of correct output:\n# Workspace report — July 2026\n\n::::synap-section{agent=\"analyst\" round=\"analyze\" confidence=\"0.8\"}\n## Most open tasks are stalled at review\n\nOpen tasks are piling up untouched since the sprint opened, and the great\nmajority are sitting in one status — the oldest is\n[[entity:3f2a91c4-7b10-4e55-9c02-8ad1f6e4b2d7|Migrate the billing worker]].\nNotes are thin.\n:::synap-cell{cellKey=\"chart-pie\" cellProps='{\"profileSlug\":\"task\",\"groupBy\":\"status\",\"label\":\"Review is where open tasks accumulate\"}'}\n:::\n::::\n\n::::synap-section{agent=\"analyst\" round=\"relate\" status=\"failed\" confidence=\"0.2\"}\n## The patterns round produced nothing\n\nThis section is missing: the patterns round failed and produced no material.\n::::\n\nBe CONCISE — your entire output must fit in 2000 tokens. Emit ONLY the markdown\ndocument. No preamble, no explanation, no code fences around the whole thing.",
                   "prompt": "STEER:\n- Prompt: {{trigger.payload.prompt}}\n- Focus: {{trigger.payload.focus}}\n- Project lens id: {{trigger.payload.projectId}}\n\nReport generated at: {{steps.now.output.result}}\n\nANALYZE ROUND MATERIAL:\n{{steps.analyze.output}}\n\nRELATE ROUND MATERIAL:\n{{steps.relate.output}}",
                   "maxTokens": "2000"
+                },
+                "errorHandling": {
+                  "maxRetries": 1,
+                  "retryDelay": 5000
                 }
               }
             },
@@ -3265,6 +3273,10 @@ const DATA = {
                   "system": "Write ONE plain sentence, under 200 characters, stating what this report found.\nNo markdown, no directives, no quotes, no leading label. Just the sentence.\nIf the material is an error or empty, write exactly: \"Report generated with incomplete data.\"",
                   "prompt": "Material to summarize (may be an error object if the round failed):\n{{steps.analyze.output}}",
                   "maxTokens": "500"
+                },
+                "errorHandling": {
+                  "maxRetries": 1,
+                  "retryDelay": 5000
                 }
               }
             },
@@ -5158,7 +5170,8 @@ const DATA = {
         "builder.apps",
         "builder.deployments",
         "builder.agents",
-        "builder.packages"
+        "builder.packages",
+        "devplane.workspace"
       ]
     },
     "profiles": [
@@ -8706,6 +8719,640 @@ const DATA = {
       }
     ]
   },
+  "business-model": {
+    "meta": {
+      "slug": "business-model",
+      "domain": "strategy",
+      "name": "Business Model",
+      "description": "Interrogate a venture as a model that rests on things — components supported by evidence, bound by real conventions, and quantified by projections whose assumptions stay visible.",
+      "icon": "layout-grid",
+      "color": "#0EA5E9",
+      "tags": [
+        "strategy",
+        "business-model",
+        "grp",
+        "ibis",
+        "viability"
+      ],
+      "isPublic": true
+    },
+    "workspace": {
+      "name": "Foundation",
+      "description": "Adds business-model interrogation to the strategic substrate — what the model rests on, which conventions bind it, and which numbers assume what.",
+      "subtype": "foundation"
+    },
+    "dependencies": [
+      {
+        "slug": "foundation",
+        "relation": "compose",
+        "reason": "The model's components ARE the foundation vocabulary — mission, audience, pain-point, positioning, offer, and the client/partner/porteur/funder roles. This pack interrogates them; it does not restate them."
+      }
+    ],
+    "profiles": [
+      {
+        "slug": "question",
+        "displayName": "Question",
+        "icon": "help-circle",
+        "profileKind": "kind",
+        "properties": [
+          {
+            "slug": "questionStatus",
+            "label": "Status",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "open",
+              "exploring",
+              "answered",
+              "abandoned"
+            ]
+          }
+        ]
+      },
+      {
+        "slug": "decision",
+        "displayName": "Decision",
+        "icon": "gavel",
+        "profileKind": "kind",
+        "properties": [
+          {
+            "slug": "decisionStatus",
+            "label": "Status",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "proposed",
+              "accepted",
+              "superseded",
+              "rejected"
+            ]
+          }
+        ]
+      },
+      {
+        "slug": "convention",
+        "displayName": "Convention",
+        "icon": "scale",
+        "color": "rose",
+        "description": "A binding rule the model must satisfy and did not choose — an eligibility threshold, a professional duty, a contractual floor, a platform policy. Distinct from a decision (nobody decided it) and from a finding (it constrains rather than informs).",
+        "profileKind": "kind",
+        "properties": [
+          {
+            "slug": "rule",
+            "label": "The Rule",
+            "valueType": "string",
+            "inputType": "textarea",
+            "description": "State the constraint in the terms the issuer uses, not in a paraphrase. Paraphrase is where eligibility collisions hide."
+          },
+          {
+            "slug": "issuer",
+            "label": "Issued By",
+            "valueType": "string",
+            "inputType": "text",
+            "description": "Who imposes it — a regulator, a funder, an ordre professionnel, a platform, a counterparty."
+          },
+          {
+            "slug": "conventionType",
+            "label": "Type",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "regulatory",
+              "deontological",
+              "eligibility",
+              "contractual",
+              "platform",
+              "fiscal",
+              "other"
+            ]
+          },
+          {
+            "slug": "bindingStatus",
+            "label": "Binding Status",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "verified",
+              "assumed",
+              "contested",
+              "expired"
+            ],
+            "description": "`assumed` is the dangerous default — it means nobody has read the source text yet."
+          },
+          {
+            "slug": "sourceReference",
+            "label": "Source Reference",
+            "valueType": "string",
+            "inputType": "text",
+            "description": "The cahier des charges, article, or guide this comes from. A convention with no reference is an assumption wearing a rule's clothes."
+          },
+          {
+            "slug": "expiresAt",
+            "label": "Expires / Review By",
+            "valueType": "date",
+            "inputType": "date"
+          },
+          {
+            "slug": "consequenceIfBreached",
+            "label": "Consequence If Breached",
+            "valueType": "string",
+            "inputType": "textarea"
+          }
+        ]
+      },
+      {
+        "slug": "projection",
+        "displayName": "Projection",
+        "icon": "trending-up",
+        "color": "violet",
+        "description": "A quantified scenario with its assumptions attached. The number is never the artifact — the assumptions are, because that is the only part anyone can argue with.",
+        "profileKind": "kind",
+        "properties": [
+          {
+            "slug": "scenario",
+            "label": "Scenario",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "pessimistic",
+              "base",
+              "optimistic"
+            ]
+          },
+          {
+            "slug": "horizon",
+            "label": "Horizon",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "month",
+              "quarter",
+              "year",
+              "three-year"
+            ]
+          },
+          {
+            "slug": "assumptions",
+            "label": "Assumptions",
+            "valueType": "string",
+            "inputType": "textarea",
+            "description": "Every input this number needs to be true. When one changes, whatever rests on this projection goes stale."
+          },
+          {
+            "slug": "revenueEstimate",
+            "label": "Revenue Estimate",
+            "valueType": "number",
+            "inputType": "number"
+          },
+          {
+            "slug": "costEstimate",
+            "label": "Cost Estimate",
+            "valueType": "number",
+            "inputType": "number"
+          },
+          {
+            "slug": "breakEvenUnits",
+            "label": "Break-Even Units",
+            "valueType": "number",
+            "inputType": "number"
+          },
+          {
+            "slug": "confidence",
+            "label": "Confidence",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "low",
+              "medium",
+              "high"
+            ]
+          }
+        ]
+      }
+    ],
+    "relationDefs": [
+      {
+        "slug": "rests_on",
+        "displayName": "Rests On",
+        "description": "The source depends on the target for its validity — not for its scheduling. Cycles are LEGAL and meaningful here: a business model is mutually supporting by nature, and forcing it into an acyclic dependency graph destroys the information. When the target changes, everything resting on it is stale until re-checked.",
+        "isDirectional": true,
+        "uiHints": {
+          "category": "reference",
+          "inverseLabel": "Supports"
+        }
+      },
+      {
+        "slug": "refutes",
+        "displayName": "Refutes",
+        "description": "The source is evidence that the target is false. Kept as a first-class edge so a refuted component stays in the graph with its refutation attached, instead of being quietly deleted — the reason a road was not taken is worth more than the road.",
+        "isDirectional": true,
+        "uiHints": {
+          "category": "reference",
+          "inverseLabel": "Refuted By"
+        }
+      }
+    ],
+    "entityLinks": [
+      {
+        "sourceProfileSlug": "offer",
+        "targetProfileSlug": "convention",
+        "type": "rests_on",
+        "label": "Rests on"
+      },
+      {
+        "sourceProfileSlug": "offer",
+        "targetProfileSlug": "audience",
+        "type": "rests_on",
+        "label": "Rests on"
+      },
+      {
+        "sourceProfileSlug": "projection",
+        "targetProfileSlug": "offer",
+        "type": "rests_on",
+        "label": "Rests on"
+      },
+      {
+        "sourceProfileSlug": "decision",
+        "targetProfileSlug": "convention",
+        "type": "rests_on",
+        "label": "Rests on"
+      },
+      {
+        "sourceProfileSlug": "decision",
+        "targetProfileSlug": "projection",
+        "type": "rests_on",
+        "label": "Rests on"
+      },
+      {
+        "sourceProfileSlug": "convention",
+        "targetProfileSlug": "offer",
+        "type": "refutes",
+        "label": "Refutes"
+      },
+      {
+        "sourceProfileSlug": "convention",
+        "targetProfileSlug": "audience",
+        "type": "refutes",
+        "label": "Refutes"
+      },
+      {
+        "sourceProfileSlug": "convention",
+        "targetProfileSlug": "question",
+        "type": "rests_on",
+        "label": "Rests on"
+      }
+    ],
+    "views": [
+      {
+        "name": "Conventions",
+        "slug": "business-model-conventions",
+        "type": "table",
+        "scopeProfileSlug": "convention",
+        "description": "Every rule the model must satisfy, who imposes it, and whether anyone has actually verified it.",
+        "defaultView": true,
+        "config": {
+          "columns": [
+            "title",
+            "conventionType",
+            "issuer",
+            "bindingStatus",
+            "expiresAt"
+          ]
+        }
+      },
+      {
+        "name": "Unverified Conventions",
+        "slug": "business-model-assumed-conventions",
+        "type": "list",
+        "scopeProfileSlug": "convention",
+        "description": "Conventions still marked assumed or contested — the model rests on these and nobody has read the source text.",
+        "config": {
+          "filters": [
+            {
+              "field": "bindingStatus",
+              "operator": "in",
+              "value": [
+                "assumed",
+                "contested"
+              ]
+            }
+          ]
+        }
+      },
+      {
+        "name": "Projections",
+        "slug": "business-model-projections",
+        "type": "table",
+        "scopeProfileSlug": "projection",
+        "description": "Scenarios with their assumptions in the open, so a number can be argued with.",
+        "config": {
+          "columns": [
+            "title",
+            "scenario",
+            "horizon",
+            "revenueEstimate",
+            "costEstimate",
+            "confidence"
+          ]
+        }
+      },
+      {
+        "name": "Open Interrogation",
+        "slug": "business-model-open-questions",
+        "type": "kanban",
+        "scopeProfileSlug": "question",
+        "groupBy": "questionStatus",
+        "description": "The nine component questions and everything they spawned, by status."
+      }
+    ],
+    "seedEntities": [
+      {
+        "profileSlug": "question",
+        "title": "Who is the porteur, and what does the model rest on them for?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "Name the person, then name the specific competence, network, capital, or legitimacy the model cannot survive without. If the answer is generic, the model has no porteur — it has a job posting."
+      },
+      {
+        "profileSlug": "question",
+        "title": "What does the porteur's situation forbid?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "Runway, hours available, geography, non-compete, dependants, health. Constraints discovered in month four were knowable in week one."
+      },
+      {
+        "profileSlug": "question",
+        "title": "What is the offer, stated as the problem it ends?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "Not a description of what is built — a statement of the situation a buyer is in before, and after. If the offer can only be described by its features, the buyer has not been found yet."
+      },
+      {
+        "profileSlug": "question",
+        "title": "Who exactly buys it, and who merely benefits from it?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "Link to `audience` entities. Payer, user, and beneficiary are frequently three different parties, and a model that conflates them forecasts revenue from people who never pay."
+      },
+      {
+        "profileSlug": "question",
+        "title": "Which conventions bind this model, and which are still assumed?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "Eligibility thresholds, professional duties, platform policies, fiscal regimes. Every convention starts `assumed`; the work is reading the source text and moving it to `verified`. An eligibility collision — where the segment with the most pull sits outside the scheme that would fund it — only becomes visible once the numbers are pulled."
+      },
+      {
+        "profileSlug": "question",
+        "title": "What does one unit of delivery actually cost to produce?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "Time, tooling, subcontracting, the unbilled parts. Link the answer to a `projection` so the assumptions stay attached to the number."
+      },
+      {
+        "profileSlug": "question",
+        "title": "Where does the money come from before revenue does?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "Attach `funder` roles to the companies or schemes involved, with their eligibility conditions. Subsidy is a credential and a discount; it is rarely a pipeline."
+      },
+      {
+        "profileSlug": "question",
+        "title": "What means — people, tools, licences, premises — must exist first?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "The means rest on the money and the money rests on the offer. That circularity is the model, not a planning error; record it with `rests_on` and stop trying to linearise it."
+      },
+      {
+        "profileSlug": "question",
+        "title": "What observation would refute this model, and by when?",
+        "properties": {
+          "questionStatus": "open"
+        },
+        "content": "Set the falsifiable test now, while it can still be set honestly. A model with no refuting observation is a belief with a spreadsheet attached."
+      }
+    ],
+    "suggestedRelations": [
+      {
+        "sourceRef": "What is the offer, stated as the problem it ends?",
+        "targetRef": "Who exactly buys it, and who merely benefits from it?",
+        "type": "rests_on"
+      },
+      {
+        "sourceRef": "What is the offer, stated as the problem it ends?",
+        "targetRef": "What means — people, tools, licences, premises — must exist first?",
+        "type": "rests_on"
+      },
+      {
+        "sourceRef": "What means — people, tools, licences, premises — must exist first?",
+        "targetRef": "Where does the money come from before revenue does?",
+        "type": "rests_on"
+      },
+      {
+        "sourceRef": "Where does the money come from before revenue does?",
+        "targetRef": "What is the offer, stated as the problem it ends?",
+        "type": "rests_on"
+      },
+      {
+        "sourceRef": "Where does the money come from before revenue does?",
+        "targetRef": "Which conventions bind this model, and which are still assumed?",
+        "type": "rests_on"
+      },
+      {
+        "sourceRef": "Who exactly buys it, and who merely benefits from it?",
+        "targetRef": "Which conventions bind this model, and which are still assumed?",
+        "type": "rests_on"
+      },
+      {
+        "sourceRef": "What does one unit of delivery actually cost to produce?",
+        "targetRef": "What does the porteur's situation forbid?",
+        "type": "rests_on"
+      },
+      {
+        "sourceRef": "What is the offer, stated as the problem it ends?",
+        "targetRef": "Who is the porteur, and what does the model rest on them for?",
+        "type": "rests_on"
+      }
+    ],
+    "playbooks": [
+      {
+        "name": "Business Model Interrogation",
+        "description": "Walk the nine components as questions, resolve each into a decision backed by evidence, and record the conventions and projections the model rests on — including the cycles.",
+        "goalTemplate": "Interrogate the business model for {venture} and record what it rests on. Steps: (1) Walk each of the nine seeded `question` entities in this workspace; where one is already answered, mark it and move on. (2) Resolve each into a `decision`, keeping the options that lost attached via `refutes` rather than deleting them. Where the evidence itself needs gathering, do that in the Research workspace and link back — do not restate sources here. (3) Every external rule discovered becomes a `convention` with its `issuer` and `sourceReference`; leave `bindingStatus` at `assumed` until the source text has actually been read, then `verified`. (4) Every number becomes a `projection` with its `assumptions` filled in — never a bare figure. (5) Wire the graph with `rests_on` — offer on audience, projection on offer, decision on convention. Do NOT try to make the graph acyclic: if the offer rests on the means and the means rest on the money and the money rests on the offer, record all three. (6) Attach `porteur` and `funder` roles to the real people and organisations instead of creating new entities for them. (7) Close by listing which conventions are still `assumed` and which projections carry `low` confidence — that list is the actual state of the model.",
+        "icon": "layout-grid"
+      }
+    ],
+    "actionPlacements": [
+      {
+        "profileSlug": "question",
+        "surface": "entity-detail",
+        "kind": "playbook",
+        "ref": "Business Model Interrogation",
+        "label": "Interrogate as model component"
+      },
+      {
+        "profileSlug": "convention",
+        "surface": "entity-detail",
+        "kind": "playbook",
+        "ref": "Business Model Interrogation",
+        "label": "Re-check what rests on this"
+      }
+    ],
+    "integrations": [
+      {
+        "templateKey": "research-methods"
+      },
+      {
+        "templateKey": "exa"
+      }
+    ]
+  },
+  "civic-france": {
+    "meta": {
+      "slug": "civic-france",
+      "domain": "knowledge",
+      "name": "France Civic Research",
+      "description": "Overlay for investigating French public data (open data / Licence Ouverte). Composes onto Research. Not a government product — a private research stub.",
+      "icon": "landmark",
+      "color": "#1D4ED8",
+      "tags": [
+        "research",
+        "civic",
+        "france",
+        "open-data",
+        "licence-ouverte"
+      ],
+      "isPublic": false
+    },
+    "workspace": {
+      "name": "Research",
+      "description": "Adds a French civic open-data lens onto the Research substrate — track public datasets consulted during investigations.",
+      "subtype": "research-base"
+    },
+    "dependencies": [
+      {
+        "slug": "research-base",
+        "relation": "compose",
+        "reason": "France civic research is a research method — it needs the Research substrate (question / research / source) to work over."
+      }
+    ],
+    "profiles": [
+      {
+        "slug": "question",
+        "displayName": "Question",
+        "icon": "help-circle",
+        "color": "blue",
+        "description": "An open question driving a civic-data investigation.",
+        "properties": [
+          {
+            "slug": "questionStatus",
+            "label": "Status",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "open",
+              "exploring",
+              "answered",
+              "abandoned"
+            ],
+            "constraints": {
+              "defaultValue": "open"
+            }
+          }
+        ]
+      },
+      {
+        "slug": "research",
+        "displayName": "Research",
+        "icon": "microscope",
+        "color": "violet",
+        "description": "An investigation into French public data — sources, findings, conclusion.",
+        "properties": [
+          {
+            "slug": "researchStatus",
+            "label": "Status",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "ongoing",
+              "concluded",
+              "abandoned"
+            ],
+            "constraints": {
+              "defaultValue": "ongoing"
+            }
+          }
+        ]
+      },
+      {
+        "slug": "source",
+        "displayName": "Source",
+        "icon": "file-text",
+        "color": "cyan",
+        "description": "Anything consulted — API payload, dataset page, decree, report.",
+        "properties": [
+          {
+            "slug": "url",
+            "label": "URL",
+            "valueType": "string",
+            "inputType": "url"
+          }
+        ]
+      },
+      {
+        "slug": "public_dataset",
+        "displayName": "Public dataset",
+        "icon": "database",
+        "color": "blue",
+        "description": "A French public dataset consulted via official open-data APIs (data.gouv.fr / api.gouv.fr / PISTE) — never scraped HTML.",
+        "scope": "WORKSPACE",
+        "properties": [
+          {
+            "slug": "sourceUrl",
+            "label": "Source URL",
+            "valueType": "string",
+            "inputType": "url"
+          },
+          {
+            "slug": "license",
+            "label": "License",
+            "valueType": "string",
+            "inputType": "text"
+          },
+          {
+            "slug": "publisher",
+            "label": "Publisher",
+            "valueType": "string",
+            "inputType": "text"
+          }
+        ]
+      }
+    ],
+    "views": [
+      {
+        "name": "Public datasets",
+        "slug": "civic-france-public-datasets",
+        "type": "table",
+        "scopeProfileSlug": "public_dataset",
+        "description": "French public datasets tracked in this research workspace.",
+        "config": {
+          "columns": [
+            "title",
+            "publisher",
+            "license",
+            "sourceUrl"
+          ]
+        }
+      }
+    ]
+  },
   "communication": {
     "meta": {
       "slug": "communication",
@@ -15856,6 +16503,95 @@ const DATA = {
             "inputType": "textarea"
           }
         ]
+      },
+      {
+        "slug": "porteur",
+        "displayName": "Porteur",
+        "icon": "user-check",
+        "color": "amber",
+        "description": "The person carrying a venture — the one whose commitment, skills, and constraints the model actually rests on. Distinct from `client` (who pays) and `partner` (who collaborates).",
+        "scope": "shared",
+        "profileKind": "role",
+        "applicableKinds": [
+          "person"
+        ],
+        "properties": [
+          {
+            "slug": "brings",
+            "label": "What They Bring",
+            "valueType": "string",
+            "inputType": "textarea",
+            "description": "The specific competence, network, capital, or legitimacy this person contributes that the model depends on."
+          },
+          {
+            "slug": "commitmentLevel",
+            "label": "Commitment",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "full-time",
+              "part-time",
+              "advisory",
+              "intermittent"
+            ]
+          },
+          {
+            "slug": "constraints",
+            "label": "Constraints",
+            "valueType": "string",
+            "inputType": "textarea",
+            "description": "What limits this porteur — time, cash runway, geography, non-compete, family. A model that ignores these is fiction."
+          }
+        ]
+      },
+      {
+        "slug": "funder",
+        "displayName": "Funder",
+        "icon": "banknote",
+        "color": "green",
+        "description": "A source of non-revenue money or subsidy — a bank, a public scheme, an investor, a grantor. A hat worn by a company or a person, never a kind of its own.",
+        "scope": "shared",
+        "profileKind": "role",
+        "applicableKinds": [
+          "company",
+          "person"
+        ],
+        "properties": [
+          {
+            "slug": "fundingType",
+            "label": "Funding Type",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "grant",
+              "subsidy",
+              "loan",
+              "equity",
+              "guarantee",
+              "prize",
+              "other"
+            ]
+          },
+          {
+            "slug": "amountCommitted",
+            "label": "Amount Committed",
+            "valueType": "number",
+            "inputType": "number"
+          },
+          {
+            "slug": "eligibilityConditions",
+            "label": "Eligibility Conditions",
+            "valueType": "string",
+            "inputType": "textarea",
+            "description": "The conditions the venture must satisfy to keep this money. These are the constraints most often discovered too late."
+          },
+          {
+            "slug": "decisionDate",
+            "label": "Decision Date",
+            "valueType": "date",
+            "inputType": "date"
+          }
+        ]
       }
     ],
     "views": [
@@ -17439,40 +18175,47 @@ const DATA = {
             "required": true
           }
         ],
+        "scope": "project",
         "stages": [
           {
             "key": "identify",
             "name": "Identify",
+            "category": "planned",
             "description": "Understand the project and which of the program's submission tracks fit — before any writing.",
             "goal": "A clear project understanding and the fitting submission track; submission stage = scope."
           },
           {
             "key": "draft",
             "name": "Draft",
+            "category": "started",
             "description": "Write the abstract, then the full proposal, from the client's real material.",
             "goal": "Abstract then full proposal drafted; submission stage abstract → build with body fields filled."
           },
           {
             "key": "submit",
             "name": "Submit",
+            "category": "started",
             "description": "Finalize against the program deadline and submit the application.",
             "goal": "Application submitted on time; submission stage = awaiting-results."
           },
           {
             "key": "awaiting",
             "name": "Awaiting",
+            "category": "paused",
             "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",
+            "category": "started",
             "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",
+            "category": "started",
             "description": "Work the program's tranche model — ship and record each tranche.",
             "goal": "Tranche deliverables filled and trancheCompletion updated as milestones ship."
           }
@@ -21491,6 +22234,19 @@ const DATA = {
       }
     ],
     "views": [
+      {
+        "name": "Knowledge",
+        "slug": "knowledge",
+        "type": "table",
+        "scopeProfileSlug": "knowledge",
+        "description": "Validated insights and cautions, with their long-form context and evidence kept in the graph.",
+        "config": {
+          "columns": [
+            "title",
+            "knowledgeForm"
+          ]
+        }
+      },
       {
         "name": "All Notes",
         "type": "table",
@@ -22329,6 +23085,12 @@ const DATA = {
           "label": "Brain Home",
           "icon": "Home"
         },
+        {
+          "kind": "profile",
+          "profileSlug": "knowledge",
+          "label": "Knowledge",
+          "icon": "Brain"
+        },
         {
           "kind": "profile",
           "profileSlug": "note",