@company-semantics/contracts 58.1.0 → 58.3.0

package/src/proactive/templates/org-became-shared.ts

@@ -0,0 +1,54 @@
+/**
+ * The org-became-shared pushed chat — the first invited person accepted, so
+ * the owner's personal workspace is now a shared one (ADR-CONTRACTS-142).
+ *
+ * The prose NAMES THE RELOCATION, and that is its job. The app ADR with slug
+ * `nav-posture-opens-on-invite-send` established that conversion is a
+ * relocation, not an addition: five sections leave My settings (Integrations,
+ * Invite team members, AI Usage, Budget, Billing) and reappear under Org
+ * settings. Unannounced, that reads as things going missing — and a banner
+ * can say "something moved" but not walk the owner through what and why.
+ * This chat is where that explanation lives, and the chips let the owner ask
+ * the question the banner cannot answer.
+ *
+ * FROZEN AT WRITE TIME (INV-PROACTIVE-CONTENT). Both interpolated facts are
+ * things the owner was entitled to at compose time: they named the org, and
+ * they invited the person who accepted. Nothing here can be revoked later in
+ * a way the transcript would have to take back.
+ */
+
+import type { ProactiveChatComposer } from "../composer";
+
+export const orgBecameSharedComposer: ProactiveChatComposer<"orgBecameShared"> =
+  {
+    template: "orgBecameShared",
+    compose: (facts) => ({
+      title: "Your workspace is now shared",
+      text:
+        `${facts.joinerDisplayName} accepted your invite, so ${facts.orgName} ` +
+        `moved from a personal workspace to a shared one.\n\n` +
+        `This is a relocation, not an addition: Integrations, Invite team ` +
+        `members, AI Usage, Budget and Billing have moved out of My settings ` +
+        `and into Org settings. Nothing was removed — the five sections now ` +
+        `belong to the workspace rather than to you.`,
+      replies: [
+        {
+          id: "plain-english",
+          label: "Explain in plain English",
+          prompt:
+            "Explain in plain English what changed when my workspace became shared.",
+        },
+        {
+          id: "what-first",
+          label: "What should I set up first?",
+          prompt:
+            "Now that my workspace is shared, what should I set up first?",
+        },
+        {
+          id: "who-can-see",
+          label: "Who can see what now?",
+          prompt: "Who can see what in my workspace now that it is shared?",
+        },
+      ],
+    }),
+  };

package/src/resource-key-types.ts

@@ -150,6 +150,15 @@ export type ResourceKey =
   // every badge in the shell, and the two have different invalidation triggers
   // (a notification being READ changes the feed and not the bucket).
   | { type: "feed"; orgId: string }
+  /**
+   * Org system events (the banner strip).
+   *
+   * Lives HERE and not in the app's `AppOnlyKey` union, whose doc bar is "the
+   * server can never need to name this key" — here the server is the publisher.
+   * Once the banner is an asynchronous projection, an unsubscribed hook means a
+   * banner that only appears on next mount or reload.
+   */
+  | { type: "orgSystemEvents"; orgId: string }
   // User-scoped
   | { type: "dismissedBanners"; userId: string }
   | { type: "userOrgs"; userId: string }

package/src/resource-keys.ts

@@ -147,6 +147,7 @@ const ORG_SCOPED_TYPES = [
   "orgUnitOwners",
   "actionItems",
   "feed",
+  "orgSystemEvents",
 ] as const satisfies readonly OrgScopedType[];
 
 const USER_SCOPED_TYPES = [
@@ -285,6 +286,7 @@ export function toQueryKey(key: ResourceKey): readonly string[] {
     case "orgUnitOwners":
     case "actionItems":
     case "feed":
+    case "orgSystemEvents":
       return [key.type, key.orgId] as const;
 
     // System-scoped (ADR-CONTRACTS-052) — tenant-less super-admin resources

package/src/user-notifications/README.md

@@ -33,6 +33,16 @@ that renders them alongside action items at the top of `/me/work`.
 - **The cursor encodes `(createdAt, id)`.** The id breaks ties so two rows
   written in one transaction cannot straddle a page boundary and be served twice
   or skipped.
+- **A row can be BORN READ.** Every proactive kind writes a durable row here
+  as its paper trail, but only the class whose badge carrier is `inbox` writes
+  it unread; `proactive.org_became_shared` is an `announcement`, so the banner
+  holds the badge and the row arrives read, and `proactive.brief_morning` is a
+  `briefing`, so the pushed chat holds the badge and the row arrives read. That
+  rule is stated once, in `bornRead` (`../proactive/classes`), never re-derived
+  per call site (ADR-CONTRACTS-142). The kind strings are `proactive.*` — the
+  producing domain owns the renderer — and are deliberately not the
+  `ProactiveEventKind` strings `org.became_shared` / `brief.morning`, so
+  neither union can quietly become derived from the other.
 
 ## Public API
 

package/src/user-notifications/kinds.ts

@@ -76,6 +76,34 @@ export const USER_NOTIFICATION_KINDS = [
   "comment.mention",
   /** A thread you took part in got a new comment. Never emitted for an edit. */
   "comment.reply",
+  /**
+   * Your org stopped being personal — its first member joined
+   * (ADR-CONTRACTS-142). The durable row of the `org.became_shared` proactive
+   * kind.
+   *
+   * BORN READ: the banner holds the badge for an `announcement`, so this row
+   * is the paper trail and never the attention carrier (`bornRead` in
+   * `../proactive/classes` is the one place that rule is stated). The
+   * producing domain in the string is `proactive` — `src/proactive/` in the
+   * backend owns the renderer, matching the `companyMd.*` / `comment.*`
+   * convention. The string is deliberately DISTINCT from the proactive kind's
+   * `org.became_shared`: identical names across two unions is how one quietly
+   * becomes derived from the other, which ADR-CONT-108 forbids.
+   */
+  "proactive.org_became_shared",
+  /**
+   * Your morning brief was written (ADR-CONTRACTS-142). The durable row of
+   * the `brief.morning` proactive kind.
+   *
+   * BORN READ: the pushed chat holds the badge for a `briefing`, so this row
+   * is the paper trail and never the attention carrier (`bornRead` in
+   * `../proactive/classes` is the one place that rule is stated). One row per
+   * recipient per org-local day, pointing at that recipient's OWN chat — the
+   * occurrence is shared, the row and the chat are not. The string is
+   * deliberately DISTINCT from the proactive kind's `brief.morning`, for the
+   * reason stated on the member above.
+   */
+  "proactive.brief_morning",
 ] as const;
 
 export type UserNotificationKind = (typeof USER_NOTIFICATION_KINDS)[number];