Part B · The screens
B.15Fields
The field sheet: for each Nutshell field, whether the AI may change it, at what autonomy and with whose approval, and which fields stay people-only. DMA signs the sheet off; every change is four-eyes.
- No.
- B.15
- Dashboard address
- /fields
What you can do here
Each core task, and how many clicks it takes from this screen.
| Task | Clicks | How |
|---|---|---|
| Change what the AI may do with a field | 3 | Fields → the field's setting → pick the new one. It is filed for a second person. |
| Request DMA's sign-off on the sheet | 2 | Fields → Request sign-off. Someone other than the requester grants it. |
| See a field's rule | 1 | Fields: each row says in words who owns the field and what the AI may do. |
How it works behind the scenes
- Every write to Nutshell passes through the write gate, and the gate looks up the field's rule before anything is written: people-only fields are never proposed; AI fields (such as AI Service Lanes) may be written at the level the sheet allows; the rest wait for a person.
- The fields the AI owns are its own "AI …" fields, so it never overwrites what a rep typed unless the sheet says it may.
- Some writes also wait for named sign-offs before they can go at all: for example, the lost-reason and source mapping, and the Phase 0 dry run. Those holds show in Approvals as held batches, not as items to approve one by one.
Rules and switches that apply here
- Each field's rule is a versioned rule; changing it needs a second person.
- Kill switches for writes to companies, people and deals stop the gate for that kind of record.
The tables behind it
PK primary keyFK reference the database enforces (solid line)ID reference kept by id (dashed line)
| Table | What it holds | Columns |
|---|---|---|
| ctrl.policy_rules | The field rules (kind field_write), one per field, versioned and approved. | 21 |
| ctrl.outbox | The write gate: each proposed change, the rule that decided it, and what it replaced. | 28 |
How the tables connect (2)
| Column | Points to | Kept by |
|---|---|---|
| ctrl.policy_rules.approval_id | ctrl.approvals | The application (by id) |
| ctrl.outbox.approval_id | ctrl.approvals | The database (foreign key) |
The screen
localhost:13301/fields
Fields: who may change which Nutshell field, and at what autonomy.
- 1DMA's sign-off for the whole field sheet.
- 2One field and what the AI may do with it.
Dashboard · Govern → Fields. Captured from the running POC on September 25, 2026; synthetic data.
See it live
Opens the screen in the running POC, in a new tab.
| Open | Where | What to try |
|---|---|---|
| Fields | DMA AI dashboard | Each Nutshell field and what the AI may do with it. |