ARCHITECT
The schema is edited on the record.
You move fields to where they will be read, and it is the object's structure that changes.
You edit where you look
Most tools keep configuration somewhere else: an admin panel, an abstract list of fields, a preview that lies a little. You set things on one side and check them on the other. Here the record is the editor. A field is grabbed, moved from one group to another, renamed inline, and dropped at the exact place where it will be read. What you see while editing is what your colleague will see.
Placing a field, or creating one
These are two distinct operations, and the platform does not conflate them. Placing rearranges the layout of an object whose vocabulary is already settled: the field exists, it changes position. Creating touches that vocabulary, so a dropzone opens a dialog that insists on a type. That type commits everything downstream, from validation to rendering.
Place
An existing field joins a group on the record, at the position you want.
Create
A dropzone opens attribute creation, and asks for its type.
Rename
The label is edited inline, without leaving the record.
What you create belongs to you
An attribute created from the workspace is never marked as coming from code, and that mark decides what can happen to it later. Yours can be renamed, reconfigured and deleted. The ones your engineering team declared refuse modification at runtime, because automations depend on them. That boundary is what lets structure editing open up without making the application fragile.
What assisted generation actually covers
The engine can produce two things from a plain-language description: a regular expression, and a calculation formula. That helps where syntax is the real obstacle, and it is bounded. Laying out objects, picking types and deciding relations remains design work, done by hand in the editor, where every move is visible and reversible.
How it works
Adding a « mandate expiry » field to the Client object.
You switch to architect mode. The record stays on screen, its fields become movable.
You rearrange. Drag and drop between groups, and fix labels inline.
You create what is missing. A dropzone opens attribute creation and asks for its type: a date.
The object has changed. For all of its records, with no redeployment or migration to schedule.