resolve-context

Resolving branch context requires consulting the index.md file first within the active gc-branch. This method reads concise summaries before expanding full documents, ensuring you load only the most relevant source-of-truth context for your planning or coding session.

The best way to load branch-scoped repository knowledge is staying strictly inside the active gc-branch. By treating linked documents as explicit source-of-truth context and preferring summary reading first, you isolate the current branch's facts and prevent unrelated repository context from mixing in.

Yes, resolving context requires consulting the index.md file first. This file acts as the primary entry point for summary reading, allowing the resolution process to selectively expand linked documents and treat them as explicit source-of-truth context for the active gc-branch.

Summary-first reading improves context resolution by looking up the index.md before fetching full documents. This technique keeps context loading efficient for source code analysis by retrieving only the concise summaries needed, selectively expanding linked documents only when deeper source-of-truth context is required.

You should avoid expanding full documents when the concise summaries from the index.md already provide sufficient repository context. Expanding linked documents should be a selective action reserved for when you need explicit source-of-truth details that the branch-scoped summaries lack.