> For the complete documentation index, see [llms.txt](https://sandgarden.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sandgarden.gitbook.io/docs/overview/concepts.md).

# Concepts

Doc Holiday uses a shared vocabulary for where documentation belongs, where source information comes from, and how work moves from request to result. Read this page first.

### Organization

An Organization is the top-level account for a workspace. It owns the Publications, the Sources, and the Library, along with the settings they all share.

### Publication

A Publication is the maintained set of documentation Doc Holiday keeps current for one area of the product, one topic, or one release surface. It names a body of content rather than a single page, so one Publication can cover several related pages, outputs, or audiences. A Publication points at Sources instead of owning them, so it defines what the docs set covers while the Sources define where the information comes from and where the finished work belongs.

### Sources

Sources are the connected systems that feed Doc Holiday and receive its output. One Source can provide context for a Publication, another can accept documentation updates, and another can do both. [Sources](/docs/sources/sources.md) tell Doc Holiday what it can verify, what it can write, and how the finished work should appear.

### The Library and instructions

The [Library](/docs/the-library/the-library.md) is the organization-wide collection of editable guidance; it keeps that shared direction visible for every Publication in the Organization. Each instruction is one entry in the Library, and it can apply to every Publication or only to selected Publications. The Library gives each Publication the same source of guidance while still letting it use the instructions it needs for its own subject matter and audience.

### Work History

[Work History](/docs/working-with-doc-holiday/work-history.md) is the record of one documentation request from the first signal to the final result. Each entry belongs to one Publication and at least one Source. A single entry opens when something triggers it, moves through working and review states such as **Running**, **Ready for Review**, and **Needs Attention**, and ends as **Merged**, **Closed**, or **Cancelled**; the entry keeps that path visible when the request needs another round of comments or another look.