Bounded Plan Sequencing
Break complex intents into owned steps, review gates, and proof-backed handoffs.
Large company intents should not move as one vague instruction. Niyatna breaks them into bounded steps so each piece has ownership, context, and proof.
When sequencing is needed
Use bounded sequencing when an intent has:
- multiple departments or assignees;
- dependent steps;
- separate review gates;
- sensitive data boundaries;
- recurring follow-up;
- different proof requirements per stage.
Plan structure
A Niyatna plan should define:
- Step owner: Human, agent, or mixed responsibility.
- Scope: What the step may touch.
- Input context: SOPs, files, prior decisions, or source material.
- Output: The artifact or decision expected from the step.
- Review gate: Who approves, rejects, or redirects.
- Proof: Evidence required before the next step begins.
- Memory update: What the system should remember.
Delegation rule
Subagents can help with independent lanes, but they should not create a hidden agent swarm. The parent intent remains the anchor, and each delegated step must report back into the same proof trail.