# Gitea Tracking Policy

Read exact issue, epic, and milestone records rather than broad tracker dumps. Current tracker scope
is desired behavior; source and accepted evidence determine implementation state.

Use these states precisely: Implementing, Engineering-complete, Acceptance-in-progress,
Candidate-ready, and Accepted/closed. Do not check an acceptance criterion without corresponding
code, automated, native, or candidate evidence. A dirty working tree cannot close an issue, and
closure requires the nominated commit plus configured release evidence.

Post at most one useful status update per completed slice or material scope delta. Keep epic
checklists, child issues, and milestone scope aligned, but do not create, close, reopen, delete, or
rewrite tracker scope without direct authority. Workflow installation and audits produce dry-run
recommendations only.

Tracker comments summarize outcomes and link durable repository evidence; they do not receive raw
build logs, entire issue listings, or speculative completion claims.
