fix(tables): the tables the assistant writes are written by nobody else; a person's save sets no field the server decides #122

Merged
james.maes merged 1 commits from fix/system-written-tables-refuse-user-writes into develop 2026-11-21 06:11:33 +00:00
1 Commits
Author SHA1 Message Date
james.maesandClaude Fable 5.2 445c6b1973 fix(tables): the tables the assistant writes are written by nobody else; a person's save sets no field the server decides
maven / build (push) Successful in 9m54s
build / maven (push) Successful in 9m54s
Every table of the assistant has a decision about who writes it, by
operation (AssistantTableWrites); a table without one is not built. The
settings are edited by an administrator on a record screen. A conversation
is renamed, archived and deleted by its owner, and started only by the
assistant. Everything else (what was said and done, and what was spent) is
written by the assistant only.

The assistant enforces the decision itself, on any QQQ version: a table has
no capability for what a person may not do to it, so a screen is offered no
button and QQQ defines no bulk action; and the permission checker of every
table refuses the insert, update or delete a table route is about to make,
for every person, with 403 and a message that says why. The assistant's own
writes go through AssistantStore, in code, and are unchanged.

A person's save of a settings table sets no field that is not editable (the
id, the create date, who granted an override, health and test results, index
counters, a scheduled task's approval and run fields): StoredRecords.ofSave,
used by every settings customizer, takes them out of a USER save before a
rule sees them. A client that sends a whole record back keeps working.

Tests go through the real table routes against the fixture application.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-20 22:17:43 -06:00