Add Discord instruction lessons research packet

research/2026-04-16-discord-instruction-lessons/00-scope-and-method.md

@@ -0,0 +1,46 @@
+# Scope and Method
+
+## What was reviewed
+
+I reviewed current and archived on-disk session transcripts under `~/.openclaw/agents/main/sessions/`, including:
+
+- active `.jsonl` session files
+- archived `.jsonl.reset.*` files
+- archived `.jsonl.deleted.*` files where relevant
+
+## Discord channels verified in scope
+
+Core channels with meaningful instruction/process lessons:
+
+- `#cass-inbox`
+- `#car-shopping`
+- `#agent-improvements`
+- `#general`
+- `#knowledge-graphs`
+- `#lesson-plans`
+- `#lesson-plans-2`
+- `#chris-stories`
+- `#remarq`
+
+Other Discord channels existed, but the strongest instruction-learning density lived in the set above.
+
+## What counted as an "instruction lesson"
+
+A lesson was included when one of these happened:
+
+- Chris or Serena explicitly corrected behavior
+- a new default was established
+- a file-backed rule was added or clarified in workspace instructions
+- a repeated failure mode showed that the current instruction layer was too weak
+- a runtime/config fix taught a better operating rule than the previous one
+
+## What did not count
+
+- routine task execution with no generalizable lesson
+- one-off domain facts
+- generic praise or reaction without process change
+
+## Summary judgment standard
+
+The goal was not "what happened in each chat".
+The goal was "what persistent operating rules led to better outcomes later".

research/2026-04-16-discord-instruction-lessons/README.md

@@ -0,0 +1,24 @@
+# Discord Instruction Lessons Review
+
+Date: 2026-04-16
+Scope: Discord session transcripts from 2026-02-27 through 2026-04-16
+Repo purpose: preserve what we learned, channel by channel, about improving Cass's instructions and operating rules for better outcomes.
+
+## Folder map
+
+- `00-scope-and-method.md` — what was reviewed and how
+- `channels/` — per-channel systematic summaries
+- `cross-cutting/01-core-lessons.md` — the main cross-channel synthesis
+- `cross-cutting/02-tweet-cards.md` — short bullets/cards for tweet digestion
+- `cross-cutting/03-long-form-article-opportunities.md` — article ideas and counts
+- `cross-cutting/04-beginner-practical-framing.md` — practical framing for readers with no agentic background
+- `digest.md` — single-file executive digest
+
+## Verified date range
+
+- Earliest Discord transcript found: 2026-02-27 (`#cass-inbox`)
+- Latest Discord transcript reviewed: 2026-04-16
+
+## Main conclusion
+
+The strongest instruction upgrades were not vague style tweaks. They were operational changes that tightened what "done" means, reduced agent wandering, improved runtime correctness, and made output immediately usable.

research/2026-04-16-discord-instruction-lessons/channels/01-cass-inbox.md

@@ -0,0 +1,42 @@
+# Channel Summary: #cass-inbox
+
+## Date coverage
+- 2026-02-27 to 2026-03-28 verified from archived Discord session transcripts
+
+## Why this channel mattered
+This was one of the earliest operational channels, so it exposed first-generation workflow rules around triage, inbox handling, and routing work into the right systems.
+
+## Main lessons learned
+
+### 1. Inbox channels need explicit triage rules
+What improved:
+- autonomous tasks should be handled directly
+- Chris-only tasks should go to his task system
+- reminders should become cron jobs
+- reference material should be logged, not left loose in chat
+
+Why it mattered:
+- this turned a random dumping ground into a structured intake surface
+- it reduced dropped tasks and reduced ambiguity about where things belong
+
+### 2. Forwarded email handling needed a real operating model
+What improved:
+- watch only the right sender path
+- process the inbox continuously
+- mark and route items intentionally instead of just acknowledging them
+
+Why it mattered:
+- made inbox processing trustworthy
+- established that operational email intake needs a deterministic workflow, not ad hoc checking
+
+### 3. Output quality improved when content was rewritten to match Chris's actual voice
+What improved:
+- content got less polished-and-preachy
+- style guides became useful constraints rather than decorative docs
+
+Why it mattered:
+- early drafts sounded generic until grounded in an explicit voice guide
+- this helped content become publishable instead of merely coherent
+
+## Durable rule from this channel
+- Every intake surface needs a routing contract, not just a response habit.

research/2026-04-16-discord-instruction-lessons/channels/02-car-shopping.md

