How it works · Flow F10

Set a goal. One3 diagnoses, plans, acts, monitors and learns.

One3's signature loop: a human goal is parsed, diagnosed, planned and approved, then run by people and agents, monitored, re-planned with evidence and closed in the Decision Journal.

What the Goal to outcome flow does

Goal to Outcome is the flow the rest of One3 exists to serve. Every other app lets this loop see (data), think (intelligence), act (Actions) and learn (the flywheel).

A human sets a goal such as "Increase Chennai sales 20% this quarter". A goal parser turns it into a KPI, region, baseline from the semantic layer and deadline. The Decision Engine diagnoses: it looks at leads, conversion, pricing, stock, complaints and competitors through the Context Graph and metrics. A plan follows: initiatives with expected impact ranges, cost, risk and owners — human or agent.

A human approves the plan, the budget and the autonomy levels. Execution then runs as Projects and tasks, agents run Actions and automations are created. Leading indicators are watched daily and KPI checkpoints weekly. If the goal is off track, the system proposes a re-plan with evidence, which goes back to the human. At the deadline, the outcome is compared with the expectation and recorded in the Decision Journal for calibration. Learnings become organisational memory and a playbook for the next goal.

In Year 1 this runs as squad goals (goal → squad → KPIs → weekly check-in). The full Goals & Autopilot and Decision Engine are W3–W4.

Every step on this page is an Action: a typed verb with a risk tier (R0 read-only to R4 irreversible or financial), a permission check and a reversibility class. Agents and humans call the same Actions, so the same approval rules apply whether a person clicks a button or a Digital Employee acts.

Goal to outcome, step by step

Eleven steps. The loop is honest: it says "I don't know" and "run an experiment first" when that is the truth.

1
1. Human sets a goal
**Strategy & Governance · Goals & Autopilot.** Plain language, for example "Increase Chennai sales 20% this quarter".
2
2. Goal parser
**Goals & Autopilot.** KPI = revenue, region = Chennai, baseline from the semantic layer, deadline.
3
3. Diagnosis
**Intelligence · Decision Engine · Context Graph.** Leads, conversion, pricing, stock, complaints and competitors, with stated confidence.
4
4. Plan
**Strategic Planner.** Initiatives with expected impact ranges, cost, risk and owners (people or agents).
5
5. Human approves plan, budget and autonomy
**Human gate.** The owner approves the plan, the budget and the autonomy level for each agent skill.
6
6. Execution
**Work · Projects · Build · Automations · AI Workforce.** Tasks are created, agents run Actions and automations start.
7
7. Monitoring
**Intelligence · Dashboards · Signal Hub.** Leading indicators daily, KPI checkpoints weekly.
8
8. On track?
**Outcome Tracker.** Compares progress with the expectation recorded before acting.
9
9. Re-plan with evidence
**Decision Engine.** If off track, proposes a re-plan with evidence. It goes back to the human gate.
10
10. Deadline review
**Decision Journal.** Outcome vs expectation is recorded, feeding calibration scores.
11
11. Learnings and playbook
**Intelligence · Knowledge · organisational memory.** Validated learnings become the playbook for the next goal.

Why this flow is the product

Every other app exists so this loop can see, think, act and learn. The Enterprise Brain is a layer of reasoning services over the kernel, not a separate product with its own data.