> For the complete documentation index, see [llms.txt](https://gilad-rubin.gitbook.io/hypster/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gilad-rubin.gitbook.io/hypster/concepts/origin-story.md). # Origin Story Hypster grew from a recurring problem in AI and ML projects: configuration is often more dynamic than a settings file, but experiment logs still need stable, replayable parameters. In practice, a workflow might need to switch between model families, providers, retrieval modes, preprocessing steps, local and remote execution, or production and evaluation paths. Each branch has different parameters. Logging every possible value is noisy, but silently ignoring inactive values makes experiments hard to trust. Hypster's answer is a small define-by-run API: * write the config as plain Python * use `hp.*` calls for the values that matter * compose nested configs with `hp.nest` * inspect active branches with `explore` * run with `instantiate` * log and replay with `instantiate_with_params` The goal is not to hide Python behind a configuration language. The goal is to make the parts of Python configuration that matter for reproducibility explicit. --- # 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://gilad-rubin.gitbook.io/hypster/concepts/origin-story.md?ask=&goal= ``` `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.