diff --git a/artifacts/MAX-547/README.md b/artifacts/MAX-547/README.md new file mode 100644 index 0000000..f3f2f12 --- /dev/null +++ b/artifacts/MAX-547/README.md @@ -0,0 +1,11 @@ +# MAX-547 proof pack + +This folder contains the rebuilt content package for the /memory reel series under the correct target repo contract for `maxtechera/orchestrator`. + +Contents: +- `package.json` — machine-readable placement schema for Content Engine +- `variants.md` — five reel variants with three hooks each +- `preview.html` — rendered review surface for screenshots +- `rendered-markdown.html` — rendered markdown review surface +- `*.png` — thumbnails and proof screenshots +- `*.mp4` — five proof-of-concept reel exports diff --git a/artifacts/MAX-547/package.json b/artifacts/MAX-547/package.json new file mode 100644 index 0000000..cb8f26d --- /dev/null +++ b/artifacts/MAX-547/package.json @@ -0,0 +1,245 @@ +{ + "ticket_id": "MAX-547", + "content_type": "reel", + "target_repo": "maxtechera/orchestrator", + "brand": "max-techera", + "locale": "en", + "variants": [ + { + "id": "v1-problem-agitate-solve", + "name": "Problem \u2192 Agitate \u2192 Solve", + "angle": "Make the pain visceral, then show /memory as the fix.", + "hooks": [ + "Your AI agent forgot everything again.", + "You are not bad at prompting. Your agent is stateless.", + "If you re-explain your project every session, this is the bug." + ], + "script": "Problem clip: blank session. Agitate with the repeat-yourself loop. Solve by revealing /memory and the surviving context: project, last decision, current focus." + }, + { + "id": "v2-contrarian", + "name": "Contrarian", + "angle": "The real problem is not the model, it is no memory architecture.", + "hooks": [ + "Your agent is not dumb, it is just stateless.", + "Bigger models do not fix zero memory.", + "The real AI productivity leak is context reset, not model quality." + ], + "script": "Open with the contrarian line. Show a capable model still starting blank. Then show /memory preserving continuity after a fresh session." + }, + { + "id": "v3-specific-number", + "name": "Specific-number", + "angle": "Quantify the loss: three things you repeat every session.", + "hooks": [ + "3 things you keep re-explaining to your AI agent.", + "Three repeated context blocks are stealing your flow.", + "Every session reset costs you the same 3 explanations." + ], + "script": "Frame the pain as three repeated context blocks: project, last decision, current focus. Then show /memory carrying all three into the next session." + }, + { + "id": "v4-insider-reveal", + "name": "Insider reveal", + "angle": "Reveal the architecture under the hood: HOT/WARM/COLD plus WAL.", + "hooks": [ + "The trick is not chat history, it is memory architecture.", + "What actually makes an AI agent feel continuous? A 3-tier memory stack.", + "The secret is HOT, WARM, COLD plus a write-ahead log." + ], + "script": "Lead with the architectural reveal. Show HOT working state, WARM durable decisions, and COLD compiled wiki, with WAL surviving compaction." + }, + { + "id": "v5-testimonial", + "name": "Testimonial", + "angle": "First-person workflow upgrade for indie hackers tired of daily resets.", + "hooks": [ + "I got tired of re-explaining my project every morning.", + "The moment my agent stopped forgetting, my workflow changed.", + "This one install saved me from the daily context reset ritual." + ], + "script": "Tell it as a first-person before/after. Before: daily re-explaining ritual. After: new session already knows the project and active focus." + } + ], + "placements": { + "instagram_reel": { + "text": "Your AI agent forgot everything again.\n\nThat is not a prompting issue. It is a memory issue.\n\nEvery new session makes you re-explain the project, the last decision, and the one thing that matters now. `/memory` keeps that context alive across session compactions so the work keeps moving.\n\nDM MEMORY and I will send the free install guide.", + "cta": { + "action": "DM \"MEMORY\"", + "reason_for_now": "because re-explaining context every session is killing momentum" + }, + "hashtags": [ + "#memory", + "#aiagents", + "#claudecode", + "#buildinpublic", + "#indiehacker", + "#opensource", + "#aiworkflow", + "#llm" + ], + "media": { + "mp4": "artifacts/MAX-547/v1-problem-agitate-solve.mp4", + "thumbnail": "artifacts/MAX-547/v1-problem-agitate-solve.png" + }, + "hook_variants": [ + "Your AI agent forgot everything again.", + "You are not bad at prompting. Your agent is stateless.", + "If you re-explain your project every session, this is the bug." + ], + "manychat_trigger": { + "keyword": "MEMORY", + "flow_id": "TBD_MAX_PROVIDES" + } + }, + "tiktok": { + "caption": "Hot take: bigger models do not fix zero memory. `/memory` does. Comment install and I will send the repo link.", + "hook_variants": [ + "Your agent is not dumb, it is just stateless.", + "Bigger models do not fix zero memory.", + "The real AI productivity leak is context reset, not model quality." + ], + "media": { + "mp4": "artifacts/MAX-547/v2-contrarian.mp4" + } + }, + "youtube_short": { + "title": "3 Things You Re-Explain Every AI Session", + "description": "Most session resets cost you the same three explanations. This short shows how /memory keeps them across compaction.", + "media": { + "mp4": "artifacts/MAX-547/v3-specific-number.mp4" + } + }, + "x_thread": { + "tweets": [ + { + "text": "Your AI agent forgot everything again. That is not a prompting problem. It is a stateless workflow problem." + }, + { + "text": "Most resets force you to re-explain 3 things: the project, the last decision, and the current focus." + }, + { + "text": "/memory keeps that context through HOT working state, WARM durable notes, and a COLD compiled wiki." + }, + { + "text": "If you want the free install guide, reply MEMORY or grab the repo: github.com/maxtechera/memory" + } + ], + "cta": { + "action": "Reply \"MEMORY\"", + "reason_for_now": "to get the free install guide before your next reset" + } + }, + "linkedin_post": { + "text": "Your AI agent is probably not underperforming because of the model. It is underperforming because every new session starts blank.\n\nThe practical fix is a memory layer that survives session compaction and preserves three things: project context, the last decision, and the current focus.\n\nThat is the promise of `/memory`: HOT working state, WARM durable context, and a COLD knowledge layer that compounds over time.\n\nIf you are building with Claude Code or any agentic workflow, this is the difference between daily reset and continuous execution.", + "cta": { + "action": "DM \"MEMORY\"", + "reason_for_now": "to get the install guide and stop losing context every session" + } + }, + "email": { + "subject_variants": [ + "Your agent forgot everything again", + "Stop resetting your AI agent daily", + "Install /memory before your next session" + ], + "preview_text": "A quick fix for stateless AI workflows that lose context every session.", + "body_html": "

Your AI agent forgot everything again

Every new session should not feel like day one.

The root problem is not prompting, it is memory. /memory preserves project context, the last decision, and the current focus across session compactions.

If you want the free install guide, reply with MEMORY or grab the repo at github.com/maxtechera/memory.

", + "utm": { + "source": "mailerlite", + "campaign": "max-547-memory-reel-series", + "medium": "email" + } + }, + "blog_post": { + "slug": "/blog/your-ai-agent-forgot-everything-again", + "title": "Your AI Agent Forgot Everything Again, Here Is the Fix", + "meta_description": "Why stateless AI sessions keep breaking your flow, and how a 3-tier memory system fixes it.", + "hero_og": "artifacts/MAX-547/v4-insider-reveal.png", + "body_md": "# Your AI agent forgot everything again\n\nEvery new session starts with a tax: repeat the project, repeat the last decision, repeat the current focus. `/memory` fixes that with HOT, WARM, and COLD memory tiers that survive session compactions.\n\n## The bug\nStateless sessions feel smart for one conversation and useless in the next.\n\n## The fix\nInstall `/memory`, connect your working context, and let the agent reload what matters.\n\n## The architecture\nHOT = live working state. WARM = durable decisions and facts. COLD = compiled knowledge that compounds over time.", + "faq": [ + { + "q": "What problem does /memory solve?", + "a": "It stops you from re-explaining durable context every new session." + }, + { + "q": "Who is this for?", + "a": "AI/LLM developers, Claude Code users, and indie hackers tired of session resets." + } + ] + }, + "landing_page": { + "slug": "/memory", + "hero": { + "headline": "Your AI agent forgot everything again", + "subhead": "/memory keeps project context, last decisions, and current focus alive across sessions.", + "hero_image": "artifacts/MAX-547/v5-testimonial.png" + }, + "features": [ + { + "name": "HOT working state", + "hero_image": "artifacts/MAX-547/v4-insider-reveal.png", + "diagram": "artifacts/MAX-547/v4-insider-reveal.png", + "demo_media": "artifacts/MAX-547/v4-insider-reveal.mp4" + }, + { + "name": "WARM durable decisions", + "hero_image": "artifacts/MAX-547/v3-specific-number.png", + "diagram": "artifacts/MAX-547/v3-specific-number.png", + "demo_media": "artifacts/MAX-547/v3-specific-number.mp4" + }, + { + "name": "COLD compounding wiki", + "hero_image": "artifacts/MAX-547/v2-contrarian.png", + "diagram": "artifacts/MAX-547/v2-contrarian.png", + "demo_media": "artifacts/MAX-547/v2-contrarian.mp4" + } + ], + "ctas": { + "primary": "DM MEMORY", + "secondary": "Comment install" + }, + "tracking_events": [ + "page_view", + "cta_click_primary", + "cta_click_secondary", + "video_play" + ], + "meta": { + "title": "/memory for AI agents", + "description": "Persistent context for agentic workflows.", + "og": "artifacts/MAX-547/v1-problem-agitate-solve.png", + "canonical": "https://github.com/maxtechera/memory" + } + } + }, + "proof": { + "pr_url": "https://github.com/maxtechera/orchestrator/pull/13", + "preview_urls": [ + "artifacts/MAX-547/preview.html", + "artifacts/MAX-547/rendered-markdown.html" + ], + "screenshots": { + "desktop": "artifacts/MAX-547/screenshot-desktop.png", + "mobile": "artifacts/MAX-547/screenshot-mobile.png", + "rendered_html": "artifacts/MAX-547/rendered-html-screenshot.png", + "rendered_html_preview": "artifacts/MAX-547/rendered-html-preview-screenshot.png", + "rendered_github_markdown": "artifacts/MAX-547/rendered-github-markdown-screenshot.png" + }, + "mp4_attachments": [ + "artifacts/MAX-547/v1-problem-agitate-solve.mp4", + "artifacts/MAX-547/v2-contrarian.mp4", + "artifacts/MAX-547/v3-specific-number.mp4", + "artifacts/MAX-547/v4-insider-reveal.mp4", + "artifacts/MAX-547/v5-testimonial.mp4" + ], + "thumbnail_pngs": [ + "artifacts/MAX-547/v1-problem-agitate-solve.png", + "artifacts/MAX-547/v2-contrarian.png", + "artifacts/MAX-547/v3-specific-number.png", + "artifacts/MAX-547/v4-insider-reveal.png", + "artifacts/MAX-547/v5-testimonial.png" + ], + "deployed_url": "https://github.com/maxtechera/orchestrator/pull/13" + } +} diff --git a/artifacts/MAX-547/preview.html b/artifacts/MAX-547/preview.html new file mode 100644 index 0000000..03771b7 --- /dev/null +++ b/artifacts/MAX-547/preview.html @@ -0,0 +1 @@ +MAX-547 Preview

MAX-547, /memory Reel Series

Five proof-first reel variants packaged for Instagram Reels, TikTok, YouTube Shorts, X, LinkedIn, email, blog, and landing-page reuse. CTA stack: DM MEMORY, comment install, or hit the repo/course link.

Variant 1

Problem → Agitate → Solve

Make the pain visceral, then show /memory as the fix.

Script spine: Problem clip: blank session. Agitate with the repeat-yourself loop. Solve by revealing /memory and the surviving context: project, last decision, current focus.

Variant 2

Contrarian

The real problem is not the model, it is no memory architecture.

Script spine: Open with the contrarian line. Show a capable model still starting blank. Then show /memory preserving continuity after a fresh session.

Variant 3

Specific-number

Quantify the loss: three things you repeat every session.

Script spine: Frame the pain as three repeated context blocks: project, last decision, current focus. Then show /memory carrying all three into the next session.

Variant 4

Insider reveal

Reveal the architecture under the hood: HOT/WARM/COLD plus WAL.

Script spine: Lead with the architectural reveal. Show HOT working state, WARM durable decisions, and COLD compiled wiki, with WAL surviving compaction.

Variant 5

Testimonial

First-person workflow upgrade for indie hackers tired of daily resets.

Script spine: Tell it as a first-person before/after. Before: daily re-explaining ritual. After: new session already knows the project and active focus.

