Interfaces
Explicit contracts shared by several concrete objects.
An interface is an abstract contract implemented by several concrete objects. It enables polymorphic references without merging unrelated business types into one table.
Define an interface
12345678export const Party = defineInterface({ id: "party", name: "Party", fields: { displayName: text({ required: true }), email: email(), },})An interface describes the fields a consumer can rely on. It does not create records of its own.
Implement an interface
123456789export const Customer = defineObject({ id: "customer", name: "Customer", fields: { name: text({ required: true }), email: email({ required: true, unique: true }), }, implements: [Party.map({ displayName: "name", email: "email" })],})An object opts in explicitly and maps its fields to the interface. Matching field names alone do not imply implementation. Reads through an interface preserve the concrete object identity.
What interfaces enable
- Typed tool parameters that accept several object types.
- Relationships to a shared business role such as Party or Owner.
- Cross-implementation search, lists, and generic rendering.
- Multiple interfaces implemented by one object.
Framework-managed relationships to an interface must preserve database-enforced identity rather than storing an unchecked type-and-ID pair.
Initial limits
The first contract supports fields, explicit mappings, multiple interfaces per object, cross-implementation reads, typed tool parameters, and generic rendering. Inheritance, interface-owned tools, and interface-specific authorization wait for demonstrated needs.