superbee 0.4.3-pre.9 → 0.4.4-pre.1

package/references/integrations/rest-json-authoring/recipe/connectors/tickets.md

@@ -0,0 +1,42 @@
+---
+type: Connector
+title: Recorded ticket board
+auth:
+  kind: none
+domains:
+  - tickets.example.org
+record_sources:
+  - name: tickets
+    profile: rest-json
+    target_kind: Ticket
+    mode: overlay
+    identity:
+      resource: https://tickets.example.org/boards/{board}
+      id: '{id}'
+    fields:
+      title: title
+      state:
+        from: status
+        values: { OPEN: open, DONE: closed }
+        unmapped: keep
+      priority:
+        from: priority
+        values: { low: low, high: high }
+      url: html_url
+    completeness: complete
+    request:
+      host: tickets.example.org
+      method: GET
+      path: /boards/{board}/items
+      query:
+        after: '{cursor}'
+      items: items
+      paging:
+        kind: cursor
+        cursor_path: next
+      complete: always
+---
+# Recorded ticket board
+
+All provider responses are synthetic. This declaration selects the shipped public rest-json
+profile, never executable code from this directory.

package/references/integrations/rest-json-authoring/recipe/conventions/ticket.md

@@ -0,0 +1,15 @@
+---
+type: Convention
+title: Ticket
+governs: Ticket
+path: tickets/
+fields:
+  required: [title, state]
+  optional: [priority, note, url]
+  values:
+    state: [open, closed]
+    priority: [low, high]
+---
+# Ticket
+
+A synthetic issue from an example board. A person's notes stay outside the source-owned fields.

package/references/integrations/rest-json-authoring/recipe/recipe.md

@@ -0,0 +1,13 @@
+---
+type: Recipe
+id: recorded-tickets
+title: Recorded ticket integration
+version: '1'
+summary: An offline integration-authoring example over a synthetic ticket board.
+content_policy: definitions-only
+connectors:
+  - connectors/tickets.md
+---
+# Recorded tickets
+
+A credential-free authoring example. Installation never fetches the synthetic provider.

package/references/modeling-and-delivery.md

@@ -54,6 +54,9 @@ Use `--body-file` for multiline Markdown. Use `superbee new "<Kind>" --help` for
 of an installed Kind. Prefer semantic no-ops, actor attribution, and version-aware updates when the
 CLI exposes them.
 
+Put write-time guidance in a Kind's field or value descriptions, never its body: a write that
+sets a described value returns that description as `guidance`.
+
 ## Evolve from use
 
 Refine fields or relationships only after actual instances expose a recurring need. Package a

package/references/sample-bundle/references/okf-spec.md

@@ -2,7 +2,7 @@
 type: Reference
 title: Open Knowledge Format v0.1 (Draft)
 description: A version-scoped OKF v0.1 interop reference, not Superbee's cross-edition authority.
-resource: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md
+resource: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/ee67a5ca27044ebe7c38385f5b6cffc2305a9c1a/okf/SPEC.md
 tags: [okf, spec, reference]
 timestamp: 2026-08-23T17:47:52Z
 ---
@@ -17,6 +17,11 @@ file is a Concept whose ID is its path minus `.md`. The only required
 frontmatter field is `type`. This document mirrors the external spec as a
 first-class concept (§8) so citations resolve inside the graph.
 
+OKF has since moved to its own repository,
+`GoogleCloudPlatform/open-knowledge-format`, which publishes v0.2. The
+`knowledge-catalog` copy is a frozen snapshot, so the v0.1 citation below is a
+permalink to the commit that published v0.1.
+
 # Key sections
 
 * §3 bundle structure and reserved filenames (`index.md`, `log.md`).
@@ -26,4 +31,5 @@ first-class concept (§8) so citations resolve inside the graph.
 
 # Citations
 
-1. [OKF SPEC.md](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md)
+1. [OKF v0.1 SPEC.md](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/ee67a5ca27044ebe7c38385f5b6cffc2305a9c1a/okf/SPEC.md)
+2. [Open Knowledge Format repository](https://github.com/GoogleCloudPlatform/open-knowledge-format)