trail.venturanomadica.com

# trail.md
<!-- This file lives at trail/meta/trail.md. It is the persistent identity of
     the product or project — what it is, who it's for, why it exists, and how
     it's shaped. Every intent inherits this context automatically.

     The Manager reads this file before producing run artifacts for every run.
     The Developer does NOT read this file directly — the Manager surfaces
     relevant product context into the run artifacts.

     Changes rarely. Only update when product identity, audience, or permanent
     constraints shift. -->

Owner: James
Last Updated: 2026-03-14

---

## Product Identity

trail.venturanomadica.com is the public website for the Trail Framework — an
artifact-driven methodology for executing work with humans, AI, or both, without
letting the conversation become the source of truth. The site exists to introduce
Trail to potential users, provide access to documentation, demonstrate Trail through
real case studies, and give people a way to download the scaffold and get started.

The site is itself built with Trail. That is not incidental — it is the primary proof
point. Every page, every build decision, and the existence of the site in the first
place is a demonstration of the framework it describes.

---

## Users / Audience

**Primary:** Developers, technical leads, and solo builders who use AI in their
workflow and are frustrated by context drift, lost decisions, and the inability to
reconstruct why things were built the way they were.

**Secondary:** Technology executives and IT/ops leaders who manage teams using AI
tools and need a coordination layer that doesn't collapse into chat threads.

**Anti-users:** People looking for a no-code tool, a prompt library, or a project
management app. Trail is intentionally unfriendly to non-planners. The site should
not try to soften that.

---

## Permanent Constraints

- No user tracking or third-party analytics. Privacy-first.
- No JavaScript frameworks. Plain HTML, CSS, and JS only. No build step required.
- No backend beyond PHP for document rendering. The site is otherwise static.
- The Docs section renders Markdown from the trail-framework repo — it is not
  authored or maintained inside this repo.
- Single maintainer. No solutions that require a team to operate.
- The trail-framework repo and trail-site repo are independent. They are not merged,
  submoduled, or otherwise coupled beyond the documented relative path for doc rendering.
- All pages must be functional without JavaScript where possible.
- Copyright: Ventura Nomadica. All rights reserved where not otherwise licensed.

---

## Technology & Architecture

- **Platform:** Web (desktop and mobile browser)
- **Stack:** PHP, HTML, CSS, vanilla JS
- **Hosting:** Infomaniak (deployment configuration is a future intent)
- **Local dev path:** `dev/trail/trail-site/`
- **Git repository:** `trail-site` (Ventura Nomadica org, does not yet exist as of
  intent-001)
- **Doc rendering:** PHP reads Markdown files from a sibling repository at the
  relative path `../trail-framework/docs/[page].md` and renders them as HTML
- **Trail-framework repo structure (read-only dependency):**
  ```
  trail-framework/
  ├── docs/       # Markdown files rendered by trail-site
  ├── trail/      # Trail folder structure and templates
  └── README.md
  ```
- **Assets:**
  - Style guide: `trail/meta/files/trail-style-guide.html`
  - Logos: `trail/meta/files/logos/` (two variants: full logo with text, logo mark only)
  - Page content: `trail/meta/files/pages/`

---

## Product Principles

1. The site demonstrates Trail by existing. Every build decision should be
   traceable to an intent. If it isn't, it shouldn't be built.
2. Content over chrome. The framework is the product. The site's job is to get
   out of the way and let Trail speak for itself.
3. No partial pages. Every page that ships must be complete. Placeholders are
   acceptable only where explicitly declared in the intent (e.g., Case Studies
   marked "Coming Soon").
4. Plain is durable. Avoid dependencies that will rot. No npm, no build tools,
   no third-party UI frameworks.
5. The footer is a proof point. "Created with Trail Framework" is not marketing
   copy — it is a verifiable claim. The Trail file structure in this repo is the
   evidence.

---

## Non-Goals (Product Level)

- This site will never be a SaaS product, dashboard, or authenticated experience.
- This site will never host user-generated content or community features.
- This site will never include advertising or third-party monetization.
- This site will never replace the trail-framework repo as the source of truth
  for Trail documentation — it renders from it, it does not own it.

---

## Prior Art / Context

Trail was created by James (Ventura Nomadica) out of frustration while building
TrekCrumbs, a privacy-first travel planning app, using AI as the developer. The
problem Trail solves — context drift, lost decisions, and accountability fragmentation
in AI-assisted work — was experienced firsthand during that build.

Trail was subsequently validated on several projects: Brushy (toothbrush timer app),
a YouTube Transcript Chrome extension, an Export ChatGPT Chat Chrome extension,
the Ventura Nomadica website (venturanomadica.com), and the Otaku Haven LLC fictional
business document proof of concept.

The Ventura Nomadica website (venturanomadica.com) is a related but separate product
under the same collective. It is not part of this Trail.

Trail Framework is licensed under CC BY 4.0 for documentation and methodology.
Scaffold files are MIT licensed. Copyright: Ventura Nomadica.