@elevasis/sdk 1.47.0 → 1.48.0

package/dist/index.d.ts

@@ -7276,7 +7276,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         route: z.ZodOptional<z.ZodString>;
     }, z.core.$loose>>>>;
-}, z.core.$strip>>;
+}, z.core.$strict>>;
 type OntologyObjectType = z.infer<typeof OntologyObjectTypeSchema>;
 type OntologyLinkType = z.infer<typeof OntologyLinkTypeSchema>;
 type OntologyActionType = z.infer<typeof OntologyActionTypeSchema>;
@@ -8648,7 +8648,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             route: z.ZodOptional<z.ZodString>;
         }, z.core.$loose>>>>;
-    }, z.core.$strip>>>;
+    }, z.core.$strict>>>;
     resources: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodDiscriminatedUnion<[z.ZodObject<{
         id: z.ZodString;
         order: z.ZodDefault<z.ZodNumber>;

package/dist/index.js

@@ -114,7 +114,7 @@ var OntologyScopeSchema = z.object({
   sharedProperties: z.record(OntologyIdSchema, OntologySharedPropertySchema).default({}).optional(),
   groups: z.record(OntologyIdSchema, OntologyGroupSchema).default({}).optional(),
   endpoints: z.record(OntologyIdSchema, OntologyEndpointTypeSchema).default({}).optional()
-}).default({});
+}).strict().default({});
 var SCOPE_KIND = {
   objectTypes: "object",
   linkTypes: "link",
@@ -612,29 +612,45 @@ var SystemUiSchema = z.object({
   path: PathSchema,
   surfaces: ReferenceIdsSchema,
   icon: IconNameSchema.optional()
-});
+}).strict();
 var SystemInterfaceKeySchema = ModelIdSchema;
 var SystemInterfaceLifecycleSchema = z.enum(["draft", "active", "disabled", "deprecated", "archived"]).meta({ label: "System interface lifecycle", color: "teal" });
 var SYSTEM_INTERFACE_PROFILES = [
   {
     systemPath: "sales.lead-gen",
     interfaceKey: "api",
-    readinessProfile: "sales.lead-gen.api"
+    readinessProfile: "sales.lead-gen.api",
+    validation: "built-in"
   },
   {
     systemPath: "sales.crm",
     interfaceKey: "api",
-    readinessProfile: "sales.crm.api"
+    readinessProfile: "sales.crm.api",
+    validation: "built-in"
   },
   {
     systemPath: "sales.lead-gen",
     interfaceKey: "crm-handoff",
-    readinessProfile: "sales.lead-gen.crm-handoff"
+    readinessProfile: "sales.lead-gen.crm-handoff",
+    validation: "built-in"
+  },
+  {
+    // Gated by `CONTENT_API_INTERFACE` in `apps/api/src/business/content/organization-model.ts`,
+    // which every `/api/content/*` and `/api/external/content/*` route asserts. Contract-validated
+    // rather than built-in because the required step catalog is per-adopter: Elevasis declares
+    // `content:catalog/long-form-to-shorts-steps`, a tenant declares its own.
+    systemPath: "content",
+    interfaceKey: "api",
+    readinessProfile: "content.api",
+    validation: "contract"
   }
 ];
