[JacobStephens2]

Summary

This is the design record for #877, ahead of its Spec. It changes no code.

 GLOSSARY.md                    # Factory work
+  Process, Built-in process, Custom process, Step
 docs/
 ├── adr/
+│   └── 0024-a-process-composes-steps-from-a-fixed-catalogue.md
 ├── grill-with-docs/
+│   └── 877-composable-by-file.md        # 4 rounds, all answered
 └── research/
+    └── file-defined-factories.md        # Warp, Archon, gh-aw, Anneal

What was decided:

~/.thirdshift/processes/<name>.toml       # Custom process, version = 1
  worktrees: throwaway | issue branch (needs a Claim, ends in Delivery)
  steps: session (skill + Harness/Model/Effort) | command | catalogue (Delivery, Self-merge, child run)
         run in sequence or in parallel, optional = true, each Step's result passed on to the next
thirdshift process [check] <name> [issue <issue>]

ADR-0024 records that a file arranges Steps from a fixed catalogue. The safety rules (Self-merge, Claim, Repair budgets, Security findings) stay inside the Steps, and a file can only tighten them.

Evidence

• Docs only, with no code change. scripts/affected-tests main ran the full suite: 1500 passed and 7 failed.
  • 4 passed when re-run on their own: ended_trial_sessions_drop_caches…, interruption_during_read_backoff…, parent_only_interruption_stops_active_github, auxiliary_keeps_its_pinned_trial…. They look flaky under load.
  • 3 fail every time on this machine: the *_ignore_shadowing_branch_and_tag_names tests in worktree::synchronization_tests, with git tag origin/main <sha> failed: fatal: no tag message? under git 2.55.0. This machine's global tag.gpgsign = true makes git tag demand a message. These tests run the same code as main (d4185d4).

Merge Danger

Door: two-way

Blast Radius: docs

Agents read GLOSSARY.md, so they'll see the four new terms. Each one describes a Process that isn't built yet.