Skip to content

Venture Scaffold Template

This directory is the reusable scaffold for creating a new venture inside the Devonshire Digital repository. It is not itself a venture — it is copied and adapted whenever a new venture is proposed.

How this template is used

  1. Copy the directory. Duplicate ventures/_template/ to ventures/[venture-slug]/, where [venture-slug] is the lowercase, hyphenated slug for the new venture (e.g. shelfery, digital-products). This is normally done by scripts/create_venture.py rather than by hand.
  2. Rename and replace placeholders. Every bracketed placeholder such as [VENTURE_NAME], [venture-slug], [Venture Display Name] must be replaced with real values throughout the copied tree, including inside venture.json, AGENTS.md, and the strategy docs.
  3. Fill in the strategy docs. At minimum, docs/strategy/venture-brief.md should be completed before any product work begins. The other strategy, ai, standards, architecture, and decisions docs can be filled in progressively as the venture matures.
  4. Do not register prematurely. The new venture should NOT be added to portfolio/venture-registry.json (company root) until it is genuinely ready to be tracked as an active venture. Registration is a deliberate, explicit step — not an automatic side effect of copying this template.
  5. Leave products/ mostly empty at first. Product specification work should not begin until the venture has a baseline strategy and the venture itself is worth pursuing. products/_template/ exists here so that, when the time comes, a first product can be scaffolded consistently.

What this template intentionally does not decide

This scaffold is structural only. It does not pre-judge brand strategy, target users, monetization, or roadmap for any future venture — those are filled in per-venture, in the copied strategy docs, by the people (or agents, under explicit human direction) doing the work.

Relationship to company-level documents

Every venture created from this template must still comply with the company-level root AGENTS.md and root docs/ policies. This template's own AGENTS.md placeholder explains that relationship; it should not be edited to weaken or bypass company-level rules.

Report an issue about this page