eld-sense-scope

Scope inheritance in task delegation uses explicit to_child and from_child definitions to control what context flows down and what returns up. Define to_child to pass only necessary context, and from_child to specify structured return artifacts, preventing scope leakage and over-inheritance between parent and child processes.

Task decomposition requires designing minimal context transfer with clear boundaries. Establish what information the parent task passes to subtasks (to_child), what structured results come back (from_child), and track deltas to ensure each subtask inherits exactly what it needs without excess or missing context.

When initiating parallel tasks, define explicit scope boundaries for each subtask using to_child and from_child sections. This isolates each subtask's context, prevents cross-contamination between parallel processes, and ensures delta reporting captures only the learnings relevant to each branch.

Child tasks return structured artifacts and delta reports that capture new learnings and changes. The from_child definition specifies what format and content the parent receives, enabling the parent to incorporate only relevant results and maintain clear scope boundaries in the parent-child relationship.

Yes. Scope inheritance rules apply at each level of nesting. Each parent-child pair defines its own to_child and from_child boundaries, allowing you to design precise context flow through deep task hierarchies while maintaining isolation and preventing scope overflow across multiple delegation levels.

Minimal context transfer reduces cognitive overhead for subtasks and prevents irrelevant information from polluting scope. By passing only necessary context to child processes and returning structured artifacts, you keep each task focused, reduce errors from context confusion, and enable efficient parallel execution.