> For the complete documentation index, see [llms.txt](https://title5.caqualityearlylearning.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://title5.caqualityearlylearning.org/general-requirements/materials-developed-with-contract-funds.md).

# Materials Developed with Contract Funds

18016

(a) If the contractor receives income from materials developed with contract funds, the use of the income shall be restricted to the child development program.&#x20;

(b) If the materials were developed in part with contract funds, the income from the sale of the materials that shall be used in the child development program shall be computed in direct proportion to the share of contract funds used in development of the materials.&#x20;

(c) Materials developed with contract funds shall contain:&#x20;

&#x20;             (1) An acknowledgement of the use of State funds in the development of materials;&#x20;

&#x20;             (2) A disclaimer that the contents do not necessarily reflect the position or policy of the California Department of Education.

> NOTE: Authority cited: Section 8261, Education Code. Reference: Section 8261, Education 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://title5.caqualityearlylearning.org/general-requirements/materials-developed-with-contract-funds.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.
