# Project Orientation

> **Seeded by `doctrine install`. Edit this to fit your project, then run
> `doctrine memory verify mem.signpost.project.orientation` to attest it.**
>
> This is the first thing an agent retrieves when onboarding. Write for an
> agent audience: concrete, operational, no marketing. One page; point to
> deeper docs rather than restating them.

## Project Purpose

<!-- What does this project build or provide? Who uses it and for what?
     (2–4 sentences. An agent needs to know the domain to make good decisions.) -->

## Guiding Principles

<!-- Design philosophy, operating heuristics, constraints that aren't obvious
     from code. What would you tell a new teammate? Bullet list preferred. -->

## Architecture

<!-- Key architectural decisions. Layering, module boundaries, data flow, key
     abstractions. Where would a newcomer trip? What's the "shape" of the
     codebase? (One paragraph + a short list of major components.) -->

## Structure

<!-- Map of important directories — where does an agent go first? Not
     exhaustive; link to deeper docs for details.

     Example shape:
     - `src/` — main source
     - `tests/` — integration tests
     - `docs/` — project documentation
     - `.doctrine/` — governance (specs, ADRs, etc.) -->

## Conventions

<!-- Coding standards, naming, commit style, branch strategy, patterns to
     follow. One-liners. If there's a linter/formatter, name it. -->

## Tooling & Development Workflow

<!-- How to build, test, lint, format, run. Concrete commands.
     Dev environment setup. Any sandbox/container concerns. -->

## Further Reading

<!-- Links to specs, ADRs, README, key docs — ordered by importance.
     Point to .doctrine/spec/ for product/tech specs and .doctrine/adr/ for
     decisions if they exist. -->
