The recs files

Skills that instruct an agent to keep the truth of a system in records, and to realize the system from them.

User workflow

UW-1 Create a record

Status
Accepted
Actor
Record keeper
Scope
The recs files
Level
User goal

Trigger

Something worth recording surfaces: a decision, a definition, a workflow, a feature, or the exact text the system gives on a refusal or a failure.

Minimal guarantee

Nothing stands before the record keeper agrees to it.

Success guarantee

The record is written in a file of its own and listed in its category's projection, and every sentence it falsifies is replaced.

Main success scenario

  1. Record keeper tells the agent what is to be recorded
  2. Agent places it in a category, and searches the standing records for one that already decides it
  3. Agent drafts the record in its category's form and writes it as proposed, with its line under the projection's Proposed heading, and finds every sentence the record falsifies, with the wording that replaces it
  4. Agent shows the record keeper the draft and the falsified sentences with their replacements
  5. Record keeper agrees
  6. Agent marks the record accepted, moves its line out from under the projection's Proposed heading, and writes the replacements

Extensions

2a. A standing record already decides it
  1. Supersede a record (UW-2: Supersede a record); the use case ends
2b. The placement tests do not settle the category
  1. Agent shows what each test found, and the record keeper picks the category
3a. The record needs a term the ubiquitous language does not define
  1. Agent proposes candidate words, built from existing words first, and waits
  2. Record keeper agrees to one; continue at 3
4a. Record keeper rewords the draft
  1. Agent redrafts; back to 4
4b. Record keeper declines
  1. Agent marks the record rejected and removes its line from the projection; the use case ends
6a. Writing turns up a falsified sentence not shown at 4
  1. Agent shows it to the record keeper; back to 5