> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_15/session_01_scheduler_config_contract.md).

# Session 01: Scheduler Config Contract And Status Read Path

**Session ID**: `phase15-session01-scheduler-config-contract` **Status**: Complete **Estimated Tasks**: \~12 **Estimated Duration**: 3-4 hours

***

## Objective

Add a deterministic repo-local scheduler settings file and make scheduler status report effective configured settings without moving reviewed job metadata out of the static registry.

***

## Scope

### In Scope (MVP)

* Sanitized scheduler config example under `data/`
* Private config ignore coverage and `data/` documentation
* TypeScript scheduler config parser/validator
* Status projection for valid, missing, and invalid config states
* Tests for missing config, valid config, invalid JSON, unsafe fields, unknown jobs, invalid cadence, and invalid Dream time
* Runbook and environment documentation updates

### Out of Scope

* Scoped scheduler job handlers
* Live-data merge writer or shared generated-data lock
* Timer unit rendering or installation
* Changes to public `bun run aggregate` behavior

***

## Prerequisites

* [ ] Phase 14 is complete.
* [ ] Current scheduler registry and status code are available.
* [ ] `docs/ongoing-projects/scheduler-config-and-aggregate-split-plan.md` remains the planning source.

***

## Deliverables

1. Scheduler config template and private-file boundary.
2. Config parser, validation, and sanitized status states.
3. Focused tests and docs proving registry defaults remain authoritative.

***

## Success Criteria

* [ ] `bun run scheduler:status` reports registry defaults when no local config exists.
* [ ] Valid local config can report configured cadence without exposing private paths.
* [ ] Invalid config does not crash status or print raw file contents.
* [ ] Registry remains the source of approved jobs and cadence candidates.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/phases/phase_15/session_01_scheduler_config_contract.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.