# __PROJECT_NAME__

## Identity

- **Name**: __PROJECT_NAME__
- **Owner**: Mathias
- **Client**: personal
- **Repo**: git.d-ma.be/mathias/__PROJECT_NAME__
- **Status**: active

## Stack

Go + ADK + LiteLLM. Claude Code tree-walks to `~/dev/CLAUDE.md` for cross-project conventions.

## Agent

TODO: describe what this agent does, what tools it has, and what it's responsible for.

## Harness & workflow

Single harness: **Claude Code + hyperguild** — session-based (you start a session, it works,
it stops; there is no push-triggered dispatch). MCP connections are in `.mcp.json`: **brain**
(knowledge query/write) and **gitea** (issues/PRs/repo — the audit trail). Provide
`BRAIN_MCP_TOKEN` and `GITEA_MCP_TOKEN` in the environment.

The loop for a unit of work:

1. **Issue** — the work is a Gitea issue (scope, acceptance criteria, report-back format).
2. **Session** — a Claude Code + hyperguild session does the work in this repo.
3. **PR** — branch off `main`, open a PR; CI (`task check`) is the gate.
4. **Report-back** — comment the outcome on the issue (issue comments are the audit surface).
5. **Brain capture** — if a learning is durable and non-obvious, write it to the brain.

## Observability

Traces → Jaeger via `OTLP_ENDPOINT`. Set `ADK_SERVICE_NAME=__PROJECT_NAME__` per deployment.
Spans emitted: `invoke_agent`, `generate_content`. Tool spans require custom callbacks.

## Boundaries

Runtime scope (network egress, file scope, approved operations) is in `AGENT_BOUNDARIES.md` —
read it before adding tools, endpoints, or write access.