SAE gives agents a shared way to describe the work before transport and runtime details take over. The aim is less renegotiation, clearer handoff, and outputs that are easier for another system or a human reviewer to understand.
SAE is intentionally small. If a field does not help preserve task meaning across systems, it probably does not belong in the public core.