article feature
Recursive subagents: spawning, depth, and family scope
Calling await rlm(...) returns an admission handle immediately and starts a child session with its own kernel, context, and history. Answers arrive through agent messages or files, not as the return value. Children can run concurrently, default max depth is one, and messaging is restricted to parent, children, and siblings.
Pinned repository file/line or test referenced in the audit.
Admission handles
Calling await rlm(...) returns an admission handle immediately and starts a child session with its own kernel, context, and history. Answers arrive through agent messages or files, not as the return value. Children can run concurrently, default max depth is one, and messaging is restricted to parent, children, and siblings.
- S008 supports the route's current claim set.
- S009 supports the route's current claim set.
- S092 supports the route's current claim set.
Answer delivery
Calling await rlm(...) returns an admission handle immediately and starts a child session with its own kernel, context, and history. Answers arrive through agent messages or files, not as the return value. Children can run concurrently, default max depth is one, and messaging is restricted to parent, children, and siblings.
- S008 supports the route's current claim set.
- S009 supports the route's current claim set.
- S092 supports the route's current claim set.
Concurrency
Calling await rlm(...) returns an admission handle immediately and starts a child session with its own kernel, context, and history. Answers arrive through agent messages or files, not as the return value. Children can run concurrently, default max depth is one, and messaging is restricted to parent, children, and siblings.
- S008 supports the route's current claim set.
- S009 supports the route's current claim set.
- S092 supports the route's current claim set.
Recursion depth
Recursion depth is configurable but bounded. Use the child registry and message limits to keep costs predictable.
Nuclear-family messaging
Calling await rlm(...) returns an admission handle immediately and starts a child session with its own kernel, context, and history. Answers arrive through agent messages or files, not as the return value. Children can run concurrently, default max depth is one, and messaging is restricted to parent, children, and siblings.
- S008 supports the route's current claim set.
- S009 supports the route's current claim set.
- S092 supports the route's current claim set.
Retained children
Calling await rlm(...) returns an admission handle immediately and starts a child session with its own kernel, context, and history. Answers arrive through agent messages or files, not as the return value. Children can run concurrently, default max depth is one, and messaging is restricted to parent, children, and siblings.
- S008 supports the route's current claim set.
- S009 supports the route's current claim set.
- S092 supports the route's current claim set.