-var SYSTEM_INTERFACE_READINESS_PROFILES = SYSTEM_INTERFACE_PROFILES.map(
+SYSTEM_INTERFACE_PROFILES.map(
   (profile) => profile.readinessProfile
 );
+var BUILT_IN_VALIDATED_PROFILE_IDS = SYSTEM_INTERFACE_PROFILES.filter(
+  (profile) => profile.validation === "built-in"
+).map((profile) => profile.readinessProfile);
 var SystemInterfaceReadinessProfileSchema = z.string().trim().min(1);
 var SystemInterfaceResourceScopeSchema = z.array(ModelIdSchema).default([]);
 var SystemApiInterfaceReadinessContractSchema = z.object({
@@ -673,7 +689,7 @@ var SystemApiInterfaceSchema = z.object({
 }).strict();
 var _customProfileIds = /* @__PURE__ */ new Set();
 function isReservedPlatformProfileId(profileId) {
-  return SYSTEM_INTERFACE_READINESS_PROFILES.includes(profileId);
+  return BUILT_IN_VALIDATED_PROFILE_IDS.includes(profileId);
 }
 function lookupReadinessProfile(profileId) {
   if (isReservedPlatformProfileId(profileId) || getBuiltInReadinessProfile(profileId) !== void 0) {

package/dist/node/index.d.ts

@@ -1622,7 +1622,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         route: z.ZodOptional<z.ZodString>;
     }, z.core.$loose>>>>;
-}, z.core.$strip>>;
+}, z.core.$strict>>;
 type OntologyScope = z.infer<typeof OntologyScopeSchema>;
 
 declare const SystemApiInterfaceSchema: z.ZodObject<{
@@ -2269,7 +2269,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             route: z.ZodOptional<z.ZodString>;
         }, z.core.$loose>>>>;
-    }, z.core.$strip>>>;
+    }, z.core.$strict>>>;
     resources: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodDiscriminatedUnion<[z.ZodObject<{
         id: z.ZodString;
         order: z.ZodDefault<z.ZodNumber>;

package/dist/test-utils/index.d.ts

@@ -6480,7 +6480,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         route: z.ZodOptional<z.ZodString>;
     }, z.core.$loose>>>>;
-}, z.core.$strip>>;
+}, z.core.$strict>>;
 type OntologyScope = z.infer<typeof OntologyScopeSchema>;
 
 declare const SystemApiInterfaceSchema: z.ZodObject<{
@@ -7127,7 +7127,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             route: z.ZodOptional<z.ZodString>;
         }, z.core.$loose>>>>;
