Records

Records

Records are Auton8's structured data. You define the shape at runtime — no redeploy, no migration — and the platform gives you list, detail, search, comments, relationships and audit for free.

Record types and fields

Records → Record Types is where the shape lives. A record type has a name, a key, and a list of fields.

Each field has a data type, and each type carries its own configuration:

Type	Shown as	Configuration
text	Text	variant (single/multi), maxLength (default 4000)
number	Number	variant (e.g. decimal), precision, min, max
date	Date	variant (date, …)
option	Option	multi (single- or multi-select), choices of {value, label}
boolean	True/False	—
email	Email	—
phone	Phone	region (default US)

Choose the type that matches the meaning, not the storage. option gives you a constrained vocabulary you can filter on cleanly; a text field holding "gold"/"silver" does not.

The editor also surfaces a schema audit panel, which flags shape problems in a type before they become data problems.

Working with records

Records lists instances. From there you can create, open, edit and archive. The list supports filters built from a field, an operator and a value — choose the field by name rather than by position, and the operator list adapts to the field's type.

Archived records are kept, not deleted, and are visually distinguished in the list.

Detail view

A record's page shows its fields, its relationships, its comments, and its history. Actions you lack permission for are not rendered — a delete button you can see is a delete button you can use.

Comments

Records carry threaded comments, with their own view/create/edit permissions, so you can let people discuss a record without letting them change it.

Watching

Watch a record to be notified about it. Watched records surface on the Home page, alongside your tasks.

Relationships

Two mechanisms, for two different jobs.

Record fields of type record point at another record — a simple, typed reference, part of the schema.

Record edges are first-class relationships between records, with their own edge types (Records → Record Edge Types) and optional fields on the edge itself. Use these when the relationship carries meaning of its own — a role, a date range, a quantity — or when you need to traverse from either end.

Edges are traversable: given a record, you can ask what it connects to and in which direction, which is what makes them worth the extra concept.

Querying records

Anything you can see in the list, you can ask for precisely in Queries-and-Dashboards. The AQL entity is Records, and it merges each record type's own fields into the schema, so field names complete as you type.

RecordActivityRollup is a companion entity for activity over time, which is usually what you want on a dashboard rather than raw rows.

Permissions

Record access is enforced per action — view, create, edit, delete, assign, comment — and grants can be scoped by a selector, so "edit records of type invoice" or "view this one record" are both expressible. See Administration for the grammar.

Two consequences in daily use:

• The record list shows what you may see; it is filtered server-side, not hidden client-side.
• If a record seems to vanish, check the grant before suspecting the data.