> 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/program-quality/program-philosophy-goals-and-objectives-program-quality.md). # Program Philosophy, Goals and Objectives - Program Quality 18271 (a) Each contractor shall have a written philosophical statement and goals and objectives which support that philosophy. The governing body of each contractor shall approve the program philosophy, goals and objectives. (b) The goals and objectives shall address the requirements contained in all of the sections in this article. (c) The goals and objectives shall reflect the cultural and linguistic characteristics of the families served by the contractor. > NOTE: Authority cited: Section 8261, Education Code. Reference: Sections 8203 and 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/program-quality/program-philosophy-goals-and-objectives-program-quality.md?ask=&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.