The execution layer is still being built, so nothing below runs yet. It describes the contract the
errands are being built against, which is fixed.
Your assistant relays, it does not decide
When Hence needs something, the task moves to needs input and your assistant repeats the question in its own voice. You answer in the conversation, and your assistant returns the answer. Hence does the errand; your assistant carries the words. What Hence needs falls into a few kinds, and the kind decides the mechanism.A data point
Something only you know, that the portals do not show: the rate written on an original car loan contract, which of two employers a plan belongs to. Asked as a single question, with options wherever the errand knows the options. Hence never asks for a value it already holds. If your profile carries the answer, that answer is used, and what you tell it here is kept so the next errand does not ask again.A yes or a no
Asked as a two-value question. Accept and decline are distinct answers, and cancelling the question counts as no. Nothing proceeds on silence.An approval
An approval is a yes that authorizes a consequence — changing a deferral rate, sending a request to an issuer. Three rules attach to it:- It names the exact parameters. Not “change your contribution rate” but the current rate, the proposed rate and what it is worth.
- It is bound to those parameters. The approval is checked again at the moment of acting; if anything changed in between, Hence asks again rather than proceeding on the old yes.
- One approval authorizes one act. There is no standing yes.