Skip to content

docs(handoff): 2026-05-19 session handoff + LLM-facing freshness updates#139

Open
dfrostar wants to merge 2 commits into
mainfrom
claude/handoff-2026-05-18
Open

docs(handoff): 2026-05-19 session handoff + LLM-facing freshness updates#139
dfrostar wants to merge 2 commits into
mainfrom
claude/handoff-2026-05-18

Conversation

@dfrostar
Copy link
Copy Markdown
Owner

Summary

Two-purpose doc-only PR. All commits are docs(...) so release-please won't bump the version.

1. docs/HANDOFF-2026-05-19.md (new file)

Session handoff for the next Claude Code agent picking up after the v0.7.0/v0.8.0/v0.9.0 release train. Modeled on the predecessor HANDOFF-v0.6.1.md that kicked off this entire session.

Includes a copy-paste prompt at the top — paste into a fresh session and the agent has everything it needs to pick up cleanly.

Sections: TL;DR · § 1 verify v0.9.0 fully landed · § 2 full audit of what shipped · § 3 prioritized "what's next" · § 4 Phase 0 hygiene maintainer-UI items · § 5 PAT secret setup · § 6 cross-release marketing arc · § 7 open questions · § 8 lessons learned · § 9 final state · § 10 compact lessons.

2. README + about.html freshness pass

The LLM/agent install-instructions surface had three stale spots that survived earlier doc rollouts:

  • README § "🕸️ Graph view": the "Coming next (Phase B)" paragraph described features that all shipped in v0.6.0. Replaced with a "Now live in the graph view (as of v0.9.0)" status listing every feature actually live today — replay overlay, edge tooltips, min-weight slider, pin UX, Cmd/Ctrl-K, depth slider, live activity feed, /healthz, GHCR image, SBOM.

  • README Hermes-Agent / OpenClaw / Agent Zero sections (×3): each said "v0.6.0 graph view works identically here." Replaced with "The live graph view (v0.6.0+) works identically here." — same claim, no longer pinned to a specific 3-releases-old version.

  • docs/about.html v0.7.0 "What's New" Docker bullet: was "GHCR auto-publish lands in a later release; build locally for now." Added a parenthetical noting it landed in v0.9.0, preserving the v0.7.0 historical context.

