# Documentation source

> How docs.tentaflake.dev stays aligned with the public tentaflake repository.

Canonical page: https://docs.tentaflake.dev/reference/website-source/

The detailed guides on this site are synchronized from the public [`timfewi/tentaflake`](https://github.com/timfewi/tentaflake) repository. That repository stays authoritative; this site adds navigation, search, theming, stable URLs, and agent-readable formats.

## How the pin works

The site is built from one exact release tag and commit of that repository. Every synchronized page starts with a source line that names the upstream file and that commit, so you can always open the text the page was built from.

- The synchronized pages, the [`llms.txt`](https://docs.tentaflake.dev/llms.txt) index, and the list of bundled skills are all generated from the pinned commit.
- The site's build fails when a published page differs from its pinned source.
- A deployment is blocked unless the pinned commit is the one the release tag resolves to.
- A new guide must have a documentation route or an explicit exclusion before
  synchronization passes. Removed sources and duplicate routes also fail validation.

## Following new releases

tentaflake tags each merge to `main`. Release drift can be checked independently
of publishing. The maintainer moves the pin to a newer tag, regenerates the guides,
and reviews the summaries before publishing. Between a release and that update,
this site can be behind the repository; the source line on each page identifies
the exact commit you are reading. Unreleased checkout changes are outside that pin.

Pages written for this site, such as [Overview](https://docs.tentaflake.dev/getting-started/overview/), [Security boundaries](https://docs.tentaflake.dev/concepts/security-boundaries/), and [Use with AI agents](https://docs.tentaflake.dev/getting-started/ai-agents/), are reviewed by hand in the same update.

## If a page looks wrong

A synchronized page is only as current as its pin. Compare it with the linked source file on GitHub, and treat the repository as correct when the two disagree.