Case Study
trail.venturanomadica.com
The Trail Framework website. Built end-to-end using Trail.
← Back to trail.venturanomadica.com
trail/runs/intent-002/run-2026-03-15-18-15-13/dev-prompt.md
dev-prompt.md
What's this? →# Run: run-2026-03-15-18-15-13
# Purpose: Finish the nav fix, case study update, deploy workflow, and git push
Read these files first and only these files:
- `trail/runs/intent-002/run-2026-03-15-18-15-13/operating-instructions.md`
- `trail/runs/intent-002/run-2026-03-15-18-15-13/tasks.md`
- `header.php`
- `case-studies.php`
- `style.css`
- `README.md`
- `footer.php`
- `index.php`
- `about.php`
- `contact.php`
- `legal.php`
- `license.php`
- `privacy.php`
- `terms.php`
- `docs/index.php`
- `assets/`
- `.git/`
If created during execution, you may also read:
- `.github/workflows/deploy.yml`
Execute the run exactly as defined by `tasks.md` and constrained by `operating-instructions.md`.
Required outputs:
- Updated `header.php`
- Updated `case-studies.php`
- `.github/workflows/deploy.yml`
- A git commit pushed to `origin main` if push access works
- `trail/runs/intent-002/run-2026-03-15-18-15-13/results.md` updated with status, assumptions, blockers, observations, surprises, deviations, and verification notes
Ambiguity handling:
- Choose the simplest interpretation consistent with the run artifacts.
- Document the decision in `results.md`.
- If blocked, stop and report the blocker in `results.md`.
Do not read or rely on any intent-level or meta-level policy or scope files.