What was deliberately NOT touched (scope-control)

  • v0.8 + v0.9 marketing artifacts (LinkedIn drafts, NotebookLM packs, screencast scripts) — substantial work, need their own focused session. Handoff doc § 6 documents the queue.
  • Wiki Comparisons / FAQ / Usage-Guide / API-Reference / Architecture / Learning-Guide: don't reference version-specific install or agent-integration instructions, so not stale in the way that affects LLM/agent consumers.
  • docs/use-cases/*.md: many use pip install neuralmind graphifyy (correct — one of the 5 paths). The install matrix is the canonical "all paths" view and these pages link to it.

Test plan

  • No code changes; no test changes
  • HANDOFF doc renders cleanly as markdown
  • No 0.6.0-only callouts remain in the Hermes/OpenClaw/Agent Zero blocks
  • README "🕸️ Graph view" section reflects v0.9.0 state
  • docs/about.html v0.7.0 section's "build locally for now" caveat now references its v0.9.0 successor

Order vs PR #138

This PR doesn't depend on #138 (v0.9.1 fixes) merging first. They're independent doc-only branches. Merge either order with merge method + conventional-commit-format title.

https://claude.ai/code/session_01SH6iHNAqeMJHXdq7ubVcuJ


Generated by Claude Code

Two-purpose commit. Both are `docs(...)` so release-please won't
trigger a version bump.

1. New docs/HANDOFF-2026-05-19.md — session handoff for the next
   Claude Code agent picking up after v0.7.0/v0.8.0/v0.9.0 shipped.
   Includes:
   - Copy-paste prompt at the top
   - § 1 verify v0.9.0 fully landed (PyPI/GHCR/SBOM commands)
   - § 2 full audit of what shipped (3 PyPI releases, infra, docs,
     renames)
   - § 3 prioritized "what's next" — high (verify + #138 merge +
     #133 triage), medium (PAT + Phase 0 + Agent Zero a0-plugins),
     lower (marketing rollout for v0.8 + v0.9), strategic
     (GitHub App, cosign, awesome-mcp-servers, PR #100 decision,
     mypy 2.0)
   - § 4 Phase 0 hygiene items still owed by the maintainer
   - § 5 PAT secret setup (the one-time UI work that auto-publishes
     all future releases)
   - § 6 cross-release marketing arc table (v0.7 done, v0.8 + v0.9
     pending)
   - § 7 open questions for the next session
   - § 8 lessons learned (conventional-commit titles, 0.x minor
     bump rules, GITHUB_TOKEN anti-loop guard)
   - § 9 final state — open PRs + issues at handoff
   - § 10 compact lessons for next agent

2. README + about.html freshness pass on the sections LLMs and
   integration consumers actually read:

   - README § "🕸️ Graph view": replaced the "Coming next (Phase B)"
     speculative paragraph with a "Now live in the graph view (as
     of v0.9.0)" status — replay overlay, edge tooltips, min-weight
     slider, pin UX, Cmd/Ctrl-K, depth slider, live activity feed,
     /healthz, GHCR image, SBOM. All have shipped; the "coming
     next" framing was stale.

   - README Hermes-Agent + OpenClaw + Agent Zero sections (×3):
     each said "v0.6.0 graph view works identically here." Replaced
     with "The live graph view (v0.6.0+) works identically here."
     so the statement stays true and is no longer pinned to a
     specific version that's now 3 minor releases old.

   - docs/about.html v0.7.0 "What's New" Docker bullet: was
     "GHCR auto-publish lands in a later release; build locally for
     now." Added a parenthetical noting it landed in v0.9.0,
     preserving the v0.7.0 historical context.

What was deliberately NOT touched here (scope-control):
   - The full v0.8 + v0.9 marketing artifacts (LinkedIn drafts,
     NotebookLM packs, screencast scripts) — these are substantial
     and need their own focused session. The handoff doc § 6
     documents the queue.
   - The wiki Comparisons.md, FAQ.md, Usage-Guide.md, etc. — these
     don't reference version-specific install/agent-integration
     instructions, so they're not stale in the way the user's
     concern (LLM/agent install paths) implies. They can be swept
     in a separate session.
   - The use-cases pages — many still say `pip install neuralmind
     graphifyy` (correct, just one path); the install matrix is
     the canonical "all paths" view and they link to it via the
     READMEs and Setup-Guide.

https://claude.ai/code/session_01SH6iHNAqeMJHXdq7ubVcuJ
Copilot AI review requested due to automatic review settings May 19, 2026 15:19
@github-actions github-actions Bot added documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested labels May 19, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 19, 2026

NeuralMind self-benchmark

Status: PASS — floor , measured 5.9×.

Phase 1 — Reduction on committed fixture

  • Average reduction: 5.9×
  • Top-k retrieval hit rate: 71.7%
  • Naive baseline: 47,360 tokens (all fixture files concatenated)
  • NeuralMind total: 8,149 tokens across 10 queries
  • Estimated monthly savings @ 100 queries/day on Claude 3.5 Sonnet: ~$35.30
# Query Shape Naive NeuralMind Ratio Hit
1 auth-flow cross-file 4,736 815 5.8× 33.3%
2 api-endpoints focused 4,736 809 5.9× 100.0%
3 billing-flow cross-file 4,736 846 5.6× 33.3%
4 user-storage cross-file 4,736 672 7.0× 50.0%
5 jwt-verify focused 4,736 681 7.0× 100.0%
6 stripe-webhook focused 4,736 838 5.7× 100.0%
7 create-user cross-file 4,736 794 6.0× 50.0%
8 refund focused 4,736 827 5.7× 100.0%
9 db-choice identity 4,736 899 5.3× 100.0%
10 invoice-send cross-file 4,736 968 4.9× 50.0%

Phase 2 — Learning uplift

  • Memory events logged: 20
  • Learned patterns: 20
  • Reduction ratio after neuralmind learn: 5.9× (Δ +0.00× vs. cold)
  • Top-k hit rate after learning: 71.7% (Δ +0.0 points vs. cold)

Note: uplift numbers on a 500-line fixture are intentionally modest — the point is to
verify the learning mechanism persists and applies. On real production repos the lift
is larger; this test only catches regressions in persistence.

Assumptions

  • Baseline: every .py file in tests/fixtures/sample_project/ concatenated.
  • Tokenizer: tiktoken GPT-4o encoding (per-model breakdown in multi_model.json if generated).
  • Pricing: Claude 3.5 Sonnet input @ $3.0/MTok.
  • Regression floor: — well below NeuralMind's typical 40–70× on real repos.

Per-model token reduction

Model Tokenizer Naive NeuralMind Ratio Source
GPT-4o / GPT-4o-mini tiktoken o200k_base 4,739 927 5.1× measured
GPT-4 / GPT-3.5-turbo tiktoken cl100k_base 4,710 918 5.1× measured
Claude 3.5 Sonnet estimated: GPT-4o × 1.08 — install anthropic for an exact count 5,118 1,001 5.1× estimated
Llama 3 (70B) estimated: GPT-4o × 1.22 — Llama tokenizer requires model weights; estimate based on published vocab ratios 5,781 1,130 5.1× estimated

Rows marked measured use the provider's real tokenizer. Rows marked
estimated apply a published vocab-size correction to the GPT-4o count —
honest approximations, not hardcoded claims.


Automated by .github/workflows/ci-benchmark.yml — regenerate locally with python -m tests.benchmark.run.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Doc-only PR that (1) adds a detailed session handoff for future agent/maintainer continuity after the v0.7.0–v0.9.0 release train and (2) refreshes README + docs/about.html to remove stale “coming next” / version-pinned statements and reflect current shipped status.

Changes:

  • Add docs/HANDOFF-2026-05-19.md with a copy/paste continuation prompt, release audit, next actions, and process lessons.
  • Update README “Graph view” section to replace outdated “Phase B coming next” language with a “now live” feature/status list; loosen “v0.6.0” pinning in 3 integration blocks to “v0.6.0+”.
  • Update docs/about.html v0.7.0 Docker install bullet to note GHCR auto-publish landed in v0.9.0 while preserving historical context.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
README.md Replaces stale “coming next” copy with current shipped graph-view status; removes hard pin to v0.6.0 in integration sections.
docs/HANDOFF-2026-05-19.md New handoff document capturing state, next steps, and release/process lessons for continuity.
docs/about.html Updates v0.7.0 Docker bullet to reference the later v0.9.0 GHCR publish path.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
activity feed of synapse co-activations + file edits. Plus
`/healthz` for Docker / systemd monitoring (v0.8.0+), GHCR
auto-built container image (v0.9.0+), and a CycloneDX SBOM on every
release. Full roadmap of what's next in [ROADMAP.md](ROADMAP.md).
https://github.com/dfrostar/neuralmind/blob/main/docs/HANDOFF-2026-05-19.md

Read CLAUDE.md and the handoff doc above, then check the open PR
list and the four open issues to confirm state before starting. The
…–6.4)

Expanding the cross-release marketing arc table into a strategic
playbook covering channels (corporates, agent hubs, Reddit) and
influencer outreach. Answers the open questions from the session
about how to actually take v0.7/v0.8/v0.9 to market.

§ 6.1 Distribution channels — tier 1/2/3 by leverage-per-effort:
 - HN Show HN (one shot, v0.9 enterprise angle is the fresh frame)
 - Agent Zero a0-plugins submission (3 min UI, 17.7k stars)
 - LinkedIn per release (three audiences across the arc)
 - punkpeye/awesome-mcp-servers, GitHub topics, MCP cheat-sheets
   for sustained discoverability
 - Hermes / OpenClaw / Agent Zero community channels for active push

§ 6.2 Reddit strategy — subreddit-specific posting frames for
r/ClaudeAI, r/LocalLLaMA, r/ChatGPTCoding, r/programming,
r/devops, r/Python. Hostile-to-promo framing, one post per release,
not the same week as HN.

§ 6.3 Influencer outreach — named specific people active in this
space:
 - Highest-signal: Simon Willison, swyx, Hamel Husain
 - Adjacent: Jeremy Howard, Eugene Yan, Chip Huyen
 - Newsletter targets: Simon's Weeknotes, Latent Space, Import AI,
   The Pragmatic Engineer
 - Podcasts: Latent Space, Practical AI, TWIML, Cognitive Revolution
 - Compact outreach template (~100 words) included

§ 6.4 Corporate playbook — frame is "make adoption frictionless +
have proof artifacts ready." v0.9.0 already ships the artifacts
(COMPLIANCE-SUMMARY.md, SBOM, GHCR image, air-gapped doc). Still
missing: pinned regulated-industry Discussions thread, named case
studies, non-personal contact channel for compliance reviewers.

https://claude.ai/code/session_01SH6iHNAqeMJHXdq7ubVcuJ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants