@elevasis/sdk 1.46.0 → 1.48.0

package/reference/sdk/cli-management.mdx

@@ -1,11 +1,11 @@
 ---
 title: CLI Management Commands
-description: elevasis-sdk management commands -- project, note, acquisition, client, agent, session, queue, schedule, om, ui, and skill subcommand families
+description: elevasis-sdk management commands -- project, note, acquisition, client, agent, session, queue, schedule, om, ui, skill, and content subcommand families
 ---
 
 This page covers the domain management commands for `elevasis-sdk`. For core SDK commands (check, deploy, exec, resources, executions, describe, creds, rename), see [CLI Reference](cli.mdx).
 
-Every command family on this page -- `project`, `note`, `acquisition`, `client`, `agent`, `session`, `queue`, `schedule`, `om:doctor`, and `request` -- also accepts `--prod` to target production, overriding `NODE_ENV=development` (live as of `@elevasis/sdk` 1.45.0). See [CLI Reference's Global Flags](cli.mdx#global-flags) for the full description; per-command flag tables below list `--api-url` and other command-specific flags only, not `--prod` or `--json`.
+Every command family on this page -- `project`, `note`, `acquisition`, `client`, `agent`, `session`, `queue`, `schedule`, `om:doctor`, `request`, and `content` -- also accepts `--prod` to target production, overriding `NODE_ENV=development` (live as of `@elevasis/sdk` 1.45.0). See [CLI Reference's Global Flags](cli.mdx#global-flags) for the full description; per-command flag tables below list `--api-url` and other command-specific flags only, not `--prod` or `--json`.
 
 ---
 
@@ -237,7 +237,7 @@ elevasis-sdk note:create --content <text>
 | Flag                      | Description                                                                               |
 | ------------------------- | ----------------------------------------------------------------------------------------- |
 | `--content <text>`      | Required. The note body text                                                              |
-| `--user <email>`        | Target user email. Defaults to the API key owner when omitted                             |
+| `--user <email>`        | **Required.** Target user email                                                           |
 | `--title <text>`        | Optional note title                                                                       |
 | `--priority <priority>` | Priority level: `low`, `normal` (default), `high`, or `urgent`                            |
 | `--pinned`                | Pin the note to the top of the panel                                                      |
@@ -248,8 +248,9 @@ elevasis-sdk note:create --content <text>
 **Behavior:**
 
 - Posts to `POST /api/external/user-notes`
-- When `--user` is omitted the note is created for the identity bound to the API key (the caller)
-- When `--user` is provided the platform resolves the email to a Supabase user UUID and verifies the resolved user is an active member of the calling organization before writing
+- `--user` is **not optional in practice**: the CLI omits `user_email` from the body when the flag is absent, and `ExternalCreateUserNoteBodySchema` requires it, so the call returns 400
+- There is no "API key owner" to default to. An API key is org-wide and its actor is the key itself, not a person -- defaulting would write a note into some human's private space they never asked for. See `.claude/rules/actor-attribution.md`
+- The platform resolves the email to a Supabase user UUID and verifies the resolved user is an active member of the calling organization before writing
 - External agent-created notes are always private; org-shared visibility is a signed-in UI capability, not a broadcast CLI mode
 - The `--source` flag is recorded as the `source` column in `user_notes`; agent runtimes should pass their resource ID here so users can see which workflow created the note
 - Priority `normal` produces no badge in the UI; `high` renders orange, `urgent` renders red, `low` renders dimmed gray
@@ -257,8 +258,8 @@ elevasis-sdk note:create --content <text>
 **Examples:**
 
 ```bash
-# Create a note for the API key owner
-elevasis-sdk note:create --content "Deal X has stalled -- follow up needed"
+# Create a note for a named user
+elevasis-sdk note:create --content "Deal X has stalled -- follow up needed" --user ops@acme.com
 
 # Create a high-priority pinned note for a specific user
 elevasis-sdk note:create \
@@ -677,7 +678,7 @@ At least one field must be provided. `--description` and `--clear-description` a
 
 Knowledge graph inspection, plus an Organization Model write surface (`om:scaffold:*`, `om:rename`, `om:deprecate`). The `om:*` (Organization Model) commands expose knowledge graph traversal via the CLI. `om:*` and `knowledge:*` are aliases of the same subcommands for the read-only surface described below -- the write commands are registered under `om:*` only, with no `knowledge:*` alias.
 
-**Path axes for `knowledge:ls` / `om:ls`:** `/by-system/<id>`, `/by-ontology/<ontologyId>`, `/by-kind/<kind>`, `/by-owner/<ownerId>`, `/by-domain/<domain>` (enumerate all items in a domain: `clients`, `roles`, `policies`, `customers`, `offerings`, `goals`), `/by-item/<domain>/<itemId>` (single domain-item profile), `/graph/<nodeId>/governs`, `/graph/<nodeId>/governed-by`, `/<nodeId>` (single node), `/all-systems`, `/all-resources`, `/all-roles`.
+**Path axes for `knowledge:ls` / `om:ls`:** `/by-system/<id>`, `/by-ontology/<ontologyId>`, `/by-kind/<kind>`, `/by-owner/<ownerId>`, `/by-domain/<domain>` (enumerate all items in a domain: `clients`, `roles`, `customers`, `offerings`, `goals`), `/by-item/<domain>/<itemId>` (single domain-item profile), `/graph/<nodeId>/governs`, `/graph/<nodeId>/governed-by`, `/<nodeId>` (single node), `/all-systems`, `/all-resources`, `/all-roles`.
 
 - `knowledge:ls <path>` -- list nodes/edges for the mount; default output is an id + summary table, `--json` returns `{ path, mount, args, results }`.
 - `knowledge:cat <id>` -- render a node's `body` MDX to stdout; `--json` returns the full node object (body, links, owners, timestamps).
@@ -703,7 +704,7 @@ These are registered as `knowledge:*` subcommands on `elevasis-sdk`. Both the SD
 
 ### knowledge:search
 
-Universal keyword search across the entire Organization Model (systems, resources, knowledge, ontology, roles, policies). Alias: `om:search`.
+Universal keyword search across the entire Organization Model (systems, resources, knowledge, ontology, roles). Alias: `om:search`.
 
 ```bash
 elevasis-sdk knowledge:search <query> [--limit <n>] [--kinds <list>] [--json] [--ids-only]
@@ -890,29 +891,174 @@ The same coverage gate runs inside `elevasis-sdk check` when the coverage regist
 
 ---
 
+## elevasis-sdk content:\*
+
+Read and review access to the content platform: content items, their attempts and distributions, the pipeline step contracts they move through, and the one write this namespace owns -- clearing an open `queued` review gate. Producing content -- creating items, recording attempts, opening distributions -- is workflow-side work through the `content` adapter from `@elevasis/sdk/worker`; see `packages/sdk/docs/scaffold/recipes/extend-content.md`. This namespace is the operator surface for the pipeline that adapter feeds, not a second way to write to it.
+
+Matches the DB-backed namespaces documented above (`project:`, `client:`, `note:`, `queue:`, `schedule:`): pretty-printed JSON by default, `--pretty` for human-readable output.
+
+### Command Boundary
+
+- `content:*` is the operator surface for the **content platform System** -- pipelines, items, attempts, and distributions, as documented in `packages/sdk/docs/scaffold/recipes/extend-content.md`. It reads the state a producer workflow is moving an item through, and it clears the review gates a human has to sign off on.
+- `content:*` is **not** the Organization Model's own `System.content` field. That is a generic, retired bridge input every System carries for compatibility and has nothing to do with the content platform System documented here, despite sharing a name.
+- `content:*` is **not** the acquisition domain's own material -- deals, companies, and CRM records reached through `acquisition:*` and `client:*`. A content item can be _about_ an acquisition client (`clientId` on the item), but the content platform does not read or write acquisition records, and `acquisition:*` does not read or write content items.
+- `content:board` renders the same columns, gates, and waiting counts the Command Center board shows, and it is the **same** placement rule rather than a second copy of it. It was deferred until 2026-08-15 because `packages/sdk` has no `@elevasis/ui` dependency and so could not reach `deriveContentBoard`; the fix was to move that helper and `getContentItemIdentity` into `@repo/core/content`, which `@repo/ui` now re-exports. Duplicating the rule inside the CLI was rejected outright -- two copies of a placement rule diverge, which is exactly what happened to the open-review-gate predicate before it was consolidated into `review-gates.ts`.
+
+### Reads
+
+```bash
+elevasis-sdk content:list --status queued --pipeline-id short-form-repurpose
+elevasis-sdk content:get <itemId>
+elevasis-sdk content:board <pipelineId> --pretty
+elevasis-sdk content:queue
+elevasis-sdk content:pipeline
+elevasis-sdk content:pipeline <pipelineId>
+elevasis-sdk content:distributions --pipeline-id short-form-repurpose
+elevasis-sdk content:source-assets --kind transcript
+elevasis-sdk content:source-asset <sourceAssetId>
+```
+
+- `content:list` -- list content items. Filters: `--status`, `--pillar`, `--pipeline-id`, `--client-id`, `--reviewed-by`, `--search` (matches title), `--limit`, `--offset`.
+- `content:get <itemId>` -- one item plus its full attempt history and its distributions, in a single response. Each attempt carries a `sourceExecutionId`, so this call is the item's execution lineage in one hop -- feed any id straight into `elevasis-sdk execution` / `pnpm exec elevasis execution`.
+- `content:board <pipelineId>` -- one pipeline rendered as columns: each declared step in `order`, each card at the first step its `processingState` has not recorded as `success`, and a gate with a waiting count on every `live` or `queued` step. Two buckets sit outside the columns: `done` (every declared step succeeded) and `unplaced` (the item's `processingState` names only steps the pipeline no longer declares). Unplaced items are never folded into column 1, so a non-empty bucket is a real signal that the step catalog moved underneath live items. `--limit` defaults to 100, the API's page ceiling for this route, and the command reports a **partial** board rather than truncating silently when a pipeline holds more items than one page.
+- `content:queue` -- items sitting on an open `queued`-gate review. Each row prints the item, the `stepKey` of the gate it is waiting on, and the attempt that opened it. This is the list `content:review` reads from -- see "Why `--step` is required" below.
+- `content:pipeline [id]` -- with no id, lists pipeline templates; with an id, returns that pipeline's step contract (step keys and review modes). Read from the **deployed** Organization Model snapshot, not a local project model -- a model edit that has not been redeployed produces a stale-snapshot 503 that looks like a code bug.
+- `content:distributions` -- list distribution rows (one per platform/format target per item). Filters: `--content-item-id`, `--pipeline-id`, `--platform`, `--status`, `--limit`, `--offset`.
+- `content:source-assets` -- list source assets, the raw material items are derived from. Filters: `--kind`, `--limit`, `--offset`. `--pretty` omits payloads, which can run to hundreds of kilobytes.
+- `content:source-asset <sourceAssetId>` -- one source asset in full, payload included. This is how you read back text you just created.
+
+**API routes:** `GET /api/external/content/items`, `/api/external/content/items/:itemId`, `/api/external/content/queue`, `/api/external/content/pipelines`, `/api/external/content/pipelines/:id`, `/api/external/content/distributions`, `/api/external/content/source-assets`, `/api/external/content/source-assets/:sourceAssetId`.
+
+### content:review
+
+One of two write commands in this namespace. Everything else that writes to an item -- creating it, recording an attempt, opening a distribution -- is producer work through the `content` worker adapter, not a CLI command.
+
+**Synopsis:**
+
+```
+elevasis-sdk content:review <itemId> --step <key> (--approve | --reject) --user <email>
+                            [--feedback <text>] [--reason <text>]
+                            [--prod] [--api-url <url>] [--pretty]
+```
+
+**Flags:**
+
+| Flag                  | Description                                           |
+| --------------------- | ----------------------------------------------------- |
+| `--step <key>`      | Required. The `stepKey` of the `queued` gate to clear |
+| `--approve`           | Approve the item at that step                         |
+| `--reject`            | Reject the item at that step. Requires `--reason`     |
+| `--user <email>`    | Required. The acting reviewer's email                 |
+| `--feedback <text>` | Optional reviewer feedback, recorded on the review    |
+| `--reason <text>`   | Rejection reason. Required when `--reject` is used    |
+| `--api-url <url>`   | Override the API base URL                             |
+| `--pretty`            | Human-readable output instead of raw JSON             |
+
+`--approve` and `--reject` are mutually exclusive; exactly one is required.
+
+**Behavior:**
+
+Posts to `POST /api/external/content/items/:itemId/review`.
+
+**Why `--step` is required.** Nothing makes a `queued` gate pause the pipeline -- a producer workflow can keep moving an item forward while an earlier step's review is still open, so a single item can have several `queued` gates open at the same time. A live run found exactly that: one item ended up with three open gates at once, and resolving the target server-side (by "most recent step-keyed attempt") cleared a step that was not a gate at all. There is no safe way to infer which gate a caller means, so the caller names it. The operator flow is `content:queue` to see which gates are open and each one's `stepKey`, then `content:review <itemId> --step <that key>` to clear the one intended.
+
+**Why `--user` is required.** API keys have no owner -- there is no signed-in user on the API-key path -- and both `content_items.reviewed_by` and `content_item_attempts.created_by` are real foreign keys to `users`. The reviewer's identity has to come from somewhere, so the caller supplies it: `--user` names an email, which must resolve to an active member of the API key's organization.
+
+**Examples:**
+
+```bash
+# Approve a clip-selection gate
+elevasis-sdk content:review 3f9c1e20-... --step clip-selection --approve --user ops@acme.com --pretty
+
+# Reject with a reason
+elevasis-sdk content:review 3f9c1e20-... --step copy-generation --reject --user ops@acme.com --reason "Off-brand tone" --pretty
+```
+
+### content:source-asset:create
+
+The namespace's second write command. It exists for a caller no other channel serves: an agent
+working from a terminal with an API key. A deployed workflow already creates source assets through
+`content.createSourceAsset` in the worker tool map, and a person uses the Command Center; a terminal
+agent can reach neither, and before this command `content_source_assets` was unreachable for it with
+no workaround.
+
+**Synopsis:**
+
+```
+elevasis-sdk content:source-asset:create --kind <kind> --title <title> (--text <value> | --url <url>)
+                                         [--field <key>] [--duration <seconds>] [--item <itemId>]
+```
+
+A source asset holds its content in one of two places, and the flags mirror that exactly: `--text` is
+inline content and lands in `payload`, `--url` is a reference and lands in `externalUrl`. They are
+mutually exclusive because an asset is one shape or the other.
+
+**There is no file upload, deliberately.** `storage_path` on the table is written by nothing, and
+`/api/storage` has no external mirror. A file lives wherever it already lives and the asset points at
+it with `--url`.
+
+**`--text` accepts `@path` to read a local file**, the same convention as `exec --input`. Anything not
+starting with `@` is the literal value. The CLI refuses content over 500KB locally rather than sending
+it for the server to reject -- that is `CONTENT_PAYLOAD_MAX_BYTES`, enforced by
+`ContentPayloadEnvelopeSchema`.
+
+**The payload key defaults to the `--kind` value.** `--kind transcript` writes `payload.transcript`,
+matching what the Organization Model's `content:catalog/source-asset-kind` declares for that kind.
+Pass `--field` when a kind's declared field is named differently. A wrong key writes successfully and
+produces an asset no producer can read, so check the kind's declaration if unsure.
+
+**An unlisted kind is legal and writes unvalidated.** URL-referencing kinds typically have no catalog
+entry at all -- the catalog declares payload fields, and a reference kind has none, so its URL is
+validated by `UrlSchema` on the request body instead. The consequence worth knowing: nothing can
+express "kind `youtube-video` requires `externalUrl`."
+
+**Examples:**
+
+```bash
+# Inline text from a local file
+elevasis-sdk content:source-asset:create --kind transcript --title "Episode 12" --text @transcript.txt --pretty
+
+# A reference, linked to an item in the same invocation
+elevasis-sdk content:source-asset:create --kind youtube-video --title "The talk" \
+  --url https://youtu.be/abc --duration 3600 --item 3f9c1e20-... --pretty
+```
+
+Posts to `POST /api/external/content/source-assets`, then `PATCH /api/external/content/items/:itemId`
+when `--item` is given. The link is a second call on purpose: the asset exists either way, so a failed
+link leaves a usable row to retry against rather than losing the content just written.
+
+**That `PATCH` is a link, not a general item update** -- `sourceAssetId` is the only field it accepts,
+and any other field is a 400. Editing an item's title, body, status, or pillar is producer work
+through `content.updateItem`, or a person's work in the Command Center. There is also no update or
+delete for a source asset: correct a bad one by creating a replacement and re-linking.
+
+**Implementation:** `packages/sdk/src/cli/commands/content/`
+
+---
+
 ## Appendix: Domain Status
 
 Current status of all SDK CLI domains. Domains marked `deferred` have no CLI commands yet.
 
-| Domain      | CLI surface                                                                                        | API surface                                                    | Status                        |
-| ----------- | -------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | ----------------------------- |
-| platform    | top-level SDK commands                                                                             | mixed platform APIs                                            | implemented                   |
-| project     | `project:*`                                                                                        | `apps/api/src/projects/`                                       | implemented                   |
-| knowledge   | `knowledge:*`                                                                                      | file/generated knowledge data                                  | implemented                   |
-| creds       | `creds *` nested Commander group                                                                   | credentials API                                                | implemented                   |
-| ui          | `ui:*`                                                                                             | local project file edits                                       | implemented                   |
-| request     | `request:submit`, `request:list`, `request:get`                                                    | requests API                                                   | implemented read/write scope  |
-| error       | `error resolve`, `error resolve-execution`                                                         | execution error APIs                                           | partial                       |
-| acquisition | `acquisition:list:*`, `acquisition:deal:*`                                                         | `/api/external/acquisition/lists*`, `/api/external/deals*`     | implemented read-only scope   |
-| client      | `client:*`                                                                                         | `/api/external/clients`                                        | implemented read/write scope  |
-| agent       | `agent:list`, `agent:get`                                                                          | `/api/external/agents*`                                        | implemented read-only scope   |
-| session     | `session:create`, `session:turn`, `session:messages`, `session:list`, `session:get`, `session:end` | `/api/external/sessions*`                                      | implemented multi-turn scope  |
-| queue       | `queue:list`, `queue:get`, `queue:select`, `queue:expire`, `queue:status`                          | `/api/external/command-queue*`                                 | implemented                   |
-| schedule    | `schedule:list`, `schedule:get`, `schedule:create`, `schedule:update`                              | `/api/external/task-scheduler/schedules*`                      | implemented                   |
-| skill       | `skill:scaffold`, `skill:check-coverage`                                                           | local CLI catalog and `.claude/registries/skill-coverage.json` | implemented developer tooling |
-| content     | none                                                                                               | not scoped here                                                | deferred                      |
-| seo         | none                                                                                               | not scoped here                                                | deferred                      |
-| monitoring  | none                                                                                               | not scoped here                                                | deferred                      |
+| Domain      | CLI surface                                                                                                                                                                                                    | API surface                                                    | Status                                                      |
+| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | ----------------------------------------------------------- |
+| platform    | top-level SDK commands                                                                                                                                                                                         | mixed platform APIs                                            | implemented                                                 |
+| project     | `project:*`                                                                                                                                                                                                    | `apps/api/src/projects/`                                       | implemented                                                 |
+| knowledge   | `knowledge:*`                                                                                                                                                                                                  | file/generated knowledge data                                  | implemented                                                 |
+| creds       | `creds *` nested Commander group                                                                                                                                                                               | credentials API                                                | implemented                                                 |
+| ui          | `ui:*`                                                                                                                                                                                                         | local project file edits                                       | implemented                                                 |
+| request     | `request:submit`, `request:list`, `request:get`, `request:update`, `request:delete`                                                                                                                            | requests API                                                   | implemented read/write scope                                |
+| error       | `error resolve`, `error resolve-execution`                                                                                                                                                                     | execution error APIs                                           | partial                                                     |
+| acquisition | `acquisition:list:*`, `acquisition:deal:*`                                                                                                                                                                     | `/api/external/acquisition/lists*`, `/api/external/deals*`     | implemented read-only scope                                 |
+| client      | `client:*`                                                                                                                                                                                                     | `/api/external/clients`                                        | implemented read/write scope                                |
+| agent       | `agent:list`, `agent:get`                                                                                                                                                                                      | `/api/external/agents*`                                        | implemented read-only scope                                 |
+| session     | `session:create`, `session:turn`, `session:messages`, `session:list`, `session:get`, `session:end`                                                                                                             | `/api/external/sessions*`                                      | implemented multi-turn scope                                |
+| queue       | `queue:list`, `queue:get`, `queue:select`, `queue:expire`, `queue:status`                                                                                                                                      | `/api/external/command-queue*`                                 | implemented                                                 |
+| schedule    | `schedule:list`, `schedule:get`, `schedule:create`, `schedule:update`                                                                                                                                          | `/api/external/task-scheduler/schedules*`                      | implemented                                                 |
+| skill       | `skill:scaffold`, `skill:check-coverage`                                                                                                                                                                       | local CLI catalog and `.claude/registries/skill-coverage.json` | implemented developer tooling                               |
+| content     | `content:list`, `content:get`, `content:board`, `content:queue`, `content:pipeline`, `content:distributions`, `content:review`, `content:source-assets`, `content:source-asset`, `content:source-asset:create` | `/api/external/content*`                                       | implemented read + review-write + source-asset-create scope |
+| seo         | none                                                                                                                                                                                                           | not scoped here                                                | deferred                                                    |
+| monitoring  | none                                                                                                                                                                                                           | not scoped here                                                | deferred                                                    |
 
 ### Promotion Criteria
 
@@ -925,4 +1071,4 @@ A domain should meet all four criteria before gaining a `*:list` / `*:get` surfa
 
 ---
 
-**Last Updated:** 2026-08-12
+**Last Updated:** 2026-08-14

package/reference/sdk/platform-tools/adapters-platform.mdx

@@ -11,16 +11,16 @@ Platform adapters are singletons — import them directly, no credential require
 | Adapter | Export | Methods | Description |
 | --- | --- | --- | --- |
 | Scheduler | `scheduler` | `createSchedule`, `updateAnchor`, `deleteSchedule`, `findByIdempotencyKey`, `deleteScheduleByIdempotencyKey`, `listSchedules`, `getSchedule`, `cancelSchedule`, `cancelSchedulesByMetadata`, `cancelScheduleByIdempotencyKey` | Scheduler — create, update, cancel, and query task schedules. |
-| Llm | `llm` | `generate` | LLM — generate structured or unstructured text via OpenAI, Anthropic, OpenRouter, or Google. |
+| Llm | `llm` | `generate` | LLM — generate structured or unstructured text via OpenAI, Anthropic, or OpenRouter. |
 | Storage | `storage` | `upload`, `download`, `createSignedUrl`, `delete`, `list` | Storage — upload, download, list, delete files, and create signed URLs in org-scoped buckets. |
 | Notifications | `notifications` | `create` | Notifications — send in-platform notifications to team members. |
-| AcqDb | `acqDb` | `listLists`, `createList`, `updateList`, `deleteList`, `addContactsToList`, `addCompaniesToList`, `updateCompanyStage`, `updateContactStage`, `createCompany`, `upsertCompany`, `updateCompany`, `getCompany`, `listCompanies`, `deleteCompany`, `createContact`, `upsertContact`, `updateContact`, `getContact`, `getContactByEmail`, `listContacts`, `deleteContact`, `bulkImportContacts`, `bulkImportCompanies`, `deactivateContactsByCompany`, `upsertDeal`, `getDealByEmail`, `getDealByEnvelopeId`, `updateDealEnvelopeId`, `getDealById`, `getContactById`, `getCompanyById`, `updateDiscoveryData`, `updateProposalData`, `markProposalSent`, `markProposalReviewed`, `updateCloseLostReason`, `updateFees`, `cacheInstantlyThreadIds`, `transitionItem`, `setContactNurture`, `cancelSchedulesAndHitlByEmail`, `cancelHitlByDealId`, `clearDealFields`, `deleteDeal`, `recordDealActivity`, `setDealStateKey`, `transitionDeal`, `loadDeal`, `createDealNote`, `listDealNotes`, `createDealTask`, `listDealTasks`, `listDealTasksDue`, `completeDealTask`, `mergeEnrichmentData`, `upsertSocialPosts` | AcqDb — full acquisition database: lists, companies, contacts, deals, notes, tasks, and enrichment. |
+| AcqDb | `acqDb` | `listLists`, `createList`, `updateList`, `deleteList`, `addContactsToList`, `addCompaniesToList`, `updateCompanyStage`, `updateContactStage`, `clearCompanyStages`, `clearContactStages`, `createCompany`, `upsertCompany`, `updateCompany`, `getCompany`, `listCompanies`, `deleteCompany`, `createContact`, `upsertContact`, `updateContact`, `getContact`, `getContactByEmail`, `listContacts`, `deleteContact`, `bulkImportContacts`, `bulkImportCompanies`, `deactivateContactsByCompany`, `upsertDeal`, `getDealByEmail`, `getDealByEnvelopeId`, `updateDealEnvelopeId`, `getDealById`, `getContactById`, `getCompanyById`, `listDeals`, `getDealPipelineAnalytics`, `updateDiscoveryData`, `updateProposalData`, `markProposalSent`, `markProposalReviewed`, `updateCloseLostReason`, `updateFees`, `cacheInstantlyThreadIds`, `transitionItem`, `setContactNurture`, `cancelSchedulesAndHitlByEmail`, `cancelHitlByDealId`, `clearDealFields`, `deleteDeal`, `recordDealActivity`, `setDealStateKey`, `transitionDeal`, `loadDeal`, `createDealNote`, `listDealNotes`, `createDealTask`, `listDealTasks`, `listDealTasksDue`, `completeDealTask`, `mergeEnrichmentData`, `upsertSocialPosts` | AcqDb — full acquisition database: lists, companies, contacts, deals, notes, tasks, and enrichment. |
 | Projects | `projects` | `listProjects`, `getProject`, `createProject`, `updateProject`, `deleteProject`, `listMilestones`, `createMilestone`, `updateMilestone`, `deleteMilestone`, `listTasks`, `getTask`, `createTask`, `updateTask`, `deleteTask`, `mergeTaskResumeContext`, `listNotes`, `createNote`, `updateNote`, `deleteNote` | Projects — manage delivery projects, milestones, tasks, notes, and resume context. |
 | Crm | `crm` | `getRecentActivity`, `listDeals`, `getDeal`, `getDealByEmail`, `createDealNote`, `listDealNotes`, `createDealTask`, `listDealTasks`, `listDealTasksDue`, `completeDealTask`, `recordActivity`, `deleteDeal` | CRM — read and update deals, notes, tasks, activity, and stage transitions. |
-| List | `list` | `getConfig`, `recordExecution`, `updateCompanyStage`, `updateContactStage`, `listPendingCompanyIds`, `listPendingContactIds` | List — list-scoped workflow execution tracking and stage updates. |
+| List | `list` | `getConfig`, `recordExecution`, `updateCompanyStage`, `updateContactStage`, `clearCompanyStages`, `clearContactStages`, `listPendingCompanyIds`, `listPendingContactIds` | List — list-scoped workflow execution tracking and stage updates. |
 | Pdf | `pdf` | `render`, `renderToBuffer` | PDF — render PDF documents from structured page definitions. |
 | Approval | `approval` | `create`, `deleteByMetadata` | Approval — create and manage HITL (human-in-the-loop) tasks. |
 | Execution | `execution` | `trigger`, `triggerAsync` | Execution — trigger other workflows or agents within the same organization. |
 | Email | `email` | `send` | Email — send platform emails (from notifications@elevasis.io) to organization members. |
-| Artifacts | `artifacts` | `listArtifacts`, `createArtifact`, `getActive` | Artifacts — org-scoped governing-document store for rules documents, idea banks, and ICP docs. |
-| Content | `content` | `createItem`, `getItem`, `listItems`, `updateItem`, `createAttempt`, `listAttempts`, `createDistribution`, `updateDistribution` | Content — create and query content_items/content_item_attempts/content_distributions rows for the content pipeline. |
+| Artifacts | `artifacts` | `listArtifacts`, `createArtifact`, `getActive` | Artifacts — org-scoped governing-document store, keyed by owner and kind, for acquisition's audits, proposals, and ICP docs. |
+| Content | `content` | `createItem`, `getItem`, `listItems`, `updateItem`, `createAttempt`, `listAttempts`, `updateAttempt`, `createSourceAsset`, `getSourceAsset`, `listSourceAssets`, `updateSourceAsset`, `createDistribution`, `updateDistribution` | Content — create, read, and update content_items/content_item_attempts/content_distributions/content_source_assets rows for the content pipeline. |

package/reference/sdk/platform-tools/index.mdx

@@ -191,8 +191,6 @@ const qualified = await platform.call({
 
 **Credential setup:** Create a credential with provider `supabase` -- config fields are `url` and `serviceRoleKey`. Workflows always use the service role key (server-side, no RLS).
 
-**`/database init`:** Guided setup that stores your Supabase credential, generates `data/schema.ts`, and creates `docs/database.mdx`.
-
 ---
 
 ## Documentation

package/reference/sdk/resources/patterns.mdx

@@ -449,7 +449,7 @@ The platform's HITL mechanism works in two parts: your workflow code creates an
 
 ### Creating approval tasks
 
-Call `approval.create()` from any workflow step to pause execution and emit a task to the Command Queue:
+Call `approval.create()` from any workflow step to emit a task to the Command Queue. It does **not** pause or suspend the step -- it inserts a row into `command_queue` and returns `{ id }`, and the workflow keeps running to completion:
 
 {/* doc-snippet:skip: illustrative excerpt -- dealId/proposalUrl are shorthand for values from the enclosing step handler's input, not a standalone compilable file */}
 
@@ -458,19 +458,27 @@ import { approval } from '@elevasis/sdk/worker'
 
 const task = await approval.create({
   actions: [
-    { id: 'approve', label: 'Approve', type: 'primary' },
+    {
+      id: 'approve',
+      label: 'Approve',
+      type: 'primary',
+      target: { resourceType: 'workflow', resourceId: 'send-proposal' },
+    },
     { id: 'reject', label: 'Reject', type: 'danger' },
   ],
   context: { dealId, proposalUrl },
   description: 'Review proposal before sending',
 })
 
-if (task.actionId === 'approve') {
-  // continue with approved path
-}
+// task is only `{ id: string }` -- the new command_queue row's id.
+// There is no `task.actionId` to branch on here.
 ```
 
-The workflow step suspends at `approval.create()` and resumes only after a reviewer submits an action. See [Platform Adapters](../platform-tools/adapters-platform.mdx) for the full `approval.create()` reference.
+**There is no resumption.** This workflow step -- and the whole workflow -- runs to completion and terminates normally right after `approval.create()` returns. When a reviewer later submits an action from the Command Queue, the API starts a **brand-new execution** of the workflow named in that action's `target`, with input `{ ...task.context, actionId, actionPayload }`. The original execution is not revived and cannot be branched on.
+
+The consequence for anything you write: state your workflow needs once the reviewer's decision comes back cannot live in a local variable -- the process holding it already exited. Put everything the follow-up execution needs into `context` (it comes back verbatim as part of that execution's input), or persist it somewhere the new execution can look up by id.
+
+See [Platform Adapters](../platform-tools/adapters-platform.mdx) for the full `approval.create()` reference.
 
 ### Built-in Command Center handling