Program

What you'll build

A multi-week structured arc assigned per kid. Units that can nest. A reading ladder. A 3rd-grade science curriculum. A summer art project broken into weeks. The kid sees a coherent path; the parent sees the whole arc.

Programs are Soon end-to-end. MCP tools exist; the kid-facing surface and the home-agent authoring path land in stages.

Pieces you'll combine

• Program: recursive unit tree.
• Templates and assignments: same template, different kid; slot substitution fills the per-kid bits.
• Existing skills as leaf actions inside units.

Build it (planned shape)

Two calls:

program.create({
name: "<Program name>",
type: "template",
units: [
{
name: "Unit 1",
children: [
{ name: "Topic A", taskRef: { skillId: "<skillId>" }},
{ name: "Topic B" },
{ name: "Topic C" }
]
},
{ name: "Unit 2", children: [...] }
],
inputVariables: [
{ name: "kid_name" },
{ name: "reading_level" },
{ name: "weekly_cadence" }
]
})
# Returns { programId: "<templateId>" }
program.assign({
templateId: "<templateId>",
childId: "<kidId>",
slots: { kid_name: "<name>", reading_level: "8-9", weekly_cadence: "Mon/Wed/Fri" }
})
# Tasks for the first unit get authored automatically.

When to use it

• The work has structure beyond "do this, then that". Curriculum, habit ladder, multi-week project.
• You want to share the template with other families (cross-family library, also Soon).
• Anti-pattern: a single skill or a one-off loop. Programs are heavier than they need to be for those.

Tools touched

• program.create, program.update, program.delete.
• program.assign: copy template to kid with slot substitution.

Recommended skills

No skills in the catalog pair with this pattern yet. Browse the catalog.

Seen in walkthroughs

Music Lab Solar system learning loop (final step)

Related patterns

• Autonomous loop: programs often replace ad-hoc loops once the arc is clear.