Typed tasks
Define each task’s purpose, inputs, output, tools, and place in the plan.
Inevitable / Task execution
Do the work.
Keep it connected.
Task execution turns a question into a plan with inputs, outputs, and dependencies. Research and analysis become deliverables your team can inspect rather than a conversation that disappears when the next prompt arrives.
- Dependency-led
- Connected task plans
- Deliverable edits
- The point of control
- Version history
- Compare revised work
In practice / Illustrative
The counterfactual is an edit to the work.
Change the financial analysis itself. Then follow that revision into the market model and decision memo that depend on it.
V1 / Retained
Pricing assumptions used in the original financial analysis.
V2 / Edited deliverable
Revise the commercial assumptions.
Update the pricing structure and delivery-cost analysis in the task output.
Revised financial analysisMarket modelDecision memo
A revision you can follow through the plan.
The task graph records which outputs depend on the edited analysis. Compare resulting deliverables without erasing the earlier version.
01 / Capabilities
The deliverable is the point of control.
Revise the analysis, assumptions, or proposed alternative directly in the task output. Follow the change into its dependent deliverables.
Connected execution
Run tasks in dependency order, with independent work able to proceed alongside other branches.
Editable outputs
Review and change a task deliverable, retain versions, and regenerate dependent work.
02 / The workflow
Change the analysis.
Revisit the call.
If financial diligence changes the pricing assumptions, the market model and executive recommendation may need to be rerun. The dependency graph makes that relationship explicit.
- Review
- Inspect the completed task’s output and its supporting context.
- Edit
- Revise the deliverable to reflect a new fact, assumption, interpretation, or proposed alternative.
- Regenerate
- Rerun dependent tasks against the revised work and compare the resulting deliverables.
03 / In the stack
Execution has boundaries.
The task plan defines the tools and actions in scope. Research, synthesis, data transformation, and drafting can share the execution layer, while external actions and approval requirements are set by the application workflow. Keep human review where the decision requires it.