Skip to content

[VENTURE_NAME] — Context Loading Order

Template placeholder describing the reading-order pattern for this venture. Fill in the concrete step list once the venture's documents exist; keep the pattern below as the shape to follow.

Purpose

This document tells an AI agent (or a new human contributor) the order in which to read venture documentation so that later documents are understood correctly in light of earlier ones, and so time isn't spent reading documents irrelevant to the task at hand.

  1. Root AGENTS.md (company-level, always first).
  2. ventures/[venture-slug]/AGENTS.md (this venture's operating contract).
  3. ventures/[venture-slug]/docs/ai/context.md (condensed context).
  4. ventures/[venture-slug]/docs/strategy/venture-brief.md.
  5. [Placeholder — remaining strategy docs, in the order most useful for a general task: product-principles.md, target-users.md, brand-and-positioning.md, roadmap.md.]
  6. [Placeholder — when the task concerns a specific product, insert: products/[product-slug]/product-brief.md and related product docs here.]
  7. docs/ai/guardrails.md (read before taking any consequential action).

Task-scoped shortcuts

[Placeholder — note any shortcuts for narrow tasks, e.g. "if the task is purely a copy edit to a single doc, steps 1-3 plus the target document are usually sufficient." Fill in once real usage patterns exist.]

Report an issue about this page