toolchain.not_built_yet

Operation is declared but not built yet.

Area 3, Logic; not declinable; the next step is usually the agent's.

The language declares some operations that aren't built yet, such as the generated oauth.approve (area 8). Calling one is an error rather than a program that can't run:

type ConsentId = Uuid {}action approve_consent(consent: ConsentId) -> Unit {    oauth.approve(consent)}

  |4 |     oauth.approve(consent)  |     ^^^^^^^^^^^^^ declared, not built

A decided feature that isn't built can also be refused where its effect would be wrong. A File in a route's output: or a failure's client: is refused, because downloads aren't built and the answer would hold the store and key the file is kept under (What a File holds). A File in a provider operation's input: or a webhook's reply: is refused for the same reason, since sending a file to a provider isn't built. A FileContents in a route's output: or a failure's client: is refused too, since the answer would hold the whole file as Base64.

An email's attachments are its File fields, one file each, so a List<File>, a Set<File> or a Map of them and a FileContents on an email or a partial are refused, as a File on a partial is, since each would compile and never be sent (Attachments).