\ No newline at end of file diff --git a/artifacts/MAX-547/rendered-github-markdown-screenshot.png b/artifacts/MAX-547/rendered-github-markdown-screenshot.png new file mode 100644 index 0000000..0e17c96 Binary files /dev/null and b/artifacts/MAX-547/rendered-github-markdown-screenshot.png differ diff --git a/artifacts/MAX-547/rendered-html-preview-screenshot.png b/artifacts/MAX-547/rendered-html-preview-screenshot.png new file mode 100644 index 0000000..5dcdb70 Binary files /dev/null and b/artifacts/MAX-547/rendered-html-preview-screenshot.png differ diff --git a/artifacts/MAX-547/rendered-html-screenshot.png b/artifacts/MAX-547/rendered-html-screenshot.png new file mode 100644 index 0000000..4e69592 Binary files /dev/null and b/artifacts/MAX-547/rendered-html-screenshot.png differ diff --git a/artifacts/MAX-547/rendered-markdown.html b/artifacts/MAX-547/rendered-markdown.html new file mode 100644 index 0000000..23443fd --- /dev/null +++ b/artifacts/MAX-547/rendered-markdown.html @@ -0,0 +1 @@ +MAX-547 Rendered Markdown

MAX-547 Memory Reel Series

Rendered markdown proof surface for review.

Core angle

Your AI agent forgot everything again. /memory fixes that.

Proof-first structure

  1. Show the blank session.
  2. Show the repeat-yourself tax.
  3. Show /memory preserving project, decision, and focus.
  4. Show the HOT/WARM/COLD architecture.

Package coverage

Instagram Reel, TikTok, YouTube Short, X thread, LinkedIn post, email, blog post, and landing page are all represented in package.json.

