trail.venturanomadica.com

# operating-instructions-override.md
<!-- This file is part of the intent package. It is read by the Manager and
     composed into the run-level operating-instructions.md for the Developer.

     Usually empty. Only create overrides when this intent genuinely needs
     different policy than meta/global-operating-instructions.md.

     If unused, leave the Overrides section as: None -->

Owner: James
Last Updated: 2026-03-25

---

## Rules
<!-- Do not remove these — they apply to every intent regardless of overrides. -->

- This file is **policy only**. No task lists, no scope, no deliverables.
- It becomes immutable once execution begins.
- Overrides apply to this intent only — they do not change global policy.
- If a rule here conflicts with global operating instructions, this file wins.

---

## Overrides

### Case Study Telemetry

This intent is being executed as a Trail Framework case study to support the v1.0
public launch. Two additional artifacts are required to capture decision rationale
and richer execution detail beyond what Trail normally requires. This is intentional
scope added for documentation purposes only and does not affect how Trail operates.

**Manager: `decisions.md`**

The Manager must produce a `decisions.md` file in this intent folder. It captures
the *why* behind structural choices: how runs were scoped, why tasks were sequenced
a certain way, key assumptions and the reasoning behind them. Append under labeled
headers as decisions are made (`## Run 01 Decisions`, etc.).

**Developer: `results.md` (enhanced)**

The Developer must produce `results.md` per normal. For this intent, results.md
should include additional detail: notable observations, anything that was surprising
or non-obvious, and reasoning behind any deviation — not just the fact of the
deviation.