Files
tom_analysis_agent/.gitignore
Jonathan Boniface 4c1f1662de docs: include each run's Deliverables in the published evaluation
The general `deliverables/` ignore matched the folder inside each run's
Execution too, so the Deliverables as markdown (operating scope,
requirements, capability model, operating model, validation, guide) were
left out. They are now included for the published run only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 09:39:02 +01:00

35 lines
779 B
Plaintext

# Environment variables
.env
*.env
# Local SQLite databases
*.db
# Python bytecode and tool caches (pytest, mypy and ruff write to .cache/)
__pycache__/
*.pyc
*.pyo
.cache/
# Virtual environments
.venv/
venv/
# Everything generated for a Customer case: operating specs and operating models
# name people, teams and suppliers
deliverables/
# Evaluation run outputs, but for the runs published (they hold fictional benchmark
# data only, and links without their signatures)
eval/results/*
!eval/results/20261021T203624Z/
!eval/results/20261021T203623Z-handoff/
!eval/results/20261021T203624Z/deliverables/
!eval/results/20261021T203624Z/deliverables/**/deliverables/
# Lesson candidates captured from Executions (may quote user feedback)
lessons/candidates/
*.log
.DS_Store