Learned screen

Tama shows proposals for contested hooks, drafted rules, named causes and unexplained operator corrections. The screen reads the sealed CLI's tama rules digest through tama request rules/digest; it does not install policy.

#What a row shows

• The contested hook, drafted rule or cause the proposal is about.
• What was observed, how often, and the first and last observation.
• For a lesson, expand Read sources to see every Oko session, the operator's words, its named cause or Cause not yet named, the linked defect when present, the readings that flagged the moment and any earlier repetitions. A linked defect groups named moments; otherwise identical causes group them. Unexplained moments appear separately, not as one assumed cause.
• The selectable command: tama adaptive repair <hook>, tama rules remove --id <rule>, oko defects show <defect-id> for a linked lesson, oko frustration show <moment-id> for an unlinked named lesson, or oko frustration list --open for unexplained moments. The Oko commands inspect evidence; they neither fix the cause nor enable a hook.

#Dismiss until new evidence

The button runs tama request rules/dismiss with the proposal's id and the operator's approval for that one request. The proposal leaves the screen and comes back when more evidence arrives than it had. A refusal is shown as the command's own sentence.

#When a source cannot be read

A failed Oko read appears as oko-frustration unreadable with the command's failure, and a failed adaptive read names that source. An existing damaged draft registry appears as drafted-rules unreadable with its path and read or parse error. The detached drafter's latest failed gateway request or write appears as frustration-drafter unreadable with the recorded operation, time and error. The same entries appear under unreadable in tama rules digest --json. Other proposals remain visible; an empty list beside a failure does not mean there were no corrections or that the model request worked.

If the local dismissal record cannot be read or parsed, the whole digest request is refused. The screen shows the file error, not a successful empty list; it cannot decide which proposals are hidden from damaged state.

The screen is under Policy and needs policy control, like the build registry.