@engine9/schemas 1.9.1 → 1.11.0

package/README.md

@@ -7,7 +7,7 @@ this code as-is.
 
 ## Documentation
 
-Each schema plugin is documented in its own `README.md`. That file is the human-readable contract: what the schema plugin is for, the data model, inbound/outbound behavior, search, **predefined segments**, and UI. Keep implementation details in code comments; keep audience and membership rules in the README. Dashboards live on `@engine9/plugins/reports/<area>`, not in this package.
+Each schema plugin is documented in its own `README.md`. That file is the human-readable contract: what the schema plugin is for, the data model, inbound/outbound behavior, segment definition clauses, **predefined segments**, and UI. Keep implementation details in code comments; keep audience and membership rules in the README. Dashboards live on `@engine9/plugins/reports/<area>`, not in this package.
 
 Schema plugins with predefined segments:
 
@@ -22,9 +22,9 @@ See [`skills/create-engine9-plugin/SKILL.md`](../skills/create-engine9-plugin/SK
 
 - **Plugin uniqueness:** `SchemaWorker.install` reuses an existing `plugin` row when the path is unique: `metadata.unique` if set, otherwise `@engine9/schemas/*` (except `person_custom`, which is `unique: false`). Native plugins that set `unique: true` behave the same. Third-party plugins and `person_custom` may have more than one instance per path; pass `id` to update an existing non-unique row.
 
-- **Public module surface:** Export only the standard building blocks documented in [`skills/create-engine9-plugin/SKILL.md`](../skills/create-engine9-plugin/SKILL.md): for example `metadata`, optional `schema`, `transforms`, `search`, `segments`, `metrics`, and the default object that aggregates them. Do **not** export `reports` from schema plugins — dashboards belong on `@engine9/plugins/reports/<area>`. Do **not** export ad hoc hooks (such as custom install helpers or segment–plugin wiring) from schema plugins; the server is responsible for any special install-time behavior tied to a specific schema plugin path.
+- **Public module surface:** Export only the standard building blocks documented in [`skills/create-engine9-plugin/SKILL.md`](../skills/create-engine9-plugin/SKILL.md): for example `metadata`, optional `schema`, `transforms`, `segmentDefinitionClauses`, `segments`, `metrics`, and the default object that aggregates them. Do **not** export `reports` from schema plugins — dashboards belong on `@engine9/plugins/reports/<area>`. Do **not** export ad hoc hooks (such as custom install helpers or segment–plugin wiring) from schema plugins; the server is responsible for any special install-time behavior tied to a specific schema plugin path.
 
-- **Segments, universes, and `plugin_id`:** Saved segments use `segment.plugin_id` = the schema plugin (or plugin) that **owns the definition**. A definition’s **`universe`** describes the span of source data searched across; input EQL entries select timeline stores, while person/table entries can restrict eligible people. Explicit `pluginId` values inside `search` options may narrow that span further, so a segment can evaluate data tied to other deployed plugins without changing its owning `plugin_id`. Export bundles use the same universe vocabulary for table and input-file artifacts.
+- **Segments, universes, and `plugin_id`:** Saved segments use `segment.plugin_id` = the schema plugin (or plugin) that **owns the definition**. A definition’s **`universe`** describes the span of source data searched across; input EQL entries select timeline stores, while person/table entries can restrict eligible people. Explicit `pluginId` values inside a clause's options may narrow that span further, so a segment can evaluate data tied to other deployed plugins without changing its owning `plugin_id`. Export bundles use the same universe vocabulary for table and input-file artifacts.
 
 ## License
 

package/channels/email/README.md

@@ -1,10 +1,10 @@
 # Email Channel Schema Plugin
 
-The `@engine9/schemas/channels/email` plugin defines email-channel search and engagement segments. It does not create its own tables. Segment builds read `global_message`, `input`, and `timeline` rows produced by email message plugins.
+The `@engine9/schemas/channels/email` plugin defines the email-channel segment definition clause and engagement segments. It does not create its own tables. Segment builds read `global_message`, `input`, and `timeline` rows produced by email message plugins.
 
 It depends on `@engine9/schemas/person` because membership is always a set of people.
 
-## Search
+## Segment definition clauses
 
 `emailEngagement` finds people who opened or clicked email in a rolling window.
 
@@ -14,13 +14,13 @@ It depends on `@engine9/schemas/person` because membership is always a set of pe
 | `timelineEntryType` | `EMAIL_OPEN` or `EMAIL_CLICK` |
 | `pluginId` | Optional. When set, only that plugin's inputs are included. When empty, scope comes from the segment universe instead |
 
-The search looks at `timeline` rows whose `entry_type_id` matches the engagement type and whose `ts` is in the window. It always joins `timeline.input_id = input.id`, so only timeline entries for inputs present in the build are counted.
+The clause looks at `timeline` rows whose `entry_type_id` matches the engagement type and whose `ts` is in the window. It always joins `timeline.input_id = input.id`, so only timeline entries for inputs present in the build are counted.
 
 ## Segments
 
 Predefined audiences shipped with this schema plugin. On install, each key becomes a `segment` row whose definition path is `@engine9/schemas/channels/email:segments:<key>`.
 
-Every segment here uses the same **universe** and the `emailEngagement` search. The universe and the search do different jobs, and both are required:
+Every segment here uses the same **universe** and the `emailEngagement` clause. The universe and the clause do different jobs, and both are required:
 
 - **Universe** chooses *which email sends* can contribute entries: messages on the email channel published in the last **90 days** (`global_message.channel = 'email'` and `publish_date` within 90 days). Those message ids become the `input` rows for the build.
 - **Search** chooses *which people* from those sends belong in the audience: a recent open or click on the timeline, inside the segment's rolling window.

package/channels/email/index.js

@@ -1,4 +1,4 @@
-import search from './search.js';
+import { segmentDefinitionClauses } from './segmentDefinitionClauses.js';
 import segments, { personSegmentTableName, universeEmailPublished90d } from './segments.js';
 
 const metadata = {
@@ -9,13 +9,13 @@ const metadata = {
 };
 
 export { metadata };
-export { search };
+export { segmentDefinitionClauses };
 export { segments };
 export { personSegmentTableName };
 export { universeEmailPublished90d };
 export default {
   metadata,
-  search,
+  segmentDefinitionClauses,
   segments,
   personSegmentTableName,
   universeEmailPublished90d

package/channels/email/{search.js → segmentDefinitionClauses.js}

@@ -3,7 +3,7 @@ import { TIMELINE_ENTRY_TYPES } from '@engine9/input-tools';
 /**
  * Build EQL for email engagement (opens / clicks) within a rolling window.
  *
- * The search always joins `timeline` → `input` on `timeline.input_id = input.id`.
+ * The clause always joins `timeline` → `input` on `timeline.input_id = input.id`.
  * During a segment build the DuckDB `input` table is populated exclusively with
  * the input ids discovered by the segment's `universe` entry (e.g.
  * `universeEmailPublished90d`), so the join scopes results to the universe even
@@ -81,6 +81,7 @@ export const emailEngagement = {
   }
 };
 
+export const segmentDefinitionClauses = { emailEngagement };
 export default {
-  emailEngagement
+  segmentDefinitionClauses
 };

package/channels/email/segments.js

@@ -1,4 +1,4 @@
-const SEGMENT_SEARCH_PATH = '@engine9/schemas/channels/email:search:emailEngagement';
+const EMAIL_ENGAGEMENT_CLAUSE_PATH = '@engine9/schemas/channels/email:segment_definition_clause:emailEngagement';
 
 /**
  * EQL over the message table: rows published in the last 90 days on the email channel.
@@ -6,12 +6,12 @@ const SEGMENT_SEARCH_PATH = '@engine9/schemas/channels/email:search:emailEngagem
  * scanned for timeline parquet.
  *
  * During a segment build the input ids returned here are copied into the DuckDB `input`
- * table.  The search EQL (see `emailEngagement` in `search.js`) always joins
+ * table.  The clause EQL (see `emailEngagement` in `segmentDefinitionClauses.js`) always joins
  * `timeline.input_id = input.id`, so only timeline rows whose input is in **this**
  * universe are considered — even when `pluginId` is empty.  This means:
  *
  * - The **universe** controls *which* message/input stores supply timeline data.
- * - The **search** applies time-window and entry-type filters *within* that scope.
+ * - The **clause** applies time-window and entry-type filters *within* that scope.
  *
  * Both layers are required for correct segment membership counts.
  */
@@ -35,7 +35,7 @@ export function personSegmentTableName(tablePrefix, segmentName) {
 /**
  * Build a segment definition for email engagement (opens or clicks).
  *
- * `pluginId` is left empty intentionally: the search handler in `search.js`
+ * `pluginId` is left empty intentionally: the `emailEngagement` clause
  * always joins `timeline` → `input`, and the segment `universe` determines
  * which input rows are present in DuckDB.  This scopes the time-window query
  * to the correct set of message inputs without hard-coding a plugin id.
@@ -44,10 +44,10 @@ function emailEngagementSegment(name, windowDays, timelineEntryType) {
   return {
     name,
     universe: [universeEmailPublished90d],
-    search: {
+    definition: {
       and: [
         {
-          path: SEGMENT_SEARCH_PATH,
+          path: EMAIL_ENGAGEMENT_CLAUSE_PATH,
           options: {
             pluginId: '',
             windowDays,
@@ -61,7 +61,7 @@ function emailEngagementSegment(name, windowDays, timelineEntryType) {
 
 /**
  * Rolling-window engagement segments.  `pluginId` is empty so scope follows the
- * segment `universe` (the `input` table join in the search EQL restricts to
+ * segment `universe` (the `input` table join in the clause EQL restricts to
  * universe-provided message input ids).
  */
 export const email_openers_30d = emailEngagementSegment('30-day email openers', 30, 'EMAIL_OPEN');

package/event/README.md

@@ -56,11 +56,11 @@ None in this package. Native event / calendar plugins should upsert `event` and
 
 None.
 
-## Search
+## Segment definition clauses
 
 | Key | Path | Purpose |
 | --- | --- | --- |
-| `responses` | `@engine9/schemas/event:search:responses` | Filter people by `person_event.response` and optional `eventId`. |
+| `responses` | `@engine9/schemas/event:segment_definition_clause:responses` | Filter people by `person_event.response` and optional `eventId`. |
 
 ## Segments
 

package/event/index.js

@@ -1,5 +1,5 @@
 import schema from './schema.js';
-import search from './search.js';
+import { segmentDefinitionClauses } from './segmentDefinitionClauses.js';
 
 const metadata = {
   name: '@engine9/schemas/event',
@@ -9,9 +9,9 @@ const metadata = {
   schemas: ['schema.js']
 };
 
-export { metadata, schema, search };
+export { metadata, schema, segmentDefinitionClauses };
 export default {
   metadata,
   schema,
-  search
+  segmentDefinitionClauses
 };

package/event/{search.js → segmentDefinitionClauses.js}

@@ -46,6 +46,7 @@ export const responses = {
   }
 };
 
+export const segmentDefinitionClauses = { responses };
 export default {
-  responses
+  segmentDefinitionClauses
 };

package/package.json

@@ -1,11 +1,11 @@
 {
   "name": "@engine9/schemas",
-  "version": "1.9.1",
+  "version": "1.11.0",
   "type": "module",
   "description": "Engine9 standard schemas: shared tables, transforms, searches, and segments",
   "main": "index.js",
   "scripts": {
-    "test": "node --test person/upsert.test.js person_address/normalize.test.js person_email/upsert.test.js person_hash/hash.test.js person_phone/upsert.test.js stacks/stacks.test.js transaction/core/attribute.test.js"
+    "test": "node --test person/upsert.test.js person_address/normalize.test.js person_email/upsert.test.js person_hash/hash.test.js person_name/upsert.test.js person_phone/upsert.test.js stacks/stacks.test.js transaction/core/attribute.test.js"
   },
   "engines": {
     "node": ">=18"

package/person/index.js

@@ -2,38 +2,31 @@ import schema from './schema.js';
 import upsertPerson from './transforms/inbound/upsert_tables.js';
 import normalizeFieldNames from './transforms/inbound/normalize_field_names.js';
 import simpleMap from './transforms/simpleMap.js';
-import appendName from './transforms/outbound/appendName.js';
+import appendName from '../person_name/transforms/outbound/appendName.js';
 import metrics from './metrics.js';
 const metadata = {
   name: '@engine9/schemas/person',
   schemas: ['schema.js'],
   // Inbound people pipeline slots -> transform export keys (woven by core when installed)
   inbound: {
-    normalize: ['normalizeFieldNames'],
-    upsert: ['upsertPerson']
+    normalize: ['normalizeFieldNames']
   }
 };
 const transforms = {
   normalizeFieldNames,
+  // Not woven. Plugin rows installed before person_name still name it in their
+  // inbound snapshot until the person_name upgrade refreshes that snapshot.
   upsertPerson,
   simpleMap,
+  // Saved export definitions still call @engine9/schemas/person:transforms:appendName.
   appendName
 };
-export const search = {
-  person: {
+const person = {
     title: 'Primary Info',
     form: {
       title: 'Primary Info',
       type: 'object',
       properties: {
-        givenName: {
-          title: 'First Name',
-          type: 'string'
-        },
-        familyName: {
-          title: 'Last Name',
-          type: 'string'
-        },
         ids: {
           title: 'Person Ids (comma delimited)',
           type: 'string'
@@ -51,7 +44,7 @@ export const search = {
     },
     optionsToEQL: (options) => {
       const text = [];
-      const { ids, idGreaterThanEqual, idLessThan, givenName = '', familyName = '' } = options;
+      const { ids, idGreaterThanEqual, idLessThan } = options;
       const conditions = [];
       if (ids) {
         let arr = ids || '';
@@ -68,14 +61,6 @@ export const search = {
         conditions.push({ eql: `id<${idLessThan}` });
         text.push(`Person ID less than ${idLessThan}`);
       }
-      if (givenName.length > 0) {
-        text.push(`First name like '${givenName}'`);
-        conditions.push({ eql: `given_name like '${givenName}'` });
-      }
-      if (familyName.length > 0) {
-        text.push(`Last name like '${givenName}'`);
-        conditions.push({ eql: `family_name like '${familyName}'` });
-      }
       return {
         text,
         eql: {
@@ -85,8 +70,8 @@ export const search = {
         }
       };
     }
-  }
-};
+  };
+export const segmentDefinitionClauses = { person };
 export { metadata };
 export { schema };
 export { transforms };
@@ -96,5 +81,5 @@ export default {
   schema,
   transforms,
   metrics,
-  search
+  segmentDefinitionClauses
 };

package/person/schema.js

@@ -3,8 +3,6 @@ export const tables = [
     name: 'person',
     columns: {
       id: 'id',
-      given_name: 'string',
-      family_name: 'string',
       created_at: 'created_at',
       modified_at: 'modified_at'
     }

package/person/ui.console.json5

@@ -17,26 +17,16 @@
     person: {
       layout: 'full_width',
       components: {
-        header: [
-          'Everybody',
-          {
-            component: 'Button',
-            properties: {
-              icon: 'plus',
-              content: 'Add Person',
-              onClick: {
-                action: 'navigate',
-                url: '/person/create'
-              }
-            }
-          }
-        ],
+        header: ['Everybody'],
         main: [
           {
             component: 'RecordList',
             properties: {
               table: 'person',
               includes: {
+                names: {
+                  table: 'person_name'
+                },
                 emails: {
                   table: 'person_email'
                 }
@@ -51,8 +41,7 @@
                 {
                   title: 'Name',
                   dataIndex: 'name',
-                  sorter: true,
-                  template: '{{given_name}} {{family_name}} {{emails.0.email}}',
+                  template: '{{names.0.given_name}} {{names.0.family_name}} {{emails.0.email}}',
                   width: '40%'
                 },
                 {
@@ -72,36 +61,6 @@
         ]
       }
     },
-    'person/create': {
-      layout: 'full_width',
-      components: {
-        main: [
-          {
-            path: 'edit',
-            component: 'RecordForm',
-            properties: {
-              table: 'person',
-              form: {
-                title: 'Todo',
-                type: 'object',
-                required: [],
-                properties: {
-                  given_name: { type: 'string', title: 'First Name', default: '' },
-                  family_name: { type: 'string', title: 'Last Name', default: '' }
-                }
-              },
-              uiSchema: {
-                family_name: { 'ui:widget': 'textarea' }
-              },
-              onSave: {
-                action: 'navigate',
-                url: '/person/{{record.id}}'
-              }
-            }
-          }
-        ]
-      }
-    },
     'person/:id/*': {
       layout: 'sidebar',
       components: {
@@ -114,19 +73,15 @@
                 table: 'person',
                 id: '{{parameters.id}}',
                 includes: {
+                  names: {
+                    table: 'person_name'
+                  },
                   emails: {
                     table: 'person_email',
                     orderBy: 'preference_order'
                   }
                 },
-                template: '{{given_name}} {{family_name}} {{#if emails.0.email}}<{{emails.0.email}}>{{/if}}'
-              }
-            },
-            {
-              component: 'Link',
-              properties: {
-                label: 'Edit',
-                to: 'edit'
+                template: '{{names.0.given_name}} {{names.0.family_name}} {{#if emails.0.email}}<{{emails.0.email}}>{{/if}}'
               }
             }
           ]
@@ -138,24 +93,12 @@
             properties: {
               table: 'person',
               id: '{{parameters.id}}',
-              template: '{{given_name}} {{family_name}}'
-            }
-          },
-          {
-            path: 'edit',
-            component: 'RecordForm',
-            properties: {
-              table: 'person',
-              id: '{{parameters.id}}',
-              form: {
-                title: 'Todo',
-                type: 'object',
-                required: [],
-                properties: {
-                  given_name: { type: 'string', title: 'First Name', default: '' },
-                  family_name: { type: 'string', title: 'Last Name', default: '' }
+              includes: {
+                names: {
+                  table: 'person_name'
                 }
-              }
+              },
+              template: '{{names.0.given_name}} {{names.0.family_name}}'
             }
           }
         ]

package/person_email/README.md

@@ -51,9 +51,9 @@ The plugin provides outbound transforms for appending email data to batches:
 - `appendEmail` looks up `person_email` rows by `person_id` and appends `email` to each batch row. It can be filtered by `subscriptionStatus`, and it preserves any existing `email` value already on the row.
 - `appendEmailHash` appends `email_hash_v1` by hashing the row's trimmed, lowercased `email` when the hash is not already present.
 
-## Search
+## Segment definition clauses
 
-The `emails` search lets users find people who have an email address, optionally filtered by:
+The `emails` clause selects people who have an email address, optionally filtered by:
 
 - `subscriptionStatus`, using the same values as `subscription_status`
 - `emailMatch`, matched against the `email` column with `LIKE`
@@ -70,7 +70,7 @@ Predefined audiences shipped with this schema plugin. On install, each key becom
 | **Definition path** | `@engine9/schemas/person_email:segments:subscribers` |
 | **Who is included** | People with at least one email whose `subscription_status` is `Subscribed` |
 | **Who is excluded** | People whose emails are only `Not Subscribed`, `Unsubscribed`, `Bouncing`, or `Spam` |
-| **How it is built** | The `emails` search with `subscriptionStatus: Subscribed` |
+| **How it is built** | The `emails` clause with `subscriptionStatus: Subscribed` |
 | **Universe** | None — membership is current `person_email` rows, not a time window or message input set |
 
 A person with mixed statuses is included if any of their addresses is `Subscribed`.

package/person_email/index.js

@@ -1,7 +1,7 @@
 import schema from './schema.js';
 import extractEmailHashes from './transforms/inbound/extract_identifiers.js';
 import upsertPersonEmail from './transforms/inbound/upsert_tables.js';
-import search from './search.js';
+import { segmentDefinitionClauses } from './segmentDefinitionClauses.js';
 import appendEmail from './transforms/outbound/appendEmail.js';
 import appendEmailHash from './transforms/outbound/appendEmailHash.js';
 import segments from './segments.js';
@@ -24,12 +24,12 @@ export const transforms = {
 };
 export { metadata };
 export { schema };
-export { search };
+export { segmentDefinitionClauses };
 export { segments };
 export default {
   metadata,
   schema,
-  search,
+  segmentDefinitionClauses,
   segments,
   transforms
 };

package/person_email/{search.js → segmentDefinitionClauses.js}

@@ -56,6 +56,7 @@ export const emails = {
     };
   }
 };
+export const segmentDefinitionClauses = { emails };
 export default {
-  emails
+  segmentDefinitionClauses
 };

package/person_email/segments.js

@@ -1,9 +1,9 @@
 export const subscribers = {
   name: 'Email Subscribers',
-  search: {
+  definition: {
     and: [
       {
-        path: '@engine9/schemas/person_email:search:emails',
+        path: '@engine9/schemas/person_email:segment_definition_clause:emails',
         options: {
           subscriptionStatus: 'Subscribed'
         }

package/person_hash/README.md

@@ -4,7 +4,7 @@
 
 It is **not** part of the standard stack. It ships in `@engine9/schemas/stacks/limited-pii`, or install it explicitly (once per account — `unique: true`). Once installed, core weaves its transforms into the inbound people pipeline automatically.
 
-Warehouse plugin setting `exclude_pii` on `@engine9/schemas/utilities/limited-pii` makes `installDefaultPlugins()` prefer the limited-pii stack over `default_stack` and refuses `@engine9/schemas/stacks/standard`, `person_email`, `person_phone`, and `person_address` even if those plugins are already installed. That does **not** uninstall leftover plaintext tables. Install the utility plugin on demand; it is not part of the limited-pii stack.
+Warehouse plugin setting `exclude_pii` on `@engine9/schemas/utilities/limited-pii` makes `installDefaultPlugins()` prefer the limited-pii stack over `default_stack` and refuses `@engine9/schemas/stacks/standard`, `person_name`, `person_email`, `person_phone`, `person_address`, and `transaction/contact_details` even if those plugins are already installed. That does **not** uninstall leftover plaintext tables. Install the utility plugin on demand; it is not part of the limited-pii stack.
 
 It does **not** depend on `person_email` or `person_phone`. Those plugins may be installed alongside it; this schema plugin never writes to their tables.
 
@@ -31,7 +31,7 @@ inbound: {
 
 How slots and the weaver work: `@engine9/core/lib/peoplePipeline/README.md`.
 
-To see the woven chain for an account: `personWorker.getInboundTransforms({ pluginId, describe: true })` (CLI: `e9 personworker getInboundTransforms --plugin_id=<plugin_id> --describe=true`). On a limited-pii account the listing has `person_hash` on `id` and `upsert` and no `person_email` / `person_phone` / `person_address` lines. Drop a step for one job with `omit_transforms`.
+To see the woven chain for an account: `personWorker.getInboundTransforms({ pluginId, describe: true })` (CLI: `e9 personworker getInboundTransforms --plugin_id=<plugin_id> --describe=true`). On a limited-pii account the listing has `person_hash` on `id` and `upsert` and no `person_name` / `person_email` / `person_phone` / `person_address` lines. Drop a step for one job with `omit_transforms`.
 
 ## Data Model
 
@@ -65,6 +65,6 @@ The `upsertPersonHash` transform writes only hash columns to `person_hash_email`
 
 `PersonWorker.search` `emails` / `phones` match `person_email` / `person_phone` when those tables exist, and also hash the query (or accept SHA-256 / MD5 hex) against `person_hash_email` / `person_hash_phone`. If the caller passed emails or phones and neither table exists, the clause matches nobody (`1=0`). Related summaries include `email_hashes` / `phone_hashes` when those tables are present.
 
-The plugin also exports `search.emailHashes` / `search.phoneHashes` for the plugin search tree (`@engine9/schemas/person_hash:search:emailHashes`).
+The plugin exports `segmentDefinitionClauses.emailHashes` and `segmentDefinitionClauses.phoneHashes` for segment definitions (`@engine9/schemas/person_hash:segment_definition_clause:emailHashes`).
 
-Default warehouse export includes the hash tables (export skips them when they do not exist). When utilities/limited-pii `exclude_pii` is set and `tables` is not explicit, `person_email` / `person_phone` / `person_address` are omitted from that default list.
+Default warehouse export includes the hash tables (export skips them when they do not exist). When utilities/limited-pii `exclude_pii` is set and `tables` is not explicit, `person_name` / `person_email` / `person_phone` / `person_address` are omitted from that default list.

package/person_hash/index.js

@@ -1,5 +1,5 @@
 import schema from './schema.js';
-import search from './search.js';
+import { segmentDefinitionClauses } from './segmentDefinitionClauses.js';
 import extractContactHashes from './transforms/inbound/extract_identifiers.js';
 import upsertPersonHash from './transforms/inbound/upsert_tables.js';
 import appendEmailHash from './transforms/outbound/appendEmailHash.js';
@@ -28,10 +28,10 @@ export const transforms = {
 
 export { metadata };
 export { schema };
-export { search };
+export { segmentDefinitionClauses };
 export default {
   metadata,
   schema,
   transforms,
-  search
+  segmentDefinitionClauses
 };

package/person_hash/{search.js → segmentDefinitionClauses.js}

@@ -80,7 +80,7 @@ export const phoneHashes = {
   }
 };
 
+export const segmentDefinitionClauses = { emailHashes, phoneHashes };
 export default {
-  emailHashes,
-  phoneHashes
+  segmentDefinitionClauses
 };

package/person_name/README.md

@@ -0,0 +1,69 @@
+# Person Name Schema Plugin
+
+`@engine9/schemas/person_name` stores a person's plaintext name: `given_name` and `family_name`, one row per person.
+
+Names are personal data, so they are not on `person`. `person` holds only the id and timestamps, and every account installs it. An account that must not store names leaves this plugin out, the same way it leaves out `person_email`, `person_phone`, and `person_address`.
+
+- The standard stack (`@engine9/schemas/stacks/standard`) and the no-argument `installDefaultPlugins()` install it.
+- The limited-pii stack (`@engine9/schemas/stacks/limited-pii`) excludes it. With `exclude_pii` set on `@engine9/schemas/utilities/limited-pii`, core refuses to install it.
+
+## Install
+
+```javascript
+await pluginWorker.install({ path: '@engine9/schemas/person_name' });
+```
+
+A second install of the same path reuses the existing plugin row.
+
+## Inbound pipeline slots
+
+```javascript
+inbound: {
+  upsert: ['upsertPersonName']
+}
+```
+
+When the plugin is installed, core weaves `upsertPersonName` into the `upsert` slot of the inbound people pipeline. When it is not installed, the step is not in the chain. Incoming `given_name` / `family_name` fields are then ignored and nothing is stored. How slots and the weaver work: `@engine9/core/lib/peoplePipeline/README.md`.
+
+## Data Model
+
+### `person_name`
+
+Primary key: `person_id`.
+
+| Field | Type | Description |
+| --- | --- | --- |
+| `person_id` | `person_id` | Person the name belongs to. |
+| `given_name` | `string` | Given (first) name. |
+| `family_name` | `string` | Family (last) name. |
+| `source_input_id` | `foreign_uuid` | Input that first wrote the row. Existing rows keep their original source. Rows copied by the core `person_name` upgrade have none. |
+| `created_at` / `modified_at` | timestamps | |
+
+## Inbound Behavior
+
+`upsertPersonName` runs for each row that has a `given_name` or `family_name` key:
+
+- A key that is present overwrites the stored value. An explicit `null` clears it.
+- A key that is absent keeps the stored value.
+- Rows for the same person in one batch merge; later keys win.
+- A row with a name and no `person_id` fails the batch.
+
+## Outbound Behavior
+
+`appendName` adds `given_name` and `family_name` to each row by `person_id`. People with no row get `null` for both.
+
+`@engine9/schemas/person:transforms:appendName` is the same transform, kept so saved export definitions keep working.
+
+## Segment definition clauses
+
+`names` matches people by `given_name` and/or `family_name` with `LIKE`. With neither, it selects everyone who has a name row.
+
+## Upgrading accounts created before this plugin
+
+Before this plugin, the names were `person.given_name` and `person.family_name`. Run the core upgrade once per account after installing this version of `@engine9/schemas`:
+
+- `PluginWorker.upgrade()` (server: `e9 personworker upgrade -a <account_id>`)
+- `npx e9core upgrade --db <connection>` for a SQLite or MySQL database
+- `npx e9core upgrade --url https://<site>` for a Cloudflare site (it posts to `/api/admin/upgrade` with `E9_ADMIN_API_KEY`)
+
+The upgrade installs this plugin and copies every non-blank name into `person_name`. It then refreshes the `person` plugin's inbound snapshot, so later loads write `person_name` only. The columns stay on `person` with the names as of the upgrade. Dropping them is a separate, opt-in step (`drop_name_columns`), for when nothing reads them. On a PII-free account the upgrade does not install this plugin, and the opt-in drop removes the columns only when they are empty, or when you also pass `discard_names`.

package/person_name/index.js

@@ -0,0 +1,28 @@
+import schema from './schema.js';
+import upsertPersonName from './transforms/inbound/upsert_tables.js';
+import appendName from './transforms/outbound/appendName.js';
+import { segmentDefinitionClauses } from './segmentDefinitionClauses.js';
+const metadata = {
+  name: '@engine9/schemas/person_name',
+  unique: true,
+  dependencies: {
+    '@engine9/schemas/person': '>=1.9.0'
+  },
+  // Inbound people pipeline slots -> transform export keys (woven by core when installed)
+  inbound: {
+    upsert: ['upsertPersonName']
+  }
+};
+export const transforms = {
+  upsertPersonName,
+  appendName
+};
+export { metadata };
+export { schema };
+export { segmentDefinitionClauses };
+export default {
+  metadata,
+  schema,
+  segmentDefinitionClauses,
+  transforms
+};

package/person_name/schema.js

@@ -0,0 +1,17 @@
+export const tables = [
+  {
+    name: 'person_name',
+    columns: {
+      person_id: 'person_id',
+      given_name: 'string',
+      family_name: 'string',
+      source_input_id: 'foreign_uuid',
+      created_at: 'created_at',
+      modified_at: 'modified_at'
+    },
+    indexes: [{ columns: ['person_id'], primary: true }]
+  }
+];
+export default {
+  tables
+};

package/person_name/segmentDefinitionClauses.js

@@ -0,0 +1,48 @@
+export const names = {
+  title: 'Names',
+  form: {
+    title: 'Names',
+    type: 'object',
+    properties: {
+      givenName: {
+        title: 'First Name',
+        type: 'string'
+      },
+      familyName: {
+        title: 'Last Name',
+        type: 'string'
+      }
+    },
+    required: []
+  },
+  optionsToEQL(options) {
+    const { givenName = '', familyName = '' } = options;
+    const text = [];
+    const conditions = [];
+    if (givenName.length > 0) {
+      text.push(`First name like '${givenName}'`);
+      conditions.push({
+        type: 'LIKE',
+        values: [{ ref: { column: 'given_name' } }, { value: { value: givenName } }]
+      });
+    }
+    if (familyName.length > 0) {
+      text.push(`Last name like '${familyName}'`);
+      conditions.push({
+        type: 'LIKE',
+        values: [{ ref: { column: 'family_name' } }, { value: { value: familyName } }]
+      });
+    }
+    return {
+      text: text.length ? text.join(' and ') : 'Has a name',
+      eql: {
+        table: 'person_name',
+        conditions
+      }
+    };
+  }
+};
+export const segmentDefinitionClauses = { names };
+export default {
+  segmentDefinitionClauses
+};

package/person_name/transforms/inbound/upsert_tables.js

@@ -0,0 +1,63 @@
+import { mergeIntoQueue } from '@engine9/input-tools';
+
+export const type = 'upsert';
+export const description =
+  'Upsert given_name / family_name into person_name, one row per person. A name key that is absent keeps the stored value; an explicit null clears it.';
+export const bindings = {
+  databaseNames: { path: 'sql.query', options: { table: 'person_name', lookup: ['person_id'] } },
+  tablesToUpsert: { path: 'sql.tables.upsert' }
+};
+
+const NAME_COLUMNS = ['given_name', 'family_name'];
+
+// person_id may arrive as number or string from different pipeline stages
+const personKey = (field, value) => (value == null ? '' : String(value));
+
+function mergeName(existing, incoming) {
+  return {
+    ...existing,
+    ...incoming,
+    person_id: existing.person_id,
+    source_input_id: existing.source_input_id ?? incoming.source_input_id
+  };
+}
+
+export async function transform({ batch, databaseNames = [], tablesToUpsert }) {
+  if (batch.length === 0) return;
+  const queue = [];
+  batch.forEach((o) => {
+    const present = NAME_COLUMNS.filter((column) => Object.hasOwn(o, column));
+    if (present.length === 0) return;
+    if (!o.person_id) throw new Error('Cannot update name, no person_id');
+    const row = { person_id: o.person_id, source_input_id: o.input_id ?? null };
+    for (const column of present) row[column] = o[column];
+    mergeIntoQueue(queue, row, {
+      keyFields: ['person_id'],
+      normalizeField: personKey,
+      merge: mergeName,
+      label: 'person_name'
+    });
+  });
+  if (queue.length === 0) return;
+  // Every queued row carries every column (upsertArray rejects mixed key sets),
+  // so a name the batch did not mention is filled from the stored row.
+  const stored = new Map(databaseNames.map((row) => [String(row.person_id), row]));
+  tablesToUpsert.person_name = tablesToUpsert.person_name || [];
+  for (const row of queue) {
+    const existing = stored.get(String(row.person_id));
+    const full = {
+      person_id: row.person_id,
+      source_input_id: existing?.source_input_id ?? row.source_input_id
+    };
+    for (const column of NAME_COLUMNS) {
+      full[column] = Object.hasOwn(row, column) ? row[column] : (existing?.[column] ?? null);
+    }
+    tablesToUpsert.person_name.push(full);
+  }
+}
+export default {
+  bindings,
+  type,
+  description,
+  transform
+};

package/{person → person_name}/transforms/outbound/appendName.js

@@ -3,20 +3,16 @@ export const bindings = {
   names: {
     path: 'sql.query',
     options: {
-      table: 'person',
-      columns: ['id', 'given_name', 'family_name'],
-      lookup: [
-        {
-          personIdField: 'person_id',
-          tableLookupField: 'id'
-        }
-      ]
+      table: 'person_name',
+      columns: ['person_id', 'given_name', 'family_name'],
+      lookup: ['person_id'],
+      optional: true
     }
   }
 };
 export const transform = ({ batch, names }) => {
   const nameMap = names.reduce((a, b) => {
-    a[b.id] = a[b.id] || b;
+    a[b.person_id] = a[b.person_id] || b;
     return a;
   }, {});
   batch.forEach((data) => {

package/person_name/upsert.test.js

@@ -0,0 +1,91 @@
+import assert from 'node:assert/strict';
+import { describe, it } from 'node:test';
+import upsertPersonName from './transforms/inbound/upsert_tables.js';
+import appendName from './transforms/outbound/appendName.js';
+import plugin from './index.js';
+
+describe('person_name upsert_tables', () => {
+  it('is declared in the inbound upsert slot', () => {
+    assert.deepEqual(plugin.metadata.inbound, { upsert: ['upsertPersonName'] });
+    assert.equal(plugin.transforms.upsertPersonName.type, 'upsert');
+  });
+
+  it('queues one person_name row with every column', async () => {
+    const tablesToUpsert = {};
+    await upsertPersonName.transform({
+      batch: [{ person_id: 1, input_id: 'input-a', email: 'ada@example.com', given_name: 'Ada' }],
+      databaseNames: [],
+      tablesToUpsert
+    });
+    assert.deepEqual(tablesToUpsert.person_name, [
+      { person_id: 1, source_input_id: 'input-a', given_name: 'Ada', family_name: null }
+    ]);
+    assert.equal('person' in tablesToUpsert, false, 'never writes the person table');
+  });
+
+  it('keeps the stored value for a name key the row did not send', async () => {
+    const tablesToUpsert = {};
+    await upsertPersonName.transform({
+      batch: [{ person_id: 2, input_id: 'input-b', family_name: 'Lovelace' }],
+      databaseNames: [{ person_id: '2', given_name: 'Ada', family_name: 'Byron', source_input_id: 'input-a' }],
+      tablesToUpsert
+    });
+    assert.deepEqual(tablesToUpsert.person_name, [
+      { person_id: 2, source_input_id: 'input-a', given_name: 'Ada', family_name: 'Lovelace' }
+    ]);
+  });
+
+  it('clears a name when the key is present and null', async () => {
+    const tablesToUpsert = {};
+    await upsertPersonName.transform({
+      batch: [{ person_id: 3, family_name: null }],
+      databaseNames: [{ person_id: 3, given_name: 'Ada', family_name: 'Lovelace', source_input_id: null }],
+      tablesToUpsert
+    });
+    assert.equal(tablesToUpsert.person_name[0].given_name, 'Ada');
+    assert.equal(tablesToUpsert.person_name[0].family_name, null);
+  });
+
+  it('merges rows for the same person in one batch, later keys winning', async () => {
+    const tablesToUpsert = {};
+    await upsertPersonName.transform({
+      batch: [
+        { person_id: 4, input_id: 'first', given_name: 'Ada', family_name: 'Byron' },
+        { person_id: '4', input_id: 'second', family_name: 'Lovelace' }
+      ],
+      databaseNames: [],
+      tablesToUpsert
+    });
+    assert.deepEqual(tablesToUpsert.person_name, [
+      { person_id: 4, source_input_id: 'first', given_name: 'Ada', family_name: 'Lovelace' }
+    ]);
+  });
+
+  it('queues nothing when no row has a name key', async () => {
+    const tablesToUpsert = {};
+    await upsertPersonName.transform({
+      batch: [{ person_id: 5, email: 'ada@example.com' }, { email: 'no-id@example.com' }],
+      databaseNames: [],
+      tablesToUpsert
+    });
+    assert.deepEqual(tablesToUpsert, {});
+  });
+
+  it('throws when a name is present and person_id is missing', async () => {
+    await assert.rejects(
+      () => upsertPersonName.transform({ batch: [{ given_name: 'Ada' }], databaseNames: [], tablesToUpsert: {} }),
+      /no person_id/
+    );
+  });
+});
+
+describe('person_name appendName', () => {
+  it('appends names by person_id', () => {
+    const batch = [{ person_id: 1 }, { person_id: 2 }];
+    appendName.transform({ batch, names: [{ person_id: 1, given_name: 'Ada', family_name: 'Lovelace' }] });
+    assert.deepEqual(batch, [
+      { person_id: 1, given_name: 'Ada', family_name: 'Lovelace' },
+      { person_id: 2, given_name: null, family_name: null }
+    ]);
+  });
+});

package/person_phone/README.md

@@ -49,9 +49,9 @@ The inbound `upsert` transform writes rows to `person_phone`.
 
 `appendPhoneHash` hashes the row's normalized `phone` into `phone_hash_v1` when the hash is not already present.
 
-## Search
+## Segment definition clauses
 
-The `phones` search lets users find people who have a phone number, optionally filtered by:
+The `phones` clause selects people who have a phone number, optionally filtered by:
 
 - `smsStatus`, using the same values as `sms_status`
 - `callStatus`, using the same values as `call_status`

package/person_phone/index.js

@@ -1,5 +1,5 @@
 import schema from './schema.js';
-import search from './search.js';
+import { segmentDefinitionClauses } from './segmentDefinitionClauses.js';
 import segments from './segments.js';
 import extractPhoneHashes from './transforms/inbound/extract_identifiers.js';
 import upsertPersonPhone from './transforms/inbound/upsert_tables.js';
@@ -22,12 +22,12 @@ export const transforms = {
 };
 export { metadata };
 export { schema };
-export { search };
+export { segmentDefinitionClauses };
 export { segments };
 export default {
   metadata,
   schema,
   transforms,
-  search,
+  segmentDefinitionClauses,
   segments
 };

package/person_phone/{search.js → segmentDefinitionClauses.js}

@@ -74,6 +74,7 @@ export const phones = {
     };
   }
 };
+export const segmentDefinitionClauses = { phones };
 export default {
-  phones
+  segmentDefinitionClauses
 };

package/person_phone/segments.js

@@ -1,6 +1,6 @@
 export const textable = {
   name: 'Textable People',
-  search: {
+  definition: {
     and: [
       {
         table: 'person_phone',

package/person_remote/index.js

@@ -14,8 +14,7 @@ const metadata = {
     upsert: ['upsertPersonRemote']
   }
 };
-export const search = {
-  all: {
+const all = {
     title: 'Remote people',
     name: 'All remote people',
     form: {
@@ -39,8 +38,8 @@ export const search = {
         }
       ]
     })
-  }
-};
+  };
+export const segmentDefinitionClauses = { all };
 export const transforms = {
   extractRemotePersonIds,
   upsertPersonRemote,
@@ -53,6 +52,6 @@ export default {
   metadata,
   schema,
   metrics,
-  search,
+  segmentDefinitionClauses,
   transforms
 };

package/segment/index.js

@@ -1,5 +1,5 @@
 import schema from './schema.js';
-import search from './search.js';
+import { segmentDefinitionClauses } from './segmentDefinitionClauses.js';
 import upsert from './transforms/inbound/upsert.js';
 const metadata = {
   name: '@engine9/schemas/segment',
@@ -12,10 +12,10 @@ export const transforms = {
 };
 export { metadata };
 export { schema };
-export { search };
+export { segmentDefinitionClauses };
 export default {
   metadata,
   schema,
-  search,
+  segmentDefinitionClauses,
   transforms
 };

package/segment/schema.js

@@ -23,15 +23,15 @@ export const tables = [
       category: 'string', // A arbitrary type, user facing, not to be used for logic
       definition_path: 'string', // a definition file path, will be used for configuring
       stars: 'int', //number of stars, good for UI organizing
-      search: 'json',
+      definition: 'json',
       build_type: {
         type: 'enum',
         nullable: false,
         default_value: 'list',
         values: [
           'list', //static list of people
-          'search', // built by the defined search
-          'scheduled_search', // built on a schedule by the search
+          'definition', // built by the segment definition
+          'scheduled_definition', // built on a schedule by the segment definition
           'remote_count', // no person records, just counts, pulled from remote site
           'remote', // pulled from remote plugin site
           'manual' // created outside normal processing

package/segment/{search.js → segmentDefinitionClauses.js}

@@ -59,6 +59,7 @@ export const segment = {
     return { text, eql };
   }
 };
+export const segmentDefinitionClauses = { segment };
 export default {
-  segment
+  segmentDefinitionClauses
 };

package/stacks/limited-pii/stack.json

@@ -1,7 +1,7 @@
 {
   "name": "@engine9/schemas/stacks/limited-pii",
-  "description": "PII-minimized Engine9 stack: hash identifiers instead of plaintext email, phone, or postal address. Excludes person_email, person_phone, and person_address even if requested.",
-  "version": "1.1.0",
+  "description": "PII-minimized Engine9 stack: hash identifiers instead of plaintext names, email, phone, or postal address. Excludes person_name, person_email, person_phone, person_address, and transaction/contact_details even if requested.",
+  "version": "1.2.0",
   "unique": true,
   "include": [
     "@engine9/schemas/plugin",
@@ -11,12 +11,13 @@
     "@engine9/schemas/timeline",
     "@engine9/schemas/source_code",
     "@engine9/schemas/transaction/core",
-    "@engine9/schemas/transaction/contact_details",
     "@engine9/schemas/person_hash"
   ],
   "exclude": [
+    "@engine9/schemas/person_name",
     "@engine9/schemas/person_email",
     "@engine9/schemas/person_phone",
-    "@engine9/schemas/person_address"
+    "@engine9/schemas/person_address",
+    "@engine9/schemas/transaction/contact_details"
   ]
 }

package/stacks/stacks.test.js

@@ -5,6 +5,8 @@ import { metadata as limitedPii } from './limited-pii/index.js';
 
 test('standard stack includes plaintext contact plugins and does not exclude them', () => {
   assert.equal(standard.name, '@engine9/schemas/stacks/standard');
+  assert.ok(standard.include.includes('@engine9/schemas/person_name'));
+  assert.ok(standard.include.includes('@engine9/schemas/transaction/contact_details'));
   assert.ok(standard.include.includes('@engine9/schemas/person_email'));
   assert.ok(standard.include.includes('@engine9/schemas/person_phone'));
   assert.ok(standard.include.includes('@engine9/schemas/person_address'));
@@ -18,6 +20,10 @@ test('standard stack includes plaintext contact plugins and does not exclude the
 test('limited-pii stack includes person_hash and excludes plaintext contact plugins', () => {
   assert.equal(limitedPii.name, '@engine9/schemas/stacks/limited-pii');
   assert.ok(limitedPii.include.includes('@engine9/schemas/person_hash'));
+  for (const path of ['@engine9/schemas/person_name', '@engine9/schemas/transaction/contact_details']) {
+    assert.ok(!limitedPii.include.includes(path), `${path} is not included`);
+    assert.ok(limitedPii.exclude.includes(path), `${path} is excluded`);
+  }
   assert.ok(!limitedPii.include.includes('@engine9/schemas/person_email'));
   assert.ok(!limitedPii.include.includes('@engine9/schemas/person_phone'));
   assert.ok(!limitedPii.include.includes('@engine9/schemas/person_address'));

package/stacks/standard/stack.json

@@ -1,11 +1,12 @@
 {
   "name": "@engine9/schemas/stacks/standard",
-  "description": "Opt-in Engine9 schema stack: person, plaintext email, phone, and postal address, timeline, source codes, and transactions. Reports install separately.",
-  "version": "1.0.0",
+  "description": "Opt-in Engine9 schema stack: person, plaintext names, email, phone, and postal address, timeline, source codes, and transactions. Reports install separately.",
+  "version": "1.1.0",
   "unique": true,
   "include": [
     "@engine9/schemas/plugin",
     "@engine9/schemas/person",
+    "@engine9/schemas/person_name",
     "@engine9/schemas/person_remote",
     "@engine9/schemas/segment",
     "@engine9/schemas/person_email",

package/transaction/contact_details/schema.js

@@ -1,9 +1,11 @@
-// Contact details captured on a transaction: address, email, phone, employer, and occupation.
+// Contact details captured on a transaction: payer name, address, email, phone, employer, and occupation.
 export const tables = [
   {
     name: 'transaction',
     prefix: false,
     columns: {
+      given_name: 'string',
+      family_name: 'string',
       street_1: 'string',
       street_2: 'string',
       city: 'string',

package/transaction/core/README.md

@@ -1,6 +1,6 @@
 # Transaction Core Schema Plugin
 
-The `@engine9/schemas/transaction/core` plugin stores payment and gift transactions for people and provides the common transaction search, metrics, and segment used by imports, reports, and exports.
+The `@engine9/schemas/transaction/core` plugin stores payment and gift transactions for people and provides the common transaction segment definition clauses, metrics, and segment used by imports, reports, and exports.
 
 It depends on `@engine9/schemas/person` because every transaction belongs to a person through `person_id`.
 
@@ -8,6 +8,8 @@ It depends on `@engine9/schemas/person` because every transaction belongs to a p
 
 The plugin creates the `transaction` table. Each row is a dated amount tied to a person, an input, and optional source-code / message attribution.
 
+The payer's name, email, phone, and address are not part of this plugin. `@engine9/schemas/transaction/contact_details` adds those columns to `transaction`; the limited-pii stack excludes it.
+
 | Field | Type | Description |
 | --- | --- | --- |
 | `id` | `id_uuid` | Primary row identifier. |
@@ -22,7 +24,6 @@ The plugin creates the `transaction` table. Each row is a dated amount tied to a
 | `recurs_id` | `int` | Recurring frequency. `0` is one-time. Defaults to `0`. |
 | `recurring_number` | `int` | Sequence number in a recurring series. |
 | `refund_amount` | `currency` | Refunded amount when applicable. |
-| `given_name` / `family_name` / `email` | `string` | Snapshot of payer identity on the transaction. |
 | `source_code_id` | `source_code_id` | Source code captured on the transaction. |
 | `override_source_code_id` | `source_code_id` | Manual source-code override. |
 | `final_source_code_id` | `source_code_id` | Source code after attribution. |
@@ -52,10 +53,10 @@ The inbound `upsert` transform writes rows to `transaction`.
 
 `appendTransactionSummary` looks up a person's transactions and attaches summary fields such as count, revenue, first/last/smallest/largest gifts, and recurring totals.
 
-## Search
+## Segment definition clauses
 
-- `all` finds people who have any transaction, optionally filtered by `plugin_id` and a `start` / `end` window on `ts` (ISO datetimes or relative expressions such as `-30d`).
-- `minimum` finds people who have a transaction of at least a given `amount`.
+- `all` selects people who have any transaction, optionally filtered by `plugin_id` and a `start` / `end` window on `ts` (ISO datetimes or relative expressions such as `-30d`).
+- `minimum` selects people who have a transaction of at least a given `amount`.
 
 ## Metrics
 
@@ -73,7 +74,7 @@ Predefined audiences shipped with this schema plugin. On install, each key becom
 | **Definition path** | `@engine9/schemas/transaction/core:segments:customers` |
 | **Who is included** | People who have at least one row in `transaction` |
 | **Who is excluded** | People with no transactions |
-| **How it is built** | A `transaction` table search that selects `person_id` with no extra filters |
+| **How it is built** | The `all` clause, which selects `person_id` from `transaction` with no extra filters |
 | **Universe** | None — any transaction from any plugin, date, or amount counts |
 
 Refunds, recurring gifts, and $0 rows are not filtered out. If a person has ever appeared on a transaction row, they are a customer.

package/transaction/core/index.js

@@ -1,5 +1,5 @@
 import schema from './schema.js';
-import search from './search.js';
+import { segmentDefinitionClauses } from './segmentDefinitionClauses.js';
 import metrics from './metrics.js';
 import segments from './segments.js';
 import upsert from './transforms/inbound/upsert_tables.js';
@@ -19,13 +19,13 @@ export const transforms = {
 export { metadata };
 export { schema };
 export { metrics };
-export { search };
+export { segmentDefinitionClauses };
 export { segments };
 export default {
   metadata,
   schema,
   metrics,
   transforms,
-  search,
+  segmentDefinitionClauses,
   segments
 };

package/transaction/core/schema.js

@@ -18,9 +18,6 @@ export const tables = [
       },
       recurring_number: 'int',
       refund_amount: 'currency',
-      given_name: 'string',
-      family_name: 'string',
-      email: 'string',
       source_code_id: 'source_code_id',
       override_source_code_id: 'source_code_id',
       final_source_code_id: 'source_code_id',

package/transaction/core/{search.js → segmentDefinitionClauses.js}

@@ -81,7 +81,7 @@ export const minimum = {
     conditions: [`amount>=${parseFloat(options.amount)}`]
   })
 };
+export const segmentDefinitionClauses = { all, minimum };
 export default {
-  all,
-  minimum
+  segmentDefinitionClauses
 };

package/transaction/core/segments.js

@@ -1,6 +1,6 @@
 export const customers = {
   name: 'Customers',
-  search: {
+  definition: {
     and: [
       {
         table: 'transaction',

package/utilities/limited-pii/settings.js

@@ -4,7 +4,7 @@ export const settings = [
     type: 'boolean',
     default: false,
     description:
-      'When true, installDefaultPlugins prefers @engine9/schemas/stacks/limited-pii over default_stack, and installs of stacks/standard, person_email, person_phone, and person_address are refused. Does not drop existing plaintext tables. Also omits those tables from the default export list when tables is not set.'
+      'When true, installDefaultPlugins prefers @engine9/schemas/stacks/limited-pii over default_stack, and installs of stacks/standard, person_name, person_email, person_phone, person_address, and transaction/contact_details are refused. Does not drop existing plaintext tables. Also omits the plaintext person tables from the default export list when tables is not set.'
   }
 ];
 export default {