One CollectionConfig, Three API Surfaces

```typescript import type { CollectionConfig } from "@aeion/types/schema";

export const Products: CollectionConfig = { slug: "products", labels: { singular: "Product", plural: "Products" }, admin: { group: "Commerce", useAsTitle: "name", defaultColumns: ["name", "price", "stockLevel", "status"], }, timestamps: true, // adds createdAt / updatedAt softDelete: true, // adds deletedAt + filters soft-deleted from defaults

fields: [ { name: "name", type: "text", required: true }, { name: "price", type: "number", required: true, min: 0 }, { name: "description", type: "richText" }, { name: "category", type: "relationship", relationTo: "product_categories", }, { name: "tags", type: "tags" }, { name: "metadata", type: "json", storage: "jsonb" }, { name: "status", type: "select", options: ["draft", "active", "archived"], defaultValue: "draft", }, ],

access: { read: ({ user }) => Boolean(user), create: ({ user }) => user?.role === "admin", update: ({ user, doc }) => doc.createdBy === user?.id || user?.role === "admin", delete: ({ user }) => user?.role === "admin", }, }; ```

What that one definition produces:

• A Postgres table named products (with tenantId, id, createdAt, updatedAt, deletedAt, plus every field above)
• 5 REST endpoints — GET /api/v1/products (list), GET /api/v1/products/:id, POST, PATCH, DELETE
• 5 MCP tool actions — list_products, read_product_by_id, create_product, update_product, delete_product
• A typed admin UI surface with the listed columns, edit form, search, and filter UI
• Zod input validators run automatically on create / update
• Tenant scoping on every query (Layer 0 enforces it)
• Optional GraphQL exposure (toggle per collection)

Text (5)

typescript { name: "title", type: "text", required: true, maxLength: 200 } { name: "bio", type: "textarea", rows: 5 } { name: "contactEmail", type: "email" } // validates RFC 5322 + DNS optional { name: "homepage", type: "url" } // validates URL parse { name: "body", type: "richText" } // ProseMirror JSON, exports to HTML / Markdown

Numbers (3)

typescript { name: "price", type: "number", min: 0, max: 1000000 } { name: "publishedAt", type: "date" } // ISO 8601 string in transit, Postgres timestamptz at rest { name: "stars", type: "rating", max: 5 }

Selection (7)

typescript { name: "subscribed", type: "checkbox" } // boolean — single checkbox { name: "featured", type: "switch" } // boolean — toggle UI { name: "status", type: "select", options: ["draft", "active", "archived"], defaultValue: "draft" } { name: "tier", type: "radio", options: ["free", "pro", "enterprise"] } { name: "tags", type: "tags" } // freeform multi-string with auto-suggest from prior values { name: "interests", type: "checkboxGroup", options: ["news", "products", "events"] } { name: "color", type: "color" } // HSL / hex picker UI

Relations (2)

```typescript { name: "category", type: "relationship", relationTo: "product_categories" } { name: "category", type: "relationship", relationTo: "product_categories", hasMany: true } { name: "author", type: "relationship", relationTo: ["users", "external_authors"] } // polymorphic

{ name: "hero", type: "upload", relationTo: "media", mimeTypes: ["image/"] } { name: "gallery", type: "upload", relationTo: "media", hasMany: true, mimeTypes: ["image/", "video/*"] } ```

Structured (4)

```typescript { name: "address", type: "group", fields: [ { name: "street", type: "text" }, { name: "city", type: "text" }, { name: "zip", type: "text" }, ]}

{ name: "phoneNumbers", type: "array", fields: [ { name: "label", type: "select", options: ["home", "work", "mobile"] }, { name: "value", type: "text" }, ]}

{ name: "pageLayout", type: "blocks", blocks: [ { slug: "hero", fields: [...] }, { slug: "callout", fields: [...] }, { slug: "twoColumn", fields: [...] }, ]}

{ name: "metadata", type: "json", storage: "jsonb" } // arbitrary JSON, Postgres jsonb under the hood ```

Advanced (1)

typescript // Computed — derived field. Not stored; calculated on read. { name: "displayName", type: "computed", compute: (doc) => ${doc.firstName} ${doc.lastName}.trim(), }

Every collection declares four optional access hooks. Returning true grants permission; returning a query fragment narrows the query; returning false denies.

```typescript access: { // Pre-query — what rows can this user list / read? read: ({ user, tenant }) => user?.role === "admin" ? true : { authorId: { equals: user?.id } },

// Pre-write — can this user create this kind of doc? create: ({ user, data }) => user?.role === "admin" || (user?.role === "editor" && data.status === "draft"),

// Pre-write — can this user update this specific doc? update: ({ user, doc }) => doc.authorId === user?.id || user?.role === "admin",

// Pre-write — can this user delete this doc? delete: ({ user, doc }) => user?.role === "admin", }, ```

Access hooks run _before_ every query — for list operations, the framework merges the returned filter fragment into the WHERE clause. There's no "load row first then check" race condition; if a row isn't permitted, it never appears in results.

Collections can declare which platform extensions a tenant must own to see them. The check happens _before_ access hooks; unauthorized tenants get an unsatisfiable filter ({id: {equals: "__no_access__"}}), so the collection effectively disappears.

typescript extension: { moduleId: "aeion-events", extensionId: ["events.pro", "events.enterprise"], // OR — any of these grants access },

This is how Aeion's pricing tiers gate features without code-level branching. The same collection definition serves Free / Pro / Enterprise — the platform handles tier enforcement transparently.