Skip to content

docs: release-dogfood-protocol — cross-town friction-sweep cadence (yggdrasil contribution)#449

Merged
the-data-viking merged 1 commit into
mainfrom
docs/release-dogfood-protocol
May 10, 2026
Merged

docs: release-dogfood-protocol — cross-town friction-sweep cadence (yggdrasil contribution)#449
the-data-viking merged 1 commit into
mainfrom
docs/release-dogfood-protocol

Conversation

@the-data-viking
Copy link
Copy Markdown
Collaborator

Summary

Codifies the cross-town friction-sweep cadence that surfaced 8 actionable beads across v1.0.4 → v1.0.5:

  • yggdrasil mayor (this PR) — orchestrator-dispatch class friction (v1+bank-ref silent drop, ensemble-no-synthesis, OR cost-table staleness, README/CLI verdict envelope mismatch, etc.)
  • midgard mayor — transport-layer class friction (OR/Anthropic image-drop, deterministic flake-rate measurement, persona-roleplay-as-masking insight)
  • jotunheim mayor (this house) — multi-round termination + MCP boundary class friction (v3 multi-round panel terminates after round 1)

None of the three would have caught the others' findings unprompted. The doc locks that property in.

What's in the doc

  • Cadence: friction sweep on each n.0.0, n.m.0, n.0.1 release (with rc as optional). 24h window from PyPI publish.
  • Roles: receiving mayor (jotunheim, this cycle) bundles into beads in synthpanel rig db (canonical store). Sweeping mayors run their own dogfoods independently — divergence is the signal.
  • Wave structure: friction items + positive verdict-equivalents + still-ahead. Each friction item: repro, observed-vs-expected, root-cause hypothesis (citing source line numbers if read), recommendation.
  • Bead conventions: `Source-wave: hq-wisp-` line in Reporter footer, optional `(item N of M)` clause. `cross-town-reported` label.
  • Friction definition (what's in / what's out — lines 80-104 of the doc).
  • Cross-rig pattern notes appendix: meta-findings that no single dogfooder produces alone. Anchored in release notes when load-bearing.

Authorship

Pattern + draft contributed by yggdrasil mayor (`openclaw@dataviking.tech`). PR opened from jotunheim per standing cross-town coord protocol (synthpanel pushes go through jotunheim's CI environment).

This is the second cross-town docs contribution this release cycle (PR #447 was midgard's openrouter-byok-visual-review.md). Same coord pattern; cleaner each time.

Test plan

  • Markdown renders cleanly (no embedded scripts, no template-engine references — pure prose)
  • Cross-references valid (the doc cites `hq-ilke`, `hq-fjdx` as sister-bug example — both filed and in-flight)
  • No markdown linter warnings if synthpanel has one wired

🤖 Generated with Claude Code

Codifies the cross-town friction-sweep cadence that surfaced 8 actionable
beads across v1.0.4 → v1.0.5 (yggdrasil, midgard, jotunheim). Three
independent dogfoods caught three different classes of friction; locking
the cadence ensures we don't lose that property as the project grows.

Pattern + draft contributed by yggdrasil mayor; PR opened from jotunheim
per the standing cross-town coord protocol that synthpanel pushes go
through jotunheim.

Co-Authored-By: yggdrasil mayor <openclaw@dataviking.tech>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@the-data-viking the-data-viking merged commit ae4b290 into main May 10, 2026
15 checks passed
@the-data-viking the-data-viking deleted the docs/release-dogfood-protocol branch May 10, 2026 19:50
the-data-viking added a commit that referenced this pull request May 10, 2026
…codified) (#450)

Three independent dogfoods on v1.0.4 → v1.0.5 (jotunheim, midgard,
yggdrasil) surfaced a tight cluster of orchestrator-dispatch and
ergonomics bugs. Fix scope:

  P1: hq-fjdx (linear v3 multi-round termination); hq-ilke (v1+bank-ref
      silent attachment drop)
  P2: hq-hjq8 (ensemble --blend no synthesis); hq-xq36 (OR cost-table
      99% drift); hq-83ye (CI integration test for MCP v3 multi-round)
  P3: hq-lux3 (README response-shape docs); hq-h5j2 (with-attachments
      example); hq-pmi1 (pack export auto-mkdir)

Cross-rig pattern: orchestrator dispatch paths silently degrade when a
feature isn't wired into every entrypoint. v1 single-round path skipped
the attachment resolver; MCP v3 multi-round path terminated after round
1. Same smell, different surface.

Cadence codified in docs/release-dogfood-protocol.md (PR #449); future
releases lock in the property.

No API break.

Co-authored-by: yggdrasil mayor <openclaw@dataviking.tech>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant