diff --git a/artifacts/MAX-669/linear_attached_visual_proof.png b/artifacts/MAX-669/linear_attached_visual_proof.png new file mode 100644 index 0000000..2e0633e Binary files /dev/null and b/artifacts/MAX-669/linear_attached_visual_proof.png differ diff --git a/artifacts/MAX-669/preview.html b/artifacts/MAX-669/preview.html new file mode 100644 index 0000000..e9131f0 --- /dev/null +++ b/artifacts/MAX-669/preview.html @@ -0,0 +1,46 @@ + + + + + MAX-669 X Thread Preview + + + +
+
+

MAX-669 — X Thread

+
Thread cut from the MAX-565 waterfall for the /orchestrator course launch. Focus: why single-agent AI workflows break and how reliable multi-agent execution becomes the next leverage point.
+
Source: artifacts/MAX-565/build.md · Channel: x_thread · Brand: maxtechera
+
+ +
+
M
Max Techera
@maxtechera
Single-agent AI workflows feel fast until context loss, duplicated work, and drift kill the result. That’s the wall most Claude Code users hit right after the first good demo. 🧵
Tweet 1 · Hook
+
M
Max Techera
@maxtechera
Most people already know how to prompt one agent. The real bottleneck starts when the job needs parallel executors, clear ticket contracts, and handoffs that survive more than one session.
Tweet 2 · Problem
+
M
Max Techera
@maxtechera
That’s where /orchestrator fits. It closes the gap between “cool demo” and “reliable workflow” by turning agent work into a system with contracts, ownership, verification, and state.
Tweet 3 · Shift
+
M
Max Techera
@maxtechera
The course packages that operating model into 6 modules: why single-agent breaks, ticket contracts, spawning teams, memory + handoff, reliability patterns, and production orchestration.
Tweet 4 · Mechanism
+
M
Max Techera
@maxtechera
This is not abstract theory. You get a free lesson on the context-limit wall, a coordinator ↔ executor preview, and cloneable templates you can drop into your own workflow right away.
Tweet 5 · Proof
+
M
Max Techera
@maxtechera
The outcome is simple: run reliable, parallel multi-agent workflows in 1 week without losing context, duplicating work, or watching agents drift while you babysit the process.
Tweet 6 · Outcome
+
M
Max Techera
@maxtechera
If you want the full framework, start with the course outline and free lesson here: https://github.com/maxtechera/orchestrator#learn-orchestrator + +Join the /orchestrator waitlist before everyone else is still babysitting one prompt at a time.
Tweet 7 · CTA
+
+
+ + diff --git a/artifacts/MAX-669/thread.json b/artifacts/MAX-669/thread.json new file mode 100644 index 0000000..4be0a76 --- /dev/null +++ b/artifacts/MAX-669/thread.json @@ -0,0 +1,36 @@ +{ + "tweets": [ + { + "text": "Single-agent AI workflows feel fast until context loss, duplicated work, and drift kill the result. That’s the wall most Claude Code users hit right after the first good demo. 🧵", + "media": null + }, + { + "text": "Most people already know how to prompt one agent. The real bottleneck starts when the job needs parallel executors, clear ticket contracts, and handoffs that survive more than one session.", + "media": null + }, + { + "text": "That’s where /orchestrator fits. It closes the gap between “cool demo” and “reliable workflow” by turning agent work into a system with contracts, ownership, verification, and state.", + "media": null + }, + { + "text": "The course packages that operating model into 6 modules: why single-agent breaks, ticket contracts, spawning teams, memory + handoff, reliability patterns, and production orchestration.", + "media": null + }, + { + "text": "This is not abstract theory. You get a free lesson on the context-limit wall, a coordinator ↔ executor preview, and cloneable templates you can drop into your own workflow right away.", + "media": null + }, + { + "text": "The outcome is simple: run reliable, parallel multi-agent workflows in 1 week without losing context, duplicating work, or watching agents drift while you babysit the process.", + "media": null + }, + { + "text": "If you want the full framework, start with the course outline and free lesson here: https://github.com/maxtechera/orchestrator#learn-orchestrator\n\nJoin the /orchestrator waitlist before everyone else is still babysitting one prompt at a time.", + "media": null + } + ], + "cta": { + "action": "Start with the /orchestrator course outline and join the waitlist.", + "reason_for_now": "Single-agent wins are getting crowded. The leverage now is reliable multi-agent execution." + } +}