symbols, booleans, characters, keywords, and null, which are treated as contracts that recognize themselves, using eq?,

strings and byte strings, which are treated as contracts that recognize themselves using equal?,

numbers, which are treated as contracts that recognize themselves using =,

regular expressions, which are treated as contracts that recognize byte strings and strings that match the regular expression, and

predicates: any procedure of arity 1 is treated as a predicate. During contract checking, it is applied to the values that appear and should return #f to indicate that the contract failed, and anything else to indicate it passed.

Flat contracts can be fully checked immediately for a given value. These kinds of contracts are essentially predicate functions. Using flat-contract-predicate, you can extract the predicate from a flat contract, and flat-contract? recognizes a flat contract.

Chaperone contracts are not always immediately checkable, but are guaranteed to not change any properties of any values that they check. That is, they may wrap a value in such a way that it signals contract violations later, as the value is used (e.g., a function contract checks the inputs and outputs to the function only when the function is called and returned), but any properties that the value had before being wrapped by the contract are preserved by the contract wrapper.

All flat contracts are also chaperone contracts (but not vice-versa).

Impersonator contracts do not provide any guarantees about values they check. Impersonator contracts may hide properties of values, or even make them completely opaque (e.g, new-∀/c).

All contracts are impersonator contracts.