Configure the repository
Add a root `.gplake` file to define source paths, exclusions, the `.contextlake/` directory, and the repository review policy.
GPDoc service
Context Lakes combine one or more authorized GitHub repositories into a private source-grounded knowledge collection. Git-tracked files remain authoritative, every result returns citations, and maintenance stays in the existing review path.
How it works
Add a root `.gplake` file to define source paths, exclusions, the `.contextlake/` directory, and the repository review policy.
A repository owner or organization administrator installs the GitHub App and chooses which repositories the service can access.
GPDoc indexes eligible text at a specific Git revision. The index is rebuildable and does not replace the repository source.
Keyword and semantic retrieval return paths, revisions, excerpts, and source locations. Context Lake maintenance uses a pull request by default.
Why teams use it
Results point back to the repository path and revision instead of presenting an uncited answer as the source of truth.
Generated `.contextlake/` pages are separate from source files. Default updates are visible in a dedicated branch and pull request.
The service checks authorization and applicable entitlement before it reads, indexes, or searches a private repository.
Service boundary
The managed service is entitlement-aware. It protects private repositories and checks access before it performs indexing or retrieval.
Add `.gplake`, choose the repositories, and use GPDoc to keep each Context Lake connected to source.