project.example.yaml

# project.yaml — Example (fictional acme-widgets, for illustration only)
# TRON's own per-project config record. Lives at <agents>/tron/project.yaml.
# The seeder builds it by detecting what it can and asking for the rest.
# Re-read every session start. Shape: contracts/schema/project.schema.yaml.
#
# TRON owns no pipeline, no work-unit format, and no agents. It READS the
# project's canon — the git-tracked pipeline + block files written by agents via
# PR — and adapts to whatever agents the project defines. The pointers below say
# where that canon lives; TRON never writes any of it.

pointers:
  agents: meta/agents/        # the project's worker personas (TRON reads these; it ships none)

# ── Canon pipeline (git-tracked; agents write via PR, TRON only reads) ──
# Paths are relative to repo.root. pipeline.md is the living doc (order);
# block files are dispatch truth (status, deps, gates).
pipeline_path: meta/pipeline.md
blocks_dir:    meta/blocks/
archive_dir:   meta/blocks/archive/

# agents: seeder-populated by scanning pointers.agents — the project's persona
# files, NOT a TRON-owned set. (Omitted in this example; role-coverage lint
# skips when absent.)

repo:
  name: acme-widgets
  root: ~/code/acme-widgets   # the trunk checkout TRON reads; agents build in worktrees off it
  main_branch: main
  staging: none               # staging | none — two-gate (staging+main) vs single-gate merge model
  remote: acme/widgets
  worktrees_dir: ../worktrees/   # <workspace>/worktrees/<repo>--<branch>/
  logs_dir: meta/logs/

conventions:
  branch_naming: "{type}/{slug}-YYMMDD"     # type in feat|fix|chore
  block_id_pattern: "block-MM-DD-{slug}"
  worker_id_pattern: "{ROLE}-{block-stripped}"   # e.g. ENG-06-19
  commit_convention: "present-tense, lowercase, scope prefix"
  pr_title_rule: "under 70 chars; body has Summary + Test plan"

notifications:
  telegram: off               # off | on  (on => heartbeat on; keys in .env)
  cron: auto                  # auto | on | off

protected_branches:
  - repo: acme-widgets
    branch: main

operator_only_tasks:
  - DNS / domain configuration
  - Third-party dashboard configuration (Stripe, Vercel, Auth0, …)
  - Production billing / paid plan changes
  - Anything requiring physical access

local_validation_gaps:
  - Mobile builds (device install)
  - Live integration tests with paid third-party services
  - End-to-end flows requiring a real account

ci: {}                        # runner / duration / stall-threshold override
deploy: {}                    # success check (the canon DoD deploy gate); inherited by blocks,
                              # overridable per block via the block's `Deploy:` field
notes: ""                     # free-form (monorepo boundaries, migration rules…)

# env keys are NOT here — they live in <agents>/tron/.env (gitignored):
#   TELEGRAM_BOT_TOKEN (optional), TELEGRAM_CHAT_ID (optional), GITHUB_TOKEN (optional)