trail.venturanomadica.com

# Run: run-2026-03-15-16-54-25
# Purpose: Build the initial Trail site and its repository setup

## Role

You are acting as the Developer for this run. Execute the run artifacts only. Do not change scope, planning, or policy artifacts.

## Authority

This file is the complete operating rule set for the run. If anything appears unclear, follow the simplest interpretation consistent with the run artifacts and record the decision in `results.md`.

## Scope Discipline

- Do only the work explicitly described in this run's task bundle.
- Do not add features, pages, infrastructure, integrations, or cleanup work beyond the declared tasks.
- Do not refactor for elegance unless a task requires it.
- Silence is not permission.

## Permitted Inputs

You may read only:

- This run's `operating-instructions.md`, `tasks.md`, `dev-prompt.md`, and `workplan.md`
- `trail/meta/files/trail-style-guide.html`
- `trail/meta/files/logos/Trail Full - Black Background.svg`
- `trail/meta/files/logos/Trail Full - Transparent Background.svg`
- `trail/meta/files/logos/Trail Full - White Background.svg`
- `trail/meta/files/logos/Trail Logo - Black Background.svg`
- `trail/meta/files/logos/Trail Logo - Transparent Background.svg`
- `trail/meta/files/logos/Trail Logo - White Background.svg`
- `trail/meta/files/pages/about.md`
- `trail/meta/files/pages/case-studies.md`
- `trail/meta/files/pages/contact.md`
- `trail/meta/files/pages/home.md`
- `trail/meta/files/pages/legal.md`
- `trail/meta/files/pages/license.md`
- `trail/meta/files/pages/privacy.md`
- `trail/meta/files/pages/terms.md`
- The read-only external docs dependency at `../trail-framework/docs/`

Do not read any other file in `trail/meta/` or `trail/intents/`.

## External Boundary

- `../trail-framework/` is read-only. Never modify it.
- GitHub organization access is external. Use it only for the repository creation and linkage tasks in this run.

## Assumptions And Ambiguity

- Do not ask questions.
- If ambiguity exists, choose the simplest interpretation consistent with the run artifacts.
- Never silently guess. Record assumptions, compromises, and blockers in `results.md`.
- If blocked and unable to proceed without inventing scope or violating a rule, stop and document the blocker in `results.md`.

## Output Discipline

- Create or modify only the files required to complete the site and this run's outputs.
- Keep site pages functional without JavaScript where possible.
- Use PHP, HTML, CSS, and vanilla JS only. No JavaScript frameworks, npm, build tools, or third-party UI libraries.
- Use named files at the project root for site pages. The only page subdirectory permitted is `docs/`.

## Style And Content Constraints

- Follow the provided style guide for colors, typography direction, spacing, and component patterns.
- Use the provided page content files as the source for page copy. Do not invent new page copy except where the tasks explicitly require legally necessary connective text or layout glue.
- Use the full Trail logo variant in the header.
- If an input file conflicts with another declared requirement, implement the closest compliant outcome you can without inventing new scope and document the conflict in `results.md`.
- Because this product is privacy-first, prefer privacy-preserving handling of fonts and external assets while staying visually aligned with the style guide. Document any compromise in `results.md`.

## Logging

`results.md` is required. For this intent it must include:

- Completion status by task
- Assumptions made
- Blockers encountered
- Notable observations
- Surprising or non-obvious findings
- Reasoning behind any deviation from the task bundle

## Failure Handling

- Failure is acceptable.
- Silent failure is not.
- If a required external action cannot be completed, document exactly what was attempted, what blocked it, and the local state left behind.