abstract-well

# Abstract well ## Contract | Field | Bound contract | |---|---| | Trigger | The user wants to classify a set of abstractions as useful, bad, or busy and keep one shallow level. | | Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. | | Side effect | A chat-output classification and one-shallow-level recommendation. Nothing is written or changed. | | Done | Every abstraction in scope is classified as useful, bad, busy, or unclassified, and a single shallow level is selected whose cooked form is easier than its raw form, or an explicit statement is returned that no useful level exists. | ## Inputs - The abstractions to review. Supply either an explicit list of named abstractions (wrappers, helpers, interfaces, layers, adapters) or a scope (file, module, or function set) from which they are enumerated. - The caller perspective: whose code uses each abstraction. If omitted, the caller is the immediate consumer of the abstraction. - The underlying operation each abstraction wraps must be knowable so a raw form can be written. If it is not, the abstraction is marked unclassified. ## Procedure 1. Enumerate the abstractions in scope. If the user named them, use that list. If the user gave a scope, list every named wrapper, helper, interface, layer, or adapter inside it. Do not invent abstractions that the input does not name or contain. Done when: every abstraction in scope is listed. 2. For each abstraction, write two concrete form...