@@ -0,0 +1,38 @@
+# Channel Summary: #car-shopping
+
+## Date coverage
+- 2026-03-06 to 2026-03-09 verified from archived Discord session transcripts
+
+## Why this channel mattered
+This channel surfaced research-quality lessons, especially around verification and uncertainty handling.
+
+## Main lessons learned
+
+### 1. Asking prices are not reality
+What improved:
+- shifted from reporting scraped listing prices to distinguishing asking price from actual market behavior
+- used contradictory evidence as a signal to investigate deeper, not something to hand-wave away
+
+Why it mattered:
+- improved decision usefulness
+- reduced false precision in purchase advice
+
+### 2. When a listing cannot be verified, say so plainly
+What improved:
+- direct admission when a specific listing URL or price could not be verified live
+- stopped treating stale search results as hard facts
+
+Why it mattered:
+- built trust
+- prevented brittle recommendations based on unverifiable inventory
+
+### 3. Good buying research needs synthesis, not just aggregation
+What improved:
+- combined dealer listings, market discussion, and financing structure into one decision frame
+
+Why it mattered:
+- the better outcome was not "more links"
+- it was a more decision-ready explanation of tradeoffs
+
+## Durable rule from this channel
+- For money decisions, explicitly separate verified facts, inferred market dynamics, and uncertainty.

research/2026-04-16-discord-instruction-lessons/channels/03-agent-improvements.md

@@ -0,0 +1,49 @@
+# Channel Summary: #agent-improvements
+
+## Date coverage
+- 2026-04-05 to 2026-04-12 verified from current Discord session transcripts
+
+## Why this channel mattered
+This was the clearest meta-operations channel. It contains direct lessons about instruction design, runtime mistakes, debugging quality, and progress update quality.
+
+## Main lessons learned
+
+### 1. Docs-only fixes are fake fixes
+Observed change:
+- an initial pass replaced Claude Code references in skills/docs, but runtime exposure was still wrong
+- later correction explicitly called out that the real fix required changing runtime/config behavior, not just text
+
+Why it mattered:
+- taught the difference between instruction cosmetics and actual behavioral control
+- prevented repeated regressions where the written rule changed but the live tool path did not
+
+### 2. Debug from actual logs, not vibes
+Observed change:
+- later debugging explicitly checked session/run history instead of guessing why a timeout happened
+- over-broad searches across all logs were identified as their own failure mode
+
+Why it mattered:
+- made debugging faster and more accurate
+- reduced narrative explanations built on the wrong evidence set
+
+### 3. Progress updates need to be sparse and meaningful
+Observed change:
+- the coding-agent guidance emphasized one start message, then updates only on milestone, blocker, error, or finish
+
+Why it mattered:
+- users stop trusting updates when they are constant but low-information
+- concise milestone-only reporting made status messages worth reading
+
+### 4. Tight working scope beats sprawling context
+Observed change:
+- coding-agent guidance increasingly favored focused workdirs, smaller context, and less wandering across unrelated workspace files
+
+Why it mattered:
+- reduced meandering and irrelevant file reads
+- improved completion speed and relevance
+
+## Durable rules from this channel
+- Fix runtime behavior, not just docs.
+- Debug from exact logs.
+- Keep progress updates milestone-based.
+- Constrain scope hard.

research/2026-04-16-discord-instruction-lessons/channels/04-general-channel-config.md

@@ -0,0 +1,37 @@
+# Channel Summary: #general and channel wiring lessons
+
+## Date coverage
+- 2026-04-06 to 2026-04-14 verified from current Discord session transcripts
+
+## Why this channel mattered
+This is where channel-level operating behavior became explicit instead of assumed.
+
+## Main lessons learned
+
+### 1. A new Discord channel is not real until it is wired
+What improved:
+- new channels were added to config and restarted properly
+- response behavior was no longer assumed from mere server membership
+
+Why it mattered:
+- prevented silent deafness
+- made channel availability deterministic
+
+### 2. Mention behavior must be intentional
+What improved:
+- some channels were configured to respond without mentions
+- others later moved toward requiring mentions
+
+Why it mattered:
+- channel norms differ
+- explicit mention policy prevents accidental spam or accidental silence
+
+### 3. Channel setup is operational work, not metadata
+What improved:
+- channel creation plus config patch plus verification became the real checklist
+
+Why it mattered:
+- this closed the gap between "channel exists" and "assistant can actually behave correctly there"
+
+## Durable rule from this channel
+- Treat channel wiring and mention policy as first-class operating rules.

research/2026-04-16-discord-instruction-lessons/channels/05-knowledge-graphs.md

