# V1 Block 07 — Child Tasks

Status: Planned

Purpose: Support breaking a large task into smaller owned child tasks without adding dependency complexity.

## Chunk 7.1 — Parent/child model rules

Recommended Codex level: medium

Tasks:

Implement parent/child ownership fields and helpers:

- parent task id on child tasks
- list/query children by parent
- parent can be incomplete while children are planned/completed

Rules:

- This is not full task dependency support.
- Do not add arbitrary DAG/dependency logic.
- Children are owned by parent only.

Acceptance criteria:

- Test: child references parent.
- Test: parent can query/aggregate children through helper.

## Chunk 7.2 — Child entry defaults

Recommended Codex level: medium

Tasks:

Support row-style child entry data:

- child title
- priority up/down/dropdown value
- reward up/down/dropdown value
- time required

Rules:

- If no priority is set, children are inserted in the order added.
- Children can have their own reward, priority, and time.
- Children inherit project from parent unless overridden.

Acceptance criteria:

- Tests cover child creation with explicit fields.
- Tests cover no priority preserving insertion order.

## Chunk 7.3 — Parent auto-completion

Recommended Codex level: high

Tasks:

Implement completion rules:

- Parent auto-completes when all children complete.
- Marking parent complete force-completes remaining children.
- Completing from any child can provide a domain-level option/result to mark entire parent complete.

Acceptance criteria:

- Test: all children completed completes parent.
- Test: parent complete force-completes children.
- Test: partial child completion does not complete parent.

BREAKPOINT: Stop here. Confirm `high` mode before implementing auto-completion propagation.

Commit suggestion:

```text
feat(tasks): support parent-owned child tasks
```