AGENTS.md: a preferences screen is not a record, so editing-as-a-mode doesn't reach it

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Greg ShuflinandClaude Opus 5.5 committed 2026-10-03 20:44:19 -07:00
1 parent da4336a791
commit 1a3eb9f65f
1 file changed
+8
+8
View File
@@ -86,6 +86,14 @@ finished, whatever else it does.
document — Humans' interactions, shared with their other attendees — is
written when the user says to write it, and lives outside the mode. The
test is whether it is a *field of this record* or a record of its own.
- A preferences screen is not a record. Settings is a set of independent
choices — a theme, a zoom level, a timezone, a sync policy — each
meaningful on its own, and some only judgeable once seen applied. So a
control there applies the moment it is touched, the way every platform's
settings do, and a free-text field (a node name, a credential) commits on
its own Save or Enter rather than per keystroke. The test is whether the
values describe one thing the user would want to back out of together, or
are separate choices that only share a screen.
- Worked examples: `rust/gui-app/src/agents/human.rs` (`DetailMode`,
`reload_detail`, `save_current`) and Android's `HumanDetailScreen.kt`.
- **The instant-feedback invariant**: anything that might not complete promptly