A request that needs several controls, such as a coupon payment, a holder notice and a filing, opens a plan instead of a single draft. The plan lists the steps in the order you wrote them, with the values taken from your words and what each step does to the asset before you sign anything.
A plan never signs and never submits. It is a prepared order of work. Every step is signed in the control that owns it, with the wallet verification that control already asks for.
Steps
Ask for a plan
Open Search on an asset page and ask for the changes you want, separating them the way you would say them: “pay the Q3 coupon on all Brightline bonds, notify holders, then file it”.
- The assistant splits the request where one instruction ends and the next begins: at a sentence end, a semicolon, a comma between two phrases, or the word “then”.
- Each part is matched to one of the controls search already drafts. A part that matches nothing is left out, and a request that matches only one control is answered as a single draft.
- A plan holds at most six steps. Parts after the sixth are cut.
The plan does not list a part it left out or cut, so compare its steps with your request before you work it.
Read each step before you sign it
Each step shows the control it opens, the values drafted from your words, and the words it took them from. Under that, it shows what the step does to the asset, simulated against the state read when the plan was built, at the time the plan shows:
- the total supply before and after.
- the balance of each holder the step moves, before and after.
- the paying treasury and its balance in the denomination asset, for a step that pays cash.
- the five largest holders, with the balance each would hold after the step.
The steps are simulated in order, so each one is applied on top of the step before it. A step that pays out after a step that mints sees the larger supply.
The simulation is DALP's own calculation over its indexed reads of the asset, not a run of the transaction. It checks the role, the pause, the supply cap, the treasury and the balances of the ten largest holders, and marks a check it could not make as “not checked”. It does not apply the token's compliance rules, so a step that reads “This step goes through on the state read.” can still be refused when you sign it.
A step that cannot go through says so, in plain words: the token is paused, a holder's balance is too small, the supply would pass its cap, the treasury does not cover the payment, or you do not hold the role the control needs. The rest of the plan still shows its own outcome.
Work the plan
Choose a step to open its control with the values filled in, then preview, approve and sign it there. When you come back, the plan shows the step as done.
A step that changes balances is marked done when the chain shows its effect. A step that leaves no trace on chain, such as a holder notice, is marked done by you with Mark done. That mark records that you marked it, not that the notice went out.
A plan is saved for you and the asset. Open Search on the same asset and your open plans are listed under Open plans, before the suggestions. Open one to carry on where you left it. Choose “Refresh simulation” after the asset has moved, so the figures and the outcome reflect the state you are about to sign against. Choose “Abandon plan” for a plan you no longer want. A plan whose steps are all done closes itself. A closed plan, abandoned or completed, still shows its steps but no longer offers to open a step or mark it done.
What leaves DALP
A plan asks the model two things per step: which control the words ask for, and which values they give. Those values are the model's reading of your words, shown next to the words they came from, so check them in the control before you sign. Every figure, verdict and check in a plan comes from DALP's indexed reads of the asset and its own calculation, not from the model. The names, masking and data scope on the Assistant data page apply to those questions as they do to any other.