\ No newline at end of file diff --git a/artifacts/MAX-547/screenshot-desktop.png b/artifacts/MAX-547/screenshot-desktop.png new file mode 100644 index 0000000..47a4bb3 Binary files /dev/null and b/artifacts/MAX-547/screenshot-desktop.png differ diff --git a/artifacts/MAX-547/screenshot-mobile.png b/artifacts/MAX-547/screenshot-mobile.png new file mode 100644 index 0000000..2b75c25 Binary files /dev/null and b/artifacts/MAX-547/screenshot-mobile.png differ diff --git a/artifacts/MAX-547/v1-problem-agitate-solve.mp4 b/artifacts/MAX-547/v1-problem-agitate-solve.mp4 new file mode 100644 index 0000000..0b15f88 Binary files /dev/null and b/artifacts/MAX-547/v1-problem-agitate-solve.mp4 differ diff --git a/artifacts/MAX-547/v1-problem-agitate-solve.png b/artifacts/MAX-547/v1-problem-agitate-solve.png new file mode 100644 index 0000000..8767da8 Binary files /dev/null and b/artifacts/MAX-547/v1-problem-agitate-solve.png differ diff --git a/artifacts/MAX-547/v1-problem-agitate-solve.txt b/artifacts/MAX-547/v1-problem-agitate-solve.txt new file mode 100644 index 0000000..7636281 --- /dev/null +++ b/artifacts/MAX-547/v1-problem-agitate-solve.txt @@ -0,0 +1,6 @@ +Problem clip: blank session. +Agitate with the repeat- +yourself loop. Solve by +revealing /memory and the +surviving context: project, +last decision, current focus. \ No newline at end of file diff --git a/artifacts/MAX-547/v2-contrarian.mp4 b/artifacts/MAX-547/v2-contrarian.mp4 new file mode 100644 index 0000000..59effb8 Binary files /dev/null and b/artifacts/MAX-547/v2-contrarian.mp4 differ diff --git a/artifacts/MAX-547/v2-contrarian.png b/artifacts/MAX-547/v2-contrarian.png new file mode 100644 index 0000000..63c2826 Binary files /dev/null and b/artifacts/MAX-547/v2-contrarian.png differ diff --git a/artifacts/MAX-547/v2-contrarian.txt b/artifacts/MAX-547/v2-contrarian.txt new file mode 100644 index 0000000..ec065a7 --- /dev/null +++ b/artifacts/MAX-547/v2-contrarian.txt @@ -0,0 +1,5 @@ +Open with the contrarian line. +Show a capable model still +starting blank. Then show +/memory preserving continuity +after a fresh session. \ No newline at end of file diff --git a/artifacts/MAX-547/v3-specific-number.mp4 b/artifacts/MAX-547/v3-specific-number.mp4 new file mode 100644 index 0000000..138b384 Binary files /dev/null and b/artifacts/MAX-547/v3-specific-number.mp4 differ diff --git a/artifacts/MAX-547/v3-specific-number.png b/artifacts/MAX-547/v3-specific-number.png new file mode 100644 index 0000000..a0d7ad7 Binary files /dev/null and b/artifacts/MAX-547/v3-specific-number.png differ diff --git a/artifacts/MAX-547/v3-specific-number.txt b/artifacts/MAX-547/v3-specific-number.txt new file mode 100644 index 0000000..e7b1624 --- /dev/null +++ b/artifacts/MAX-547/v3-specific-number.txt @@ -0,0 +1,6 @@ +Frame the pain as three +repeated context blocks: +project, last decision, +current focus. Then show +/memory carrying all three +into the next session. \ No newline at end of file diff --git a/artifacts/MAX-547/v4-insider-reveal.mp4 b/artifacts/MAX-547/v4-insider-reveal.mp4 new file mode 100644 index 0000000..bcd7beb Binary files /dev/null and b/artifacts/MAX-547/v4-insider-reveal.mp4 differ diff --git a/artifacts/MAX-547/v4-insider-reveal.png b/artifacts/MAX-547/v4-insider-reveal.png new file mode 100644 index 0000000..466b487 Binary files /dev/null and b/artifacts/MAX-547/v4-insider-reveal.png differ diff --git a/artifacts/MAX-547/v4-insider-reveal.txt b/artifacts/MAX-547/v4-insider-reveal.txt new file mode 100644 index 0000000..6ceab13 --- /dev/null +++ b/artifacts/MAX-547/v4-insider-reveal.txt @@ -0,0 +1,5 @@ +Lead with the architectural +reveal. Show HOT working +state, WARM durable decisions, +and COLD compiled wiki, with +WAL surviving compaction. \ No newline at end of file diff --git a/artifacts/MAX-547/v5-testimonial.mp4 b/artifacts/MAX-547/v5-testimonial.mp4 new file mode 100644 index 0000000..aefbb8d Binary files /dev/null and b/artifacts/MAX-547/v5-testimonial.mp4 differ diff --git a/artifacts/MAX-547/v5-testimonial.png b/artifacts/MAX-547/v5-testimonial.png new file mode 100644 index 0000000..f8be99b Binary files /dev/null and b/artifacts/MAX-547/v5-testimonial.png differ diff --git a/artifacts/MAX-547/v5-testimonial.txt b/artifacts/MAX-547/v5-testimonial.txt new file mode 100644 index 0000000..3f8bf10 --- /dev/null +++ b/artifacts/MAX-547/v5-testimonial.txt @@ -0,0 +1,5 @@ +Tell it as a first-person +before/after. Before: daily +re-explaining ritual. After: +new session already knows the +project and active focus. \ No newline at end of file diff --git a/artifacts/MAX-547/variants.md b/artifacts/MAX-547/variants.md new file mode 100644 index 0000000..dcfd4b2 --- /dev/null +++ b/artifacts/MAX-547/variants.md @@ -0,0 +1,44 @@ +# MAX-547 Memory Reel Series Output Package + +Target repo: `maxtechera/orchestrator` + +## Variants +### Problem → Agitate → Solve (`v1-problem-agitate-solve`) +- Angle: Make the pain visceral, then show /memory as the fix. +- Hooks: + - Your AI agent forgot everything again. + - You are not bad at prompting. Your agent is stateless. + - If you re-explain your project every session, this is the bug. +- Script spine: Problem clip: blank session. Agitate with the repeat-yourself loop. Solve by revealing /memory and the surviving context: project, last decision, current focus. + +### Contrarian (`v2-contrarian`) +- Angle: The real problem is not the model, it is no memory architecture. +- Hooks: + - Your agent is not dumb, it is just stateless. + - Bigger models do not fix zero memory. + - The real AI productivity leak is context reset, not model quality. +- Script spine: Open with the contrarian line. Show a capable model still starting blank. Then show /memory preserving continuity after a fresh session. + +### Specific-number (`v3-specific-number`) +- Angle: Quantify the loss: three things you repeat every session. +- Hooks: + - 3 things you keep re-explaining to your AI agent. + - Three repeated context blocks are stealing your flow. + - Every session reset costs you the same 3 explanations. +- Script spine: Frame the pain as three repeated context blocks: project, last decision, current focus. Then show /memory carrying all three into the next session. + +### Insider reveal (`v4-insider-reveal`) +- Angle: Reveal the architecture under the hood: HOT/WARM/COLD plus WAL. +- Hooks: + - The trick is not chat history, it is memory architecture. + - What actually makes an AI agent feel continuous? A 3-tier memory stack. + - The secret is HOT, WARM, COLD plus a write-ahead log. +- Script spine: Lead with the architectural reveal. Show HOT working state, WARM durable decisions, and COLD compiled wiki, with WAL surviving compaction. + +### Testimonial (`v5-testimonial`) +- Angle: First-person workflow upgrade for indie hackers tired of daily resets. +- Hooks: + - I got tired of re-explaining my project every morning. + - The moment my agent stopped forgetting, my workflow changed. + - This one install saved me from the daily context reset ritual. +- Script spine: Tell it as a first-person before/after. Before: daily re-explaining ritual. After: new session already knows the project and active focus. diff --git a/docs/course-outline.md b/docs/course-outline.md index 0999b0f..96562d1 100644 --- a/docs/course-outline.md +++ b/docs/course-outline.md @@ -102,10 +102,12 @@ Students launch a coordinator with three executors, each with a narrow scope, th - **Lesson 4.2:** The 3-tier memory model for agent teams - **Lesson 4.3:** Session state, handoff docs, and durable operating context - **Lesson 4.4:** SESSION-STATE, pre-compact discipline, and recovery after interruption -- **Lesson 4.5:** Designing memory flows for multi-session work +- **Lesson 4.5:** What to store, what to summarize, and what to throw away +- **Lesson 4.6:** Designing memory flows for multi-session work ### Apply -- **Lesson 4.6:** Build a persistent memory flow across a 2-session task +- **Lesson 4.7:** Build a persistent memory flow across a 2-session task +- **Lesson 4.8:** Repair a broken handoff without restarting the whole workflow ### Demo / exercise Students run one task across two sessions using memory notes, session state, and a formal handoff document. @@ -122,9 +124,12 @@ Students run one task across two sessions using memory notes, session state, and - **Lesson 5.2:** Critic evaluators and rubric-driven review - **Lesson 5.3:** Retry policies, bounded loops, and fail-fast triggers - **Lesson 5.4:** Human-in-the-loop gates for risky or taste-sensitive tasks +- **Lesson 5.5:** Guardrails that prevent wrong-surface and wrong-proof failures +- **Lesson 5.6:** Taste review for content, design, and public-facing assets ### Apply -- **Lesson 5.5:** Add a critic and retry loop to your orchestrator +- **Lesson 5.7:** Add a critic and retry loop to your orchestrator +- **Lesson 5.8:** Add one human approval gate without slowing the whole system down ### Demo / exercise Students wire a critic pass into a real orchestration flow and tune retry logic so the system improves instead of looping forever. @@ -155,10 +160,10 @@ Students turn one manual weekly workflow into an orchestrated recurring system w - **Module 1:** 5 lessons - **Module 2:** 7 lessons - **Module 3:** 6 lessons -- **Module 4:** 6 lessons -- **Module 5:** 5 lessons +- **Module 4:** 8 lessons +- **Module 5:** 8 lessons - **Module 6:** 6 lessons -- **Total:** 35 lesson units in outline format, which is in range for a recorded delivery trimmed to about 30 final lessons by combining adjacent teach segments during production +- **Total:** 40 lesson units in outline format, which supports a trimmed recorded delivery of ~30 final lessons by combining adjacent teach segments during production ## Teaching assets to produce - 6 module workbooks