@useatlas/types - npm Package Compare versions

Comparing version 0.1.6 to 0.1.7

dist/catalog.d.ts

@@ -44,2 +44,40 @@ /**
 /**
+ * The three orthogonal ways Atlas reaches the outside world, per ADR-0006:
+ *
+ * - `datasource` — Atlas reads tabular data from it (SQL / SOQL / equivalent).
+ *   Lives on `/admin/connections`. Examples: Postgres, MySQL, Snowflake,
+ *   ClickHouse, BigQuery, DuckDB, Salesforce.
+ * - `chat` — Customer talks to Atlas through it. Lives on
+ *   `/admin/integrations` (Chat section). Examples: Slack, Teams, Discord,
+ *   Google Chat, Telegram, WhatsApp.
+ * - `action` — Atlas writes to / acts on it. Lives on `/admin/integrations`
+ *   (Actions section). Examples: GitHub, Linear, Email, Webhooks.
+ *
+ * Multi-pillar systems (e.g. GitHub-as-Action-Target + future
+ * GitHub-as-Datasource) carry one catalog row per pillar, not one row
+ * with a pillar array — see ADR-0006 for the least-privilege rationale.
+ *
+ * Mirrors the `chk_plugin_catalog_pillar` and `chk_workspace_plugins_pillar`
+ * CHECK constraints on the DB (migration 0092).
+ */
+export declare const PILLARS: readonly ["datasource", "chat", "action"];
+export type Pillar = (typeof PILLARS)[number];
+/**
+ * Whether Atlas has shipped a working install path for a catalog row.
+ *
+ * - `available` — install handler is wired; the card renders a working
+ *   Connect / Configure CTA (gated by plan + deploy-config).
+ * - `coming_soon` — Atlas hasn't shipped it yet; the card renders an
+ *   inert grey badge with no CTA. Operators can override per deploy via
+ *   `atlas.config.ts:overrideImplementationStatus`.
+ *
+ * `coming_soon` dominates every other gate in the install-status state
+ * machine (`@atlas/api/lib/integrations/install-status-machine`).
+ *
+ * Mirrors the `chk_plugin_catalog_implementation_status` CHECK constraint
+ * on the DB (migration 0092).
+ */
+export declare const IMPLEMENTATION_STATUSES: readonly ["available", "coming_soon"];
+export type ImplementationStatus = (typeof IMPLEMENTATION_STATUSES)[number];
+/**
  * Canonical chat platform names supported by `@useatlas/chat`. The chat
@@ -46,0 +84,0 @@ * SDK's `Adapter` interface types `name` as a bare `string` because

dist/catalog.js

 // src/catalog.ts
 var CATALOG_INSTALL_MODELS = ["oauth", "form", "static-bot"];
 var CATALOG_ENTRY_TYPES = ["chat", "integration"];
+var PILLARS = ["datasource", "chat", "action"];
+var IMPLEMENTATION_STATUSES = ["available", "coming_soon"];
 var CHAT_ADAPTER_NAMES = [
@@ -15,2 +17,4 @@ "slack",
 export {
+  PILLARS,
+  IMPLEMENTATION_STATUSES,
   CHAT_ADAPTER_NAMES,
@@ -17,0 +21,0 @@ CATALOG_INSTALL_MODELS,

dist/index.js

@@ -534,2 +534,4 @@ // src/auth.ts
 var CATALOG_ENTRY_TYPES = ["chat", "integration"];
+var PILLARS = ["datasource", "chat", "action"];
+var IMPLEMENTATION_STATUSES = ["available", "coming_soon"];
 var CHAT_ADAPTER_NAMES = [
@@ -810,2 +812,3 @@ "slack",
   PLAN_TIERS,
+  PILLARS,
   PII_DETECTION_METHODS,
@@ -829,2 +832,3 @@ PII_CONFIDENCE_LEVELS,
   INTEGRATION_PLATFORMS,
+  IMPLEMENTATION_STATUSES,
   HEALTH_STATUSES,
@@ -831,0 +835,0 @@ GATEWAY_MODEL_TYPES,

package.json

 {
   "name": "@useatlas/types",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "Shared types for the Atlas text-to-SQL agent",
@@ -5,0 +5,0 @@ "type": "module",

No alert changes

Improved metrics

Total package byte prevSize

213290

1.04%

Lines of code

5376

0.86%

No dependency changes