unoverse 0.1.200 → 0.1.201

package/operator/.env.example

@@ -42,7 +42,7 @@ DOCR_TOKEN=
 # Page intelligence (promote-page extraction)
 HYPERBROWSER_API_KEY=
 
-# Marketplace catalogue to install from (docs/architecture/MARKETPLACE.md).
+# Marketplace catalogue to install from (docs/architecture/authoring/MARKETPLACE.md).
 # Empty = local items only. No default: a URL is never hardcoded.
 UNOVERSE_MARKETPLACE_URL=
 

package/operator/docker-compose.yml

@@ -372,7 +372,7 @@ services:
     restart: unless-stopped
 
   # unoverse-runtime REMOVED 2026-07-28: WIP, excluded from the platform
-  # (docs/architecture/INFRASTRUCTURE.md). Returns when the user declares it ready.
+  # (docs/architecture/deployment/INFRASTRUCTURE.md). Returns when the user declares it ready.
 
   # ===========================================================================
   # OBSERVABILITY — log viewer (runs by default)

package/operator/infra/aws/main.tf

@@ -1,4 +1,4 @@
-# The Universe — AWS POC (docs/architecture/AWS_DEPLOYMENT.md)
+# The Universe — AWS POC (docs/architecture/deployment/AWS_DEPLOYMENT.md)
 #
 # One VM + managed Postgres/Redis + Cognito + a scoped Bedrock IAM user.
 # Deliberately flat and minimal: this is the POC tier. Terraform provisions,

package/operator/infra/digitalocean/main.tf

@@ -1,4 +1,4 @@
-# The Universe — DigitalOcean ground (docs/architecture/INFRASTRUCTURE.md)
+# The Universe — DigitalOcean ground (docs/architecture/deployment/INFRASTRUCTURE.md)
 #
 # Same five-input contract as infra/aws, DO implementation: Droplet + Managed
 # Postgres (fronted by its built-in PgBouncer, per the Postgres law) + Managed

package/operator/lib/db-verify.sh

