> For the complete documentation index, see [llms.txt](https://t22.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://t22.caqualityearlylearning.org/continuing-requirements-1/toddler-component-in-an-infant-care-center.md).

# Toddler Component in an Infant Care Center

101417

(a) Licensees serving infants may create a special program component for children who are between 18 months and 36 months of age. The provisions of Sections 101151 through 101239.2 and 101351 through 101439.1 shall apply to infant care centers operating a toddler component in addition to those specified in Health and Safety Code section 1596.956.&#x20;

&#x20;  (1) The infant care center shall obtain written permission from the child's authorized representative for the placement of the child in the toddler program.

> NOTE: Authority cited: Sections 1596.81 and 1596.956, Health and Safety Code. Reference: Section 1596.956, Health and Safety Code.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://t22.caqualityearlylearning.org/continuing-requirements-1/toddler-component-in-an-infant-care-center.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