-    }, z.core.$strip>>>;
+    }, z.core.$strict>>>;
     resources: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodDiscriminatedUnion<[z.ZodObject<{
         id: z.ZodString;
         order: z.ZodDefault<z.ZodNumber>;

package/dist/test-utils/index.js

@@ -8541,6 +8541,8 @@ createAdapter("acqDb", [
   "addCompaniesToList",
   "updateCompanyStage",
   "updateContactStage",
+  "clearCompanyStages",
+  "clearContactStages",
   // Company operations
   "createCompany",
   "upsertCompany",
@@ -8567,6 +8569,8 @@ createAdapter("acqDb", [
   "getDealById",
   "getContactById",
   "getCompanyById",
+  "listDeals",
+  "getDealPipelineAnalytics",
   // Deal transitions
   "updateDiscoveryData",
   "updateProposalData",
@@ -8644,6 +8648,8 @@ createAdapter("list", [
   "recordExecution",
   "updateCompanyStage",
   "updateContactStage",
+  "clearCompanyStages",
+  "clearContactStages",
   "listPendingCompanyIds",
   "listPendingContactIds"
 ]);
@@ -8777,7 +8783,7 @@ var OntologyScopeSchema = z.object({
   sharedProperties: z.record(OntologyIdSchema, OntologySharedPropertySchema).default({}).optional(),
   groups: z.record(OntologyIdSchema, OntologyGroupSchema).default({}).optional(),
   endpoints: z.record(OntologyIdSchema, OntologyEndpointTypeSchema).default({}).optional()
-}).default({});
+}).strict().default({});
 var SCOPE_KIND = {
   objectTypes: "object",
   linkTypes: "link",
@@ -9030,29 +9036,45 @@ var SystemUiSchema = z.object({
   path: PathSchema,
   surfaces: ReferenceIdsSchema,
   icon: IconNameSchema.optional()
-});
+}).strict();
 var SystemInterfaceKeySchema = ModelIdSchema;
 var SystemInterfaceLifecycleSchema = z.enum(["draft", "active", "disabled", "deprecated", "archived"]).meta({ label: "System interface lifecycle", color: "teal" });
 var SYSTEM_INTERFACE_PROFILES = [
   {
     systemPath: "sales.lead-gen",
     interfaceKey: "api",
-    readinessProfile: "sales.lead-gen.api"
+    readinessProfile: "sales.lead-gen.api",
+    validation: "built-in"
   },
   {
     systemPath: "sales.crm",
     interfaceKey: "api",
-    readinessProfile: "sales.crm.api"
+    readinessProfile: "sales.crm.api",
+    validation: "built-in"
   },
   {
     systemPath: "sales.lead-gen",
     interfaceKey: "crm-handoff",
-    readinessProfile: "sales.lead-gen.crm-handoff"
+    readinessProfile: "sales.lead-gen.crm-handoff",
+    validation: "built-in"
+  },
+  {
+    // Gated by `CONTENT_API_INTERFACE` in `apps/api/src/business/content/organization-model.ts`,
+    // which every `/api/content/*` and `/api/external/content/*` route asserts. Contract-validated
+    // rather than built-in because the required step catalog is per-adopter: Elevasis declares
+    // `content:catalog/long-form-to-shorts-steps`, a tenant declares its own.
+    systemPath: "content",
+    interfaceKey: "api",
+    readinessProfile: "content.api",
+    validation: "contract"
   }
 ];
-var SYSTEM_INTERFACE_READINESS_PROFILES = SYSTEM_INTERFACE_PROFILES.map(
+SYSTEM_INTERFACE_PROFILES.map(
   (profile) => profile.readinessProfile
 );
+var BUILT_IN_VALIDATED_PROFILE_IDS = SYSTEM_INTERFACE_PROFILES.filter(
+  (profile) => profile.validation === "built-in"
+).map((profile) => profile.readinessProfile);
 var SystemInterfaceReadinessProfileSchema = z.string().trim().min(1);
 var SystemInterfaceResourceScopeSchema = z.array(ModelIdSchema).default([]);
 var SystemApiInterfaceReadinessContractSchema = z.object({
@@ -9090,7 +9112,7 @@ var SystemApiInterfaceSchema = z.object({
   readinessContract: SystemApiInterfaceReadinessContractSchema.optional()
 }).strict();
 function isReservedPlatformProfileId(profileId) {
-  return SYSTEM_INTERFACE_READINESS_PROFILES.includes(profileId);
+  return BUILT_IN_VALIDATED_PROFILE_IDS.includes(profileId);
 }
 function isBuiltInReadinessProfile(profileId) {
   return isReservedPlatformProfileId(profileId) || getBuiltInReadinessProfile(profileId) !== void 0;
@@ -27635,6 +27657,8 @@ var mockAcqDb = (overrides) => createMockAdapter(
     "addCompaniesToList",
     "updateCompanyStage",
     "updateContactStage",
+    "clearCompanyStages",
+    "clearContactStages",
     "createCompany",
     "upsertCompany",
     "updateCompany",
@@ -27658,6 +27682,8 @@ var mockAcqDb = (overrides) => createMockAdapter(
     "getDealById",
     "getContactById",
     "getCompanyById",
+    "listDeals",
+    "getDealPipelineAnalytics",
     "updateDiscoveryData",
     "updateProposalData",
     "markProposalSent",
@@ -27734,6 +27760,8 @@ var mockList = (overrides) => createMockAdapter(
     "recordExecution",
     "updateCompanyStage",
     "updateContactStage",
+    "clearCompanyStages",
+    "clearContactStages",
     "listPendingCompanyIds",
     "listPendingContactIds"
   ],

package/dist/worker/index.d.ts

@@ -6654,7 +6654,7 @@ declare const OntologyScopeSchema: z.ZodDefault<z.ZodObject<{
         aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
         route: z.ZodOptional<z.ZodString>;
     }, z.core.$loose>>>>;
-}, z.core.$strip>>;
+}, z.core.$strict>>;
 type OntologyScope = z.infer<typeof OntologyScopeSchema>;
 
 declare const SystemApiInterfaceSchema: z.ZodObject<{
@@ -7301,7 +7301,7 @@ declare const OrganizationModelSchema: z.ZodObject<{
             aliases: z.ZodOptional<z.ZodArray<z.ZodString>>;
             route: z.ZodOptional<z.ZodString>;
         }, z.core.$loose>>>>;
-    }, z.core.$strip>>>;
+    }, z.core.$strict>>>;
     resources: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodDiscriminatedUnion<[z.ZodObject<{
         id: z.ZodString;
         order: z.ZodDefault<z.ZodNumber>;
@@ -12539,7 +12539,7 @@ declare const notifications: TypedAdapter<NotificationToolMap>;
  * Typed wrapper over platform.call() for acquisition lead management.
  * Singleton export -- no credential needed (platform tool).
  *
- * 56 methods covering lists, companies, contacts, deals, list-stage updates, deal-sync, deal notes, deal tasks, enrichment, and social monitoring operations.
+ * 60 methods covering lists, companies, contacts, deals, list-stage updates, deal-sync, deal notes, deal tasks, enrichment, and social monitoring operations.
  * organizationId is injected server-side by the dispatcher -- never sent from the SDK.
  */
 
@@ -12613,9 +12613,9 @@ declare const list: TypedAdapter<ListToolMap>;
 /**
  * Artifacts Platform Tool Adapter
  *
- * Focused wrapper for the org-scoped governing-document store (rules
- * documents, idea banks, ICP docs). Singleton export -- no credential needed
- * (platform tool).
+ * Focused wrapper for the org-scoped governing-document store, keyed by
+ * owner and kind, for acquisition's audits, proposals, and ICP docs.
+ * Singleton export -- no credential needed (platform tool).
  *
  * `kind` convention: any artifact written for the content pipeline (an
  * `ownerKind: 'organization'` document -- a selection brief, an idea bank,
@@ -12645,13 +12645,23 @@ declare const artifacts: TypedAdapter<ArtifactsToolMap>;
  * Decision 4, enforced by omission).
  *
  * `createAttempt.sourceExecutionId` is `string | null | undefined` on the
- * underlying `ContentToolMap` (it is nullable for a future non-execution
- * caller), but this adapter narrows it to a **required** `string` for
- * producer-authored attempts -- the SDK-layer analog of `organizationId`
- * never appearing in the params type at all. A worker always has its own
- * `context.executionId` available, so requiring it here is a compile-time
- * guarantee that a workflow cannot forget it, matching the step-state
- * model's write-at-start/patch-at-end contract (see `mock-pipeline-shared.ts`).
+ * underlying `ContentToolMap`, and this adapter narrows it to a **required
+ * key with a nullable value**: the caller must supply it, but may supply
+ * `null`. Requiring the key is the SDK-layer analog of `organizationId` never
+ * appearing in the params type at all -- a worker always has its own
+ * `context.executionId`, so a producer cannot silently forget it, which is
+ * what the step-state model's write-at-start/patch-at-end contract depends on
+ * (see `mock-pipeline-shared.ts`).
+ *
+ * Permitting `null` is what makes a backfill expressible. The narrowing was
+ * briefly `sourceExecutionId: string`, which excluded the one-time import of
+ * records that have no execution behind them and never will -- core's
+ * `CreateContentItemAttemptRequestSchema` types it `UuidSchema.nullable().optional()`
+ * and the DB column is nullable, so the restriction was an SDK compile-time
+ * guard rather than a data constraint, and the API already accepts null
+ * (`reviewItem` writes a review attempt with `sourceExecutionId: null`).
+ * Passing `null` states "no execution, and never will be"; it is not an
+ * invitation to invent an execution id to satisfy the type.
  *
  * `createAttempt.status` is a real field on `ContentToolMap` -- a producer
  * starting a step sends `'running'` and the dispatcher forwards it. It was
@@ -12663,7 +12673,7 @@ declare const artifacts: TypedAdapter<ArtifactsToolMap>;
 /** The content adapter's public shape -- `TypedAdapter<ContentToolMap>` with `createAttempt` narrowed. */
 type ContentAdapter = Omit<TypedAdapter<ContentToolMap>, 'createAttempt'> & {
     createAttempt: (params: Omit<ContentToolMap['createAttempt']['params'], 'sourceExecutionId'> & {
-        sourceExecutionId: string;
+        sourceExecutionId: string | null;
     }) => Promise<ContentToolMap['createAttempt']['result']>;
 };
 /**

package/dist/worker/index.js

@@ -6700,6 +6700,8 @@ var acqDb = createAdapter("acqDb", [
   "addCompaniesToList",
   "updateCompanyStage",
   "updateContactStage",
+  "clearCompanyStages",
+  "clearContactStages",
   // Company operations
   "createCompany",
   "upsertCompany",
@@ -6726,6 +6728,8 @@ var acqDb = createAdapter("acqDb", [
   "getDealById",
   "getContactById",
   "getCompanyById",
+  "listDeals",
+  "getDealPipelineAnalytics",
   // Deal transitions
   "updateDiscoveryData",
   "updateProposalData",
@@ -6803,6 +6807,8 @@ var list = createAdapter("list", [
   "recordExecution",
   "updateCompanyStage",
   "updateContactStage",
+  "clearCompanyStages",
+  "clearContactStages",
   "listPendingCompanyIds",
   "listPendingContactIds"
 ]);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.47.0",
+  "version": "1.48.0",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -55,9 +55,9 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.62.0",
-    "@repo/eslint-config": "0.0.0",
-    "@repo/typescript-config": "0.0.0"
+    "@repo/core": "0.63.0",
+    "@repo/typescript-config": "0.0.0",
+    "@repo/eslint-config": "0.0.0"
   },
   "scripts": {
     "lint": "eslint src --max-warnings 0",

package/reference/_navigation.md

@@ -210,7 +210,7 @@ Universal scaffold documentation for all SDK projects. Source locations are co-l
 
 The bundled agent-rule corpus. Locations are relative to this file -- the `reference/` root of the installed `@elevasis/sdk` package -- so every row resolves offline in a cloned project with no monorepo.
 
-Agent rules indexed: 18.
+Agent rules indexed: 19.
 
 ### Core Config
 
@@ -226,6 +226,7 @@ Agent rules indexed: 18.
 | Operations | `rules/operations.md` | Platform workflows, agents, resource definitions, and deployment for the operations/ surface | Editing anything under `operations/` -- workflows, agents, or resource definitions. |
 | Platform | `rules/platform.md` | Platform conventions -- SDK workflows, agents, deployment, resource registry | Authoring a workflow or agent definition, or registering a resource in the registry. |
 | Deployment | `rules/deployment.md` | Deployment workflow -- check-first, dev vs prod, version bumping, common errors | Before any deploy -- a plain `run deploy` targets production by default. |
+| Content | `rules/content.md` | Building the content System behind the shipped pipeline, item, and distribution routes -- which recipe to read, and the catalog vocabulary that is model-owned rather than coded | Editing anything under `ui/src/routes/content/` -- items, pipelines, distributions, or a review gate. |
 | Execution Model | `rules/execution.md` | Execution model -- timeouts, memory, concurrency, org isolation, runtime constraints | Hitting a timeout, memory ceiling, concurrency limit, or org-isolation question at runtime. |
 | Agent Runtime | `rules/agent-runtime.md` | Agent runtime behavior -- iteration response shape, session memory and replay, prose normalization, and why a redeploy is what makes a platform fix live | Debugging an agent turn -- a missing reply, a corrupted one, a session that forgot, or an unenforced schema. |
 | Error Handling | `rules/error-handling.md` | Error handling -- ExecutionError vs PlatformToolError, retry logic, no auto-retry | Writing or debugging a step handler that throws, catches, or retries. |
@@ -235,7 +236,7 @@ Agent rules indexed: 18.
 
 | Rule | Location | Description | When to Load |
 | --- | --- | --- | --- |
-| Organization OS | `rules/organization-os.md` | Organization OS orientation -- what the semantic contract layer is, which surface owns what, and where the full reference docs live; concrete edit rules live in organization-model.md | Before an org-model change, to see how Systems, ontology, resources, policies, and knowledge relate. |
+| Organization OS | `rules/organization-os.md` | Organization OS orientation -- what the semantic contract layer is, which surface owns what, and where the full reference docs live; concrete edit rules live in organization-model.md | Before an org-model change, to see how Systems, ontology, resources, roles, and knowledge relate. |
 | Package Taxonomy | `rules/package-taxonomy.md` | Package taxonomy (consumer view) -- external projects consume the published @elevasis/* surface only; workspace-internal @repo/elevasis-* packages are not installable here | Adding a dependency, or resolving an `@elevasis/*` import or subpath question. |
 | Active Change Index | `rules/active-change-index.md` | Which bundled references to load for platform areas under active change, and how to resolve drift between the bundled snapshot and live platform behavior | Before trusting a stable scaffold doc in a fast-moving area -- lists what in-progress work overrides. |
 

package/reference/_reference-manifest.json

@@ -949,6 +949,16 @@
       "sourcePath": "packages/sdk/docs/agent-rules/deployment.md",
       "referencePath": "rules/deployment.md"
     },
+    {
+      "packageName": "@elevasis/sdk",
+      "title": "Content",
+      "description": "Building the content System behind the shipped pipeline, item, and distribution routes -- which recipe to read, and the catalog vocabulary that is model-owned rather than coded",
+      "group": "Operations",
+      "order": 4,
+      "loadWhen": "Editing anything under `ui/src/routes/content/` -- items, pipelines, distributions, or a review gate.",
+      "sourcePath": "packages/sdk/docs/agent-rules/content.md",
+      "referencePath": "rules/content.md"
+    },
     {
       "packageName": "@elevasis/sdk",
       "title": "Execution Model",
@@ -995,7 +1005,7 @@
       "description": "Organization OS orientation -- what the semantic contract layer is, which surface owns what, and where the full reference docs live; concrete edit rules live in organization-model.md",
       "group": "Orientation",
       "order": 1,
-      "loadWhen": "Before an org-model change, to see how Systems, ontology, resources, policies, and knowledge relate.",
+      "loadWhen": "Before an org-model change, to see how Systems, ontology, resources, roles, and knowledge relate.",
       "sourcePath": "packages/sdk/docs/agent-rules/organization-os.md",
       "referencePath": "rules/organization-os.md"
     },

package/reference/packages/core/src/organization-model/README.md

@@ -35,24 +35,27 @@ The model is versioned and currently validates against `version: 1`.
 Top-level fields:
 
 - `version`
+- `snapshotHash`
 - `domainMetadata`
 - `branding`
 - `navigation`
-- `sales`
-- `prospecting`
-- `projects`
 - `identity`
+- `clients`
 - `customers`
 - `offerings`
 - `roles`
 - `goals`
 - `systems`
+- `ontology`
 - `resources`
-- `capabilities`
-- `statuses`
+- `topology`
+- `actions`
+- `entities`
 - `knowledge`
 
-The pure collection domains are id-keyed maps: `systems`, `roles`, `goals`, `customers`, `offerings`, `resources`, `capabilities`, and `statuses`. The map key must match the entry `id`. Entries carry `order` for deterministic ordered views; use `listDomain(record)` when order matters.
+`sales`, `prospecting`, `projects`, `statuses`, and `policies` were removed from the top-level contract; do not author against them.
+
+The pure collection domains are id-keyed maps: `systems`, `roles`, `goals`, `clients`, `customers`, `offerings`, `resources`, `actions`, `entities`, and `knowledge`. `ontology` is an `OntologyScope` object (not an id-keyed map at the top level) and `topology` is a relationships record. The map key must match the entry `id` for id-keyed domains. Entries carry `order` for deterministic ordered views; use `listDomain(record)` when order matters.
 
 Resource identity is authored in `resources`. Runtime workflows, agents, integrations, and scripts import those descriptors, derive `resourceId` and kind from them, and attach executable behavior in operations code.
 

package/reference/rules/content.md

@@ -0,0 +1,27 @@
+---
+description: Building the content System behind the shipped pipeline, item, and distribution routes -- which recipe to read, and the catalog vocabulary that is model-owned rather than coded
+paths:
+  - ui/src/routes/content.tsx
+  - ui/src/routes/content/**
+---
+<!-- @generated by packages/sdk/scripts/copy-reference-docs.mjs -- DO NOT EDIT -->
+<!-- Regenerate: pnpm scaffold:sync -->
+
+
+# Content
+
+- **These routes render and do nothing until the System behind them is built.** Unlike CRM and lead-gen, `content` has no entry yet in `core/config/organization-model/systems.ts` -- the routes gate on `accessKey="content"` with no System, ontology, or resources behind it on a fresh project.
+- **One recipe covers this surface and no other rule names it.** `extend-content.md` covers the System, its pipeline/step/status/pillar/platform catalogs, and the `content` workflow adapter. Read it before authoring.
+- **A pipeline is data, not code.** Pipelines and their ordered steps are catalog records (`content:catalog/pipeline`, `content:catalog/{pipelineId}-steps`); adding one is an org-model edit plus one workflow per step, never a shared-UI or route change.
+- **Pipeline, step, status, and pillar vocabulary is model-owned, never a local constant.** Copying catalog entries into a `const` is architecturally excluded -- every project owns its own model, so the copy rots silently. Read catalog entries from the resolved model.
+- **`apiInterface` is adopt-only here.** Content uses the flat `system.apiInterface` marker on the `content` System path; readiness is derived from scoped resources, ontology bindings, and required catalogs -- never invent a readiness profile.
+
+## Related Rules
+
+- **organization-model.md** -- authoring the System, its ontology catalogs, and the resource descriptors
+- **operations.md** -- registering the per-step workflows so they actually deploy
+- **ui.md** -- the navigation and surface declarations these pages bind to
+
+## References
+
+- `operations/node_modules/@elevasis/sdk/reference/scaffold/recipes/extend-content.md` -- the System, catalog model, and content workflow adapter build recipe

package/reference/rules/organization-model.md

@@ -11,7 +11,7 @@ paths:
 
 # Organization Model Edit Guide
 
-`core/config/organization-model.ts` is the single source of truth for this project's organizational identity -- it encodes customers, offerings, roles, goals, Systems, ontology, Policies, Knowledge, config, and Resources descriptors that agents, workflows, and the UI shell all consume at runtime. This rule owns the edit rules for that file; `organization-os.md` is the orientation and reference index around it.
+`core/config/organization-model.ts` is the single source of truth for this project's organizational identity -- it encodes customers, offerings, roles, goals, Systems, ontology, Knowledge, config, and Resources descriptors that agents, workflows, and the UI shell all consume at runtime. This rule owns the edit rules for that file; `organization-os.md` is the orientation and reference index around it.
 
 New semantic authoring should start in system-colocated `ontology` scopes. Top-level `entities` and top-level `actions` remain compatibility mirrors while published consumers finish moving to compiled ontology indexes. `System.content` is retired.
 
@@ -53,7 +53,7 @@ Bare `/om` runs the layered flow (identity → customers → offerings → roles
 - `System.config` owns system-local JSON settings and defaults.
 - `resources` own executable workflow/agent descriptors, `systemPath`, owners, governance status, code references, and runtime implementation links. Resource identity is authored once in the id-keyed `resources` map; operations imports those descriptors and derives runtime `resourceId` / `type` while assembling the `DeploymentSpec`.
 - `resource.ontology.actions` describes the ontology actions a Resource performs, `resource.ontology.primaryAction` names the default/selectable action when a Resource has one, and `resource.ontology` also describes reads, writes, catalog use, and emitted events.
-- `topology.relationships` owns durable operational wiring between Systems, Resources, ontology nodes, policies, roles, triggers, checkpoints, and external resources. Keep credential values, provider webhook mechanics, deployment environment settings, execution logs, and per-run scheduler state outside the OM.
+- `topology.relationships` owns durable operational wiring between Systems, Resources, ontology nodes, roles, triggers, checkpoints, and external resources. Keep credential values, provider webhook mechanics, deployment environment settings, execution logs, and per-run scheduler state outside the OM.
 - `knowledge` owns long-form playbooks, strategies, references, and governance context.
 - Top-level `entities` and top-level `actions` are compatibility mirrors only. Keep them aligned when current published consumers still need them, rather than inventing a separate source of truth, but do not treat them as the primary authoring surface.
 
@@ -63,7 +63,13 @@ Do not add `sales.actions` to the org model -- the v1 server-side override surfa
 
 ## `System.apiInterface`
 
-`System.apiInterface` is an adopt-only marker for platform-provided API capabilities, with derived readiness requirements. Use only cataloged profiles from `scaffold/reference/system-interface-capabilities.md`, on their convention-locked System paths such as `sales.lead-gen` and `sales.crm`, and satisfy readiness through ontology/resources/catalogs/topology authoring. Custom Systems do not declare `apiInterface` and must never invent readiness profiles; route custom behavior through workflows/operations and the OM layers this project owns.
+`System.apiInterface` is an adopt-only marker for platform-provided API capabilities, with derived readiness requirements. Use only cataloged profiles from `scaffold/reference/system-interface-capabilities.md`, on their convention-locked System paths -- `sales.lead-gen`, `sales.crm`, and `content`. Satisfy readiness through ontology/resources/catalogs/topology authoring. A System that adopts no cataloged capability does not declare `apiInterface` and must not invent a readiness profile; route that behavior through workflows/operations and the OM layers this project owns.
+
+**Why the catalog is closed, and why that is not a ceiling.** A `readinessProfile` is not a label you choose -- it names a capability the platform API actually gates a route on, so only the platform can mint one. `SystemInterfaceReadinessProfileSchema` accepts any non-empty string, but that permissiveness lives at the schema layer and is not a statement that any id is meaningful: an uncataloged id names no route, so the System computes as **ready** and every call still fails. That is strictly worse than a missing marker, which at least reports `missing-interface`. If your project needs an API capability that is not cataloged, that is a platform request -- adding a route and a catalog entry -- not something to work around locally by inventing an id.
+
+**Adopting `content`.** `content.api` gates every `/api/content/*` and `/api/external/content/*` route. It is cataloged and adoptable, and unlike the three `sales.*` profiles it is **contract-validated**: its structural requirements differ per project (each declares its own pipeline step catalog), so a System adopting it MUST declare a `readinessContract` alongside it. Omitting the contract produces `missing-readiness-contract` at deploy preflight.
+
+`registerBuiltInReadinessProfile` is **not** available to you as an extension point, despite what older guidance said. It mutates an in-process registry, and the readiness assertion that gates the API runs in the API process -- a registration made from your worker is never seen by it. `readinessContract` is your route to structural readiness.
 
 A System with no `apiInterface` is the designed opt-out for a capability this project does not use. That absence is silent by construction and is NOT a defect -- never "fix" it by adding a marker. The anomaly is a stub marker with `resourceIds: []`, which the deploy gate rejects.
 

package/reference/rules/organization-os.md

@@ -7,7 +7,7 @@ description: Organization OS orientation -- what the semantic contract layer is,
 
 # Organization OS
 
-Organization OS is the semantic contract layer defining how organizations, Systems, Actions, ontology, resources, policies, roles, goals, knowledge, and runtime surfaces relate. This project consumes it through published `@elevasis/core` / `@elevasis/sdk` configuration and does not maintain the upstream schema.
+Organization OS is the semantic contract layer defining how organizations, Systems, Actions, ontology, resources, roles, goals, knowledge, and runtime surfaces relate. This project consumes it through published `@elevasis/core` / `@elevasis/sdk` configuration and does not maintain the upstream schema.
 
 **This rule is orientation and an index only.** The concrete edit rules -- the `/om` ceremony and its gates, `System.apiInterface` versus ontology `interface` records, resource identity and `systemPath` attachment, the ontology/config/knowledge authoring boundary, and validation -- live in `organization-model.md`. Read that rule before changing anything under `core/config/`; never author org-model changes from this rule alone.
 
@@ -26,7 +26,7 @@ Organization OS is the semantic contract layer defining how organizations, Syste
 
 - **Platform configuration:** `systems`, `branding`, `navigation`
 - **Organizational reality:** `identity`, `customers`, `offerings`, `roles`, `goals`
-- **Governance:** `resources`, `policies`, and resource-to-System relationships
+- **Governance:** `resources` and resource-to-System relationships
 - **Ontology, config, and knowledge:** `System.ontology` owns durable semantic contracts (object types, action types, catalog types, link types, event types, interfaces, surfaces). `System.config` owns system-local JSON settings and defaults. `knowledge` is a flat id-keyed map of playbooks, strategies, and references that explain or govern systems and ontology records.
 
 `System.apiInterface` is a flat, adopt-only System field marking a platform-provided API capability -- not an ontology record and not a general extension point. Its authoring rules, readiness requirements, and opt-out semantics are owned by `organization-model.md`.