--- title: "Decisions and Tasks" url: "https://hurukan.com/modules/decisions-and-tasks" description: "One approval inbox for every agent proposal, with sources and risk, bulk approval and routing by risk, and tasks that always have an owner and a reason when waiting." --- # Decisions and Tasks When agents do the preparing, people do the deciding, and they need one place to do it. Decisions and Tasks is that place: one approval inbox for every proposal from every module, with its sources and its risk, and a task list in which nothing is ownerless and nothing waits without a reason. [Talk to us](https://hurukan.com/contact) A manager approving items on a tablet at a desk in a minimal office Module - One approval inbox for every agent proposal - Sources and risk shown with each proposal - Bulk approval and routing by risk - Tasks always have an owner, and a reason when waiting ## Where people decide Every other module ends in a proposal: a quote ready to send, a purchase order ready to place, a payment run ready to release, a change to the system ready to ship. If those proposals were scattered across ten screens, the bottleneck would simply move from typing to searching. So they all arrive in one approval inbox, routed to the people entitled to decide them. ## A proposal that carries its evidence Each proposal shows what the agent was asked to do, the records and documents it used, what it concluded and what risk it sees. The approver can accept it, change it or reject it with a reason. All three outcomes are recorded by the **Security and Sovereignty** layer, and rejections feed back into how the agent’s limits are set in **Agentic Logic**. ## Routing and bulk approval Proposals are routed by area, value and risk. Low-risk proposals of the same kind — a batch of routine reorders, say — can be approved together within limits the company sets. Critical operations are always reviewed one at a time by a person, and the server enforces that their approval comes from people. ## Tasks that stay visible Not everything is a proposal. Some work is simply work, and it needs an owner. In Hurukan every task has one, every task has a due date, and a task that is waiting has to say what it is waiting for. When someone goes on leave or changes role, their tasks move to a deputy with the history attached, and **People** supplies the structure that decides who that deputy is. ## What the module covers 01 ### Approval inbox Proposals from every module — a purchase order, an offer, a payment run, a change to the system — in one inbox, for the people entitled to decide them. 02 ### Sources and risk Each proposal shows the records and documents the agent relied on, what it concluded, and the risk it sees, so a decision does not require redoing the research. 03 ### Routing by risk Proposals go to the right person by area, value and risk. Higher risk means a more senior approver or a second approval, by rule. 04 ### Bulk approval Low-risk proposals of the same kind can be approved together, within limits the company sets. Critical operations are always approved one by one. 05 ### Tasks with owners Every task has an owner and a due date. A task that is waiting must say what it is waiting for, so stalled work is visible. 06 ### Handover history When a task changes hands, the history goes with it: who held it, what was done and why it moved. ## Works with [Three people around a large touch table in a glass meeting room, one pointing at a flow of cards ### Agentic Logic Domain agents that act within written limits, with people deciding on critical steps. → ](https://hurukan.com/system/agentic-logic)[A person holding an access card to the reader at the glass door of a server room ### Security and Sovereignty Server-side permissions, an audit of every change, your infrastructure, open source and a written exit. → ](https://hurukan.com/system/security-and-sovereignty)[A long data-centre aisle between rows of graphite server racks with small status lights ### Super Intelligence Frontier and local models, routed per task under the company's rules. → ](https://hurukan.com/system/super-intelligence)[A person reviewing cash-flow charts on a large monitor at a tidy desk with a calculator and documents ### Finance Finance and controlling: budgets from plan to forecast, inbound invoices, invoicing, payments and cash flow, linked to accounting. → ](https://hurukan.com/modules/finance)[A small team at a whiteboard wall with sticky notes, one person explaining while others listen ### People People registry, org units, access, certifications with expiry, leave, rosters and time-and-attendance anomalies. → ](https://hurukan.com/modules/people) ## Questions What can be approved in bulk? Only proposals below a risk level the company sets, and only of the same kind. Critical operations — money leaving, a commitment to a customer, a change to permissions — are approved individually. Why must a waiting task have a reason? Because a task that waits without one is how work quietly disappears. A stated reason — waiting for a supplier, waiting for a document — makes it possible to chase the right thing. What happens when someone is on leave? Their open approvals and tasks are routed to a deputy according to the rules, with the full history attached, and the handover itself is recorded. [← PreviousProjects and Documents](https://hurukan.com/modules/projects-and-documents)[Next →The whole architecture](https://hurukan.com/system) ## Build the company's operating system with us Hurukan is pre-launch. If you run a company and want a sovereign, agentic system rather than another suite, we would like to hear what you need. [Talk to us](https://hurukan.com/contact)