Dependency Mapper
Ki · Single Ability
The Problem
What happens without this ability. Tasks A through E can run in any order since they're all in the same sprint, the sequential assumption holds and no hidden dependency exists, so assigning by team availability avoids any bottleneck.
The Operation
The model is directed to extract all tasks and enumerate dependency relationships between them as directed edges. Construct the dependency graph and scan for cycles indicating impossible dependency chains. Compute the critical path: the longest sequential chain that constrains total duration. Do not assume tasks are sequential by default. If cycles are detected, isolate the circular chain and flag for resolution. The reasoning applies a formal computation: critical path = longest path(dependency DAG); duration = sum(task duration on critical path). Assume tasks sequential default is rejected.
The Structure
The reasoning structure is a cascade propagation where effects ripple through each stage of the analysis.
If tasks are listed without their prerequisite relationships being explicitly mapped, dependency mapping was not performed.
Haki · Multi Ability
Synergy Topology
In Haki mode, the API retrieves the primary ability first, then fans out to three synergy roles that compound its reasoning.
When retrieved in Haki mode, these four abilities don't run in sequence. They merge into a single injection where the dependency grounds the reasoning context, the amplifier sharpens the primary's output, and the alternative provides a fallback path if the primary's topology cannot converge. The result is a multi-angle reasoning scaffold that covers failure modes no single ability can reach alone.
Appears in Use Cases