@@ -0,0 +1,37 @@
+# Channel Summary: #knowledge-graphs
+
+## Date coverage
+- 2026-04-07 to 2026-04-10 verified from current Discord session transcripts
+
+## Why this channel mattered
+This channel produced one of the cleanest lessons about delegated work: stalls were often wandering, not crashing.
+
+## Main lessons learned
+
+### 1. "Stalled" often meant "wandering"
+Observed change:
+- direct session-log inspection showed Pi was re-reading `SOUL.md`, `USER.md`, memory files, and unrelated workspace content instead of advancing the assigned chunk
+
+Why it mattered:
+- changed the diagnosis from vague slowness to a concrete failure mode
+- made the remedy obvious: narrow scope, redirect architecture, or take over directly
+
+### 2. Architecture should converge early
+Observed change:
+- after the wandering diagnosis, recommendations shifted toward a Logseq-native, markdown-first architecture rather than over-building the system too early
+
+Why it mattered:
+- reduced speculative complexity
+- gave the work a clearer source-of-truth model
+
+### 3. Delegates need intervention rules
+Observed change:
+- child sessions were used in parallel, but the transcripts showed the need for better steering when delegated work drifts
+
+Why it mattered:
+- without intervention rules, delegation becomes a delay multiplier
+
+## Durable rules from this channel
+- When a delegate stalls, inspect the log before speculating.
+- Wandering is a distinct failure mode.
+- Narrow context and re-scope early.

research/2026-04-16-discord-instruction-lessons/channels/06-lesson-plans.md

@@ -0,0 +1,38 @@
+# Channel Summary: #lesson-plans
+
+## Date coverage
+- 2026-04-05 to 2026-04-13 verified from current Discord session transcripts
+
+## Why this channel mattered
+This was the first dense Little Lab Coats quality channel. It revealed that lesson output needed much stricter completeness and usability standards.
+
+## Main lessons learned
+
+### 1. Completeness bugs must be treated as real product failures
+Observed change:
+- lesson/unit mismatches were explicitly called out and folded into a completeness pass
+- partial libraries stopped being treated as "basically done"
+
+Why it mattered:
+- curriculum trust depends on internal consistency
+- gaps in unit structure break the product, not just the polish
+
+### 2. Honest status beats fake finish
+Observed change:
+- updates began distinguishing confirmed fixes from known unresolved gaps
+
+Why it mattered:
+- preserved trust with Serena
+- made next actions obvious
+
+### 3. LLC quality depends on teaching usability, not just page generation
+Observed change:
+- lessons increasingly optimized around parent usability, household materials, and classroom flow rather than generic content volume
+
+Why it mattered:
+- turned pages into teachable materials instead of just long HTML documents
+
+## Durable rules from this channel
+- Completeness is product quality.
+- Status should separate fixed, known-broken, and next-to-fix.
+- Teaching usability matters more than raw content length.

research/2026-04-16-discord-instruction-lessons/channels/07-lesson-plans-2.md

@@ -0,0 +1,62 @@
+# Channel Summary: #lesson-plans-2
+
+## Date coverage
+- 2026-04-12 to 2026-04-15 verified from current Discord session transcripts
+
+## Why this channel mattered
+This was the highest-density channel for instruction hardening around deliverables, review workflows, links, preview gates, and what "done" actually means.
+
+## Main lessons learned
+
+### 1. Always include the usable link
+Observed change:
+- explicit promise: when a lesson revision finished, the direct revised lesson link would be pasted into the channel
+- later, this became a broader rule to include the link automatically when the deliverable needs one
+
+Why it mattered:
+- removed a whole class of frustrating follow-up questions
+- made completion messages immediately actionable
+
+### 2. Review-ready and publish-ready are different states
+Observed change:
+- review mode, reviewer council, and live review paths became explicit requirements before anything was described as fully ready
+
+Why it mattered:
+- prevented premature claims of completion
+- aligned the work with actual stakeholder review flow
+
+### 3. The preview window must be meaningful
+Observed change:
+- previews were explicitly extended through the Learning Objectives section instead of being cut off too early
+
+Why it mattered:
+- improved product conversion logic
+- made public pages useful enough to evaluate before subscription
+
+### 4. Remarq wiring must use real document IDs
+Observed change:
+- lesson workflows increasingly required explicit real Remarq document IDs rather than placeholders or assumptions
+
+Why it mattered:
+- prevented fake-integrated pages
+- made review feedback operational instead of decorative
+
+### 5. "Done" means live, verified, and reviewable
+Observed change:
+- live links, public-path checks, review mode verification, and commit/push became part of the definition of done
+
+Why it mattered:
+- transformed deliverables from local progress into actually shippable outcomes
+
+### 6. Mention policy also matters at the channel level
+Observed change:
+- this channel later moved toward requiring mention behavior explicitly
+
+Why it mattered:
+- reduced accidental interruption in a high-volume review channel
+
+## Durable rules from this channel
+- Include direct links automatically.
+- Keep review-ready separate from publish-ready.
+- Make previews meaningful.
+- Treat integration as incomplete until real IDs and live checks exist.