@@ -36,7 +36,7 @@ cmd_db_verify() {
         "id", "name", "description", "nodes", "edges", "active",
         "execution_mode", "test_inputs", "umap_settings", "viewport",
         "mcp_schema", "memory_config", "content_taxonomy", "created_at", "updated_at",
-        "workflow_document", "layout_document"
+        "workflow_document", "layout_document", "org"
       ],
       workflow_executions: [
         "execution_id", "workflow_id", "status", "start_time", "end_time",
@@ -93,42 +93,42 @@ cmd_db_verify() {
         "needs", "source_url", "source_id", "umap_x", "umap_y", "umap_z",
         "umap_cluster_id", "color_hex", "needs_umap_update", "created_at",
         "updated_at", "workflow_id", "key_need", "metadata", "embedding_original",
-        "cluster_distance"
+        "cluster_distance", "org"
       ],
       dictionary_clusters: [
         "cluster_id", "workflow_id", "parent_id", "depth", "name", "description",
         "name_embedding", "medoid_id", "terms", "member_count", "umap_x", "umap_y",
         "umap_z", "radius", "created_at", "updated_at",
         "region_id", "carried_overlap", "derived_from", "name_locked", "locked_at",
-        "locked_by", "member_ids"
+        "locked_by", "member_ids", "org"
       ],
       user_region_events: [
         "id", "workflow_id", "user_id", "region_id", "region_name", "stage",
-        "source", "evidence", "occurred_at"
+        "source", "evidence", "occurred_at", "org"
       ],
       dictionary_regions: [
         "region_id", "workflow_id", "depth", "name", "description", "name_locked",
         "locked_at", "locked_by", "stage", "stage_set_by", "needs_review",
         "skills", "skills_set_by", "skills_set_at",
-        "derived_from", "first_seen", "last_seen", "closed_at"
+        "derived_from", "first_seen", "last_seen", "closed_at", "org"
       ],
       dictionary_content_chunks: [
         "chunk_id", "text", "source_url", "source_type", "metadata",
-        "workflow_id", "created_at", "updated_at", "embedding_original"
+        "workflow_id", "created_at", "updated_at", "embedding_original", "org"
       ],
       dictionary_chunk_need_matches: [
         "chunk_id", "need_id", "similarity_score", "rank", "match_type",
-        "created_at", "workflow_id"
+        "created_at", "workflow_id", "org"
       ],
       dictionary_ingestion_configs: [
         "id", "name", "description", "connector_type", "connector_config",
         "main_category", "workflow_id", "created_at", "updated_at",
-        "last_run_at", "run_count"
+        "last_run_at", "run_count", "org"
       ],
       dictionary_ingestion_jobs: [
         "job_id", "workflow_id", "status", "connector_type", "category",
         "config", "extraction_config", "started_at", "completed_at",
-        "progress", "error", "created_at"
+        "progress", "error", "created_at", "org"
       ],
       goals: [
         "goal_id", "user_id", "workflow_id", "status", "description",
@@ -141,13 +141,16 @@ cmd_db_verify() {
       goal_scratch: [
         "goal_id", "agent_id", "agent_name", "state", "updated_at"
       ],
+      orgs: [
+        "slug", "name", "settings", "website", "logo", "created_at", "updated_at"
+      ],
       knowledge_docs: [
         "id", "workflow_id", "title", "doc_type", "sections", "version",
         "links", "metadata", "created_at", "updated_at"
       ],
       content_sources: [
         "workflow_id", "connector", "source_key", "group_path", "label",
-        "status", "last_ingested", "metadata", "created_at", "updated_at"
+        "status", "last_ingested", "metadata", "created_at", "updated_at", "org"
       ],
       security_attack_corpus: [
         "id", "category", "label", "attack_prompt", "expected_result",

package/operator/lib/setup.sh

@@ -343,7 +343,7 @@ OPENAI_API_KEY=${OPENAI_API_KEY}
 # back it up with the database. Kept on re-runs.
 CREDENTIAL_ENCRYPTION_KEY=${CREDENTIAL_ENCRYPTION_KEY}
 HYPERBROWSER_API_KEY=${HYPERBROWSER_API_KEY}
-# Marketplace catalogue to install from (docs/architecture/MARKETPLACE.md).
+# Marketplace catalogue to install from (docs/architecture/authoring/MARKETPLACE.md).
 # Empty = local items only. No default: a URL is never hardcoded.
 UNOVERSE_MARKETPLACE_URL=
 DOMAIN=

package/operator/operator.sh

@@ -223,7 +223,7 @@ case "${1:-}" in
       echo "" >&2
       echo "    scripts/operator.sh publish" >&2
       echo "" >&2
-      echo "  See docs/architecture/DEVELOPER_GUIDE.md § Releasing." >&2
+      echo "  See docs/architecture/platform/DEVELOPER_GUIDE.md § Releasing." >&2
       echo "" >&2
       exit 1
     else

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.200",
+  "version": "0.1.201",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",

package/vendor/base/items/collect.js

@@ -97,7 +97,8 @@ export function collectProject(designRoot, project) {
     // A prompt block is NEVER qualified this way — see the blocks/ walk below for why.
     // Apps keep their bare ids: those are org-qualified by convention
     // (`<org>-chat`). docs/unoverse/UNOVERSE_COMPONENT_ORGS.md.
-    const QUALIFIED_KINDS = new Set(["component", "skill", "template"]);
+    // `identity` (2026-09-05): the org's four documents, `<org>/brand` like a component.
+    const QUALIFIED_KINDS = new Set(["component", "skill", "template", "identity"]);
     const add = (kind, name, definition) => items.push({
         kind,
         name: QUALIFIED_KINDS.has(kind) ? `${project}/${name}` : name,
@@ -121,7 +122,10 @@ export function collectProject(designRoot, project) {
     // 029): apps publish as kind `app` and the Template Model kind owns the bare
     // word. Forgetting a design dir here ships deploys that silently drop every
     // artifact of that kind.
-    for (const [dir, kind] of [["components", "component"], ["apps", "app"], ["templates", "template"], ["atoms", "atom"]]) {
+    // IDENTITY (owner ruling 2026-09-05): design/<org>/identity/<doc>/ publishes as kind
+    // `identity`, the same walk as a component folder, so it reaches the registry, the
+    // spatial catalogue and the map through the one publish path everything else takes.
+    for (const [dir, kind] of [["components", "component"], ["apps", "app"], ["templates", "template"], ["atoms", "atom"], ["identity", "identity"]]) {
         const home = join(root, dir);
         if (!existsSync(home))
             continue;

package/vendor/base/items/publish.js

@@ -10,7 +10,7 @@
  * new, changed, unchanged, or refused because the name belongs to someone else. Publishing
  * blind is how a project half-lands and nobody can tell by looking.
  *
- * See docs/architecture/DECLARATIVE_NODES.md §9.
+ * See docs/architecture/authoring/DECLARATIVE_NODES.md §9.
  */
 import { existsSync } from "node:fs";
 import { join } from "node:path";

package/vendor/base/lint/design/vocabulary.mjs

@@ -57,7 +57,7 @@ export const PROP_KEYS = [
  */
 export const INTERFACE_FIELDS = new Set([
   "universal_id", "title", "description", "object_type", "key_need", "source_url", "source_id",
-  "tagline", "shortDescription", "introParagraph", "callToAction", "actionPrompt", "primaryImage", "images", "action",
+  "tagline", "shortDescription", "introParagraph", "callToAction", "primaryImage", "images", "action",
   "bodyCopy", "features", "mainCategory", "section", "needs",
 ]);
 

package/vendor/base/lint/nodes/_schema/_defs.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://docs.unoverse.ai/schemas/nodes/_defs.schema.json",
   "title": "Shared node definitions",
-  "description": "Fragments $ref'd by the sibling node schemas. Not authored directly. See docs/architecture/DECLARATIVE_NODES.md.",
+  "description": "Fragments $ref'd by the sibling node schemas. Not authored directly. See docs/architecture/authoring/DECLARATIVE_NODES.md.",
   "definitions": {
     "nodeType": {
       "type": "string",

package/vendor/base/lint/nodes/_schema/api.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://docs.unoverse.ai/schemas/nodes/api.schema.json",
   "title": "Unoverse node API call",
-  "description": "api.yaml — the upstream call this node makes, and how its response maps onto the node's outputs. This is the file that replaces an executor. NAMED api, not service: `service` already means serviceConnectors / isService / MCP providers / /service-call in this platform. See docs/architecture/DECLARATIVE_NODES.md §8.\n\nEVERY enum below is the EXECUTOR'S CAPABILITY LIST. A manifest may only name a capability that is already implemented in code. Adding a value here without implementing it produces a node that lints clean and fails at run time, and allowing a manifest to name arbitrary code would end the safety property this whole format exists for (§2).\n\nA node is reached two ways, and they never cross. The GRAPH RUNS it: `run` is the ordered list of calls it makes, and `events` says what lands on its output connectors. Or a SERVICE CALLS it ad-hoc, exposed as MCP: `service` holds those methods, each with its own list of calls, each handing one value straight back to the caller rather than touching a connector. A pure service node has only `service`.\n\nCalls are ALWAYS a `run` list, even when there is one of them. There is no `request` key.",
+  "description": "api.yaml — the upstream call this node makes, and how its response maps onto the node's outputs. This is the file that replaces an executor. NAMED api, not service: `service` already means serviceConnectors / isService / MCP providers / /service-call in this platform. See docs/architecture/authoring/DECLARATIVE_NODES.md §8.\n\nEVERY enum below is the EXECUTOR'S CAPABILITY LIST. A manifest may only name a capability that is already implemented in code. Adding a value here without implementing it produces a node that lints clean and fails at run time, and allowing a manifest to name arbitrary code would end the safety property this whole format exists for (§2).\n\nA node is reached two ways, and they never cross. The GRAPH RUNS it: `run` is the ordered list of calls it makes, and `events` says what lands on its output connectors. Or a SERVICE CALLS it ad-hoc, exposed as MCP: `service` holds those methods, each with its own list of calls, each handing one value straight back to the caller rather than touching a connector. A pure service node has only `service`.\n\nCalls are ALWAYS a `run` list, even when there is one of them. There is no `request` key.",
   "type": "object",
   "required": [],
   "definitions": {

package/vendor/base/lint/nodes/_schema/interface.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://docs.unoverse.ai/schemas/nodes/interface.schema.json",
   "title": "Unoverse node interface",
-  "description": "interface.yaml — the node's WIRING SURFACE, and nothing else. Everything another node, an agent, or a developer needs in order to connect to this one: what goes in, what comes out, what services it offers or consumes, and what credentials it needs.\n\nIt has its own file because this is the question asked most often about a node, and it should never require reading past a node's branding to answer. See docs/architecture/DECLARATIVE_NODES.md §5.",
+  "description": "interface.yaml — the node's WIRING SURFACE, and nothing else. Everything another node, an agent, or a developer needs in order to connect to this one: what goes in, what comes out, what services it offers or consumes, and what credentials it needs.\n\nIt has its own file because this is the question asked most often about a node, and it should never require reading past a node's branding to answer. See docs/architecture/authoring/DECLARATIVE_NODES.md §5.",
   "type": "object",
   "properties": {
     "$schema": {

package/vendor/base/lint/nodes/_schema/node.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://docs.unoverse.ai/schemas/nodes/node.schema.json",
   "title": "Unoverse node",
-  "description": "node.yaml — what this node IS: its identity, its kind, and how it is discovered. The only required file in a node folder.\n\nThe wiring surface lives next door in interface.yaml, so \"what can I connect to this?\" is answered without reading past the node's branding. config/api/test/interface may each be inlined here instead of living in their own file, but never both (that is a lint error, not a merge). See docs/architecture/DECLARATIVE_NODES.md §5.",
+  "description": "node.yaml — what this node IS: its identity, its kind, and how it is discovered. The only required file in a node folder.\n\nThe wiring surface lives next door in interface.yaml, so \"what can I connect to this?\" is answered without reading past the node's branding. config/api/test/interface may each be inlined here instead of living in their own file, but never both (that is a lint error, not a merge). See docs/architecture/authoring/DECLARATIVE_NODES.md §5.",
   "type": "object",
   "required": [
     "type",
@@ -143,7 +143,7 @@
     },
     "auth": {
       "type": "object",
-      "description": "WHO MAY RUN THIS NODE — inbound, about the caller (docs/architecture/DECLARATIVE_NODES.md §9.13). Not to be confused with a call's `credential` in api/run.yaml, which is outbound: how the node proves itself to a vendor. Both were spelled `auth` until 2026-07-28.\n\nCOMPULSORY, which is the point. It was optional (`requires: { role }`) until 2026-07-28, and every node in the tree said nothing — so a node that had been considered and left open looked exactly like a node nobody had thought about. Silence is not an answer to this question.",
+      "description": "WHO MAY RUN THIS NODE — inbound, about the caller (docs/architecture/authoring/DECLARATIVE_NODES.md §9.13). Not to be confused with a call's `credential` in api/run.yaml, which is outbound: how the node proves itself to a vendor. Both were spelled `auth` until 2026-07-28.\n\nCOMPULSORY, which is the point. It was optional (`requires: { role }`) until 2026-07-28, and every node in the tree said nothing — so a node that had been considered and left open looked exactly like a node nobody had thought about. Silence is not an answer to this question.",
       "additionalProperties": false,
       "properties": {
         "required": {

package/vendor/base/lint/nodes/_schema/package.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://docs.unoverse.ai/schemas/nodes/package.schema.json",
   "title": "Unoverse node package",
-  "description": "package.yaml — the envelope for a folder of nodes. Replaces the `gravity` block in package.json for packages that no longer ship code. See docs/architecture/DECLARATIVE_NODES.md §5.",
+  "description": "package.yaml — the envelope for a folder of nodes. Replaces the `gravity` block in package.json for packages that no longer ship code. See docs/architecture/authoring/DECLARATIVE_NODES.md §5.",
   "type": "object",
   "required": [
     "name",

package/vendor/base/lint/nodes/_schema/test.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://docs.unoverse.ai/schemas/nodes/test.schema.json",
   "title": "Unoverse node test data",
-  "description": "test.yaml — the fixture behind Studio's \"Load sample, Run\" button and behind `unoverse node test`. Every node must have one: a node nobody can run is a node nobody can trust, and lint enforces it.\n\nTemplate fields are supplied ALREADY RESOLVED, because the bench has no upstream node to resolve them from. See docs/architecture/DECLARATIVE_NODES.md §6.",
+  "description": "test.yaml — the fixture behind Studio's \"Load sample, Run\" button and behind `unoverse node test`. Every node must have one: a node nobody can run is a node nobody can trust, and lint enforces it.\n\nTemplate fields are supplied ALREADY RESOLVED, because the bench has no upstream node to resolve them from. See docs/architecture/authoring/DECLARATIVE_NODES.md §6.",
   "type": "object",
   "required": [
     "testData"

package/vendor/base/lint/nodes/index.mjs

@@ -13,7 +13,7 @@
  * without it is the gap LOCAL_STUDIO.md:246 names: "a malformed definition is one restart
  * from a broken server", and a published row does not even need the restart.
  *
- * FOUR TIERS (docs/architecture/DECLARATIVE_NODES.md §6). This is tiers 2 and 3.
+ * FOUR TIERS (docs/architecture/authoring/DECLARATIVE_NODES.md §6). This is tiers 2 and 3.
  *   1  editor    $schema pointers + .vscode yaml.schemas, no tool
  *   2  structural   every part validated against the node schemas (packages/docs/schemas/nodes)
  *   3  semantic     the cross-file rules a schema cannot express

package/vendor/base/manifests/source.js

@@ -9,7 +9,7 @@
  * Everything past this file works on the composed definition and never learns where
  * it came from.
  *
- * See docs/architecture/DECLARATIVE_NODES.md.
+ * See docs/architecture/authoring/DECLARATIVE_NODES.md.
  */
 import * as fs from "fs";
 import * as path from "path";