Skip to content

Instantly share code, notes, and snippets.

@LiuShiyuMath
Created May 13, 2026 11:06
Show Gist options
  • Select an option

  • Save LiuShiyuMath/ff7ff1f27bfe02257407faf9ac9cb51d to your computer and use it in GitHub Desktop.

Select an option

Save LiuShiyuMath/ff7ff1f27bfe02257407faf9ac9cb51d to your computer and use it in GitHub Desktop.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Symphony setup — what does "REMOVE MY EXISTING WORKFLOW" mean?</title>
<style>
body { font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; max-width: 900px; margin: 2em auto; padding: 0 1.5em; line-height: 1.55; color: #222; }
h1 { font-size: 1.5em; border-bottom: 2px solid #333; padding-bottom: .3em; }
h2 { font-size: 1.15em; margin-top: 1.8em; }
.opt { border: 1px solid #ccc; border-radius: 6px; padding: .8em 1em; margin: .6em 0; background: #fafafa; }
.opt.danger { border-color: #b00; background: #fff3f3; }
.opt.safe { border-color: #1a7f37; background: #f0f9f3; }
code, pre { font-family: ui-monospace, Menlo, Consolas, monospace; }
code { background: #eee; padding: 1px 5px; border-radius: 3px; font-size: 0.92em; }
pre { background: #2a2a2a; color: #f3f3f3; padding: .9em 1em; border-radius: 6px; overflow-x: auto; font-size: 0.85em; }
.tag { display: inline-block; font-size: 0.75em; padding: 2px 8px; border-radius: 10px; margin-right: 6px; font-weight: 600; }
.tag-safe { background: #1a7f37; color: white; }
.tag-danger { background: #b00; color: white; }
.tag-mid { background: #c97a00; color: white; }
.conflict { background: #fff8e1; border-left: 4px solid #c97a00; padding: .8em 1em; margin: 1em 0; }
.ascii { font-family: ui-monospace, Menlo, monospace; font-size: 0.85em; white-space: pre; background: #f5f5f5; padding: 1em; border-radius: 6px; overflow-x: auto; }
</style>
</head>
<body>
<h1>Symphony setup — clarify scope before I delete anything</h1>
<p>You asked me to <b>set up <a href="https://github.com/openai/symphony/blob/main/elixir/README.md">openai/symphony Elixir</a></b> AND <b>"REMOVE MY EXISTING WORKFLOW"</b>. The second half is ambiguous in this repo and the most aggressive interpretations would delete things that the project's own canonical rules (in <code>CLAUDE.md</code>) say must stay.</p>
<div class="conflict">
<b>⚠ Direct conflict with canonical TeamBrain rules.</b><br>
<code>docs/TWO-DRIVER-COEXISTENCE.md</code> + <code>docs/SYMPHONY-FLOW.md</code> + <code>docs/FIXEDFLOW.md</code> already say Symphony and <code>/fixed-flow-driver</code> are <b>two drivers that coexist</b>, routed by the <code>track:symphony</code> issue label. The CLAUDE.md anchor sentences for <code>3-METHODS-WORKFLOW</code> and <code>TWO-DRIVER-COEXISTENCE</code> would also become invalid if fixed-flow is removed.
</div>
<div class="ascii">Current designed coexistence:
issue opened
|
+----+----+
| track: |
| symphony|
| label? |
+----+----+
yes | | no
v v
Symphony /fixed-flow-driver
(auto) (manual gate)
\ /
\ /
PR
</div>
<h2>What "existing workflow" could mean — pick one:</h2>
<div class="opt safe">
<span class="tag tag-safe">A · SAFE</span>
<b>The old <code>/tmp/teamagent/symphony-flow/</code> scratch setup only.</b><br>
That directory is already gone — nothing to delete. I just install Symphony fresh per the OpenAI README. <b>Fixed-flow docs and <code>.github/workflows/</code> stay intact.</b> Recommended interpretation given the existing coexistence design.
</div>
<div class="opt" style="border-color:#c97a00; background:#fff8e8;">
<span class="tag tag-mid">B · MEDIUM</span>
<b>The Symphony track in TeamBrain (this repo).</b><br>
Remove <code>docs/SYMPHONY-FLOW.md</code>, <code>docs/TWO-DRIVER-COEXISTENCE.md</code>, <code>docs/3-METHODS-WORKFLOW.md</code>, the related <code>CLAUDE.md</code> anchors, and any wired-up labels — because you're moving Symphony OUT of TeamBrain and into the standalone openai/symphony orchestrator. Fixed-flow + CI workflows stay.
</div>
<div class="opt danger">
<span class="tag tag-danger">C · DANGEROUS</span>
<b>Replace fixed-flow with Symphony — delete <code>docs/FIXEDFLOW.md</code> + all 20+ FIXEDFLOW-related anchor cards in <code>CLAUDE.md</code>.</b><br>
This invalidates dozens of canned-answer rules (PRE-IMPLEMENT-CLAIM, HOW-TO-CLAIM-ISSUE, POSTPR, ISSUE-LIFECYCLE, FAST-PATH-PR, etc.) and the entire two-driver coexistence design. Irreversible without git restore. <b>I will not do this without explicit confirmation.</b>
</div>
<div class="opt danger">
<span class="tag tag-danger">D · CATASTROPHIC</span>
<b>Delete <code>.github/workflows/*.yml</code>.</b><br>
There are 10 files: <code>ci.yml</code>, <code>release-branch.yml</code>, <code>install-verify.yml</code>, <code>landing-deploy.yml</code>, etc. This would brick CI, release pipeline, install checks, and the canned-answer probe. <b>I will not do this.</b>
</div>
<h2>Independent question: install <code>mise</code>?</h2>
<p>The Symphony README requires <code>mise</code> (Elixir/Erlang version manager) globally. Not currently installed on this machine. Options:</p>
<ul>
<li><b>Yes</b> — <code>brew install mise</code>, then follow the README.</li>
<li><b>No</b> — I'll stop after laying out the WORKFLOW.md scaffolding and you install mise yourself.</li>
</ul>
<h2>Where should openai/symphony live?</h2>
<ul>
<li><b>Sibling clone</b> at <code>/Users/m1/projects/symphony/</code> (recommended — keeps Elixir orchestrator out of TeamBrain repo).</li>
<li><b>Inside</b> TeamBrain at <code>./symphony/</code> as untracked dir or git submodule.</li>
</ul>
<h2>Reply format</h2>
<p>Reply in chat with: <b>scope=A|B|C|D</b>, <b>mise=yes|no</b>, <b>clone=sibling|inside</b>. Example: <code>scope=A, mise=yes, clone=sibling</code>.</p>
<p style="color:#666; font-size:0.85em; margin-top: 2em;">Generated by Claude in this background job. Nothing has been deleted or installed yet.</p>
</body>
</html>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment