ANIMA-NODE / 02
Autonomy needs a boundary.
From agent behaviour to the design of budgets, decisions and refunds.
JOURNAL / ANIMA-NODE
Ideas, decisions and lessons from a project in development.
The next question
Overseeing an agent is not only about observing its answer. The effort needed to reach it also matters. If a task runs longer, repeats attempts or changes scope, the system needs a way to decide when to continue and when to request authorisation again.
More activity is not always more value
One of Anima-node’s central ideas is to separate resources consumed from necessary work. Repeating an action should not make it more valuable. I want the design to account for useful progress rather than automatically reward the amount of activity.
The budget is part of the experience
The proposal distinguishes a task’s execution budget from the total authorised limit. If an increase is needed, the decision returns to the person authorising it. From a user experience perspective, that means showing what is happening, what is needed and what happens if they choose to stop.
The ending needs design too
A task may succeed, remain incomplete or be cancelled. Each ending needs understandable rules about settlement and refunds. Designing for those situations from the beginning is part of the trust the project aims to build. The model remains experimental and needs validation.