marfrit/bullpen
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs/ORCHESTRATION.md: add §8 Campaign sandbox convention #5

New Issue
Closed
opened 2026-07-25 15:59:55 +00:00 by marfrit · 0 comments
marfrit commented 2026-07-25 15:59:55 +00:00
Owner
Copy Link
Copy Source

Done

Added §8 Campaign sandbox — the /tmp/sandbox convention to docs/ORCHESTRATION.md.

The /bullpen/sandbox namespace in mneme (referenced in §7 since 2026-07-25) existed as a label but had no referenceable content in the repo. The actual operational depth was only in docs/deus_ex.md. This closes the gap.

What was added

§8.1 Build-dir convention — /tmp/bullpen-build/<slug> + /tmp/sandbox alias, why alias (removes slug-handoff failures), why /tmp not / (different root filesystems per host, safety risk on bare-metal boltzmann), auto-scaffold vs fix-existing-code, baseline commit requirement.

§8.2 Host boundary — .runtime file determines execution host, agent placement table, failure signatures when the agent is on the wrong machine, pre-flight check commands.

§8.3 Ticket rules — required ticket fields in order: PROBLEM, REPO (always /tmp/sandbox), TRAPS (highest-value), STEP 1 (@testdesigner), STEP 2 (grinder by type), Constraints, Dispatch-then-END. SPEC path requirement for grinder tickets.

§8.4 Route by test file type — routing table (py/godev/jsdev), coordinator wiring note.

§8.5 Result extraction — where the green artifact lives (grinder's working clone /tmp/grind-<ts>/<target>/), not the build dir, how to review diff.

Also updated §7's /bullpen/sandbox entry to point to §8 and docs/deus_ex.md.

Files changed

  • docs/ORCHESTRATION.md — +117 lines (347 total)

Cross-refs

  • Operational workflow: docs/deus_ex.md
  • Existing §7 mneme namespace table (sandbox entry now points here)
## Done Added §8 Campaign sandbox — the `/tmp/sandbox` convention to `docs/ORCHESTRATION.md`. The `/bullpen/sandbox` namespace in mneme (referenced in §7 since 2026-07-25) existed as a label but had no referenceable content in the repo. The actual operational depth was only in `docs/deus_ex.md`. This closes the gap. ### What was added **§8.1 Build-dir convention** — `/tmp/bullpen-build/<slug>` + `/tmp/sandbox` alias, why alias (removes slug-handoff failures), why /tmp not / (different root filesystems per host, safety risk on bare-metal boltzmann), auto-scaffold vs fix-existing-code, baseline commit requirement. **§8.2 Host boundary** — `.runtime` file determines execution host, agent placement table, failure signatures when the agent is on the wrong machine, pre-flight check commands. **§8.3 Ticket rules** — required ticket fields in order: PROBLEM, REPO (always /tmp/sandbox), TRAPS (highest-value), STEP 1 (@testdesigner), STEP 2 (grinder by type), Constraints, Dispatch-then-END. SPEC path requirement for grinder tickets. **§8.4 Route by test file type** — routing table (py/godev/jsdev), coordinator wiring note. **§8.5 Result extraction** — where the green artifact lives (grinder's working clone `/tmp/grind-<ts>/<target>/`), not the build dir, how to review diff. Also updated §7's `/bullpen/sandbox` entry to point to §8 and `docs/deus_ex.md`. ### Files changed - `docs/ORCHESTRATION.md` — +117 lines (347 total) ### Cross-refs - Operational workflow: `docs/deus_ex.md` - Existing §7 mneme namespace table (sandbox entry now points here)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
marfrit (Markus Fritsche)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marfrit/bullpen#5
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?