Recognises a record editable after declaration
Declared records whose content can change.
Can AI do this?
Not settled yet The benchmark tested this, but the models' answers do not settle yet whether they master it. 0 of 4 models in the current benchmark master it.
| Model | Tier | Probability of mastery | Status |
|---|---|---|---|
| gemini-4-argon | Flagship | 84% | Not shown |
| gemini-3.5-flash-lite | Low cost | 83% | Not shown |
| gpt-6-luna | Low cost | 84% | Not shown |
| claude-haiku-5-5 | Low cost | 84% | Not shown |
Mastered means a probability of at least 90% that the model has this knobit, estimated from its graded answers. “Not shown” means the answers do not settle it either way. How the models are tested.
What it looks like in practice
Expected result: The record class and the lock it needs
How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: RP-001 signed agreements stored as editable .docx, replaced on correction Acceptable: Locked on declaration; corrections as linked new records
Also known as: Record editable after declaration
Related knobits
Builds on
Usually followed by
All 15 knobits of Control the repository, access and audit trail.
Source: Review checklist 05-repository-audit-trail, row 1 (15489 5.2; MoReq)